docs(atelier): add accountable dogfood runbook - #793
Merged
Conversation
shaug
force-pushed
the
scott/issue-781-dogfood-guide
branch
2 times, most recently
from
July 30, 2026 10:03
b267cc6 to
e6e87c7
Compare
added 9 commits
July 30, 2026 05:10
Document the separate planner, worker, recovery, audit, and operator roles for one real Atelier changeset. Define the durable evidence needed at promotion, delegation, recovery, delivery, audit, and explicit acceptance while preserving the v0 boundaries around merge, deployment, and native-ticket mutation.
Clarify that a declined audit fence must not create an invented rejection record. The work remains delivered until an explicitly authorized product boundary adds a durable rejection transition.
Document that a delegated requires-epic result is recorded as a blocked planner handoff, retains any transferable candidate, and never invokes epic execution from the dogfood runbook.
Branch fresh-task recovery by reconstructed work state so released candidates are reclaimed with a fresh claim and delivered work remains available for audit unless separately authorized rework requires takeover.
Require recovered active claims to seal a new delegated invocation, launch a fresh Agent Scripts worker, service checkpoints, and finalize with current evidence while preserving blocked recovery truth.
Document which lifecycle evidence survives through GitHub and the canonical mailbox. Treat previews, provider observations, and audit outputs as live-boundary artifacts and fail closed when their raw retention is required.
Require the approval commit before claiming, retain the actual claim transition fence, and distinguish the host-local delegated invocation from its durable mailbox digest.
Require the fresh audit task to rerun review-code-change against the receipt-bound candidate and treat normalized audit evidence as temporary host state.
Explain that blocked takeover preserves the unresolved decision, then requires explicit resolution, release of the exact blocked fence, and a separate fresh claim before preparing another invocation.
shaug
force-pushed
the
scott/issue-781-dogfood-guide
branch
from
July 30, 2026 12:31
e6e87c7 to
0e677e4
Compare
This was referenced Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
Documents the production v0 dogfood lifecycle for one accountable Atelier changeset, from separate planning and worker tasks through recovery, audit, and explicit operator acceptance.
Summary
requires_epicrouting without adding runtime behavior or provider mutation.Exact candidate evidence
0e677e46fb0cb9e80ca2bcc6f943ce8eb756fd45e339a669a8fd311d2fafb648a825788b02c88494just testpassed with 176 tests and all 16 mailbox protocol scenarios at the exact candidate.just lintpassed at the exact candidate.review-code-changeaggregate verdictcleanat the exact candidate and comparison base.lintandtestpassed at the exact candidate.2026-07-30T12:35:08Z: zero conversation comments, published reviews, and unresolved review threads.Non-goals
No runtime, provider, daemon, automation, merge, deployment, ticket mutation, or post-v0 #782/#783 behavior is included.
Tickets
Refs #781