Define the durable domain and audit model #41
Labels
No labels
ready-for-agent
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#43 Choose the application architecture and technology stack
caleb-brown/temper
#30 Define Temper's developer-facing review contract
caleb-brown/temper
#31 Define Temper's trust, authorization, and data-handling policy
caleb-brown/temper
#35 Define revision, trigger, deduplication, retry, and stale-run semantics
caleb-brown/temper
#37 Define Review Policy and Reviewer Profile semantics
caleb-brown/temper
#38 Define repository onboarding and connection lifecycle
caleb-brown/temper
Reference
caleb-brown/temper#41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
#29 — Temper v1 Greenfield Product and Architecture
Question
Which aggregates, identities, immutable snapshots, state machines, invariants, retention boundaries, secret references, and audit events should durably represent Forgejo deliveries, review requests and attempts, policies and profiles, results and coverage, publications, repository installations, connections, providers, and Temper Operator actions?
Blocked by