Propose browser verification + tear-down phase (counsel consensus) - #35
Draft
walker-tx wants to merge 1 commit into
Draft
Propose browser verification + tear-down phase (counsel consensus)#35walker-tx wants to merge 1 commit into
walker-tx wants to merge 1 commit into
Conversation
Capture the Opus / GPT 5.6 Sol / Fable counsel consensus for an opt-in post-convergence verify-guide phase: deterministic Playwright walk of setup.md, Verification Ledger, redacted screenshots, mandatory tear-down to a re-runnable baseline, and Dossier-first re-entry for material denies/amends. Plan only — no pipeline implementation yet. Co-authored-by: Walker Lockard <walker-tx@users.noreply.github.com>
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
2 participants
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.
Summary
Counsel of three frontier agents (Claude Opus 5, GPT 5.6 Sol, Claude Fable 5) produced independent plans, ran a dispute round, and ratified a joint architecture for extending the guide pipeline with browser verification — including the tear-down requirement so flows stay re-validatable.
Plan only — no Playwright harness or doctrine edits are implemented in this PR. Concrete doctrine diffs still need human approval (I8).
The recommendation (one sentence)
Add an opt-in, post-convergence
verify-guidephase that deterministically click-throughs convergedsetup.mdin Playwright/Chromium, records a Verification Ledger (confirm/deny/amend/blocked), captures redacted screenshots, always tears down created resources to a re-runnable baseline, and — only on material denies/amends — re-enters the fact flow by amending the Research Dossier then re-rendering affected setup anchors.What landed
proposals/browser-verification.md— full consensus (architecture, credentials/1Password, tear-down, screenshots, local+CI commands, factory labels/exit codes, doctrine impact, phased delivery, open questions)proposals/README.md— proposals indexFACTORY.mdandREADME.mdSettled disputes (highlights)
guide:verify(not on every draft)setup.mdorder + Dossier locators → deterministic claim plan4outranks allteardown: cleanHuman decisions still needed
See §12 of the proposal (Speakeasy sandbox ownership, ToS sign-off, 1Password bootstrap, constitution I1/I9 edits, catalog surfacing of verify status, etc.).
Suggested next step
Approve Phase 0 spike against the GitHub throwaway org (local
mise run verify-guidepath) before any doctrine or factory wiring.