Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I1308

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

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
external-workspaces
Milestone status
ACTIVE
Wave
3
Waiting on
I1303
Holds back
I1309I1310
Behind it in all
2
Evidence
0 of 4
In the waySubjectDetail
issueI1303I1303 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1308

majordomus plan verify I1308

majordomus plan done I1308

What it is

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.
Now
No capability reads .ai/local/workspaces/. continuity reads .ai/local/state/ and is the model to follow.
Wanted
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.
Done when
unknown: the record declares no `completion`
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.

Acceptance

  • 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-featuresmajordomus generate --checkbash test/run.sh
Evidence required
one_declarationnot_publishedabsence_honestno_new_dependency
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/capability/builtindocstest/cases
Not
Any new dependency in majordomus-cli; ADR 0025 forbids it and I1309 gates itAny site, docs/generated or public projection of workspace contentServing conversation bodies over HTTP before a person has decided that is wanted
Depends on
I1303
Priority
p1
Profile
deep-work
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-09
Updated
2026-09-09
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.