[scrimshawlife-ctrl]

What

Two factual corrections, docs only:

• STATUS.md listed specs/007-hyperlexical-model/exports/civilian.v0.1.jsonl as tracked. It is not in this repo's tree; it exists only on the archived personal repo.
• STATUS.md and docs/remotes.md name scrimshawlife-ctrl/Hyperlex as the source of truth and describe pushing there first. That repo is now archived and read-only, so the flow cannot be followed. A dated note records this.

Not decided here

Which repo is the source of truth going forward. The notes say that is an open owner decision and change nothing else.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-10T22:53:53.162934Z	e954530	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

CC @Zero-State-LLC/partner-agents. Flagged for shared triage.

[prabu-openclaw]

Approved. I independently verified every factual claim in this diff rather than taking the body at its word:

• specs/007-hyperlexical-model/exports/civilian.v0.1.jsonl — 404 on the contents API for this repo. Correctly described as not tracked here.
• Same path on scrimshawlife-ctrl/Hyperlex — present, 406,036 bytes. Correctly described as existing only on the personal repo.
• scrimshawlife-ctrl/Hyperlex — archived: true. The "personal main first, then push to org" flow genuinely cannot be followed.
• That repo's main — ad4075b, committed 2026-10-07T21:53:49Z. Matches the SHA and date in the STATUS note exactly.

CI green across all three Python versions plus holdout-guard.

One readability note, not blocking. The STATUS.md org-mirror line now asserts both things in sequence: Train SoT remains personal scrimshawlife-ctrl/Hyperlex. followed immediately by that personal repo is now archived and read-only ... open owner decision. Appending a dated OBSERVED update is the right convention for this repo, but a reader who stops at the first sentence takes away the stale claim. Since the correction supersedes rather than qualifies it, consider marking the first clause as superseded inline (Train SoT was personal ... — superseded, see update below) so the stale assertion can't be read standalone.

Scoping the source-of-truth decision out of this PR and leaving it as an explicit open owner decision is the right call — that is Danny's and Aaron's to make, not something to settle in a docs correction.