Skip to content

I1308 — The executable's share is one capability, shaped like continuity

Add one capability to majordomus-cli that reads the store and reports what is declared, what is synced, how fresh each workspace is and at what support level — served, never published, with no site or documentation projection.

BLOCKED wave 3 · p1 · deep-work profile · parallel safe

Part of external-workspaces — An external workspace is read the way this repository reads anything else, and its content never becomes public by accident.

Blocked. This issue cannot start until I1303 is done. The status is derived from that, not declared.

Objective

Add one capability to majordomus-cli that reads the store and reports what is declared, what is synced, how fresh each workspace is and at what support level — served, never published, with no site or documentation projection.

Why

The only precedent for local state reaching a capability is continuity: a hand-written reader over a hardcoded state directory, exposed as exactly one resource that is served and never published. That is the shape, and its restraint is the point — a corpus of private conversation must not acquire a public projection because the machinery made one cheap.

Current state

No capability reads .ai/local/workspaces/. continuity reads .ai/local/state/ and is the model to follow.

Desired state

One capability lists workspaces with declaration, sync freshness, record counts, support levels and the last checkpoint. It appears on the command line, HTTP and MCP as any capability does, and in no generated document, no site data and no public projection.

Scope

  • apps/majordomus-cli/src/capability/builtin
  • docs
  • test/cases

Out of scope

  • Any new dependency in majordomus-cli; ADR 0025 forbids it and I1309 gates it
  • Any site, docs/generated or public projection of workspace content
  • Serving conversation bodies over HTTP before a person has decided that is wanted

Dependencies

What waits on this

Acceptance criteria

  • The capability is declared once and reaches CLI, HTTP and MCP through the existing registry with no second registration
  • No generated document, site dataset or published projection carries workspace content
  • A missing store is reported as absent, not as an empty success
  • majordomus-cli gains no dependency

Validation

  • cargo test --workspace --all-features
  • majordomus generate --check
  • bash test/run.sh

Evidence required

  • one_declaration
  • not_published
  • absence_honest
  • no_new_dependency

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

The registry makes surfaces cheap, which is exactly the hazard here. The default for this capability is the narrowest exposure that answers the question, and widening it is a separate decision.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I1308.yaml. Read it back with majordomus plan show I1308.