FinanceOS — Analyst Workflow Playbook (Z6)

(How analysis is allowed to happen)

Summary (LOCK)

The Analyst Workflow Playbook defines the only valid paths from signal → claim → action. Any analysis that skips a step is automatically downgraded to P1 commentary and cannot act.

This page answers one question only:

“In what order is the system allowed to think?”

Z-level

Z6 — Governance / Meta-Control

This page constrains process, not outcomes.

Universal Workflow Skeleton (LOCK)

Every workflow must follow this order:

INGEST → SERIALIZE → SENSE → VERIFY → CLAIM → GATE → ACT or BLOCK → PATCH

If any step is skipped → P1 only.

STEP 1 — INGEST (raw inputs)

Allowed inputs:

filings, releases, transcripts
macro datasets
price/volume data
news, rumors, social feeds
on-chain data (crypto)

❌ Not allowed:

“model intuition”
vibes without source
conclusions before serialization

STEP 2 — SERIALIZE (mandatory)

Every workflow must create or update at least one register:

FIN×EVENT
FIN×DATA
COM×ISSUER / COM×ORG

Hard rule:

If it isn’t in a register, it doesn’t exist.

STEP 3 — COMPUTE SENSORS (mandatory)

Minimum sensors per run:

TTC — Time-to-Core
VOL — Volatility regime
CMS — Coupling map shift
SIS — Source integrity
LGI — Liquidity gap

Optional (recommended):

NOI (narrative overhang)

STEP 4 — VERIFICATION (VERIF Pack)

Apply all relevant gates:

VERIF-01: triangulation
VERIF-02: Z-separation
VERIF-03: serialization
VERIF-04: revision awareness
VERIF-06: TTC safety

Failure of any gate ⇒ cap at P1.

STEP 5 — EMIT CLAIM (mandatory)

Every workflow must output at least one CLAIM.

CLAIM (required fields)

statement (1 sentence, testable)
zoom_basis
phase_stamp (P0–P3)
evidence_links (IDs)
disconfirm_tests
expiry_time
controls

No CLAIM → no action.

STEP 6 — PORTFOLIO GATES

Before action, check:

phase permission (P2/P3)
VOL / CMS / TTC overrides
limits & budgets
liquidity constraints

If any gate fails → BLOCK.

STEP 7 — ACT or BLOCK

Two valid outcomes only:

ACT

bounded
logged
with exits

BLOCK

with reason
with next review time

STEP 8 — PATCH (learning loop)

If:

loss occurred
near-miss occurred
gate failed late

Then create:

PATCH record
tighten rule / sensor / threshold

This is how the system evolves without collapse.

Canonical Workflows (Z6)

Workflow A — Earnings / Results

Purpose:
Update issuer capability organs, not price narratives.

Required serialization

FIN×EVENT×EARNINGS
FIN×DATA×METRICS
COM×ORG×OPS / FIN / DIST

Phase rules

P2: metrics + organ proxies updated
P3: multi-quarter robustness + disconfirm tests

Action

P2: adjust
P3: allocate
VOL=V3 → TRUNCATE first

Workflow B — Macro / Policy Print (Z4)

Purpose:
Treat macro as mechanism inputs, not “beat/miss”.

Required serialization

FIN×DATA×SERIES
FIN×EVENT×MACRO

Hard rule (LOCK)

Macro cannot affect decisions unless bound to:

a risk mechanism, or
a CompanyOS organ

No mechanism → P1 only.

Workflow C — Breaking News / Rumor (Z5)

Purpose:
Prevent P0 trading.

Required serialization

FIN×EVENT×NEWS

Phase rules

SIS ≤ S1 → P1 max
Z5-only → P1 max

Action

Watchlist only
Hedging allowed only under truncation mode

Workflow D — Incident / Failure (exchange, ops, cyber)

Purpose:
Protect TTC before narratives spread.

Required serialization

FIN×EVENT×INCIDENT
bind to RISK×COUNTERPARTY / RISK×LIQUIDITY

Sensors

TTC almost always degrades
LGI often jumps

Action

TRUNCATE first
then reassess

Workflow E — Portfolio Review (daily / weekly)

Purpose:
Prevent slow drift into P0.

Required outputs

portfolio TTC
budget status
claims without P2 backing
EXP positions nearing expiry

Mandatory actions

close orphan positions
stitch only under stability
create PATCH for near-misses

Singapore Mini-Example (embedded)

MAS policy statement released

Serialized as SGP×FIN×EVENT×MAS-POLICY
SIS = S3
Z4 anchor present
CMS checked (FX + funding channels)

→ P2 claim allowed
→ scaling blocked if VOL=V3

New York Mini-Example (embedded)

SEC rumor on social media

Serialized as USA×FIN×EVENT×SEC-RUMOR
SIS = S1
Z5-only

→ Capped at P1
→ trade blocked
→ watchlist only

Failure Mode Trace (required)

Analysis skips serialization → jumps to conclusion → no sensors → no gates → action at P0/P1 → TTC collapses.
Repair: force workflow order + CLAIM requirement.

Internal Links

Up: Verification Circuits & Phase Rules (Z6)
Next: Narrative Register & Controls (Z5)
Down: Macro & Policy as DATA+EVENT (Z4)

FinanceOS — Analyst Workflow Playbook (Z6)

FinanceOS — Analyst Workflow Playbook (Z6)

Summary (LOCK)

Z-level

Universal Workflow Skeleton (LOCK)

STEP 1 — INGEST (raw inputs)

STEP 2 — SERIALIZE (mandatory)

STEP 3 — COMPUTE SENSORS (mandatory)

STEP 4 — VERIFICATION (VERIF Pack)

STEP 5 — EMIT CLAIM (mandatory)

CLAIM (required fields)

STEP 6 — PORTFOLIO GATES

STEP 7 — ACT or BLOCK

STEP 8 — PATCH (learning loop)

Canonical Workflows (Z6)

Workflow A — Earnings / Results

Required serialization

Phase rules

Action

Workflow B — Macro / Policy Print (Z4)

Required serialization

Hard rule (LOCK)

Workflow C — Breaking News / Rumor (Z5)

Required serialization

Phase rules

Action

Workflow D — Incident / Failure (exchange, ops, cyber)

Required serialization

Sensors

Action

Workflow E — Portfolio Review (daily / weekly)

Required outputs

Mandatory actions

Singapore Mini-Example (embedded)

New York Mini-Example (embedded)

Failure Mode Trace (required)

Internal Links

Share this:

Like this: