- Decision
- ADR-044
- Date
- 2026-08-23
- Status
- SupersededSuperseded by ADR-240. Accepted
- Mentions
- ADR-019, ADR-035, ADR-240
- Mentioned by
- ADR-240
1Decision
Record closure of ADR-035/036's flagged vendor/aegisos/guardian source-durability gap: the tree on the build server is git-tracked, with a real, active commit history.
2Why and evidence
This plan's Task 9 (docs/superpowers/plans/2026-08-23-session-hygiene-and-serena-fix.md) was written to investigate and, if needed, fix this gap on a read-only-first, human-approval-gated basis.
A read-only check ([ -d .../vendor/aegisos/guardian/.git ]) found git already initialized, working tree clean, 19 commits deep from baseline commit afeb157 ("Baseline: current Guardian Android app state before residuals hardening") to 91cea5c, on branch master — matching the Guardian residuals-hardening and visual-identity work already reflected elsewhere in this project's records.
The gap was closed in an earlier working session that never recorded it here; no state-changing action was taken by this task, only a read-only confirmation, so Task 9's proposal-and-approval step and Task 10's execution step were both unnecessary and were not run.
3Consequences
Future Guardian source changes on the build server should continue as real commits in this tree, matching the practice already established for frameworks/base's boot-identity patch (ADR-019/035).
4Review when
If a future audit finds vendor/aegisos/guardian un-tracked or in an inconsistent git state again, treat it as a regression worth investigating (e.g. an accidental .git deletion), not a repeat of the original gap.
Read from docs/governance/decision-log.md, entry ADR-044.