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
work-graph-github
The projection to GitHub is gated, identified and traversable, and a merged pull request leads back to the outcome it served
10issuesdevtask.milestone
0readydevtask.milestone
0blockeddevtask.milestone
0activedevtask.milestone
10completedevtask.milestone
The milestone
devtask.milestone- Title
- The projection to GitHub is gated, identified and traversable, and a merged pull request leads back to the outcome it served
- Outcome
- The projection cannot rot silently: a gate runs the drift check on every change that can move the model or the adapter, and drift is a CI failure with the record named. Identity travels with the record rather than being parsed out of its title, so renaming a GitHub title moves nothing and creates no duplicate, and the remote can be a fixture, so which record is which is provable with no network. The reconciliation vocabulary distinguishes the states it currently conflates, so `missing` no longer stands for both a record never created and a record a person deleted, and a remote edit is reported as a remote edit. Above the projection, a pull request names the issue it realises and the edge is derived from git and GitHub rather than remembered, so a merged commit leads back to the acceptance criteria it satisfied and an outcome leads forward to the evidence that it holds. The derivations the shell already computes — ready, blocked, waves, next, status — are readable through the same capability surface as every other thing this repository knows, rather than only from a terminal.
- Status
- VERIFY
- Rank
0- Depends on
- none
- Waiting on
- none
- Holds back
- none
- Record
.ai/repo/project/milestones/work-graph-github.yaml- Its issues
- Every issue of this milestone
Where the work is
- Ready
- —
- Blocked
- —
- Waiting
- —
- Active
- —
- In review
- —
- Completion blocked
- —
- Complete
- Cancelled
- —
What holds the most back
No unfinished issue holds another back.
What may run at the same time
Nothing here can be started now.
Every issue
| Readiness | Status | Issue | Title | Wave | Priority | Waiting on | Holds back |
|---|---|---|---|---|---|---|---|
| complete | DONE | I1401 | The identity of a projected record is what the record carries, not what its title says | 0 | p0 | — | 6 |
| complete | DONE | I1402 | A finding says which of six states it found, and the state that could hide a person's edit is no longer one of them | 1 | p1 | — | 4 |
| complete | DONE | I1403 | Backfill the projection once, deliberately, and record what it created | 3 | p0 | — | 0 |
| complete | DONE | I1404 | The drift check is a gate, so a projection that stops being applied cannot stay silent | 2 | p0 | — | 3 |
| complete | DONE | I1405 | A pull request names the issue it realises, and the edge is derived rather than remembered | 1 | p1 | — | 1 |
| complete | DONE | I1406 | The plan's derivations are capabilities, so every surface reads the readiness the terminal reads | 0 | p1 | — | 1 |
| complete | DONE | I1407 | One issue travels the whole path and back, as an executable case | 3 | p1 | — | 0 |
| complete | DONE | I1408 | The documents stop claiming a projection nobody runs | 3 | p2 | — | 0 |
| complete | DONE | I1516 | The adapter composes a projected body in one place | 0 | p0 | — | 0 |
| complete | DONE | I2300 | A head is judged against what it changes, not against GitHub's live state | 0 | p1 | — | 0 |
Findings
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | milestone_evidence_missing | work-graph-github: every issue is DONE but milestone evidence is missing for drift_gated,identity_stable,offline_provable,traceability_both_ways; status stays VERIFY | majordomus plan validate |