scope.jsonl

{"id":"P1","kind":"identity","statement":"Observatory demonstrates whether procedural memory derived from a verified failure changes a warm rerun for the right, attributable reason.","status":"superseded","superseded_by":"P9","since":"D2","refs":["D9"]}
{"id":"P2","kind":"flow","statement":"The flagship slice is WorkItem to cold failure to GPT-5.6 memory proposal to deterministic admission and GraphReFly application to warm rerun to replay UI and evidence bundle.","status":"superseded","superseded_by":"P10","since":"D2,D3","refs":["D9"]}
{"id":"P3","kind":"boundary","statement":"GPT-5.6 performs semantic interpretation and structured proposal generation; an independent deterministic verifier owns pass or fail.","status":"superseded","superseded_by":"P11","since":"D3","refs":["D10"]}
{"id":"P4","kind":"success","statement":"Cold and warm executions use the same canonical WorkItem input; relevant admitted memory makes the warm run avoid the prior failure route and pass verification.","status":"superseded","superseded_by":"P12","since":"D2,D3","refs":["D9"]}
{"id":"P5","kind":"success","statement":"Proposal-only, admission-rejected, irrelevant-applied, and wrong-scope-applied controls cannot manufacture success.","status":"superseded","superseded_by":"P12","since":"D3","refs":["D10"]}
{"id":"P6","kind":"success","statement":"Every applied or rejected memory record has exact trace attribution and a reason code.","status":"superseded","superseded_by":"P13","since":"D3","refs":["D10"]}
{"id":"P7","kind":"success","statement":"A fixture-backed replay works without an API key and a live GPT-5.6 path demonstrates actual model use.","status":"locked","since":"D5,D10","refs":["E5"]}
{"id":"P8","kind":"success","statement":"A first-time judge can understand the problem, changed decision, verifier result, and proof within the under-three-minute demo.","status":"active","since":"D9","refs":[]}
{"id":"P9","kind":"identity","statement":"GraphReFly Stack is a semantic stacked-diff layer above Git that tells developers whether an agent-generated change is still valid under the architecture it was planned against.","status":"locked","since":"D9","refs":["STACK-2"]}
{"id":"P10","kind":"flow","statement":"The flagship slice runs task to GPT-5.6 ChangePlan to real stacked commits and commit-indexed GraphBlueprint snapshots to a textually clean but semantically invalidating architecture change to selective replan, deterministic gate recovery, and high-level review.","status":"locked","since":"D9,D10,D12","refs":["STACK-2","C2","C5"]}
{"id":"P11","kind":"boundary","statement":"GPT-5.6 proposes semantic plans, claims, implementation, explanations, and replans; deterministic code owns snapshot derivation, scope validation, freshness, impact, checks, and GateResult.","status":"locked","since":"D10","refs":["C3","C4","E8"]}
{"id":"P12","kind":"success","statement":"The flagship proof keeps an unaffected upstream work unit valid, invalidates only stale downstream work despite a clean Git rebase, and admits the affected work only after a fresh selective replan passes deterministic checks.","status":"locked","since":"D9,D10","refs":["E3","STACK-5"]}
{"id":"P13","kind":"success","statement":"Every material validity, invalidation, and recovery claim resolves to exact witnesses, reason codes, and reproducible check outputs rather than model confidence or commit prose.","status":"locked","since":"D10,D12","refs":["E1","E8","E9"]}
{"id":"P14","kind":"success","statement":"A reviewer can understand intent, architectural delta, affected capabilities, stack dependencies, unresolved risk, and merge readiness before choosing whether to inspect the raw code diff.","status":"locked","since":"D12","refs":["C5"]}
{"id":"P15","kind":"boundary","statement":"The Build Week MVP implements only the GraphReFly BlueprintProvider, the canonical CLI, a local review UI, one flagship scenario, and manual semantic approval; other graph providers, MCP, hosted CI, and automatic merge remain deferred.","status":"locked","since":"D9,D11,D12","refs":["N2","N3","N4","N5"]}
{"id":"P16","kind":"success","statement":"Selecting any flagship work-unit commit shows its real Git identity, the full GraphBlueprint produced by that commit's pinned GraphReFly runtime, its structural delta from the stack parent, its deterministic gate state, and a readable GitHub-style code diff; the primary review surface contains only developer-facing review information and collapses relevant secondary details.","status":"locked","since":"D18","refs":["C2","C5","C20","SC10"]}
{"id":"P17","kind":"boundary","statement":"The first production release supports linear semantic stacks. Stable WorkUnit identity, explicit dependencies, and semantic-parent bindings remain independent of linear position so a later DAG extension does not require replacing the domain identity model.","status":"locked","since":"D19","refs":["C9","C10","C21","B7"]}
{"id":"P18","kind":"boundary","statement":"Repository-owned runners retain raw source, unredacted GraphBlueprints, raw provider responses, and execution details by default; hosted surfaces receive only repository-policy-selected, schema-validated, content-addressed redacted evidence unless a broader upload is explicitly authorized and audited.","status":"locked","since":"D20","refs":["C22","E6","E11"]}
{"id":"P19","kind":"boundary","statement":"Production GraphReFly Stack generalization waits for upstream @graphrefly/ts Blueprint parsing and validation, hash verification, Blueprint-direct readable rendering, and canonical structural delta semantics; Stack may not make its MVP consistency checks or hand-maintained graph logic the permanent abstraction.","status":"locked","since":"D21","refs":["C20","C23","PRODUCT-0","N6"]}
{"id":"P20","kind":"success","statement":"A developer can point GraphReFly Stack at any local repository satisfying the supported GraphReFly repository contract and a linear base-to-head range, then select every discovered commit and see its real Git identity, commit-parent GraphBlueprint delta, and GitHub-style structured code diff without fixture-specific IDs, paths, or generated review artifacts.","status":"locked","since":"D22","refs":["C24","C25","PRODUCT-1","E12"]}
{"id":"P21","kind":"flow","statement":"The deadline sequence is upstream Blueprint capabilities, generic linear-repository review, refreshed event-delivery work evidence and submission information, then only deadline-safe product polish before the final submission refresh.","status":"locked","since":"D22","refs":["PRODUCT-0","PRODUCT-1"]}
{"id":"P22","kind":"roadmap","statement":"After the first usable review release, GraphReFly Stack expands toward DAG stacks, fully hosted SaaS collaboration, semantic planning, mutual exclusion, proactive conflict avoidance, enforceable AI and human edit scopes, and evidence-backed revert and rollback.","status":"superseded","superseded_by":"P31","since":"D23","refs":["B1","B7","B8","B9","B10","B11","B12"]}
{"id":"N1","kind":"non-goal","statement":"Authentication, teams, and collaboration are outside the MVP.","status":"locked","since":"D9","refs":["B1"]}
{"id":"N2","kind":"non-goal","statement":"Replacing Git, GitHub, Graphite, or other stacked-diff transport and review mechanics is outside the MVP.","status":"locked","since":"D9","refs":["B2"]}
{"id":"N3","kind":"non-goal","statement":"Nx, Turborepo, TypeScript project-reference, and other non-GraphReFly BlueprintProvider implementations are outside the MVP.","status":"locked","since":"D11","refs":["B3"]}
{"id":"N4","kind":"non-goal","statement":"An MCP server, GitHub App, and hosted required-check integration are outside the MVP.","status":"locked","since":"D11","refs":["B4"]}
{"id":"N5","kind":"non-goal","statement":"Automatic semantic approval, automatic merge, and unattended production mutation are outside the MVP.","status":"locked","since":"D12","refs":["B5"]}
{"id":"N6","kind":"non-goal","statement":"Reimplementing or vendoring GraphReFly is prohibited.","status":"locked","since":"D4","refs":["AP3"]}
{"id":"N7","kind":"non-goal","statement":"Multiple unrelated demo scenarios and a production database are outside the MVP.","status":"locked","since":"D9","refs":["B6"]}
{"id":"N8","kind":"non-goal","statement":"DAG stack discovery, merge-parent selection, and partial-order review are outside the first production release.","status":"locked","since":"D19","refs":["P17","B7"]}
{"id":"P23","kind":"success","statement":"A generic local reviewer can understand how Git commits, commit-indexed GraphReFly Blueprints, parent deltas and code diffs relate, then record an approve or request-changes decision that survives browser restarts, never appears in working-tree changes, remains bound to the exact reviewed witnesses, and can be explicitly exported for sharing without implying a semantic GateResult or merge authorization.","status":"locked","since":"D29","refs":["C5","C13","C31","PRODUCT-VERIFY"]}
{"id":"P24","kind":"flow","statement":"After PRODUCT-VERIFY, productization proceeds through one explicitly designed and approved production-usable tranche at a time; event-delivery work presentation and submission work remains parked until explicit user reactivation, while the canonical sequencer and Goal preserve rather than fabricate submission readiness.","status":"locked","since":"D30","refs":["P22","PRODUCT-ROADMAP"]}
{"id":"P25","kind":"roadmap","statement":"The ordered post-verification roadmap is repository-owned semantic planning and deterministic generic gate first; CI and required-check adapters second once the gate runner is stable; hosted authentication, teams and redacted persistence third; reservations and enforceable actor scopes fourth; proactive conflict avoidance fifth; DAG topology sixth; and evidence-backed rollback last. Per-revision runtime or monorepo support and adoption features enter only when their backlog triggers have concrete evidence.","status":"superseded","superseded_by":"P31","since":"D31","refs":["P22","B1","B4","B7","B8","B9","B10","B11","B12","B14","B15","B16","B17"]}
{"id":"P26","kind":"success","statement":"A compatible independent GraphReFly repository can explicitly accept a versioned semantic plan before implementation, bind every linear implementation commit to a stable WorkUnit, and obtain a deterministic GateResult that passes a normal stack, selectively blocks architecture-stale work after a clean rebase, preserves unrelated work through immutable rebind, rejects ambiguous or widened model proposals, and recovers only invalid work through a selective replan without treating human approval or model output as validity.","status":"locked","since":"D31","refs":["P9","P11","P12","P13","C3","C4","C9","C10","B8","PRODUCT-SEMANTIC-VERIFY"]}
{"id":"N9","kind":"non-goal","statement":"The repository semantic lifecycle tranche does not add hosted accounts or source upload, CI or GitHub integrations, reservations, authenticated actor enforcement, proactive multi-agent conflict avoidance, DAG review, per-revision package installation, monorepo target selection, automatic merge, rollback, screenshots, video or submission work.","status":"locked","since":"D31","refs":["P25","B1","B4","B7","B9","B10","B11","B12","B14"]}
{"id":"P27","kind":"flow","statement":"After the verified repository semantic lifecycle, the remaining committed roadmap advances through six canonical macro phases in P25 order. Each phase first completes and obtains approval for a full Q1-Q9 design, then implements and verifies only that locked tranche before unblocking its successor; trigger-gated adoption work is inserted only through a later explicit design decision, and event-delivery work remains parked after the product sequence.","status":"superseded","superseded_by":"P31","since":"D32","refs":["P24","P25","PRODUCT-CI","PRODUCT-HOSTED","PRODUCT-COLLAB","PRODUCT-CONFLICT","PRODUCT-DAG","PRODUCT-ROLLBACK","B14","B15","B16","B17"]}
{"id":"P28","kind":"success","statement":"For a compatible repository-owned merge-free pull-request stack, one generated GitHub Actions required job installs the repository-pinned engine without lifecycle scripts, resolves the exact event base and immutable head, selects exactly one current accepted plan, invokes the same deterministic GateResult as local grfs gate, reports pass, blocked or error without semantic translation, preserves a strict redacted content-addressed CI artifact, and fails closed for stale head, ambiguity, tamper, fork permission, sandbox, cancellation and retry cases without secrets or repository mutation.","status":"locked","since":"D33","refs":["P18","P26","C4","C34","C39","C40","C41","C42","E10","E11","E13","PRODUCT-CI"]}
{"id":"N10","kind":"non-goal","statement":"PRODUCT-CI v1 does not support direct-push gating, pull_request_target, GitHub merge-group or merge-queue revisions, merge commits, GitHub Check Runs or annotations, GitHub App or MCP operation, hosted persistence or upload, OIDC or signed artifact attestations, automatic merge, per-revision dependency installation, monorepo package selection, lifecycle-script execution or any repository mutation.","status":"locked","since":"D33","refs":["P17","P25","P28","B1","B4","B5","B7","B14","PRODUCT-HOSTED","PRODUCT-DAG"]}
{"id":"P29","kind":"success","statement":"For a selected compatible GitHub repository, a separate repository-owned no-checkout hosted-sync workflow can exchange exact GitHub OIDC run identity for a short-lived grant, upload one policy-selected content-addressed redacted envelope, and let a currently authorized team member discover the immutable GateResult, exact redacted witnesses, provenance, append-only hosted decision history and audit without giving the hosted service source, execution or verdict authority; forged, replayed, cross-tenant, stale, oversized, over-quota, revoked and tampered requests fail closed while local and required CI gates remain usable during hosted outage.","status":"locked","since":"D36","refs":["P18","P25","P27","C22","C43","C44","C45","C46","C47","E11","E14","PRODUCT-HOSTED"]}
{"id":"P30","kind":"boundary","statement":"PRODUCT-HOSTED v1 is GitHub-first at the provider adapter while tenant, repository, actor, role, evidence and decision identities remain provider-neutral. It stores only fixed-profile redacted evidence and append-only review state in one United States control-plane region under explicit retention and quotas; it never executes repository code, changes GateResult or merge authority, mutates repositories or plans, upgrades unverified local identity, or silently grants access when provider authorization or hosted availability is unknown.","status":"locked","since":"D36","refs":["D20","D36","P18","C43","C44","C45","C46","C47","N11"]}
{"id":"N11","kind":"non-goal","statement":"PRODUCT-HOSTED v1 does not add non-GitHub provider adapters, multi-region or customer-selected residency, BYOK, billing, source browsing or editing, repository execution, arbitrary artifact profiles, plan acceptance, policy mutation, check execution, merge automation, reservations, actor scope enforcement, proactive conflict detection, DAG topology, rollback, screenshots, video or submission work.","status":"locked","since":"D36","refs":["P24","P25","P30","PRODUCT-COLLAB","PRODUCT-CONFLICT","PRODUCT-DAG","PRODUCT-ROLLBACK"]}
{"id":"P31","kind":"roadmap","statement":"After the verified semantic, CI and hosted tranches, GraphReFly Stack next applies Git-style optimistic concurrency at the pull-request boundary: evaluate the current target and contributor head as one exact three-way integration candidate, then proceed to general DAG topology and evidence-backed rollback. Preventive reservations, actor-specific edit credentials and pre-implementation conflict prediction are not fixed roadmap requirements and return only on concrete usage evidence. Every remaining tranche still requires approved Q1-Q9 design and complete stack-qa; event-delivery work remains parked.","status":"locked","since":"D37","refs":["P24","P26","P28","P29","P32","N12","B7","B9","B10","B11","B12","PRODUCT-COLLAB","PRODUCT-DAG","PRODUCT-ROLLBACK"]}
{"id":"P32","kind":"success","statement":"For a compatible pull request with one unique merge base, a merge-free linear contributor range and one current target endpoint, GraphReFly Stack constructs an isolated Git three-way candidate, derives verified base, target, head and candidate GraphBlueprints, distinguishes non-blocking shared graph identity from reproducible incompatible effects, and emits an exact IntegrationResult that is compatible only when textual merge, candidate execution, topology, accepted claims, dependencies, policy and the unchanged semantic GateResult remain valid. A target update makes prior evidence stale; conflicts guide rebase, implementation change or selective replan without creating commits, mutating refs, auto-merging or preventing independent work.","status":"locked","since":"D37","refs":["P9","P11","P13","P14","P17","C4","C21","C32","C33","C34","C48","E15","PRODUCT-COLLAB"]}
{"id":"N12","kind":"non-goal","statement":"The PR semantic integration tranche does not reserve files, graph identities or WorkUnits; issue leases or delegated-agent credentials; enforce pre-implementation actor ownership; predict conflicts before code exists; treat shared node, edge, subgraph or metadata identity as conflict by itself; review arbitrary DAGs or merge queues; execute merge or repository mutation; or perform event-delivery work work.","status":"locked","since":"D37","refs":["B9","B11","PRODUCT-CONFLICT","PRODUCT-DAG"]}
{"id":"P33","kind":"success","statement":"For one compatible repository, explicit ancestor base and head whose selected history contains at most 64 Git objects, topological width at most eight and only one- or two-parent commits, GraphReFly Stack discovers the complete bounded Git DAG, derives verified GraphBlueprint evidence at every object, binds normal implementation commits to stable WorkUnits, proves binary clean merges as transport-only joins, and evaluates an independent acyclic semantic dependency graph in canonical partial order. It preserves unaffected branches, blocks exact ambiguous ancestry, invalid join, stale claim, dependency or policy witnesses, and recovers only through new immutable rebase, implementation or selective-replan evidence. Local review, gate, pull-request integration and a bounded merge_group adapter invoke the same domain result without queue management, merge authority or repository mutation.","status":"locked","since":"D38","refs":["D19","D37","D38","P13","P17","P31","P32","C9","C10","C21","C34","C48","C49","C50","C51","E16","PRODUCT-DAG"]}
{"id":"N13","kind":"non-goal","statement":"PRODUCT-DAG v2 does not support more than 64 selected Git objects, topological width above eight, octopus merges, multiple heads, an implicit or non-ancestor base, unattributed manual merge resolution, arbitrary history rewriting, automatic merge, merge-queue management, reservations, actor-specific edit credentials, non-GraphReFly providers, rollback execution. These limits fail closed and may expand only through their recorded trigger or a later approved design.","status":"locked","since":"D38","refs":["D37","P31","P33","B18","PRODUCT-CONFLICT","PRODUCT-ROLLBACK"]}
{"id":"P34","kind":"success","statement":"For one exact GitHub merge_group checks_requested event whose selected history satisfies the bounded clean binary DAG contract and contains at most eight independently accepted Plans, GraphReFly Stack derives Plan ownership from explicit repository evidence, treats each WorkUnit as the planId and workUnitId pair, evaluates every Plan against the same final topology and Blueprint evidence, computes real shared join and semantic integration witnesses, and emits one deterministic aggregate required-check result that passes only when every nested GateResult and the group integration result pass. Event drift, ambiguous or missing Plan ownership, unsupported topology, policy or artifact staleness, cross-Plan dependency, conflict, tamper and aggregate translation fail closed without queue management, hosted authority, merge or repository mutation.","status":"locked","since":"D42","refs":["D20","D33","D37","D38","D41","D42","P28","P32","P33","C48","C49","C50","C51","C53","C54","E17","PRODUCT-DAG"]}
{"id":"N14","kind":"non-goal","statement":"The first multi-Plan merge-group adapter does not support more than eight Plans, cross-Plan semantic dependencies, merge-queue rebase or squash rewriting, heuristic Plan ownership, GitHub API or hosted-state verdict authority, hosted DAG sync, queue configuration or management, automatic merge, repository mutation, rollback. These capabilities remain fail closed or trigger-gated and may not weaken explicit conversion, exact event identity or repository-owned deterministic evidence.","status":"locked","since":"D42","refs":["P18","P30","P34","B5","B19","B20","B21","PRODUCT-DAG","PRODUCT-ROLLBACK"]}
{"id":"P35","kind":"success","statement":"For one compatible repository at an exact current head, GraphReFly Stack targets exact Plan-qualified WorkUnit records or deterministically expands one accepted Plan, derives a reproducible dependant impact closure, admits a recovery-step DAG with per-unit inverse, compensate or retain dispositions, and after explicit digest-bound authorization works only through a new isolated recovery branch. Drift, ambiguous inverse, incomplete dependant coverage, unresolved external effects, partial failure, malformed or tampered evidence remain truthfully stale, blocked, error or resumable; recovery is complete only when an independently verified RecoveryResult covers every required disposition and embeds a passing unchanged canonical DAG GateResult for the post-recovery stack without changing the caller worktree, auto-pushing, merging or treating Git success, review or hosted identity as execution authority.","status":"locked","since":"D44","refs":["D9","D10","D12","D16","D20","D29","D36","D38","D43","C4","C8","C13","C22","C54","C55","E8","E9","PRODUCT-ROLLBACK"]}
{"id":"N15","kind":"non-goal","statement":"PRODUCT-ROLLBACK v1 does not use release-level targets without a canonical release identity; execute external infrastructure compensation; infer semantic targets from commits, patches or repeated WorkUnit names; mutate the caller's current branch or worktree; force-update non-recovery refs; push, merge or delete refs; let hosted decisions authorize local execution; automatically clean up recovery branches; reinterpret existing semantic v1, DAG v2 or D43 bytes; or perform event-delivery work work.","status":"locked","since":"D44","refs":["D9","D20","D36","D43","P35","B5","B12","PRODUCT-ROLLBACK"]}
{"id":"P36","kind":"success","statement":"A developer or reviewer can open one compatible change and decide from three stable questions without knowing GraphReFly Stack's evidence vocabulary: Intent states the outcome and protected behavior, Reach distinguishes expected from observed and unexpected code or graph effects, and Readiness states the deterministic verdict, failed promise and next action. Unambiguous semantic evidence is discovered automatically, broad refactors remain truthful rather than artificially narrow, exact technical proof stays available on demand, and the same underlying artifacts continue to drive local review and CI.","status":"locked","since":"D45","refs":["P9","P11","P13","P14","P23","D12","D41","C53","PRODUCT-SIMPLIFY"]}
{"id":"N16","kind":"non-goal","statement":"PRODUCT-SIMPLIFY does not delete, reinterpret or migrate existing semantic, DAG, hosted, integration or recovery contracts; silently infer or widen accepted intent or repository policy; claim declarative capability labels prevent runtime actions; make the browser execute or translate the gate; prevent arbitrary filesystem edits; auto-approve, merge, push or mutate repositories; add a second product authority.","status":"locked","since":"D45","refs":["D10","D16","D20","D29","D45","P11","P18","C4","C22","C31","C53"]}
{"id":"P37","kind":"flow","statement":"The next product tranche completes the ordinary developer-to-reviewer correction loop around the existing Intent, Reach and Readiness surface: a change receives an understandable contract, a reviewer can request a bounded correction, the developer or agent returns with new commits and fresh evidence, stale decisions are unmistakable, and review can be requested again without exposing Plan, WorkUnit, predicate, binding or witness machinery as required user ritual.","status":"locked","since":"D47","refs":["D45","D47","D48","P23","P36","P38","C58","AP11","PRODUCT-FLOW-DESIGN","PRODUCT-FLOW"]}
{"id":"N17","kind":"non-goal","statement":"The ongoing product sequencer contains no hackathon deadline, judging path, Devpost state, submission checklist, feedback-session requirement, presentation screenshot or demo-video gate. Product documentation and reusable evidence may explain and verify behavior, but external-event packaging is not a product milestone.","status":"locked","since":"D47","refs":["D47","PRODUCT-FLOW-DESIGN","PRODUCT-FLOW"]}
{"id":"P38","kind":"success","statement":"For one compatible structural, semantic or bounded DAG change, a reviewer can record a whole-change request-changes summary, the developer or agent can append a correction on the same feature branch, and a fresh grfs review classifies every old decision as visibly outdated, recomputes unchanged Intent, Reach and Readiness semantics, returns the current human state to Needs review and permits a new whole-change decision. The loop preserves append-only local history, never carries approval across a changed review target, keeps provider re-request and merge authority outside local Stack state, and requires no Plan, WorkUnit, predicate, witness, revert or commit-fork ritual.","status":"locked","since":"D48","refs":["D29","D45","D48","P23","P36","P37","C13","C31","C52","C57","C58","E20","PRODUCT-FLOW"]}
{"id":"P39","kind":"success","statement":"A reviewed user-visible change carries one small Changeset release intent; main maintains a reviewable version and changelog PR; merging that PR publishes the exact public @graphrefly/stack package through a non-cancelling GitHub-hosted workflow only after complete quality and packed-consumer gates, with an immutable Git tag, GitHub release, npm OIDC Trusted Publishing and public provenance but no long-lived npm token.","status":"locked","since":"D49","refs":["D4","D6","D7","D13","D47","D49","C29","C59","E21","PRODUCT-RELEASE"]}
{"id":"N18","kind":"non-goal","statement":"PRODUCT-RELEASE does not auto-publish from pull requests or arbitrary tags, grant npm identity to CI jobs, keep an NPM_TOKEN, skip review of the release PR, infer SemVer from commit messages, force every documentation-only change to create a release, publish private workspace packages, synchronize the next dist-tag, deploy hosted services, or let release success alter product evidence, GateResult or review state.","status":"locked","since":"D49","refs":["D10","D13","D20","D29","D49","P39","C59","E21","PRODUCT-RELEASE"]}
{"id":"P40","kind":"success","statement":"Before designing another adoption tranche, a prospective user can review public @graphrefly/stack 0.1.8 against the real test-graphrefly consumer and experience the existing Intent, Reach and Readiness decision surface, request-changes correction lifecycle, pull-request semantic integration and bounded DAG routing where applicable without changing its established main or linear CI branch or operating Plan, WorkUnit, policy, predicate, binding or witness vocabulary as normal ritual. Dedicated local scenario refs and a linked worktree may supply the exact DAG history while before-and-after witnesses protect the original checkout. The walkthrough records observed setup friction and missing user guidance rather than turning deterministic conformance into an adoption claim.","status":"locked","since":"D51","refs":["D37","D41","D45","D48","D51","P32","P33","P36","P38","C48","C53","C57","C58","AP11","PRODUCT-DOGFOOD"]}
{"id":"N19","kind":"non-goal","statement":"PRODUCT-DOGFOOD does not change test-graphrefly main, codex/ci-semantic-gate-proof, the original checkout's files, HEAD, index, uncommitted dependency upgrade or existing .git/grfs review records; add product contracts; deploy the hosted control plane; execute rollback; activate line comments, reservations, actor credentials or unsupported DAG shapes; push branches; or claim broad adoption readiness. Only new local codex/dogfood-dag-* refs and their linked-worktree commits are authorized by D51.","status":"locked","since":"D51","refs":["D20","D37","D44","D45","D48","D51","B9","B11","B17","B18","PRODUCT-DOGFOOD"]}