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
derived-data-integrity
A committed derivation describes something it can be a projection of
1issuesdevtask.milestone
0readydevtask.milestone
0blockeddevtask.milestone
0activedevtask.milestone
1completedevtask.milestone
The milestone
devtask.milestone- Title
- A committed derivation describes something it can be a projection of
- Outcome
- A committed derived artifact is a projection of inputs the commit owns. Landing an unrelated change on the trunk does not invalidate it, a fixture whose object database has no history can still evaluate it, and the staleness refusal exists on the path merges actually take - so the first thing that says no is a check rather than the published site.
- Status
- VERIFY
- Rank
0- Depends on
- unknown: the record declares no `depends_on`
- Waiting on
- none
- Holds back
- none
- Record
.ai/repo/project/milestones/derived-data-integrity.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 | I1409 | Derived data stops hashing inputs it cannot control | 0 | p1 | — | 0 |
Findings
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | milestone_evidence_missing | derived-data-integrity: every issue is DONE but milestone evidence is missing for derivation_survives_an_unrelated_merge,fixture_without_history_evaluates; status stays VERIFY | majordomus plan validate |