Define review-context assembly and model-execution policy #36
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
#42 Define reliability, observability, and recovery behavior
caleb-brown/temper
#43 Choose the application architecture and technology stack
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
#34 Define review-quality and safety acceptance criteria
caleb-brown/temper
Reference
caleb-brown/temper#36
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
How should Temper acquire and bound pull-request context, select and chunk files, preserve cross-file reasoning, enforce provider capabilities and token, time, cost, and concurrency budgets, isolate untrusted content, validate and repair structured output, deduplicate findings, and report complete versus partial coverage?
Blocked by