/method/workspace-memory-index

Workspace Memory Index

The public comparator

Workspace Memory Index is the public-safe name for a governed project-memory posture. The contrast is simple: consumer memory stores what the agent says. GARP stores what the substrate admits.

This GARPedia page explains that contrast for readers. It does not display private workspace memory, it does not query a registry, and it does not stand in for the operator cockpit. It is an explainer for the boundary, not the boundary itself.

Why this exists

Many project-memory tools treat the agent's remembered notes, summaries, and workspace hints as if they were enough to guide the next action. GARP keeps that useful user experience separate from institutional record posture. A memory-like pointer can be useful to the operator, but it is not an admitted record merely because it was remembered.

The Workspace Memory Index stack creates a refs-only map of project memory posture: which workspace is being discussed, whether its registry confirmation is available, which typed document-directory pointers are in view, which policy rules constrain writes, and which blockers or refusal references make the path dormant until a named condition changes.

Owner split

The stack is intentionally split across repos so no public page, operator cockpit, local endpoint, or adapter becomes the whole authority.

garp-sdk owns the canonical portable Workspace Memory Index contract.
garp-local owns the read-only local producer and the GET /workbench/workspace-memory-index read model.
garp-workbench owns the read-only operator cockpit. The cockpit distinguishes live read-model data from synthetic preview posture.
garp-ops owns the advisory cross-plane contract that records the seam and prevents future lanes from reassigning ownership by accident.
arcs-amnesiac owns the ShadowGraph/refusal consumer adapter: a projection of refusal refs, blockers, and dormant reopening conditions. It does not own the Workspace Memory Index contract.
garpedia_org owns this public explanation. It explains the posture; it does not render private workspace memory.

What the index can point at

A Workspace Memory Index is a pointer surface, not a source-text surface. The document directory is a table of typed refs and purposes. It can describe why a pointer exists and what it may be used for, but it does not publish private source text on this public method page.

Workspace identity and sovereignty class.
Registry confirmation posture.
Document Directory entries as typed pointers.
Write rules as policy renderings, not public write authority.
Capability flags as posture, not permission grants.
Blocker codes, refusal refs, and dormant reopening conditions.

Durable non-claims

These non-claims hold on this public surface and across the current stack.

Workspace Memory Index is not admission.
Workspace Memory Index does not verify model output.
Workspace Memory Index does not mutate a registry.
Workspace Memory Index does not admit source text.
Workspace Memory Index does not create records.
Workspace Memory Index does not authorize publication.
GARPedia is not the source of truth.
This page does not render private workspace memory.

Dormant paths and reopening conditions

The most important thing to remember about a blocked memory path is not merely that it was blocked. The important part is the reopening condition: what would make the dormant path worth revisiting.

The arcs-amnesiac adapter projects refusal refs, blocker codes, and capability failures into ShadowGraph-compatible records with dormant conditions such as registry confirmed, a new admission decision ref, a fresh external-memory snapshot, or operator review resolution. Those conditions are not automatic reopening. They are a receipt-bearing reason to know when a path deserves another look.