Define Temper's trust, authorization, and data-handling policy #31
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
#35 Define revision, trigger, deduplication, retry, and stale-run semantics
caleb-brown/temper
#36 Define review-context assembly and model-execution policy
caleb-brown/temper
#38 Define repository onboarding and connection lifecycle
caleb-brown/temper
#41 Define the durable domain and audit model
caleb-brown/temper
Reference
caleb-brown/temper#31
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 actors, systems, and inputs are trusted; who may trigger which reviews, especially for forks; what repository data may leave the Temper Deployment for the configured model provider; and which safeguards, disclosure, storage, retention, purge, and abuse-control rules form the v1 policy?
Blocked by