Essential Workflows for FinanceOS: Analysis to Action

Summary (LOCK)

This playbook defines the only allowed workflows for “analysis → action” in FinanceOS. Each workflow forces: serialization → sensors → verification → phase-stamped claim → bounded action (or block).

If a workflow skips a step, it is automatically P1 commentary and cannot act.

0) Universal Workflow Skeleton (applies to all cases)

PIPELINE-0: Ingest → Act (or Block)

INGEST (documents / data / reports)
EXTRACT entities (ASSET / ISSUER / EVENT / DATA candidates)
SERIALIZE into registers (create/update records)
COMPUTE SENSORS (TTC, VOL, CMS, SIS, LGI, NOI)
RUN VERIF PACK (triangulation, Z-gate, revision awareness, TTC gate)
EMIT CLAIM with phase_stamp + disconfirm tests + expiry
CHECK PORTFOLIO GATES (limits, budgets, emergency mode)
EXECUTE (if allowed) OR BLOCK + WATCHLIST
PATCH (post-mortem if action taken or if near-miss)

Hard law: Steps 3–7 are mandatory for P2/P3.

1) Workflow A — Earnings / Results Day (Issuer-driven)

Purpose

Convert earnings + guidance into Z2 organ updates and FinanceOS risks/events, not vibes.

A1) Required Inputs

earnings release / filing / transcript (primary if possible)
key metrics table (revenue, margin, cash flow)
guidance changes
segment notes

A2) Serialization (must create/update)

FIN×EVENT×EARNINGS-<ISSUER>-<YYYYQ>
FIN×DATA×<METRIC>-<ISSUER>-<YYYYQ> (for each key metric)
COM×ORG updates (ORG-OPS, ORG-FIN, ORG-DIST minimum)

A3) Mandatory Sensors

SIS (source is S3 if primary filing)
CMS (sector coupling shift? yes/no)
VOL (market state)
TTC (earnings can be TTC-short if leveraged positioning is high)
COM sensors: OV/DC/RL/SA for critical organs

A4) Verification Gates

VERIF-02 Z-gate (block narrative-only)
VERIF-03 serialization gate (must pass)
VERIF-05 contradiction injection (for P3 thesis updates)

A5) Output Claim (required)

CLAIM-earnings-1: “Issuer organ X improved/declined and will affect risk Y”
phase_stamp P2 if metrics serialized and organ proxies updated
phase_stamp P3 only if:
multi-quarter consistency OR
strong disconfirm tests + stress path defined

A6) Action policy

P2: allow small adjustments within limits
P3: allow scaling / reallocation
If VOL=V3 or CMS≥C2: run TRUNCATE, then reassess

2) Workflow B — Macro Print (ISM/CPI/Jobs)

Purpose

Treat macro prints as DATA + EVENT that binds to mechanisms, not “market mood”.

B1) Required Inputs

DATA point (value + timestamp)
revision_state (initial/revised/final)
context: prior value, trend, dispersion (optional)

B2) Serialization

FIN×DATA×<SERIES>-<YYYYMM> (e.g., ISM-PMI-202602)
FIN×EVENT×MACRO-<SERIES>-<YYYYMM>

B3) Mandatory Sensors

SIS (primary dataset source)
VERIF-04 revision awareness (must pass)
CMS (regime shift detection)
VOL
TTC (macro can shorten TTC if it changes funding/FX rapidly)

B4) Mechanism Binding Rule (LOCK)

Macro prints cannot affect decisions unless bound to at least one:

COM organ mechanism (ORG-FIN, ORG-DIST, ORG-SUP)
FIN risk mechanism (e.g., REGIME-SHIFT, LIQUIDITY-CLIFF)

If no mechanism binding exists → cap at P1.

B5) Output Claims (required)

CLAIM-macro-1: “Macro print implies regime shift risk ↑/↓ via mechanism M”
disconfirm tests:
“If next print reverses or revisions erase delta → downgrade”
“If credit spreads do not respond as predicted → downgrade”

B6) Action policy

Never act purely on “beat/miss”
Act only if:
CMS indicates shift, AND
mechanism binding exists, AND
portfolio gates permit

3) Workflow C — Breaking News / Rumor

Purpose

Prevent P0 trading and force SIS + triangulation.

C1) Required Inputs

source(s)
timestamp
direct evidence (if any)

C2) Serialization

Always create FIN×EVENT×NEWS-<TOPIC>-<YYYYMMDDhhmm>
verification_state starts at P0/P1

