FinanceOS — Verification Circuits & Phase Rules (Almost-Code) (CivOS-Aligned)

Summary (LOCK)

Verification Circuits convert raw signals into Phase-stamped claims (P0–P3), and block actions that would otherwise be driven by rumor, narrative, or untracked assumptions.

This is the “rail system” that turns Claude-style autonomy into CivOS-governed autonomy.

0) Phase Definitions (LOCK)

P0 — Unverified

single source
unclear provenance
“someone said”
model inference with no anchors

P1 — Plausible (Weak)

some evidence exists
but incomplete / not triangulated
may be Z5 narrative only

P2 — Verified (Actionable)

triangulated sources
structured record created (EVENT/DATA/ISSUER/ASSET)
at least one Z0–Z4 anchor

P3 — Robust (Stable under variation)

verified across cycles / stress
survives contradictory evidence tests
includes explicit failure conditions + controls

Hard law:

Trades require P2 minimum (unless pre-authorized hedge rule).
Allocations / strategy require P3 or explicit experimental budget.

1) Claim Object (Everything becomes a claim)

Every model output must be serialized as a CLAIM.

Place×FIN×Z6×O×CLAIM×ID

CLAIM fields

claim_id
statement (one sentence, testable)
scope {asset|issuer|macro|portfolio}
zoom_basis [Z-levels used]
phase_stamp {P0|P1|P2|P3}
evidence_links [DATA/EVENT/ISSUER/ASSET IDs]
assumptions [ASSUMP IDs]
disconfirm_tests [TEST IDs]
expiry_time (when claim must be revalidated)
controls [RULE IDs]

2) Verification Circuit Set (VERIF Pack v0.1)

VERIF-01: Two-Source Triangulation

Rule

P2 requires ≥2 independent sources OR one primary source (S3) + a structured dataset confirmation.

Inputs

SIS (Source Integrity Score)
source independence flag

Output

eligible_for_P2 {yes|no}

VERIF-02: Z-Separation Gate (Narrative cannot override reality)

Rule

If zoom_basis = {Z5 only} → phase_stamp cannot exceed P1.
To reach P2, must include ≥1 anchor from Z0–Z4.

Purpose
Stops “everyone says” from becoming “it is”.

VERIF-03: Evidence Serialization Gate

Rule
A claim cannot be P2 unless it creates at least one of:

EVENT record, or
DATA record, or
ISSUER update record

Purpose
If it isn’t in the directory, it doesn’t exist.

VERIF-04: Revision Awareness Gate (Macro prints)

Rule
If a claim references a revisable series (e.g., macro prints), it must declare:

revision_state {initial|revised|final}
Else cap at P1.

VERIF-05: Contradiction Injection Test

Rule
To reach P3, the claim must list at least 2 disconfirm tests:

“If X happens, this claim is wrong”
“If data shows Y, we downgrade”

Purpose
Prevents narrative lock-in.

VERIF-06: Time-to-Core (TTC) Safety Gate

Rule
If TTC = D (danger), then:

raise required phase by +1 (P1→P2, P2→P3)
OR
apply truncation controls (RULE-T) before action.

3) Source Grading (SIS) Rules

SIS scale

S0 untrusted (anonymous, unverifiable)
S1 weak (single outlet, no primary evidence)
S2 credible (reputable, some evidence)
S3 primary (filing, official release, direct dataset)

Action constraints

SIS≤S1 → no trades, only watchlist + monitor
SIS=S2 → can reach P2 only with triangulation
SIS=S3 → can reach P2 with serialization + sanity checks

4) Action Permission Matrix (LOCK)

Phase	What’s allowed	What’s blocked
P0	monitor only, create watchlist	any trade, any allocation
P1	small “probe” only if pre-budgeted	scaling, leverage, thesis write-up
P2	normal trade allowed (with controls)	strategic allocation without P3
P3	strategic allocation, sizing, policy changes	none (except explicit constraints)

Probe rule (experimental lane):

probes must be capped and labeled EXP
probes must have expiry_time and downgrade triggers

5) Downgrade / Escalation Logic (RULE-D)

RULE-D1: Downgrade triggers

A P2/P3 claim is downgraded if:

a disconfirm test fires
source retraction occurs
CMS ≥ C2 (coupling break)
VOL = V3 (shock regime)

RULE-D2: Escalation triggers

A claim may be escalated if:

it survives 1–2 cycles of contradictory data
independent confirmations accumulate
model reproduces result under different assumptions

6) “No Z5-Only Trading” (Hard Law)

If a thesis is driven primarily by social narrative, sentiment, or headlines (Z5), it cannot exceed P1 and cannot trigger trades.

Exception

pre-authorized hedges (risk reduction) may execute under RULE-T.

7) Experimental Lane Budget (EXP) (CivOS Safe Exploration)

EXP definition

A controlled sandbox where exploration is allowed without infecting core stability.

EXP constraints

max_loss_per_period
max_position_size
no leverage (unless explicitly allowed)
automatic stop-loss and expiry
mandatory post-mortem (PATCH record)

Purpose
This is how you allow “Visionary exploration” without dragging the system into P0.

8) Required Outputs for Any Model (Claude/GPT/etc.)

Every response that proposes an action must output:

CLAIM block (with phase_stamp)
Evidence IDs (DATA/EVENT/ISSUER/ASSET)
Sensor state (TTC, VOL, CMS, SIS at minimum)
Controls (RULE-T / RULE-S / exposure caps)
Disconfirm tests (for P3)

If any item missing → cap at P1 and block action.

9) Copy-Paste Templates

Template A — CLAIM

claim_id: GLB×FIN×Z6×O×CLAIM×_____
statement: _____
scope: {asset|issuer|macro|portfolio}
zoom_basis: [Z__ , Z__]
phase_stamp: {P0|P1|P2|P3}
evidence_links: [_____]
assumptions: [_____]
disconfirm_tests:

TEST-1: If _____ then downgrade to P1
TEST-2: If _____ then invalidate (P0)
expiry_time: _____
controls: [RULE-T, RULE-D, ...]

Template B — VERIF result line

VERIF summary:

SIS=S__
Z-gate: pass/fail
Triangulation: pass/fail
Serialization: pass/fail
TTC gate: pass/fail
→ final phase stamp

10) Failure Mode Trace (required)

Z5 headline → SIS=S1 → (if ungated) P0 trade → TTC-D → forced sell channel opens → LGI=L3 → VOL=V3 → portfolio fracture.
Repair path: VERIF-02 blocks Z5-only → VERIF-01 forces triangulation → VERIF-03 serializes EVENT/DATA → RULE-T truncates → downgrade logic contains spillover.