§01 Current State — Viska × boas.dev

‹ Index

§ 01 / 05Current State

In Build · Paper · Phase 1

Intelligence Layer 01 / 04

∞

Information Streams

Any source, plumbed the same way. CLI-first for reliability.

Plumbing · Adapters · Routing

Streams the platform can carry

01Market data — Alpaca, IBKR, exchanges via CLI/SDK; tick through daily barTesting
02Macro & quant — FRED series, QuantOracle, custom economic calendarsTesting
03Central bank corpus — Fed FOMC, ECB, BIS statements with structured parsingTesting
04Social & sentiment — X via Grok, news APIs, targeted keyword watchTesting
05Filings & regulatory — SEC EDGAR, ESMA, disclosure trackersScoped
06Crypto on-chain — exchange flows, DeFi metrics, wallet surveillancePhase 2
07Internal research — PDFs, notes, meeting transcripts indexed into retrieval layerTesting
08Custom private feeds — broker reports, LP data rooms, bespoke scrapesOn request

⟳

Deliverables

Subject to change. Viska's priority drives the build order.

Flex · Priority-driven · Cited

Intelligence outputs

01Daily macro brief — Grok narrative synthesis, overnight moves, catalystsTesting
02Pre-market & EOS snapshots — positions, risk envelope, session thesisTesting
03Weekly performance report — QuantStats metrics, attribution, lessonsTesting
04Alert dispatch — L1 info, L2 warning, L3 halt — tiered routingBuilt
05Wiki query — ask anything across the corpus, cited answerTesting
06Event briefings — FOMC, earnings, geopolitical triggers on demandBuilt
07Scenario notes — overnight "what if" runs against current bookMonth 5

Slack + Web UI

Day 1 surface. Any platform after — Teams, email, custom.

Day 1 · Slack · Web UI

Slack surface — what is live now vs. planned

01App Home dashboard — entry point, quick actions, pinned artifactsLive
02Direct message with Mímir — conversational query across the corpusLive
03Channel-scoped agent posts — dedicated channels per strategy / themeMonth 1
04Alert routing — L1/L2/L3 routed by severity, ack-required for L3Month 2
05Approvals in thread — CIO signs off on order bundles inlineMonth 3
06Scheduled briefs — morning brief + EOS summary delivered to #intelMonth 1
07Threads as sessions — every thread persists as a research session recordMonth 2

24/7

Surveillance

Agents between sessions. Quiet until thresholds trip.

Watch · Threshold · Wake

Continuous monitors

01Position watchdog — every 5 min during market hours, L1/L2/L3 thresholdsTesting
02Drawdown monitor — intraday + session cumulative haltsBuilt
03Crypto surveillance — exchange flows, whale moves, DeFi anomaliesMonth 2
04Macro sentiment — central bank speech delta, rates repricingMonth 2
05Geo-risk scanner — filings, sanctions, elections, policy shiftsMonth 2
06Partner surveillance — distribution partner behavior for fund flowsMonth 6

◈

Data Lake

One shared store. Every stream, every artifact, every member can query.

Shared · Flexible · Member-wide

Built as Viska needs it

01New source — new adapter, same pipeline shape, no rewriteScoped
02New deliverable — new workflow on top of the storeScoped
03Shared store — macro brief, session notes, analyst thesis — same lakeMonth 1
04Queryable by every role — no silos, no duplicated pipelinesMonth 1

The intelligence layer is a flexible research spine, not a fixed product. Any source that matters to Viska becomes an adapter. Any deliverable Viska wants becomes a workflow. The same plumbing carries all of it.

Underneath, every stream flows into a shared data lake. One queryable surface. Every member of the fund reaches the same store — CIO macro brief, analyst thesis, session notes, position history. No silos, no duplicated pipelines.

Day 1 Viska receives through Slack and a private web UI. Teams, email, custom — any surface we choose to add next. Viska decides the build order at every phase boundary. We listen, we adjust, we ship in value order.

Execution Layer 01 / 04

Order Flow

Four agents, four artifacts, one audited order.

Analyst → Risk → Operator → Execution

Pipeline stages

01Signal arrives — TradingView webhook or agent proposal with thesisTesting
02Analyst validates — chart + pandas-ta confirmation, writes thesis-context.jsonTesting
03Risk sizes & sets guards — 8-rule pre-trade check, writes risk-parameters.jsonTesting
04Operator reviews bundle — reads all artifacts, signs or rejectsTesting
05Execution agent fires — reads signed bundle, calls Alpaca, writes trade-log.jsonTesting
06Watchdog monitors — position surveillance begins immediatelyTesting

Risk Framework

Eight rules. Every order. Logged, tunable per strategy.

Pre-trade · Per-strategy · Audited

Enforced rules

01Position size cap — % of book per instrumentTesting
02Exposure caps — sector, factor, correlation cluster limitsTesting
03Stop & target required — no naked entriesTesting
04R-multiple floor — minimum reward/risk ratio per tradeTesting
05Session drawdown halt — hard stop at configured thresholdTesting
06Daily trade count ceiling — prevents tilt cyclesTesting
07Liquidity check — minimum ADV, spread, recent volumeTesting
08Blackout windows — earnings, FOMC, holidays — configurableTesting

Hard Gates

Schema-enforced approval. Any failure halts the cycle.

Schema · Signature · Halt

Execution gates

G1Schema validation — order-submission.json must parse, all required fieldsTesting
G2Risk sign-off present — risk_manager_sign_off field populated and signedTesting
G3Operator approved — operator_approved: enum [true] — schema rejects any other valueLocked
G4Thesis context attached — linked thesis, catalyst, stop, target all presentTesting
—On failure — bundle rejected, reason logged, watchdog notified, no retryTesting

Phase 1 Guardrails

Paper only. Promotion to live is earned, not toggled.

Paper · Audit · Earn promotion

What Phase 1 forbids and records

01Paper trading only — Alpaca Paper, no live broker credentials in reach of agentsTesting
02Daily kill switch — operator can halt all agents instantly, no queued ordersTesting
03Session budget — max trades, max exposure, max session loss configured per dayTesting
04Immutable audit — trade-log.json + session-log.json per event, replayableTesting
05Promotion gate — paper → live requires review, not a flag flipPlanned

The execution layer turns a signal into an audited order through four specialised agents. Analyst validates the idea. Risk sizes the position and sets the guards. Operator approves the bundle. Execution fires the broker call. Each step writes a JSON artifact the next step reads — no agent both decides and executes.

Risk is not a library call. It is a dedicated agent running eight pre-trade rules on every order — sizing, exposure, stops, R-multiple, drawdown halts, trade ceilings, liquidity, blackout windows. Execution cannot fire without a bundle that passes four schema-enforced hard gates, including the locked operator_approved field the schema itself rejects without.

Phase 1 is paper trading only. Alpaca Paper, no live broker credentials in reach of agents. Kill switch, session budget, immutable audit per event. Promotion to live capital is a separate governance step, not a config flag. The system earns the right to move real money.