Prove the complete v1 operating envelope #28

Open
opened 2026-07-14 22:32:32 -04:00 by caleb-brown · 0 comments
Owner

What to build

The team can demonstrate that the released Temper v1 satisfies its complete product, security, compatibility, reliability, recovery, and performance contract under the agreed production envelope.

Acceptance criteria

  • The released artifacts complete the full signed-webhook-to-Forgejo-feedback journey against the supported Forgejo release and a deterministic model provider.
  • The agreed repository count, event burst, concurrent review, maximum PR, latency, usage, and recovery scenarios meet their documented targets.
  • Failure injection covers database interruption, worker death, expired leases, provider outage, Forgejo rate limits, ambiguous publication, stale revisions, and restore from backup.
  • Security, quality, compatibility, migration, upgrade, rollback, retention, and purge gates all run against the release candidate.
  • Operator and developer journeys are demonstrated for healthy, partial, denied, failed, stale, recovered, paused, and uninstalled states.
  • Remaining known limitations are documented inside the accepted v1 support boundary rather than hidden as silent degradation.
  • The release is accepted only when every blocking ticket and the full operating-envelope evidence are complete.

Blocked by

  • #26 — Establish Forgejo compatibility and review-quality gates
  • #27 — Package a recoverable production release
## What to build The team can demonstrate that the released Temper v1 satisfies its complete product, security, compatibility, reliability, recovery, and performance contract under the agreed production envelope. ## Acceptance criteria - [ ] The released artifacts complete the full signed-webhook-to-Forgejo-feedback journey against the supported Forgejo release and a deterministic model provider. - [ ] The agreed repository count, event burst, concurrent review, maximum PR, latency, usage, and recovery scenarios meet their documented targets. - [ ] Failure injection covers database interruption, worker death, expired leases, provider outage, Forgejo rate limits, ambiguous publication, stale revisions, and restore from backup. - [ ] Security, quality, compatibility, migration, upgrade, rollback, retention, and purge gates all run against the release candidate. - [ ] Operator and developer journeys are demonstrated for healthy, partial, denied, failed, stale, recovered, paused, and uninstalled states. - [ ] Remaining known limitations are documented inside the accepted v1 support boundary rather than hidden as silent degradation. - [ ] The release is accepted only when every blocking ticket and the full operating-envelope evidence are complete. ## Blocked by - [#26](https://git.caleb-brown.dev/caleb-brown/temper/issues/26) — Establish Forgejo compatibility and review-quality gates - [#27](https://git.caleb-brown.dev/caleb-brown/temper/issues/27) — Package a recoverable production release
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
caleb-brown/temper#28
No description provided.