Acquire required CI evidence without unrelated check census

.agents/skills/atlas/assets/seed/records/dc8c31e3075adeb63113852569b83dcd432485621eb77fef62cf3cce5c84a214.json

@@ -0,0 +1 @@
+{"citations":[{"path":"docs/coordination/2026-10-19-board-clearing-lifecycle-design.md","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"856090ec8b4b50a177a89c307a69b7a0591796648e50529487a5f0a3ea4ddc32"},{"path":".agents/skills/work-board/SKILL.md","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"367bbcf86f45dd128fbcc09dd604b90561e8fb91699452fdfec14f321de10e98"},{"path":".agents/skills/work-board/references/lifecycle-contract.md","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"cf9144b311192bd80a2c8fd2f7b427d96103c35d6f8d6d2825d32b8407c3650d"},{"path":"src/FS.GG.Coord.GitHub/V2InspectionAcquisition.fs","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"488be6af486379844ed7437217359653506e4ce062df663721fd2055843b91be"},{"path":"scripts/board_v2_native_results.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"3e0756ff54a29960f05cd3be9d05ccb995f60dd020235538cc7c88b0d550430e"},{"path":"scripts/creator_source_qualification.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"f840c0a9b2ef88b6284d4de305471a65ce0895315b12153a8168f37ea346e512"},{"path":"scripts/release_successor_journal.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"4d0c396d0e4ec54c234d87171e38187f5343e4028c166010691478ddf5a56d37"},{"path":"scripts/new-sdd-workspace-successor-publish.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"ceeee0254c097da7971e082eea902df3167f5ce22fcc32bb7b55041cea0e5d23"},{"path":"tests/new-sdd-workspace-successor/current_dependencies.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"601a29debef7c4085fcd08a80926818937c35eeb7a0e4ec5ae7274f201e0585b"},{"path":"tests/release-effect-sealing/run.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"b16fe0e9729be5f1f9f25f7df4baa0862768a2d7e46049c7705c5b7309a20707"},{"path":".agents/skills/work-board/references/intake.md","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"af51853d3c89f465de6389a97aad5c260cf80f02a377179287bbe5d84ac6d1c8"},{"path":"scripts/NewSddWorkspace/ProductBoard.fs","repository":"FS-GG/.github","revision":"699f60851288f5f817b98856bdd3d220cf27dd09","sha256":"2dfb52e8cb5944fbf01d76f7183dadda2de00c1f524da956e8fb8548077ed196"},{"path":"scripts/NewSddWorkspace/Program.fs","repository":"FS-GG/.github","revision":"699f60851288f5f817b98856bdd3d220cf27dd09","sha256":"4a4f3012f61a484ed09d3a14d923293c32d0ae8914ebdb53cc3abbde56ba0d06"},{"path":"scripts/fsgg-skill-registry-check","repository":"FS-GG/.github","revision":"699f60851288f5f817b98856bdd3d220cf27dd09","sha256":"21e36ffd2c04a50379ea4623ca5681fbf663a2d0fd31686304becb605431e547"},{"path":"tools/v2-ci-ordinary-observe.py","repository":"FS-GG/.github","revision":"419b14a2a2e755df72e97997ccf84458782d5f63","sha256":"ff8b0f6cae46b446ae2e8e57457fd74ccfbaede6b255bbc4460bcf32d5c9c39e"},{"path":"scripts/fsgg-coord","repository":"FS-GG/.github","revision":"699f60851288f5f817b98856bdd3d220cf27dd09","sha256":"a0689f0ba8cd0180fd1ca60a63bba55e93513732b36e099c541847336ddb3ccf"}],"conflictsWith":[],"id":"github/board-clearing-lifecycle","kind":"architecture","recordedAt":"2026-10-19T19:30:40Z","repository":"FS-GG/.github","schema":"fsgg.atlas/1","status":"recorded","summary":"One unified board/process Outcome uses work-board as the continuous coordinator, pnext-item as one meaningful Delivery executor and work-roadmap as an already-selected-plan adapter. Recover the same unambiguous owner/PR/attempt, triage complete unfiltered All items including missing Status/classification/enrollment, select within actual scope/prerequisites/capacity, implement/test/review/fix/deliver, verify the whole selected promise and return to selection. Native six-field owning issues and parent/sub-issue links preserve full promises and useful decomposition; metadata and links never enroll or authorize. Outcome nodes are not implementation assignments. Source merge, publication, installed discovery/caller adoption and native acceptance are separate joins; quiescence is not whole-board completion. Retired mandatory analyst/claim/packet/presence chains and six unreachable organization renderers do not revive through compatibility entries. Retained public/product contracts and original histories remain scoped.\nDepth follows risk: trivial reversible non-governing prose/metadata uses owner validation and cheap checks; ordinary code/governing skills use one owner, one independent source review, relevant tests and final required CI. Architecture reuses its design and specialists add only distinct needed input. Sensitive effects keep exact identity, fresh admission, original custody and independent readback. Reviews converge on substantiated in-scope defects/adjudicated disputes; reject hypothetical expansion and defer independent improvements. Rerun affected checks, broadening for changed inputs/assumptions, integration/provenance uncertainty or actual required CI, preserving ADR-0084. Full-board refresh belongs at meaningful coordination boundaries; local repair loads relevant context. Existing comparable-risk delivery time, escapes, warranted findings, CI wait/reruns and recovery evidence inform sizing; missing coverage creates no new gate/store/campaign. Optional primary-source rationale supports individual practices, not controlled whole-workflow validation, state-of-the-art status or transferable savings.\nComplete-cohort readonly acquisition batches inside fresh initial/final phases with unchanged500-request/270-second invocation bounds and no selective inspection shortcut. The40-member fixture731→137actual sends preserves facts/selection, not installed efficiency. Maintained native result interpretation handles closed families, exact text/select unions and genuine custody-file readback; Observed is not authority, CAS or replay. Scope-changing rulings need verified authority, durable citation and independent issue/PR readback. Intake compares relevant prior issues plus feedback/reports; no prior issue does not prove no prior record. Searches stay bounded. All439inherited and46later original Unknowns remain distinct/unreleased; unavailable historical searches stay closed.\nCreator020 source-only qualification remains release-ineligible even with flipped flags. Its distinct release qualification and existing eight-effect publisher authenticate the first-attempt candidate source/archive and recompute exact package/dependency/output joins, reusing genuine108 dependency bytes. Complete019 attestation, older seals and013 recovery remain intact. Governing109 artifacts and Creator020 have separate actual publication/installed/native gates; source or fixture results establish none of those operational claims.\nRetained product instruction upgrades need explicit generated-preimage authority rather than blind overwrite or fresh-scaffold substitution. Current code pins the accepted immutable predecessor source/manifests, authenticates the complete820-leaf old instruction closure and selected binding/provenance identities, replaces only verified old instruction destinations, and permits absent new leaves. Existing configuration receives guards without nonmerge replacement authority. Owner edits, unexpected destinations, symlinks, identity mismatch and preview races refuse. The original whole provenance and historical42-leaf adoption remain preserved while active generated ownership can move to48; unchanged product108 binding/tool/settings and user files stay intact, rollback restores bytes/modes/mtimes and exact repeats are no-op. Actual selected retained receivers still require the public installed acceptance path, distinct from fresh creation. Qualification callers must choose current published108, historical frozen099 or source-only109 from the actual selected mode rather than inferring a wrong dependency axis.\nExplicit HTTP(S) source navigation is not a receiver-local materialization dependency; local paths on the same line still are. The registry classifier distinguishes these without inventing rows or widening payloads. Ordinary CI observation likewise collects the finite policy-required check names rather than coupling admission to every unrelated check on a commit. Each named response remains complete and bounded100; malformed counts/names, selected duplicates and missing/failed/unauthenticated producers refuse. App, workflow/job/head/attempt, latest selection, PR/source/tree/policy barriers and activation remain unchanged. This source correction requires its own actual native qualification and does not settle an earlier failed observer.\nThe workspace wrapper resolves global/PATH tooling before a local manifest. An isolated organization successor must therefore use its absolute installed path and account for automatic selector writers while qualified products retain their actual108 route; a local pin alone is insufficient isolation. Durable issue/PR and stable Atlas-ID pointers recover ownership; reports save genuine missing recovery state. Private copy/restore equality is bounded custody, never off-machine/disk-loss/restart or operation-settlement proof. Original effect readbacks and admission remain authoritative; Atlas is curated navigation, not a grant.","supersedes":["1cfd18d1b12b25604d818389a34bbaa746f450e70246c7f4242fc4e215fc46a4"],"tags":["work-board","lifecycle","intake","decomposition","retirement","recovery","batching"],"title":"One continuous board-clearing lifecycle with explicit acceptance and retirement"}

.claude/skills/atlas/assets/seed/records/dc8c31e3075adeb63113852569b83dcd432485621eb77fef62cf3cce5c84a214.json

@@ -0,0 +1 @@
+{"citations":[{"path":"docs/coordination/2026-10-19-board-clearing-lifecycle-design.md","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"856090ec8b4b50a177a89c307a69b7a0591796648e50529487a5f0a3ea4ddc32"},{"path":".agents/skills/work-board/SKILL.md","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"367bbcf86f45dd128fbcc09dd604b90561e8fb91699452fdfec14f321de10e98"},{"path":".agents/skills/work-board/references/lifecycle-contract.md","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"cf9144b311192bd80a2c8fd2f7b427d96103c35d6f8d6d2825d32b8407c3650d"},{"path":"src/FS.GG.Coord.GitHub/V2InspectionAcquisition.fs","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"488be6af486379844ed7437217359653506e4ce062df663721fd2055843b91be"},{"path":"scripts/board_v2_native_results.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"3e0756ff54a29960f05cd3be9d05ccb995f60dd020235538cc7c88b0d550430e"},{"path":"scripts/creator_source_qualification.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"f840c0a9b2ef88b6284d4de305471a65ce0895315b12153a8168f37ea346e512"},{"path":"scripts/release_successor_journal.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"4d0c396d0e4ec54c234d87171e38187f5343e4028c166010691478ddf5a56d37"},{"path":"scripts/new-sdd-workspace-successor-publish.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"ceeee0254c097da7971e082eea902df3167f5ce22fcc32bb7b55041cea0e5d23"},{"path":"tests/new-sdd-workspace-successor/current_dependencies.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"601a29debef7c4085fcd08a80926818937c35eeb7a0e4ec5ae7274f201e0585b"},{"path":"tests/release-effect-sealing/run.py","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"b16fe0e9729be5f1f9f25f7df4baa0862768a2d7e46049c7705c5b7309a20707"},{"path":".agents/skills/work-board/references/intake.md","repository":"FS-GG/.github","revision":"18636b9cd9d195a0e747ad34f47ee1a6e2e2465c","sha256":"af51853d3c89f465de6389a97aad5c260cf80f02a377179287bbe5d84ac6d1c8"},{"path":"scripts/NewSddWorkspace/ProductBoard.fs","repository":"FS-GG/.github","revision":"699f60851288f5f817b98856bdd3d220cf27dd09","sha256":"2dfb52e8cb5944fbf01d76f7183dadda2de00c1f524da956e8fb8548077ed196"},{"path":"scripts/NewSddWorkspace/Program.fs","repository":"FS-GG/.github","revision":"699f60851288f5f817b98856bdd3d220cf27dd09","sha256":"4a4f3012f61a484ed09d3a14d923293c32d0ae8914ebdb53cc3abbde56ba0d06"},{"path":"scripts/fsgg-skill-registry-check","repository":"FS-GG/.github","revision":"699f60851288f5f817b98856bdd3d220cf27dd09","sha256":"21e36ffd2c04a50379ea4623ca5681fbf663a2d0fd31686304becb605431e547"},{"path":"tools/v2-ci-ordinary-observe.py","repository":"FS-GG/.github","revision":"419b14a2a2e755df72e97997ccf84458782d5f63","sha256":"ff8b0f6cae46b446ae2e8e57457fd74ccfbaede6b255bbc4460bcf32d5c9c39e"},{"path":"scripts/fsgg-coord","repository":"FS-GG/.github","revision":"699f60851288f5f817b98856bdd3d220cf27dd09","sha256":"a0689f0ba8cd0180fd1ca60a63bba55e93513732b36e099c541847336ddb3ccf"}],"conflictsWith":[],"id":"github/board-clearing-lifecycle","kind":"architecture","recordedAt":"2026-10-19T19:30:40Z","repository":"FS-GG/.github","schema":"fsgg.atlas/1","status":"recorded","summary":"One unified board/process Outcome uses work-board as the continuous coordinator, pnext-item as one meaningful Delivery executor and work-roadmap as an already-selected-plan adapter. Recover the same unambiguous owner/PR/attempt, triage complete unfiltered All items including missing Status/classification/enrollment, select within actual scope/prerequisites/capacity, implement/test/review/fix/deliver, verify the whole selected promise and return to selection. Native six-field owning issues and parent/sub-issue links preserve full promises and useful decomposition; metadata and links never enroll or authorize. Outcome nodes are not implementation assignments. Source merge, publication, installed discovery/caller adoption and native acceptance are separate joins; quiescence is not whole-board completion. Retired mandatory analyst/claim/packet/presence chains and six unreachable organization renderers do not revive through compatibility entries. Retained public/product contracts and original histories remain scoped.\nDepth follows risk: trivial reversible non-governing prose/metadata uses owner validation and cheap checks; ordinary code/governing skills use one owner, one independent source review, relevant tests and final required CI. Architecture reuses its design and specialists add only distinct needed input. Sensitive effects keep exact identity, fresh admission, original custody and independent readback. Reviews converge on substantiated in-scope defects/adjudicated disputes; reject hypothetical expansion and defer independent improvements. Rerun affected checks, broadening for changed inputs/assumptions, integration/provenance uncertainty or actual required CI, preserving ADR-0084. Full-board refresh belongs at meaningful coordination boundaries; local repair loads relevant context. Existing comparable-risk delivery time, escapes, warranted findings, CI wait/reruns and recovery evidence inform sizing; missing coverage creates no new gate/store/campaign. Optional primary-source rationale supports individual practices, not controlled whole-workflow validation, state-of-the-art status or transferable savings.\nComplete-cohort readonly acquisition batches inside fresh initial/final phases with unchanged500-request/270-second invocation bounds and no selective inspection shortcut. The40-member fixture731→137actual sends preserves facts/selection, not installed efficiency. Maintained native result interpretation handles closed families, exact text/select unions and genuine custody-file readback; Observed is not authority, CAS or replay. Scope-changing rulings need verified authority, durable citation and independent issue/PR readback. Intake compares relevant prior issues plus feedback/reports; no prior issue does not prove no prior record. Searches stay bounded. All439inherited and46later original Unknowns remain distinct/unreleased; unavailable historical searches stay closed.\nCreator020 source-only qualification remains release-ineligible even with flipped flags. Its distinct release qualification and existing eight-effect publisher authenticate the first-attempt candidate source/archive and recompute exact package/dependency/output joins, reusing genuine108 dependency bytes. Complete019 attestation, older seals and013 recovery remain intact. Governing109 artifacts and Creator020 have separate actual publication/installed/native gates; source or fixture results establish none of those operational claims.\nRetained product instruction upgrades need explicit generated-preimage authority rather than blind overwrite or fresh-scaffold substitution. Current code pins the accepted immutable predecessor source/manifests, authenticates the complete820-leaf old instruction closure and selected binding/provenance identities, replaces only verified old instruction destinations, and permits absent new leaves. Existing configuration receives guards without nonmerge replacement authority. Owner edits, unexpected destinations, symlinks, identity mismatch and preview races refuse. The original whole provenance and historical42-leaf adoption remain preserved while active generated ownership can move to48; unchanged product108 binding/tool/settings and user files stay intact, rollback restores bytes/modes/mtimes and exact repeats are no-op. Actual selected retained receivers still require the public installed acceptance path, distinct from fresh creation. Qualification callers must choose current published108, historical frozen099 or source-only109 from the actual selected mode rather than inferring a wrong dependency axis.\nExplicit HTTP(S) source navigation is not a receiver-local materialization dependency; local paths on the same line still are. The registry classifier distinguishes these without inventing rows or widening payloads. Ordinary CI observation likewise collects the finite policy-required check names rather than coupling admission to every unrelated check on a commit. Each named response remains complete and bounded100; malformed counts/names, selected duplicates and missing/failed/unauthenticated producers refuse. App, workflow/job/head/attempt, latest selection, PR/source/tree/policy barriers and activation remain unchanged. This source correction requires its own actual native qualification and does not settle an earlier failed observer.\nThe workspace wrapper resolves global/PATH tooling before a local manifest. An isolated organization successor must therefore use its absolute installed path and account for automatic selector writers while qualified products retain their actual108 route; a local pin alone is insufficient isolation. Durable issue/PR and stable Atlas-ID pointers recover ownership; reports save genuine missing recovery state. Private copy/restore equality is bounded custody, never off-machine/disk-loss/restart or operation-settlement proof. Original effect readbacks and admission remain authoritative; Atlas is curated navigation, not a grant.","supersedes":["1cfd18d1b12b25604d818389a34bbaa746f450e70246c7f4242fc4e215fc46a4"],"tags":["work-board","lifecycle","intake","decomposition","retirement","recovery","batching"],"title":"One continuous board-clearing lifecycle with explicit acceptance and retirement"}