Define revision, trigger, deduplication, retry, and stale-run semantics #35
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
#39 Prototype the Forgejo review presentation and feedback lifecycle
caleb-brown/temper
#41 Define the durable domain and audit model
caleb-brown/temper
#42 Define reliability, observability, and recovery behavior
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
#33 Research the supported Forgejo capability and version envelope
caleb-brown/temper
Reference
caleb-brown/temper#35
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
What are the canonical identities and state transitions for a pull-request revision, review request, execution attempt, result, and publication; how do automatic and manual triggers compose; and what exact deduplication, rerun, retry, supersession, cancellation, and current-head checks guarantee correct user-visible effects?
Blocked by