Define Review Policy and Reviewer Profile semantics #37
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
#40 Prototype Temper Operator workflows and information architecture
caleb-brown/temper
#41 Define the durable domain and audit model
caleb-brown/temper
#30 Define Temper's developer-facing review contract
caleb-brown/temper
#34 Define review-quality and safety acceptance criteria
caleb-brown/temper
Reference
caleb-brown/temper#37
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 configuration belongs to a repository's Review Policy versus a reusable Reviewer Profile; how do defaults, activation predicates, composition, precedence, manual overrides, thresholds, caps, budgets, validation, and immutable revisions determine the effective policy for a review request?
Blocked by