ui: align command-center shell with audience journey - #649
ndrorchestration wants to merge 21 commits into
Conversation
|
Deployment failed for project dynamicgovernanceagenticformation with the following error: Learn More: https://vercel.com/ndrorchestration?upgradeToPro=build-rate-limit |
e99c9fd to
87f6c73
Compare
|
Deployment failed for project dynamicgovernanceagenticformation with the following error: Learn More: https://vercel.com/ndrorchestration?upgradeToPro=build-rate-limit |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Current-state reconciliation — 2026-09-11 This stacked presentation lane is now behind accepted scientific state. Signed/verified Keep #649 DRAFT / HOLD. Its current presentation of immutable freeze as the next actionable transition is stale, and it remains dependent on #636. Do not merge it independently or advance When the scientific sequence stabilizes, reconcile #636 first to the then-current accepted frontier, then reconcile/rebase #649 onto that accepted UI lineage and rerun fresh exact-head UI/GitHub/Vercel validation. No prior Vercel or GitHub evidence transfers after head changes. Controlling posture: |
Scope
Preserve the presentation-only audience-navigation/accessibility refinement stacked on #636. The intended journey remains Understand → Verify → Inspect → Operate, with Decision-Frontier-first control-room flow, runtime-observability disclaimers, keyboard/mobile navigation, focus restoration, skip link, and grouped hierarchy.
Current disposition — 2026-09-15
DRAFT / HOLD / STALE-LINEAGE / STACKED UNIQUE WORK. DO NOT MERGE AS-IS.
Current protected
mainis1fb2c665587d5a0e7b213aef1cc5c870097cdc9b. Track A Epoch 002 collection is COMPLETE; operator retained-byte provenance is PENDING; dataset lock is NOT ESTABLISHED; unblinding and primary analysis are NOT AUTHORIZED; canonical efficacy is NOT_ESTABLISHED; High-Assurance remains PRE-FREEZE / FAIL-CLOSED / NOT AUTHORIZED / N=0.This branch is stacked on stale #636 and inherits historical governance presentation. Its accessibility/navigation work remains potentially reusable, but it cannot be accepted independently or on historical validation.
Because the active #679 retained-byte checkpoint is bound to exact executing repository
HEAD, do not reconcile this UI lane before that checkpoint. Avoid movingmainsolely to reduce UI backlog.Future reconciliation
After #636 is reconstructed on a stable accepted frontier:
Governance boundary
No backend API, runtime telemetry authority, evidence class, empirical result, scientific N, efficacy, collection authority, dataset lock, unblinding, or analysis authority changes.