Page context

The Context panel on a published Page keeps a shared brief right on the Page: what it is for, who it is for, what has already been decided or rejected, and what questions remain open. Reviewers see the reasoning behind the work, and connected agents and Turner read the same brief before making changes.

Open Context

On a published Page, click Page settings in the toolbar and choose Context. A dialog titled Context opens with the Page title underneath; close it with the Close Context button.

Context is only on the live published Page. It does not appear in the Pages library menu, on locked Pages, or when you view an older version in read-only mode.

What it holds

The panel starts with who last updated the brief and when, then shows up to seven sections in this order. Empty sections stay hidden.

• Purpose and Audience state what the Page is for, who asked for it, and who reads it. When Turner designs a Page that has no brief yet, these two are filled in from the design brief.
• Decisions, Rejected, and Open questions are logs that grow as the work goes on, from agents when they publish and from editors in the panel. Each entry ends with its author and date. A resolved question stays in the list, struck through and marked with who resolved it. When every question is resolved, the section reads None open.
• Sources and Notes hold files, links, or data the Page draws on, plus any extra background.

Edit it

If you can edit the Page, click Edit beside the update line (or Add context when the panel says No context yet. Add what this Page is for and what was decided.).

Fill in Purpose, Audience, Sources, one per line, or Notes. Under Decisions, Rejected, and Open questions, click Add to add a row or Remove to delete one. In Open questions, use Resolve or Reopen to change a question's state. Entries you leave alone keep their original author and date.

Click Save (or Cancel to discard your edits). A brief cannot be saved completely empty; keep at least one field. If someone else saves while you have the editor open, click Reload to load their version before editing again.

Every change to the brief appears in Version history as Context updated, listing which sections changed.

Who can see it

Signed-in people with Commenter or Editor access to the Page can open and read Context. Only people with Editor access (including the owner) can edit it. Signed-out visitors and people with Viewer access cannot see the brief. See Sharing and visibility for how Page roles work.

How agents fill it in

Connected agents read the current brief with read_page (which returns context, including revision and updated_by) and write to it through the optional context argument on create_page and update_page. Both tools return the new context_revision.

• State fields replace their value when sent, and an empty value clears them: purpose, audience, sources, notes.
• Log fields are append-only for agents: decisions, rejected, open_questions. Duplicate entries are ignored, and each new entry is stamped with the author, date, and Page version.
• resolve_open_questions closes questions by entry id or exact text.
• base_revision is required whenever an existing brief has a state field changed or a question resolved.

The brief is checked before the Page version is published. If base_revision is missing or stale, the call fails with context_base_revision_required or context_conflict and nothing is published. See Publishing flow and MCP reference for the full publish sequence.

How Turner uses it

When Turner revises a Page, it loads the latest Context brief at the start of the run, so edits you save in the panel apply on the next revision.

Turner reads the brief as the owner's stated intent. It is told not to contradict a recorded decision or bring back a rejected option without saying so in its reply, and to name any open question a request touches. The brief is guidance, not a rule Turner is forced to follow, so check the result. Turner never writes to Context itself.