Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/skills/atlas/assets/seed/catalog.json

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"citations":[{"path":"docs/coordination/2026-10-19-board-clearing-lifecycle-design.md","repository":"FS-GG/.github","revision":"13f6ef38f67a8a858ce88a71dbdc2c28ce643900","sha256":"f08bef7c80d27bc1c137878e74710f0c3bb810c8ff1770291daa2ce1bd83061a"},{"path":".agents/skills/work-board/SKILL.md","repository":"FS-GG/.github","revision":"13f6ef38f67a8a858ce88a71dbdc2c28ce643900","sha256":"319271d0103479b0275418b488884502828b4986d3c7ed63f41064b93c7bae96"},{"path":"src/FS.GG.Coord.GitHub/V2InspectionAcquisition.fs","repository":"FS-GG/.github","revision":"13f6ef38f67a8a858ce88a71dbdc2c28ce643900","sha256":"a16b6b79b4562168f854e9cae401d895adf5d08dda7d0adbd5f99a58cb6492b1"},{"path":"tests/coord-board-v2-projection/V2InspectionAcquisitionTests.fs","repository":"FS-GG/.github","revision":"13f6ef38f67a8a858ce88a71dbdc2c28ce643900","sha256":"d045c91301c09a331c8b16050337edc049b59d5eaf6a6fb08b6b8ce8ed4812fd"}],"conflictsWith":[],"id":"github/board-clearing-lifecycle","kind":"architecture","recordedAt":"2026-10-19T15:54:17Z","repository":"FS-GG/.github","schema":"fsgg.atlas/1","status":"recorded","summary":"The user selected one unified board/process outcome (#4701), including comprehensive design, meaningful shaping of all15current broad Outcomes, intake/p-add, useful parallelism, same-owner execution, stop/resume/handoff and retirement. The source candidate makes work-board the continuous coordinator and pnext-item the single-Delivery executor; work-roadmap supplies an already selected technical slice. Missing Status/classification/enrollment triggers All-items triage, never exclusion. Native six-field issues retain whole promises; independently useful Deliveries retain dependent installed/publication/recovery acceptance. Source merge returns the coordinator to selection; complete acceptance ends work, while complete intake and no admitted remaining action establish only quiescence with suppliers/reopening conditions. One native intake reference replaces active organizationV1 filing and mandatory analyst/claim/packet/phase chains; optional evidence analysis and qualified product compatibility remain scoped. Both runtime roots, Claude bindings, metadata, actual package/receiver references and guards require coherent delivery. Six unreachable org generator renderers are removed, retaining the separate anti-resurrection algorithm. New reader acquisition batches complete cohorts with separate fresh initial/final phases; a40member synthetic comparison observes731to137actualrequests with identical facts/selection decisions and133focusedtests pass. This is source/fixture evidence, not live installed efficiency or economic benefit. Actual publication, selected installed caller/receiver qualification, expanded protected enrollment, native decomposition and continuous-use acceptance remain separate open gates under4701. Original439inherited and46later Unknown holds remain distinct/unreleased; no original-effect replay or fleet-retirement claim follows. Native issue/PR and stableAtlaspointers carry recovery; reports save only missing information.","supersedes":[],"tags":["work-board","lifecycle","intake","decomposition","retirement","recovery","batching"],"title":"One continuous board-clearing lifecycle with explicit acceptance and retirement"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"citations":[{"path":"docs/coordination/2026-10-19-board-clearing-lifecycle-design.md","repository":"FS-GG/.github","revision":"13f6ef38f67a8a858ce88a71dbdc2c28ce643900","sha256":"f08bef7c80d27bc1c137878e74710f0c3bb810c8ff1770291daa2ce1bd83061a"},{"path":".agents/skills/work-board/SKILL.md","repository":"FS-GG/.github","revision":"13f6ef38f67a8a858ce88a71dbdc2c28ce643900","sha256":"319271d0103479b0275418b488884502828b4986d3c7ed63f41064b93c7bae96"},{"path":"src/FS.GG.Coord.GitHub/V2InspectionAcquisition.fs","repository":"FS-GG/.github","revision":"b252999a499e26b1e2cad0bcf8fa27bbff788c65","sha256":"01ea4f0cb88be64c9f51a7ab89784b09961919639b7fadb52ef90be56cd5f339"},{"path":"tests/coord-board-v2-projection/V2InspectionAcquisitionTests.fs","repository":"FS-GG/.github","revision":"b252999a499e26b1e2cad0bcf8fa27bbff788c65","sha256":"d86c0a25ec6bfa4632ee1e2273877b1dff8344a54e58f4a0baf8662c125b7850"}],"conflictsWith":[],"id":"github/board-clearing-lifecycle","kind":"architecture","recordedAt":"2026-10-19T15:59:48Z","repository":"FS-GG/.github","schema":"fsgg.atlas/1","status":"recorded","summary":"The user selected one unified board/process outcome (#4701), including comprehensive design, meaningful shaping of all15current broad Outcomes, intake/p-add, useful parallelism, same-owner execution, stop/resume/handoff and retirement. The source candidate makes work-board the continuous coordinator and pnext-item the single-Delivery executor; work-roadmap supplies an already selected technical slice. Missing Status/classification/enrollment triggers All-items triage, never exclusion. Native six-field issues retain whole promises; independently useful Deliveries retain dependent installed/publication/recovery acceptance. Source merge returns the coordinator to selection; complete acceptance ends work, while complete intake and no admitted remaining action establish only quiescence with suppliers/reopening conditions. One native intake reference replaces active organizationV1 filing and mandatory analyst/claim/packet/phase chains; optional evidence analysis and qualified product compatibility remain scoped. Both runtime roots, Claude bindings, metadata, actual package/receiver references and guards require coherent delivery. Six unreachable org generator renderers are removed, retaining the separate anti-resurrection algorithm. New reader acquisition batches complete cohorts with separate fresh initial/final phases; a40member synthetic comparison observes731to137actualrequests with identical facts/selection decisions and135focusedtests pass. This is source/fixture evidence, not live installed efficiency or economic benefit. Actual publication, selected installed caller/receiver qualification, expanded protected enrollment, native decomposition and continuous-use acceptance remain separate open gates under4701. Original439inherited and46later Unknown holds remain distinct/unreleased; no original-effect replay or fleet-retirement claim follows. Native issue/PR and stableAtlaspointers carry recovery; reports save only missing information. Independent exact-source review of the first candidate found discarded unmatched GraphQL error paths and a name-regex punctuation bug. Two new regressions failed the original source; fixed acquisition globally refuses missing/malformed/unattributable error paths while scoping only valid known aliases, and preserves single-character names/quoted literals. The full135tests then passed; original133PASS did not establish these omitted cases. Creator closure grew42to48leaves; its actual fixture inventories/signature were corrected after review rather than treating manifest parity as compiled acceptance.","supersedes":["0a9df276d42b56d98a7802befc2404204e0e5ee8bc7f5c032f7bb29aa4ae2091"],"tags":["work-board","lifecycle","intake","decomposition","retirement","recovery","batching"],"title":"One continuous board-clearing lifecycle with explicit acceptance and retirement"}
Loading
Loading