Skip to content

docs: refresh foundation layer pins and evidence dates - #859

Merged
seathatflowsinourveins merged 2 commits into
mainfrom
codex/ns2604-layer-map-refresh-20261008
Oct 8, 2026
Merged

seathatflowsinourveins merged 2 commits into
mainfrom
codex/ns2604-layer-map-refresh-20261008

Conversation

@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator

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.

  • Base commit: eb5fee4db9a494729deb29bdf38dbabac23ee643
  • Lane: lane:foundation
  • Owned paths: docs/foundation-layer-map-20261008.md, catalogs/foundation/README.md, and the final hash registration in manifests/evidence.json.

SOTA sources

  • affaan-m/ECC, pin dd6ee538aee0f548d4a6b520118f875431fd749e, skills/search-first/SKILL.md: research and reuse before implementation.
  • The map's Exact source-pin provenance table names each selected vendor repository and current package/source pin, including openai/codex, dagucloud/dagu, max-sixty/worktrunk. Package versions, Git revisions, tags and artifact SHA256 digests retain their distinct meanings.
  • Native Stack at the reviewed base: 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

Claim Evidence class Command / receipt
All 20 foundation layers and 61 current repository component pins are represented source_review New dated map, checked against canonical manifest/stack and an independent completeness critic
Receipt timestamps, source-pin types and optional/trial/source-review boundaries are preserved source_review Exact linked JSON fields; separate SDK/Pi and Apple Silicon candidate pointers
References and evidence hashes are consistent local_integration python3 scripts/validate.py, python3 scripts/validate_catalogs.py, python3 scripts/build_ecosystem.py --check, and git diff --check
Historical upstream/client/host operations native_proven only within each original receipt's scope Linked original receipts; no operation was rerun or strengthened by the map

Local commands run

python3 scripts/validate.py
exit 0: 69 components, 10,831 hashed files, 4 profiles, 228 receipts; passed

python3 scripts/validate_catalogs.py
exit 0: catalog structure and evidence classes validated

python3 scripts/build_ecosystem.py --check
exit 0: passed; retained 18 dated architecture-pin differences

git diff --check
exit 0

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.md is 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

  • Existing workflow/action pins and permissions are preserved.
  • No credential values, native sign-ins or private host paths are included.
  • No paid hosting, subscription or billing surface is introduced.
  • Peer-owned files and worktrees are preserved.
  • The evidence registry is the branch's last commit.
  • Publication is a review PR; landing remains on the command center's cue.

@seathatflowsinourveins seathatflowsinourveins added the lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers label Oct 8, 2026
@seathatflowsinourveins
seathatflowsinourveins marked this pull request as ready for review October 8, 2026 14:27
@seathatflowsinourveins
seathatflowsinourveins merged commit 64a8cda into main Oct 8, 2026
35 of 36 checks passed
@seathatflowsinourveins
seathatflowsinourveins deleted the codex/ns2604-layer-map-refresh-20261008 branch October 8, 2026 14:33
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant