Vortex Dev Log #10 — inVision Goes Live, Legitimacy Referendum, and Stability Engine

Vortex Dev Log #10 — inVision Goes Live, Legitimacy Referendum, and Stability Engine

TL;DR

inVision is now a live system-state dashboard instead of a placeholder. The simulator now exposes a real Legitimacy mechanic driven by active human-node objections, a distinct referendum flow when legitimacy collapses, and a server-owned Stability engine with explainable components, crisis caps, confidence, and governor alerts on threshold changes.

What shipped

1) inVision is now live and server-owned

  • The inVision page is no longer a blurred placeholder.
  • GET /api/invision now returns live system-state data computed on the server.
  • The page now renders:
  1. top-level system-state banner
  2. Legitimacy
  3. Stability
  4. Decentralization
  5. governance signals
  6. treasury/economy indicators
  7. risk signals
  8. general chamber proposal pressure
  9. largest factions

2) Legitimacy is now a real system mechanic

  • Legitimacy is now derived from live active human-node objections.
  • Any currently active human node can open My Governance and declare:
  1. VORTEX IS ILLEGITIMATE
  • Each active human node carries equal legitimacy weight.
  • Governors do not receive extra weight.
  • Chamber membership, delegation, and treasury do not directly change the legitimacy percentage.
  • My Governance now shows the legitimacy section and objection controls directly.

3) Legitimacy breach now creates a distinct referendum

  • When legitimacy falls below the trigger threshold, the system auto-creates a referendum.
  • This is not a proposal-pool flow and not a normal chamber vote.
  • The referendum is its own vote surface with its own route and vote action.
  • Only currently active human nodes can participate.
  • CM/MM scoring is not used in the referendum path.
  • The referendum flow is treated as a constitutional emergency mechanism rather than ordinary chamber governance.

4) Passed legitimacy referendum now resets the simulation

  • If the referendum passes, the simulator wipes simulation state and restarts from a clean governance baseline.
  • Indexed human-node proof data is preserved:
  1. proof_ledger
  2. chain_indexer_state
  3. This makes legitimacy a real constitutional control, not a cosmetic UI signal.

5) Stability is now a real explainable engine

  • Stability is no longer a placeholder percentage.
  • The engine is server-owned and computed from canonical governance/execution signals.
  • It uses a rolling Last 30d + live backlog snapshot.
  • The current engine includes:
  1. decision closure
  2. backlog health
  3. delay health
  4. formation continuity
  5. governor continuity
  6. constitutional calm
  7. concentration health
  • The published inVision payload now includes:
  1. score
  2. band
  3. confidence
  4. component breakdown
  5. applied caps/floors
  6. window label

6) Crisis caps and confidence are built into stability

  • Stability can now be hard-capped during crisis conditions such as:
  1. active legitimacy referendum
  2. no active governors with live governance load
  3. severely stale chamber-vote backlog
  4. legitimacy dropping below 40%
  • A confidence layer prevents low-data conditions from pretending to be precise.

7) System threshold alerts now reach governors

  • Both Legitimacy and Stability now emit feed alerts when they cross decile thresholds.
  • Alerts trigger in both directions:
  1. upward
  2. downward
  • Crossings at 10% through 90% are persisted as system feed items.
  • These alerts surface in Urgent and route users into inVision.
  • Alert delivery is now aligned with the actual governor baseline, including genesis/bootstrap governors.

8) Reliability and cleanup during closeout

  • Tightened local migration reconciliation so current local schemas can be brought back into sync reliably.
  • Removed leftover debug and hardcoded placeholder behavior in active simulator surfaces.
  • Restored Courts to a blocked WIP state so unfinished placeholder metrics are not shown as live production data.
  • Performed additional bug-fix passes on alert routing, recipient resolution, and urgent-feed visibility.

Validation

  • Server:
  1. yarn prettier:check passed
  2. yarn typecheck passed
  3. targeted regressions passed:

    - tests/api/invision.test.ts

    - tests/api/my-governance.test.ts

    - tests/api/stability.test.ts

    - tests/api/system-metric-alerts.test.ts

  • Web:
  1. yarn prettier:check passed
  2. yarn typecheck passed
  3. yarn build passed

Why this matters

  • inVision is now a real political/economic systems page instead of a stub.
  • Legitimacy is now enforceable at the human-node layer, not just described in docs.
  • The system now has a constitutional emergency path when consent collapses.
  • Stability is now explainable, server-owned, and visible as a first-class system metric.
  • Governors now get feed/urgent warnings when the system materially changes state.