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

I1310

The subsystem is documented where a person looks, and the plan is closed against the repository

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
external-workspaces
Milestone status
ACTIVE
Wave
5
Waiting on
I1308I1309
Holds back
none
Behind it in all
0
Evidence
0 of 4
In the waySubjectDetail
issueI1308I1308 is not DONE
issueI1309I1309 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 I1310

majordomus plan verify I1310

majordomus plan done I1310

What it is

Objective
Write docs/WORKSPACES.md, add the row to the documentation index, and re-audit the repository against this milestone: what was reinvented, what legacy duplication survives, and which of the pack's phases turned out not to apply here.
Why
The pack this milestone came from assumes surfaces that the audit showed are unreachable for local content, and a later worker reading the pack rather than this milestone would rebuild that assumption. The documentation is where that is settled for whoever comes next.
Now
ADR 0025 records the decision and its withdrawal of two earlier positions. Nothing in docs/ describes the subsystem.
Wanted
docs/WORKSPACES.md states what a workspace is, how it differs from a provider, the transport policy and its honesty about acquisition mode, the store and its boundary, what is deliberately not published, and how a second vendor is added. The index row exists; the site renders it; the re-audit is recorded.
Done when
unknown: the record declares no `completion`
Risk
Documentation written from the plan rather than from the built subsystem. It is written last for that reason.

Acceptance

  • docs/WORKSPACES.md exists, is linked from the documentation index, and renders on the site
  • The document states the distinction from ADR 0024's provider in its own words, so that a reader who never opens the ADR does not conflate them
  • The re-audit names every place a second implementation of an existing mechanism was avoided, and every place one survives
  • ADR 0025 is accepted or amended by a person, and its status reflects what was actually built
Validation
bash test/run.shmajordomus generate --check
Evidence required
documentedindexedreauditedadr_settled
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docs.ai/repo/adrs
Not
Documenting a capability that does not exist yet
Depends on
I1308I1309
Priority
p2
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.