Latchboard an un_Fragged_ WebMCP experiment
creating isolated demo session…

WORKSTREAM DELEGATION · NATIVE WEBMCP

Delegate the outcome.
Keep control of the boundary.

The agent can read the context it needs, propose work only inside the delegated lane, and commit nothing on its own. If the work changes underneath it, stale intent stops being eligible.

Connecting…
CAN SEERelevant board context
CAN PROPOSEDelegated workstream only
CANNOTCommit canonical state

CANONICAL BOARD

Release desk

illustrative · seeded demo data

REVIEW TRAY

No proposals waiting

agent work stays proposed until reviewed
Delegate the release workstream, then ask the agent to propose a batch.

90-SECOND JUDGE PATH

One outcome. Three proof moments.

  1. Engage the latch on Release 0.4 blockers. Watch the proposal capability appear.
  2. Ask the agent to read context and prepare three proposals. While it reasons, click “Mark key rotated” on the API-key task.
  3. Review the tray. Fresh work can commit; the old API-key proposal is visibly stale. End delegation and the proposal capability disappears.

No signup. No API key. Separate judge sessions. The human-side board remains usable even if this browser does not expose WebMCP.