Orders (Standing orders)
Standing orders are prose the model reads with every decision — how to weigh the report’s evidence in words.
Nothing written here is enforced. A hard rule belongs in Signal rules, Conditions, or the other Policy axes. Standing orders shape judgment; they do not replace gates, levels, or exits.
| Field | Bound |
|---|---|
| Strategy field | marketReadText |
| Cap | 2,000 characters |
| Empty prose | Allowed — no Standing Orders text is fine |
What it is for
- Priorities among report sections (“prefer structure over short-horizon RSI noise”)
- How to treat crowded or conflicting evidence
- Coin- or regime-flavored reminders that should travel with every call
It is not for: numeric thresholds you need enforced, must-fire lists, stop geometry, or entry timing.
Markers
Prose may embed {tokens} that resolve at decision time. The insertable token list is server-served — do not invent forms.
Syntax
| Form | When |
|---|---|
{header} | Bare header — only when that header is unique across the whole report |
{sectionKey.header} | Section-qualified — when the same header appears in more than one section, or when the bare header collides with a condition key |
Examples (illustrative):
Size only when {vol24hUsd} clears the desk floor.
If {SQUEEZE_ON} is true, wait for {custom.pctB} to release.
Sources
| Source | Meaning |
|---|---|
| Report columns | Each output’s markerToken from Metrics |
| Conditions | This strategy’s own keys — when referenceable |
Unreferenceable condition keys
If a condition key is also a report header, there is no legal marker form:
- Bare
{KEY}is ambiguous (condition vs column) → rejected - Qualified
{section.KEY}selects the column, not the condition
Those keys stay listed in the vocabulary as disabled with a served reason until you rename the condition (or the column). Only the server decides which keys are unreferenceable.
Resolution statuses
Each {…} span resolves as: column · condition · unknown · ambiguous · collision. Ambiguous / collision entries carry the exact qualified forms to use. Unknown markers fail authoring — they do not silently survive to runtime.
Preview lens
Marker values in the trade register resolve against an optional lens ticker you name. The server never picks a cohort coin for you. Without a lens, you still get names (grid register); values wait until a coin is chosen.
Ownership
| Layer | Role |
|---|---|
| Strategy | Authors Standing Orders with the rest of the playbook |
| Agent | Receives the materialized prose on bind / propagation |
| Model | Reads it beside the rendered report and condition outcomes |
← Metrics · Conditions · Signal rules