I3100 — What the ChatGPT project decided is promoted into the layer, each record naming the conversation and message it came from
Read every conversation of the declared workspace chatgpt-majordomus once, extract what the owner ordered, decided and learned, verify each candidate against master and the peer board, and promote what is not yet recorded as intents, milestones, issues, proposed ADRs and curated knowledge, each record citing its sources as chatgpt-majordomus:<conversation>#<message> so it drills back to its root; raw content stays in the git-ignored workspace store.
READY wave 0 · p1 · deep-work profile · runs alone
Ready. Every dependency is done, so majordomus plan start I3100 will be accepted.
Objective
Read every conversation of the declared workspace chatgpt-majordomus once, extract what the owner ordered, decided and learned, verify each candidate against master and the peer board, and promote what is not yet recorded as intents, milestones, issues, proposed ADRs and curated knowledge, each record citing its sources as chatgpt-majordomus:<conversation>#<message> so it drills back to its root; raw content stays in the git-ignored workspace store.
Why
On 2026-10-18 the owner asked that every conversation of the ChatGPT Project Majordomus (297 of them, 2026-09-06 to 2026-10-18) be assembled into .ai/ so the work they decided can be run the IDD way from the UI. Until now nothing read the project: its decisions were carried into the repository only when a session happened to paste one, and one such paste sits untracked as an intent whose statement is a raw ChatGPT answer.
Current state
The workspace is declared (I1301); no capability or command reads it; promoted records exist only where sessions copied text by hand.
Desired state
Each decision, intent, work item and lesson of the project is accounted for once: promoted with its sources, found already recorded (with the record it maps to), superseded, left as an open question, or dropped as off-topic. The promoted records validate (plan, intent, adr and knowledge checks) and appear on /ui/idd, /ui/roadmap and the ADR and knowledge pages with no other edit.
Scope
- .ai/repo/project/intents
- .ai/repo/project/milestones
- .ai/repo/project/issues
- .ai/repo/project/critiques
- .ai/repo/adrs
- .ai/repo/knowledge/curated
Out of scope
- Raw conversation content in any tracked file
- The sync command, store layout and read capability of I1303-I1308
- Accepting an ADR: the records are proposed and the owner accepts them
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- Every conversation of the project is accounted for in a coverage ledger: promoted, already recorded, superseded, open question or off-topic
- Every promoted record names at least one source conversation and message
- majordomus plan validate, majordomus intent validate, majordomus adr check and majordomus knowledge check pass on the branch
- No tracked file carries raw conversation text, a credential or third-party personal data
Validation
- majordomus plan validate
- majordomus intent validate
- majordomus adr check
- majordomus knowledge check
Evidence required
- plan_validate
- intent_validate
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
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/I3100.yaml. Read it back with majordomus plan show I3100.