Repository navigation
docs: refresh foundation layer pins and evidence dates - #859
Merged
seathatflowsinourveins merged 2 commits intoOct 8, 2026
Merged
Conversation
seathatflowsinourveins
marked this pull request as ready for review
October 8, 2026 14:27
seathatflowsinourveins
deleted the
codex/ns2604-layer-map-refresh-20261008
branch
October 8, 2026 14:33
6 tasks done
seathatflowsinourveins
added a commit
that referenced
this pull request
Oct 8, 2026
### Scope Codex cloud review remains in use, but the landing procedure has no per-thread disposition step. This adds that step to the existing **Landing** section: read every connector thread and comment, retain a fixed/replied/not-applicable disposition and evidence, and re-read the exact head and all conversations before declaring readiness. - Base commit: `64a8cda01700d5e823c18e4b989e856de2ee2241` - Lane: `lane:foundation` - Owned paths: `docs/command-center.md`; its evidence hash is refreshed in the last registry-only commit. ### SOTA sources - [Official OpenAI Codex GitHub review](https://developers.openai.com/codex/integrations/github), fetched 2026-10-08: supported cloud review remains the native route. - [cli/cli v2.102.0](https://github.com/cli/cli/releases/tag/v2.102.0), installed native client, and [gh api manual](https://cli.github.com/manual/gh_api): GraphQL pagination requires an end cursor and pageInfo for the connection being paged. - [GitHub GraphQL pagination](https://docs.github.com/en/graphql/guides/using-pagination-in-the-graphql-api) and [native conversation resolution](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#resolving-conversations), fetched/reviewed 2026-10-08. Live native schema and thread returns distinguish outdated, resolved, author and original-commit state. ### Evidence-class table | Claim | Evidence class | Command / receipt | | --- | --- | --- | | Native thread metadata supports the documented read | native_proven within the RPC scope | Read-only paginated `gh api graphql` on PR #854: 4 connector threads, all outer/nested comment pages complete, 0 unresolved; no reply/resolution mutation | | Every disposition is bound to evidence and the landing head | source_review | Existing Landing subsection plus independent completeness critic; no workflow/bot/ruleset code | | The document and registered hash are consistent | local_integration | `python3 scripts/validate.py` and `git diff --check`, both exit 0 | ### Local commands run ```text gh --version gh version 2.102.0 gh api graphql --paginate --slurp -f query=<retained query> exit 0: PR #854 returned 4 connector review threads; all pageInfo.hasNextPage fields false python3 scripts/validate.py exit 0: repository integrity/scope passed git diff --check exit 0 ``` The full native query/output is retained privately with its actual post-exec argv. A CLI option-validation failure before the request was retained and corrected; it is not a provider failure. Metadata reads do not prove semantic triage or future enforcement. No low-impact document test was added. **Modified test files:** none. **Declared modified-test failing set:** empty. ### Decision record The new `docs/command-center.md#codex-cloud-review-thread-triage` subsection is the source-reviewed B3 procedure. It explicitly covers resolved/outdated threads and nested comments, both connector login spellings, current-head evidence, justified resolution, zero-thread proof and invalidation after a push, thread or comment. A reply, outdated flag or green CI cannot justify resolving a valid outstanding finding. PR #859 was independently confirmed MERGED first at `64a8cda01700d5e823c18e4b989e856de2ee2241`; its landed map blob matches the retained SHA256. The inverse for B3 is to revert the documentation and its final registry hash coherently. ### Host evidence No host installation, platform status, client configuration or credential change. ### Checklist - [x] No workflow, ruleset, frozen input or always-loaded instruction surface changed. - [x] No credential value or private host state is published. - [x] No paid service or billing surface introduced. - [x] Peer-owned worktrees and private landing code preserved. - [x] Evidence registry is the final commit. - [x] Landing remains with 5f under the standing cue when required-green and zero threads.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
The foundation guide currently leaves reviewers to join historical layer verdicts, current package pins and receipt timestamps by hand. This adds a dated map for all 20 foundation layers, with 61 canonical component pins, exact evidence links and recorded dates. For example, the ai-memory receipt named September 25 is correctly dated September 26 in the map.
eb5fee4db9a494729deb29bdf38dbabac23ee643lane:foundationdocs/foundation-layer-map-20261008.md,catalogs/foundation/README.md, and the final hash registration inmanifests/evidence.json.SOTA sources
dd6ee538aee0f548d4a6b520118f875431fd749e,skills/search-first/SKILL.md: research and reuse before implementation.manifests/stack.json,catalogs/foundation/{manifest,decisions,automation}.json,adoption/pins-linux-x86_64.json, registered native receipts and the unchanged repository validators. This is a source review and reference join; it introduces no custom foundation executable.Evidence-class table
python3 scripts/validate.py,python3 scripts/validate_catalogs.py,python3 scripts/build_ecosystem.py --check, andgit diff --checkLocal commands run
These are deterministic repository checks, not new upstream functional acceptance. The separate artifact check confirmed 20 unique layer IDs, 61 exact package pins, resolving relative links and both registered byte hashes. The independent critic passed after source-pin type, SDK modality and Apple Silicon candidate corrections.
Decision record
docs/foundation-layer-map-20261008.mdis the dated record at the stated source commit. Historical winner pins, profile proposals, partial qualification and failed controls keep their original statuses. Layer 1.5, ranking, both-client wiring/fast-tier disposition and S4 closure remain independently owned gates.Host evidence
No host receipt or platform-status change is included. The inverse is to revert the two documentation files and their final hash registration.
Checklist