STRAT Arc Board

The judgment seat's lane: consume the measurement, join the book, author the brief. Sibling of the RES arc board — same terminal state, this side of the pipeline.
built 2026-08-08 16:51 · repo 6e8acb5 · every figure measured at build time · "unmeasured" is rendered, never a guessed zero

1 · Where the seat is now

Stage 4shared gate current_stage
31book positions (oracle, live)
6/6payload days consumed / delivered
14authored so-lines standing
34/140consolidation queue decided
31entities classified (universe)
12 + 10harness: safe-state facts + laws
1Daily Signal issues (test)

2 · Gate 0 — IBKR statement freshness (live, operator-ruled 2026-08-08)

FAIL — no daily analysis may reportstatements through 2026-08-06, need 2026-08-07 (weekday clock; market holidays not modelled)
The first action of any daily analysis. A report for day D needs statements through the last trading day before D. Zero tolerance for reporting: the feed's own stale_after is a health marker, not the reporting bar. fill ledger complete: True · 4449 fills · last fill 2026-08-05.

3 · The nearest safe point

viska.fund-signal/0.1 shipped + the whole August chain green.
Six payload days consumed end to end (fund-conviction → strategy → fe-signal → delivery manifest), every gate PASS, byte-identical re-runs. The harness (docs/contracts/STRAT-HARNESS.md) carries the safe state in full: 12 settled facts, 10 laws, each cited. If anything downstream is in doubt, this is the state to return to.

4 · The shared gate — one gate for the arc, viska-pm advances it

Stage 0 — RES reads12 sources, one specific sentence each — RES's stagepassed
Stage 1 — RES rules on 08-06consequence only; the cause is settledpassed
Stage 2 — RES states deliverable 2matched against the record, not inventedpassed
Stage 3 — viska-pm dispatches STRATdeliverable-2 BUILD starts on this dispatch, never beforepassed
Stage 4 — RES resumes buildDELIVERY FIRST applies againYOU ARE HERE
Operator override on record: a live, explicit operator instruction overrides the gate for this seat and does not advance it. The Daily Signal test issue was built under that clause; deliverable-2 BUILD still waits for the Stage-3 dispatch.

5 · The pipeline, and where it stops today

RES conviction payloadviska.theme-conviction/0.6, the measurement · ViskaRes research/analysis/<date>/UPSTREAM
Fund joinbook joined, holdings classified, refuses unclassified · emit_fund_conviction.pyHAND-RUN
Strategy sectionsrank by rollups, so-lines injected · emit_strategy.pyHAND-RUN
Selection layerviska.fund-signal/0.1 — SHIPPED · emit_fe_signal.pySHIPPED
FE delivery manifestthree artifacts per date, quadrant by reference · emit_fe_delivery.pyHAND-RUN
Daily Signalthe client brief beside the quadrant — CONTRACT FORMING · data/daily-signal/ · test issue onlyGATED
Client deliverythe incumbent n8n Mímir brief still sends at 8:05 · n8n-client-viska-ai — replaced at cutover, not beforeINCUMBENT
Everything between the upstream payload and the delivery manifest is hand-run, deliberately — manual until the contracts are settled, then a workflow delivers at the same time daily. The brief itself is the piece that does not exist yet: one test issue, contract forming. The client's 8:05 email today still comes from the incumbent n8n pipeline.

6 · Remaining goals, ending at the terminal state

idgoalstate
G1Selection layer shipped
viska.fund-signal/0.1, 529 rows to 34 signals. Input to deliverable 2, not the deliverable.
DONE
G2Harness + hard gates standing
STRAT-HARNESS.md wired into session start; Gate 0 (IBKR freshness) ruled and live on this board.
DONE
G3Daily Signal contract settled
08-03 test issue built and reviewed. Next: head-to-head vs the incumbent's 08-03 issue, then the contract items become the brief schema.
IN PROGRESS
G4Deliverable 2 — the synthesis
Synthesis not selection: signals joined to holdings, four majors x four horizons, macro strip, emerging strength-only. Waits for the Stage-3 dispatch.
GATED
G5ANAV on every surface
Wiki and oracle legs closed. App and Supabase legs routed to viska-pm.
OPEN
G6Daily build runs unattended
Manual by design until the contracts are settled end to end; then a workflow delivers at the same time daily.
NOT STARTED
G7THE ARC ENDS HERE
The daily war room overtakes all tasks and contracts and produces a payload on a set timeline each day and delivers it into the full pipeline (strat-db-fe) and the client reads it every morning.
TERMINAL
The terminal state, operator's words: the arc ends when the daily war room overtakes all tasks and contracts and produces a payload on a set timeline each day and delivers it into the full pipeline (strat-db-fe) and the client reads it every morning.