coulomb/the-custodian
5
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Clarify fleet cleanliness boundary and preserved evidence
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Reject generated-only commits / generated-commit-guard (push) Successful in 10s
Details

Browse source
This commit is contained in:
codex 2026-10-19 13:35:32 +02:00
parent b2effc84d7
commit 392ab7f0d8
1 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/CUST-WP-0079-deterministic-security-flow.md
View file

@ -304,7 +304,9 @@ shared generated-only rejection and existing exact-scope secret scans remained
in force. No native runtime, credentials, public policy or schedule activation
was performed by this adoption.
Current provider source revisions at clean-checkout verification:
All 25 provider checkouts were clean at verification (3 earlier adopters, 11
security-fleet adoptions, 4 isolation providers and 7 sizing providers). Current
source revisions:
| Repository | Commit |
| --- | --- |
@ -385,3 +387,9 @@ execution remain to be implemented/verified without changing authored source
inventory dispositions. T03, T04 and T06 retain their independent schedule,
publication and attended acceptance gates. No new owner acceptance is inferred
from clean checkouts or the earlier clean seven-day Git window.
State Hub's five older metric snapshots remain intentionally dirty after owner
review; they were not included in the 25 clean provider claim. Custodian's
inherited NetKingdom assessment receipts also remain outside these owner cleanup
commits. Neither source adoption nor clean provider worktrees authorizes deleting
unrelated observations.