Vortex Alpha v.0.3: Courts Dev Log #20 - From Reports To Verdicts

Governance needs a credible way to address conduct that ordinary proposals and votes cannot resolve. A report must preserve the record that prompted it. A case must protect the people involved. A jury must receive enough information to decide without gaining access to material it has no right to see. Any result must remain explainable after the moment has passed.

Vortex now has a complete reporting and Court system implemented behind a deliberate activation gate. The release connects contextual reporting, deterministic case formation, twelve-Governor Courts, evidence boundaries, structured findings and remedies, appeals, reopening, enforcement contracts, and a public Humanode Codex reference surface.

The implementation is ready for review and remains inactive in production until its migration, providers, authorities, executors, and operational release receive separate approval.

Reporting Begins With A Real Record

Reports now begin from the Vortex record where the issue occurred. A proposal, public draft, Human profile, chamber, faction, Initiative, Formation project, thread, message, board card, delegation, governance action, or status event can expose a report action only when the server can resolve a canonical target.

That target carries a stable type, id, revision, digest, route, and access class. The reporter cannot replace it with a convenient description or point the Court at a different mutable record later. 

The server then determines which reasons are available for that exact target and incident time. The report form presents the verified offense, route, standing basis, statement access, supporting evidence, and protective-review eligibility before the reporter attests and submits.

Twenty-five target families share this contract. Database-backed adapters cover the Vortex records that already have stable identities; protocol actions and external incidents remain unavailable until trusted verifiers can establish their provenance.

Reports Build Cases Through Explicit Rules

A report records an allegation. It does not establish guilt, select a penalty, or automatically create a Court.

Related reports join a canonical bundle bound to the same target snapshot, offense, lane, policy version, and policy hash. The trigger engine can then use one of four approved paths: direct standing, objective protocol proof, community support from a frozen eligible population, or an authorized emergency referral.

Concurrent submissions serialize on the bundle fingerprint. The server reloads the winning state inside the transaction, prevents duplicate Human contributions, freezes the relevant population basis, and can open at most one case. Trigger thresholds and hidden reporter identities never enter the public case projection.

A Twelve-Governor Court With A Defined Procedure

Every Court uses exactly twelve Governors. Candidate selection starts from finalized public seed material, applies party and conflict exclusions, ranks eligible Governors deterministically, and records ordered alternates.

Invitations, acceptance windows, recusals, replacement seats, and insufficient capacity are all represented as states rather than improvised administrator actions. A case waits for capacity instead of quietly proceeding with fewer jurors. Ordinary appeals and reopening requests use distinct panels and exclude the people whose prior participation would compromise the new review.

The procedure moves through service, response, evidence exchange, jury selection, deliberation, finding, remedy, appeal, and finality. Deadlines are advanced by the simulator scheduler. Merely opening a page never changes a case.

Evidence Has An Audience

Court evidence is stored as exact references and metadata. Vortex does not fetch arbitrary submitted URLs or place raw biometric material, private keys, exploit archives, or illegal content into ordinary Court tables.

Each record carries one enforced access class: public after finality, parties and seated jury, jury-only pending summary, security-sealed, or enforcement only. Separate server projections serve public observers, parties, jurors, safety authorities, and executors. The web receives only the channel the viewer is authorized to read.

Party status alone does not unlock a private case file. Service confirmation, jury acceptance, conflict clearance, safety assignment, and executor assignment remain distinct facts with independent scopes and expiry.

Findings And Remedies Stay Inside The Codex

The Court does not invent a punishment after reaching a finding. The frozen policy compiles the selected offense and severity into an allowed sentence envelope before voting begins.

The normalized Humanode Codex contains 27 transgressions across security, operational, user-error, Vortex, and Vortex-compliance domains. Every enabled offense level defines its evidence standard, minimum disposition, available corrections or sanctions, required alternatives, quantitative bounds, compatibility rules, and aggregate burden ceiling.

Jurors first decide whether the allegation is substantiated and at what severity. Remedy voting then uses twelve complete structured ballots. Support thresholds determine which components may enter the result, while bounded numeric recommendations use exact server-side aggregation. The calculation stores its numerator, denominator, rounding rule, envelope, and digest so the outcome can be replayed without trusting a client total.

Measures that conflict with one-Human-one-vote, exceed Vortex authority, or lack an approved executor remain reserved or prohibited. The interface shows those boundaries instead of presenting every conceivable punishment as an available button.

Appeals, Reopening, And Finality

An appeal creates a new review record without rewriting the original finding or ballot. The appellate Court can affirm, reverse, remand, or adopt a reduced remedy package that contains only components from the original decision.

One verified reopening may be requested when qualifying new evidence appears. The evidence basis is digest-bound, the reopening panel is independent, and a granted request leads to a fresh trial jury that excludes prior trial and appellate jurors.

Enforcement remains idempotent and reversible by design. Apply, retry, expire, reverse, and restore operations have explicit records and executor versions. No executor is registered in the production composition root yet, so the implementation cannot claim powers that have not been approved.

The Humanode Codex Becomes A Product Surface

The Humanode Codex now has its own page beneath Vortexopedia. Participants can search the transgression matrix, inspect every available or excluded measure, and read the procedure, severity, and evidence clauses that govern a Court.

Stable references such as HC-3.GOV-03, HC-4.L3, HC-4.E2, and HC-5.G-12 link directly to one definition. The same references appear beside report reasons, findings, evidence standards, remedy choices, policy versions, and case history throughout the Court interface.

Hover hints remain anchored to the term that opened them and can be entered with a pointer. Keyboard and touch users receive the same definition and exact Codex destination. Deep links preserve the selected view and expanded clause, and unknown references produce a visible error instead of silently opening an unrelated entry.

Designed Around The Person Doing The Work

The final interface was tested as a set of complete user journeys rather than a collection of isolated screens.

A reporter can discover a valid entry point, understand standing and evidence requirements, review access and protective choices, submit, amend, supplement, or withdraw. A respondent sees service, response, evidence, challenge, and appeal work in procedural order. A juror receives only their current duty and the record authorized for that duty. An observer receives a redacted public history without private counts, identities, evidence, or ballots.

Long ids and digests remain exactly copyable without breaking narrow layouts. Loading, empty, unauthorized, unavailable, stale, retry, and destructive states all have explicit outcomes. Court records were checked at 390, 768, 1024, and 1440 CSS pixels across Sky, Light, Night, and Fire.

A Smaller And More Auditable Codebase

The implementation finished with an ownership refactor across both product repositories.

Server policy primitives, digests, input constraints, procedure schedules, jury-capacity recovery, appellate invitation scheduling, panel workflows, and transaction handling now have focused owners. The former persistence monolith is a stable facade over policy, report, and case repositories. Obsolete deadline and projection implementations were removed after the current behavior received characterization coverage.

The web now separates Court actions, reusable records, form composition, lifecycle hooks, and pure presentation models. Reporting evidence choices and labels come from one typed source, including the enforcement-only state. Large report-review and protective-control blocks moved into reusable form sections, while route pages continue to own navigation, validation, and API effects.

No runtime dummy records, preview wiring, hardcoded account exceptions, or localized user data entered either release branch.