ui: clarify governance truth, blockers, evidence, and next actions

[ndrorchestration]

Purpose

Preserve the presentation-only Governance Command Center refinement: repository truth beacon, reusable Decision Frontier, Evidence → Verification → Authority → Permission grammar, explicit NOT AUTHORIZED treatment, operator handoff, formation-first roster presentation, evidence lineage, and responsive/accessibility work.

Current disposition — 2026-09-15

DRAFT / HOLD / STALE-LINEAGE / UNIQUE UI WORK. DO NOT MERGE AS-IS.

Current protected main is 1fb2c665587d5a0e7b213aef1cc5c870097cdc9b. #692 is accepted and the current Track A frontier is collection COMPLETE with operator retained-byte provenance PENDING, dataset lock NOT ESTABLISHED, unblinding NOT AUTHORIZED, primary analysis NOT AUTHORIZED / NOT RUN, efficacy NOT_ESTABLISHED, and High-Assurance PRE-FREEZE / FAIL-CLOSED / NOT AUTHORIZED / N=0.

This branch still contains unique presentation work, but its embedded governance constants/handoff text predate the accepted collection and current retained-byte frontier. Historical validation cannot transfer.

Because the current dataset-lock evidence preparer binds its evidence to exact executing repository HEAD, do not reconcile or merge this UI lane before the #679 operator-local retained-byte checkpoint. Moving main first would create avoidable checkpoint lineage churn without adding evidence.

Future reconciliation

After the controlling retained-byte/evidence-admission sequence reaches a stable accepted boundary:

1. reconstruct/reconcile the useful UI delta onto exact then-current main;
2. replace all historical governance constants with the then-current repository SSoT;
3. prove the effective delta remains presentation-only;
4. preserve runtime-health vs governance-authority separation;
5. run fresh exact-head UI/build/governance validation and applicable deployment checks;
6. merge only from fresh evidence.

Draft #649 remains stacked on this historical branch and must not merge independently.

Governance boundary

No backend authority, scientific state, collection status, dataset lock, unblinding, primary-analysis authority, efficacy, High-Assurance status, or scientific-N increment is changed by this PR.

[vercel]

Deployment failed for project dynamicgovernanceagenticformation with the following error:

Resource is limited - try again in 1 day (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/ndrorchestration?upgradeToPro=build-rate-limit

[ndrorchestration]

Validation checkpoint for exact head 10abbd16ae6c4064c19bcb7d3629c967a29c3cb5 — FINAL EXACT-HEAD CI STATE:

• 19/19 GitHub workflow runs: PASS / completed-success. This includes UI Command Center Validation, Governance CI, PDMAL Pre-Freeze, Python Tests & Quality Checks, Truth Layer Validation/Tests, Claim Hygiene, Vocabulary Translation Matrix, Control-State Consistency/HEAD Binding, PPTL, regression, custody guard, PDMAL Harness, IP Hygiene, coverage, and propagation.
• UI Command Center Validation: PASS. Locked dependency install, UI semantic/contract tests, and the production Next.js application build all passed on this exact head.
• main remains 0e3effb3ce3ab3aaf5229c93df60bcd2f0a0c3e9; this PR is not stale against a newer main.
• Branch protection requires PPTL CI, Governance CI, and PR Issue-State Keyword Guard; all three are green.
• Vercel status remains FAILURE solely because the Hobby project exceeded the free deployment quota (api-deployments-free-per-day, more than 100 deployments; retry in 1 day). Vercel did not create a preview deployment, so there is no exact-head Vercel visual/runtime preview to claim.

Merge decision: HOLD. Although repository CI is fully green and the Vercel failure is infrastructure/quota rather than a code/build defect, the standing policy is not to reinterpret a failed check as success. No merge performed.

The PR remains presentation-only and preserves PRE-FREEZE · FAIL-CLOSED · SUCCESSOR COLLECTION NOT AUTHORIZED · N=0; it establishes no custody, freeze, authorization, efficacy, or scientific-state transition.

[vercel]

Deployment failed for project dynamicgovernanceagenticformation with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/ndrorchestration?upgradeToPro=build-rate-limit

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
dynamicgovernanceagenticformation	Ready	Preview	Sep 11, 2026 11:12am UTC

[ndrorchestration]

Current-candidate checkpoint after #639 integration:

• Exact PR head: 7bb7d7f6db30a17e066602977aa02cdd8365e469
• Current accepted main/base: 8a436285ed7bacf94fcd2069d51ed82e9785dbc0 (feat(track-a): add fail-closed custody admission helper #639)
• The branch now contains feat(track-a): add fail-closed custody admission helper #639's accepted fail-closed custody-admission helper, procedure, and adversarial tests through an explicit merge integration; the PR is no longer stale against pre-feat(track-a): add fail-closed custody admission helper #639 main.
• The UI frontier is bound to the accepted operator contract: branch track-a-successor-custody-evidence-v2, command py -3 scripts/prepare_track_a_successor_custody_admission.py, then git diff --cached --name-only to verify the exact two-file staged scope.
• The helper is presented as staging only: no commit/push, freeze, collection authorization, secret handling, efficacy, or scientific-N transition is inferred.
• PR [SUPERSEDED] feat(track-a): admit validated successor custody-v2 recovery evidence (non-secret) #630 is now closed as superseded; the UI does not route operators to that stale admission attempt.

Vercel evidence

Vercel has recovered enough capacity to produce READY preview deployment dpl_BMVmmKYZd765hY7EiW2Q2C1jZ29E, and its build completed successfully (Next.js compile, TypeScript, static generation, deployment). However, that preview is bound to earlier branch commit 02a0072457e5c6da6798631704ef07d1192843aa, not current exact head 7bb7d7f6.... Therefore it is useful preview evidence but not exact-head deployment acceptance.

Exact-head CI

The fresh 7bb7d7f6... wave has begun. PR Issue-State Keyword Guard and Critical PR Lane Custody are completed-success; the remaining lanes are currently runner-queued rather than failed.

Decision remains HOLD. Do not merge until the exact current head completes the required validation wave and no newer main invalidates it.

Governance/scientific state remains PRE-FREEZE · FAIL-CLOSED · SUCCESSOR COLLECTION NOT AUTHORIZED · N=0; canonical DGAF efficacy remains NOT ESTABLISHED.

[ndrorchestration]

Current-state reconciliation — 2026-09-11

This draft UI branch remains useful presentation work, but its embedded scientific frontier is now historical. Accepted signed/verified main is 874945374dd4a00a56d6cb8d212c0aacd9ba6157 after #655, where Epoch 002 immutable freeze is ESTABLISHED.

Do not merge #636 in its present form. Its CURRENT_FRONTIER_ID = 'immutable-freeze', PRE-FREEZE banner, and immutable-freeze operator handoff are stale relative to accepted repository truth. Current controlling posture is:

FREEZE ESTABLISHED · FAIL-CLOSED · SUCCESSOR COLLECTION NOT AUTHORIZED · N=0

Active maintenance #657 is sequencing-held on exact head 9711557b58e55c13e3f2d5024f7cbc8da184c8f3: all 22 returned GitHub workflows are terminal SUCCESS, but the exact-head Vercel context remains failed from the Hobby deployment-rate limit. To avoid moving main underneath the scientific chain, keep this UI PR draft/hold until #657 and the immediate final-closure / verification-classification sequence stabilizes. Then reconcile this branch from the then-current accepted main and require a fresh exact-head validation wave.

No presentation branch state is authority for scientific acceptance.