C3) Mandatory Sensors

SIS (most important)
TTC (rumors can be TTC-short because of reflexive markets)
VOL (often rising)
LGI (exit feasibility under stress)

C4) Verification Gates (LOCK)

SIS≤S1 → block trades, watchlist only
SIS=S2 → require two-source triangulation for P2
SIS=S3 → can reach P2 with serialization + sanity check

C5) Output Claim

P0/P1 claim allowed: “There is an unverified report of X”
P2 claim allowed only after triangulation/primary source

C6) Action policy

If TTC=D (danger), default to TRUNCATE not “trade the rumor”
Allow hedges only if they reduce risk and are pre-authorized

4) Workflow D — Crypto Exchange Incident / Hack / Outage

Purpose

Model operational + counterparty failure as a structured EVENT with TTC.

D1) Required Inputs

exchange status page / official statement
on-chain evidence (if relevant)
user reports (low SIS)

D2) Serialization

FIN×EVENT×EXCHANGE-INCIDENT-<VENUE>-<YYYYMMDD>
bind to:
FIN×RISK×COUNTERPARTY-FAIL
FIN×RISK×LIQUIDITY-CLIFF
FIN×CHANNEL×LIQUIDATION-CASCADE (if applicable)

D3) Mandatory Sensors

SIS
TTC (often D)
LGI (often L2→L3 quickly)
VOL

D4) Verification gates

Z-gate: avoid “Twitter says hack” as action driver
TTC gate: if TTC=D, force TRUNCATE

D5) Output Claim

P2 only if official confirmation or strong on-chain evidence exists
Must include:
“funds at risk?” (unknown vs confirmed)
“withdrawals paused?” (yes/no)
“contagion channels” (stablecoin, leverage platforms)

D6) Action policy

prioritize survivability: reduce venue concentration, reduce leverage exposure
staged execution only

5) Workflow E — Portfolio Review Cycle (Daily/Weekly)

Purpose

Keep the system Phase-stable over time (avoid slow drift).

E1) Required Inputs

current positions
updated sensor states (FIN + PRT)
upcoming events calendar

E2) Mandatory Outputs

PTTC
budget status
positions lacking P2 claims (must be closed or re-justified)
EXP positions expiring soon

E3) Actions

apply limits
run STITCH if stable, TRUNCATE if unstable
create PATCH records for near-misses

6) Mandatory Output Format (Model Contract)

Every workflow run must output, in order:

Register updates created/changed (IDs)
Sensor summary line (TTC, VOL, CMS, SIS, LGI)
VERIF summary line (pass/fail per gate)
CLAIM block (phase stamped)
Allowed actions (if any) + the gate that permits them
Blocked actions + why (which gate failed)
Next revalidation time (expiry_time)

If any section missing → cap output at P1 and block actions.

7) Failure Mode Trace (required)

Fast headline → SIS ignored → no serialization → TTC collapses → action taken → liquidity cliff → budget breach → post-hoc rationalization.
Repair: workflow forces serialization + gates + truncation before TTC collapse.

Analyst Workflow Playbook (Almost-Code) — FinanceOS Runtime Pipelines

Summary (LOCK)

0) Universal Workflow Skeleton (applies to all cases)

PIPELINE-0: Ingest → Act (or Block)

1) Workflow A — Earnings / Results Day (Issuer-driven)

Purpose

A1) Required Inputs

A2) Serialization (must create/update)

A3) Mandatory Sensors

A4) Verification Gates

A5) Output Claim (required)

A6) Action policy

2) Workflow B — Macro Print (ISM/CPI/Jobs)

Purpose

B1) Required Inputs

B2) Serialization

B3) Mandatory Sensors

B4) Mechanism Binding Rule (LOCK)

B5) Output Claims (required)

B6) Action policy

3) Workflow C — Breaking News / Rumor

Purpose

C1) Required Inputs

C2) Serialization

C3) Mandatory Sensors

C4) Verification Gates (LOCK)

C5) Output Claim

C6) Action policy

4) Workflow D — Crypto Exchange Incident / Hack / Outage

Purpose

D1) Required Inputs

D2) Serialization

D3) Mandatory Sensors

D4) Verification gates

D5) Output Claim

D6) Action policy

5) Workflow E — Portfolio Review Cycle (Daily/Weekly)

Purpose

E1) Required Inputs

E2) Mandatory Outputs

E3) Actions

6) Mandatory Output Format (Model Contract)

7) Failure Mode Trace (required)

Share this:

Like this: