Pulling ranked themes, signals, and content outputs from the API.
Civitas
Governed adjudication results received from Civitas over the HTTPS plus mTLS submission path, with explicit coverage and fallback posture.
Ready bundles can now submit automatically when the governed flow is enabled and eligibility holds. Manual submission remains available for bounded operator intervention.
0 adjudications are currently publishable as-is. Fallback rows remain on manual-review hold.
secure mtls · evidence ≥ 60 · confidence ≥ 55 · contradiction ≤ 45
34 active branches · challenger Hunter branch: probe new source ... · 10 visible changes
Open war roomKeep adjudication review bounded and truthful.
Civitas remains external. Orbital submits bundles over HTTPS/REST with mTLS and never fabricates a verdict on failure.
Success requires a configured HTTPS endpoint, CA trust, client certificate, client key, and host-authority alignment. If any part of that chain fails, Orbital stores a fallback manual-review result instead of pretending adjudication happened.
This queue is integrated into Orbital’s governed lifecycle, with explicit manual checkpoints where automation does not yet exist.
Current runtime truth: bundle readiness is computed by Orbital, automatic generation and automatic submission run when this workspace enables them, and result storage, fallback/manual-review posture, and proposal-lineage seeding happen automatically after submission. Operators still intervene for manual submission, revision, override, and escalation.
Bounded workspace controls for automatic bundle generation, automatic submission, and truthful fallback posture.
Ready bundles available for governed challenge now, including bundles generated automatically by Orbital when the workspace policy allows it.
6 claims · 6 interventions · evidence 81 · contradiction 48
6 claims · 6 interventions · evidence 88 · contradiction 48
6 claims · 6 interventions · evidence 88 · contradiction 48
6 claims · 6 interventions · evidence 89 · contradiction 48
Stored Civitas results and truthful fallback/manual-review outcomes.
Coverage 0.00 · assessed 0 · partial 0 · not assessed 0
Civitas rejected the adjudication request with status 422.
Coverage 0.00 · assessed 0 · partial 0 · not assessed 0
Civitas rejected the adjudication request with status 422.
Coverage 0.00 · assessed 0 · partial 0 · not assessed 0
Civitas rejected the adjudication request with status 422.
Coverage 0.00 · assessed 0 · partial 0 · not assessed 0
Civitas rejected the adjudication request with status 422.
Coverage 0.00 · assessed 0 · partial 0 · not assessed 0
Civitas rejected the adjudication request with status 422.
6 claims · 6 interventions · evidence 89 · contradiction 48
6 claims · 6 interventions · evidence 88 · contradiction 52
6 claims · 6 interventions · evidence 80 · contradiction 52
6 claims · 6 interventions · evidence 92 · contradiction 48
6 claims · 6 interventions · evidence 91 · contradiction 48
6 claims · 6 interventions · evidence 88 · contradiction 48
6 claims · 6 interventions · evidence 89 · contradiction 48
6 claims · 6 interventions · evidence 69 · contradiction 48
Coverage 0.00 · assessed 0 · partial 0 · not assessed 0
Civitas rejected the adjudication request with status 422.
Coverage 0.00 · assessed 0 · partial 0 · not assessed 0
Civitas rejected the adjudication request with status 422.
Coverage 0.00 · assessed 0 · partial 0 · not assessed 0
Civitas HTTPS/mTLS transport failed.