Atlas reshapes the register and proposes catalog writes — applied in the browser, confirm-first, no fabrication

What a counsel sees

• set_view On the Documents Register, the counsel types “group these by status and show only evidence.” Atlas replies, and the already-loaded list regroups and slices in place — no spinner, no refetch, no fabricated rows.
• propose_operation The counsel says “create a forum called NCLT-Mumbai.” Atlas renders a confirm card (“Create forum NCLT-Mumbai?”). Nothing is written until the counsel taps Confirm; then the forum is created and the list cache refreshes. Cancel writes nothing.
• delete → archive The counsel asks to delete a matter type. The brain refuses and offers archive instead; the app renders the archive proposal. There is no delete control, ever (D-10).
• graceful refusal A reshape by a field that does not exist on the surface is refused with a toast — the view is left untouched, nothing crashes (UAT-020).

The wire contract (consumed, not redefined)

On the dock-chat turn (atlas-dock-turn-v1), two new terminal fields, null on a plain turn:

view_intent      = {"kind":"set_view","edits":[{"op":"set_group_by","field":"status","value":null,"mode":null}]}
propose_operation = {"kind":"propose_operation","operation":"create","entity":"forum",
                     "params":{"name":"NCLT-Mumbai"},"confirm_prompt":"Create forum NCLT-Mumbai?"}

op ∈ set_group_by · set_slice_by · set_primary_sort · set_field_sum · toggle_hierarchy · toggle_field — the exact verbs of the shipped view-edits.ts. operation ∈ create | edit | archive; delete is unrepresentable by design.

How set_view applies (Transport C — client-side)

view_fields — grounding the no-invented-field guarantee

The Documents Register publishes its reshapeable column/axis set as the surface’s view_fields ({key,label}), which rides into the Dock’s current_context each turn (cpc-store → buildCurrentPageContext). Without it the brain offers no reshape and refuses; with it, it can only name fields that exist.

How propose_operation applies (confirm-first write)

delete is unrepresentable (D-10)

The operation union admits only create | edit | archive, and the executor registry has no delete path. Forums archive resolves to null too (the backend exposes only forum delete, which is unrepresentable) — so the app refuses gracefully rather than rendering a destructive control. The brain offers archive; the app applies archive.

Acceptance criteria → evidence

What is not in this Story

• edit has no UAT path this Story — it resolves to null (graceful refusal) and is left to a follow-up.
• End-to-end demo needs the staging brain deploy emitting the two terminal fields; the app side is wired and unit-proven now.
• No Dock .feature scenario for forums create/archive exists in this repo to wire (the referenced @pending-until-Atlas scenario is not present here).