Flight Deck — surviving your own context window

An agent's memory of what it is doing is the first casualty of a long session. Tool output scrolls away, context gets summarized, and what remains is a plausible narrative with the operational details sanded off. The work keeps running; the agent's model of it quietly goes stale. Then it re-runs a paid job it already ran, reports a number from memory, or forgets that something is blocked.

The fix is not a better memory. It is writing state down where it cannot be summarized.

The flight deck is STATUS.md, LOG.md and the owner's page. In any session where the Artifact tool exists, build the page in the first pass as an artifact with a database (capabilities: {db: {}}) from assets/owner-page.html, following references/owner-page.md; use OWNER.md only when the tool does not exist. A test run, or a run with nothing for the owner to decide yet, still builds the page: it carries the status too, and a test is where the page gets exercised.

The two files (per area, not per repo)

STATUS.md — the instrument panel. Rewritten in place. Only ever describes NOW.