Plan ↔ receipt lab: the run's two bookends - #10
Draft
arielconti10 wants to merge 2 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
What
New playground lab at
/playground/plan-receipt(stacked on #9).An agent run has two bookends with the same content model: the plan is the prospective account ("here's what I'll touch, how, and when I'll stop"), the receipt the retrospective one. The lab's centerpiece is the pattern no shipping product does well: a receipt that diffs against the plan.
Reuses the shared run script from
run-surface-data.ts(extended with aRUN_PLANstructure) and the same fixture ask, so the three labs — composer dressing, run surface, plan↔receipt — form one continuous story.Why
Completes the bookend thesis from the four-surface framework: deviations are acceptable when traced to a human decision, and the receipt proves the tracing, not just the delta. A receipt without a plan can only list what happened; it can never reconcile delivery against intent. This is the candidate content model for a future
run-receiptregistry primitive.Verification
Typecheck, lint, audit-ui, Prettier all pass. Browser QA at desktop and 390px: both escalation branches, run-again loop, plan phase. Playground-only — no registry changes.