WAT Operating Rules (Workflows → Agents → Tools)¶
Purpose¶
Make the Edge Factory scalable and reproducible: - Workflows (SOPs) define the steps and gates. - Agents do reasoning, planning, review, and decision-making. - Tools do deterministic execution (scripts, tests, runners).
Tool-First Rule¶
Before writing new logic in chat: 1) Check if a tool exists in /tools or /src. 2) If not, create a tool with stable I/O + tests. 3) Update the workflow to call the tool. 4) Only then proceed.
Self-Improvement Loop (Mandatory)¶
If anything fails: 1) Capture error + context (inputs, environment, logs). 2) Fix or create the tool (deterministic). 3) Add or update tests so it never regresses. 4) Update the workflow SOP with the lesson. 5) Resume.
Filesystem Rules¶
.tmp/is disposable scratch space.outputs/is for kept artifacts/results..envstores secrets and must never be committed.
Strategy Promotion Pipeline (Hard Gates)¶
A strategy/indicator must move through these stages:
1) Spec - File: research/reports/STRAT__<name>__spec.md - Must include hypothesis, rules, costs assumptions, validation plan, failure modes, kill-switch.
2) Backtest - Must include realistic costs + slippage assumptions per asset class. - Must include walk-forward + out-of-sample protocol.
3) Audit - File: docs/audits/STRAT__<name>__audit.md - Verdict must be PASS or PASS-WITH-FIXES before prototype implementation is "promoted".
4) Paper - Run in paper mode with monitoring and incident rules. - Validate alert integrity (no repaint) and execution realism.
5) Live (Small) - Small size only. Strict kill-switch triggers. - Monitor drift/decay and execution quality.
6) Scale - Only after stable live performance and no policy violations.
Definition of "Done"¶
A strategy is only "done" when: - Spec exists - Audit exists - Backtest evidence exists - Paper validation evidence exists - Risk policy alignment is confirmed