what-a-workspace-decides-reaches-the-repository-with-its-source — What the owner decides in a vendor workspace reaches the repository, and every promoted record opens the message it came from
The owner thinks aloud in the ChatGPT project. What the owner decides there is read into this checkout's own store, promoted by a person into intents, ADRs, milestones, issues and knowledge, and every promoted record names the conversation and message it came from, so that from the UI one click opens that message for the operator who holds the store, while the public repository and site carry only the reference.
BLOCKED 0 of 2 issues done
- ready
- 0
- blocked
- 2
- active
- 0
- verify
- 0
- done
- 0
- cancelled
- 0
Problem
The owner thinks aloud in the ChatGPT project. What the owner decides there is read into this checkout's own store, promoted by a person into intents, ADRs, milestones, issues and knowledge, and every promoted record names the conversation and message it came from, so that from the UI one click opens that message for the operator who holds the store, while the public repository and site carry only the reference. Proposed in ADR 0212 (A workspace is read in the operator's own signed-in browser or from the vendor's export, never through a launched automation profile or another tool's credential) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c239#0, chatgpt-majordomus:c239#9, chatgpt-majordomus:c267#0.
Outcome
The owner thinks aloud in the ChatGPT project. What the owner decides there is read into this checkout's own store, promoted by a person into intents, ADRs, milestones, issues and knowledge, and every promoted record names the conversation and message it came from, so that from the UI one click opens that message for the operator who holds the store, while the public repository and site carry only the reference.
Current state
Its issues extend existing milestones; see each issue's why.
Desired state
Every criterion of the intent is carried by an issue here and proven by its test.
Acceptance criteria
- majordomus workspaces reports chatgpt-majordomus as synced, with the checkpoint age, conversation and message counts and support level, from .ai/local/workspaces/chatgpt-majordomus/
- A plan, ADR or knowledge record whose provenance names workspace:<id>/<conversation>#<message> validates in a clone with no store, and an unknown workspace id is refused
- On /ui a promoted record's workspace reference opens the cited message for a loopback caller when the store holds it, reads 'not held in this checkout' when it does not, and a caller beyond loopback never receives message text
- The published snapshot and the site build contain no message text or title from the store, and a gate fails when one does
- No record promoted by the 2026-10-18 import still cites a positional message index, in typed provenance or in prose
- A vendor caller, authenticated as an ADR amending ADR 0126 defines, reads plan records through a listener of its own and is refused every repository_mutation capability and all workspace message text
- An intent proposed from a workspace lands as a proposed intent whose provenance is its workspace reference, and nothing is recorded as accepted until a person accepts it
Validation
- majordomus plan validate
Issues
Each one is an execution contract with its own acceptance criteria, validation command and required evidence. The wave column is the layer of the dependency graph it sits in.
| issue | status | wave | depends on | title |
|---|---|---|---|---|
| I3278 | BLOCKED | 5 | I1302, I1303, I1305, I1306, I1308 | The 2026-10-18 import is the workspace store's first sync, not a scratchpad |
| I3279 | BLOCKED | 4 | I1302, I1305 | The vendor's own data export is a transport, and it carries the message identities an in-page read did not keep |
The graph
flowchart LR
I3278["I3278<br/>The 2026-10-18 import is the workspace store's first sync, not a scratchpad"]:::blocked
I3279["I3279<br/>The vendor's own data export is a transport, and it carries the message identities an in-page read did not keep"]:::blocked
classDef done stroke:#16a34a,fill:#dcfce7,color:#14532d,stroke-width:2px
classDef active stroke:#2563eb,fill:#eff6ff,color:#1e3a8a,stroke-width:2px
classDef verify stroke:#7c3aed,fill:#f5f3ff,color:#4c1d95,stroke-width:2px
classDef ready stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
classDef planned stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
classDef blocked stroke:#b45309,fill:#fffbeb,color:#78350f,stroke-width:2px
classDef cancelled stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2px
classDef superseded stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2pxCanonical record: .ai/repo/project/milestones/what-a-workspace-decides-reaches-the-repository-with-its-source.yaml. Read it back with majordomus plan show what-a-workspace-decides-reaches-the-repository-with-its-source.