canary-harnesslisted

Updated: 2026-07-24 08:40 CEST ## Contract Use the typed `canary` MCP tools for read-only brief, account, positions, rulebook, named-symbol technical, proposal, opportunity, settings, trading, health, and order-status/history work. Use `canary ... --json` when MCP is unavailable, a CLI-only policy/reconciliation diagnostic is required, or the project needs an exact reproducible CLI artifact. The MCP surface cannot place, modify, cancel, exercise, liquidate, or transmit. An explicit current-turn broker-write request uses only the agent-origin gated CLI; trading readiness, route/account/client pins, preview tokens, broker WhatIf/eligibility, freeze state, journaling, and daemon authorization remain binding. A minted preview token is not submit authority. Settings/freeze changes, policy/reconciliation governance writes, and destructive daemon maintenance remain human-only. Preserve typed evidence exactly: nil is unavailable rather than zero; report live/delayed/frozen data, freshness, stale reasons, session context, source health, and warning details when material. Local order history is intent and lifecycle evidence, not an IBKR statement or complete broker audit. ## Canonical References This is only the repo-development safety overlay. Detailed command selection, schemas, and domain authority stay in: - [command catalog](../../../skills/canary/SKILL.md) - [Rulebook design and authority](../../../internal-docs/design/trading-rulebook.md) ## Project Workflow Read the ro