Skip to content

Your files

You instruct the desks with plain Markdown files. The desks read them at every turn, and they can never change them: they can only propose a new version, which you accept or reject on the Files page.

File Where What it says
Agents.md workspace/shared/ How every desk should work: its tools, its habits, what it may and may not do
User.md workspace/shared/ Who you are: your capital, your risk appetite, your markets, your schedule and what you want reported
TradingRules.md workspace/shared/ The strategies, and the hard limits the risk engine enforces
Persona.md workspace/desks/<desk>/ One desk's style, holding period, products and cadence
Your files become the prompt The prompt builder reads your files into each model session; desks can only propose changes to them. Your files tracked in git, edited only by you Agents.md User.md TradingRules.md Persona.md plus the desk's own Memory.md limits as % of the live balance Prompt builder reads the files before every turn 20,000 characters a file, 60,000 in all adds the first-run interview while User.md is still a template fingerprint: 16 hex digits Gemma and Qwen loops the system prompt is simply replaced every turn Claude session a resumed session ignores a new prompt, so changed files arrive inside the next message, once Desk /status /model /new /pause answered by code, no model every message starts with [India time ยท woken by] proposals/ propose_file_change the complete new file and a reason; nothing changes yet You proposals accept <id> read every turn you review the diff, then accept or reject; the old file is kept your files becoming the instructions a desk's suggested change, through you The desk can read your files every turn but can only change them by asking you.
Your files flow into each desk's instructions through the prompt builder, for the local models and for Claude alike. The blue dot is a desk proposing a change, which waits in proposals/ until you decide.

The prompt builder caps each file at 20,000 characters and all of them together at 60,000, so a long file cannot crowd out the conversation.

Proposals

When a desk thinks one of your files should change, it calls propose_file_change with the complete new text and its reason. The proposal appears on the Files page with a coloured diff, and on the command line:

bin/trading-agent proposals list
bin/trading-agent proposals accept <id>

Accepting a proposal for TradingRules.md is checked like any edit: if the risk engine could not read the new limits, nothing is saved.

The desks' own files

Each desk may write only inside its own memory/, notes/ and scratch/ folders, and its own Memory.md and skills. It writes one to three notes after a turn in which it learned something, and at each day's rollover it folds the day's notes into Memory.md. You can read and correct Memory.md on the Files page; a checkpoint is taken first.