FinanceOS — Z5 Narrative Register & Controls (WordPress Paste-Ready)

Summary (LOCK)

Z5 is the narrative layer: headlines, sentiment, rumors, and “what people believe.” FinanceOS treats Z5 as observable input data — but forbids it from becoming actionable without Z0–Z4 anchors.

Hard law: Z5-only claims are capped at P1 and cannot trade.

Z-level

Z5 — Narrative Layer

This layer exists because narratives move prices, but narratives are not reality.

1) What counts as Z5 (Narrative)

Z5 inputs include:

news headlines
social media threads
influencer commentary
“market consensus” takes
rumors (“X will happen tomorrow”)
sentiment indicators (fear/greed, positioning stories)

Z5 is high-speed and high-noise.

2) Z5 Record Types (Registers)

A) Narrative Event (NEWS / RUMOR)

Record ID: Place×FIN×Z5×O×EVENT×NEWS-<TOPIC>-<YYYYMMDDhhmm>

Required fields

event_type {news|rumor|commentary}
timestamp_utc
source_list (raw)
impacted_assets [ASSET IDs] (optional)
claimed_mechanism (if any)
initial_phase {P0|P1}
SIS (source integrity score)
expiry_time (narratives decay fast)

B) Narrative Claim (Z5 CLAIM)

Record ID: Place×FIN×Z6×O×CLAIM×Z5-<ID>

Required fields

statement (one sentence)
zoom_basis = [Z5]
phase_stamp = P1 maximum
evidence_links = [Z5 EVENT IDs]
controls = [RULE-Z5-0, VERIF-02]
expiry_time

3) Source Integrity Score (SIS) — Z5 rules

SIS scale (same as FinanceOS)

S0 untrusted
S1 weak
S2 credible
S3 primary

Z5 constraints (LOCK)

SIS≤S1 → watchlist only
SIS=S2 → still capped at P1 unless Z0–Z4 anchor appears
SIS=S3 (rare in Z5) → can promote only if serialized as Z4 EVENT/DATA (i.e., it becomes reality-layer input)

4) Narrative Overhang Index (NOI) (optional but powerful)

Purpose: detect “everyone believes the same story.”

NOI outputs

N0: low crowding
N1: mild
N2: crowded
N3: extremely crowded (fragile)

Control

NOI=N3 → treat upside as fragile; require asymmetric risk rule and stricter verification
NOI never upgrades phase by itself

5) Hard Controls (Rules)

RULE-Z5-0 (LOCK): No Z5-only trading

If zoom_basis = [Z5] only → phase ≤ P1 → no trades.

RULE-Z5-1: Z5 must route through Z4/Z3 mechanism

To become actionable (P2), the narrative must:

be matched to a mechanism (Z3 risk/channel), and
be anchored by Z0–Z4 evidence (EVENT/DATA/ISSUER/ORG update)

If either is missing → remains P1.

RULE-Z5-2: Narrative expiry

Every Z5 record must expire:

if not anchored within the expiry window → auto-downgrade to P0 (discard)

This prevents stale narratives from lingering.

6) Verification Gates Applied to Z5

VERIF-02 (Z-Separation) — the core gate

Z5-only → P1 max
must include Z0–Z4 anchor to reach P2

VERIF-01 (Triangulation)

Even with multiple Z5 sources, triangulation does not create reality.
It only increases confidence that “the narrative exists.”

7) Allowed Outputs for Z5 (what the system may do)

Z5 may trigger:

watchlist creation
monitoring schedule
request for primary evidence
mapping to possible mechanisms (hypotheses only)
risk reduction hedges only if pre-authorized under truncation mode

Z5 may NOT trigger:

opening positions
scaling positions
allocation changes

8) Copy-Paste Templates

TEMPLATE — Z5 EVENT (news/rumor)

event_id: USA×FIN×Z5×O×EVENT×NEWS-_____
event_type: {news|rumor|commentary}
timestamp_utc: _____
source_list: [_____]
SIS: S__
impacted_assets: [_____]
claimed_mechanism: _____ (optional)
initial_phase: P0|P1
expiry_time: _____
controls: [RULE-Z5-0, RULE-Z5-2]

TEMPLATE — Z5 CLAIM (capped)

claim_id: USA×FIN×Z6×O×CLAIM×Z5-_____
statement: _____
zoom_basis: [Z5]
phase_stamp: P1 (maximum)
evidence_links: [Z5 EVENT IDs]
controls: [RULE-Z5-0, VERIF-02]
expiry_time: _____

9) Singapore example (Z5 → blocked unless anchored)

Scenario

“Telegram says MAS will change stance tomorrow.”

Serialize: SGP×FIN×Z5×EVENT×NEWS-MAS-RUMOR-...
SIS likely S0/S1
zoom_basis [Z5]

Result

Claim capped at P1
action blocked
watchlist only
request Z4 anchor (MAS official release)

10) New York example (Z5 → blocked)

Scenario

“X says SEC will sue a major exchange.”

Serialize: USA×FIN×Z5×EVENT×NEWS-SEC-RUMOR-...
SIS S1
zoom_basis [Z5]

Result

P1 max
trade blocked
monitor only
if SEC filing/release appears → becomes Z4 EVENT and can be evaluated

11) Failure mode trace (required)

Z5 narrative treated as truth → trades executed → TTC collapses under volatility → liquidity cliff → forced error.
Repair: RULE-Z5-0 caps at P1 → block actions → require Z0–Z4 anchoring.

Internal links (up/down one layer)

Up: Analyst Workflow Playbook (Z6)
Next: Macro & Policy as DATA+EVENT (Z4)
Down: Risk & Channel Registry (Z3)

FinanceOS — Z5 Narrative Register & Controls (WordPress Paste-Ready)

Summary (LOCK)

Z-level

1) What counts as Z5 (Narrative)

2) Z5 Record Types (Registers)

A) Narrative Event (NEWS / RUMOR)

B) Narrative Claim (Z5 CLAIM)

3) Source Integrity Score (SIS) — Z5 rules

SIS scale (same as FinanceOS)

Z5 constraints (LOCK)

4) Narrative Overhang Index (NOI) (optional but powerful)

5) Hard Controls (Rules)

RULE-Z5-0 (LOCK): No Z5-only trading

RULE-Z5-1: Z5 must route through Z4/Z3 mechanism

RULE-Z5-2: Narrative expiry

6) Verification Gates Applied to Z5

VERIF-02 (Z-Separation) — the core gate

VERIF-01 (Triangulation)

7) Allowed Outputs for Z5 (what the system may do)

8) Copy-Paste Templates

TEMPLATE — Z5 EVENT (news/rumor)

TEMPLATE — Z5 CLAIM (capped)

9) Singapore example (Z5 → blocked unless anchored)

Scenario

10) New York example (Z5 → blocked)

Scenario

11) Failure mode trace (required)

Internal links (up/down one layer)

Share this:

Like this: