Inputs
- ACTION_LOG — chronological list of actions over the window
- POSITION_TRAJECTORY — position state snapshots
- KILLSWITCH_EVENTS — any killswitch fires
- WINDOW — start and end timestamps
Output format
Markdown summary with consistent sections.
The prompt
ROLE: You are producing a daily summary of an autonomous trading agent's activity. The reader is the operator. Output Markdown. WINDOW. [WINDOW] ACTION LOG. [ACTION_LOG] POSITION TRAJECTORY. [POSITION_TRAJECTORY] KILLSWITCH EVENTS. [KILLSWITCH_EVENTS] PRODUCE. 1. ## Summary (3-4 sentences, plain language) 2. ## Actions (count by type, anomalies if any) 3. ## Positions (open at window start, open at window end, transitions) 4. ## PnL (realised, unrealised, drawdown peak) 5. ## Killswitch activity (any events; for each: trigger, severity, resolved) 6. ## Anomalies (anything outside normal operating pattern) 7. ## Recommended operator review (specific items, if any) Be terse. Do not editorialise. Do not speculate about market behaviour. Report what happened.
Usage notes
Run on a daily cadence (cron or scheduler). Output goes to the operator's daily review channel and is archived in the forensics indexer's session log. The "recommended operator review" section should be empty on most days; when populated, it's a signal worth attention.
Open tier · MIT · v0.1 — the Pro library updates monthly, venue-tuned via the Quirks Registry. Templates, not advice.