Repository navigation
Claude/coderoast claude md malf p80u1w - #20
Merged
Merged
Conversation
…LAW-n addresses The superproject's flaw register minted registry-form addresses on 2026-09-16. That pass repointed the superproject doc tier and the DF/LF citations; its F<n> half was scoped to the superproject and said so. This closes it here. Every site was read before it was rewritten. The MetaLog entries kept their numbers, so these are prefix changes that cannot mis-map. Deliberately untouched and distinguished by reading, not by pattern: the ML F1 score, float16 and hex literals, flake8 suppressions, and the MetaLog specification's own F2(b) clause — a public standard's numbering, in a different number space. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…heck module in three sentences The superproject deleted `scripts/docs_lint.py` on 2026-09-16 (DN-108.D2, plan row P1.2: every gate becomes a `pharos check` module). An audit of that migration swept every live surface for the old spelling and found this record naming it three times — one of them an OPERATOR INSTRUCTION under OPS-8 (`python3 scripts/docs_lint.py`), which the next operator would have typed and watched fail. The two prose mentions now name the module; the instruction is the one spelling, `./pharos check --module docs` from the superproject root, and says the script existed at the time of the run so the measurement it quotes stays attributable. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…e the `pin_coherence` check module `technical_docs/operations/ccc_migration.md` named `scripts/pin_coherence.py` as the reader of the `pin-coherence: mirrors` marker (lines 2298, 2575, 4655) and as the owner of the `INV-17-EXEMPT-OBJECT-STORE` token (lines 2830, 3017). On 2026-09-17 that script became the `pin_coherence` check module of the superproject's `pharos check` fleet (DN-108.D2, plan row P1.2) and was deleted; the five sentences state which instrument reads those declarations today, so they name the module. No measurement in the ledger moved. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…e_declaration_lint.py name the closure_declaration check module The superproject deleted `scripts/closure_declaration_lint.py` on 2026-09-17 (DN-108.D2, plan row P1.2: every gate becomes a `pharos check` module; the `source` family). A sweep of every live surface for the old spelling found five present-tense sentences in this ledger — the comment-token census lines that say which live superproject gate READS the `CLOSURE MODEL` marker. Each now names the `closure_declaration` check module (spelled `./pharos check --module closure_declaration` from the superproject root); the first keeps "(`scripts/ closure_declaration_lint.py` then)" so the dated measurement still reads. The sibling gate names on the same lines (`log_seat_routing_lint.py`, `wallclock_lint.py`, `random_determinism_lint.py`) are repointed when each of those gates migrates, in its own commit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…lock_lint.py name the wallclock check module The superproject deleted `scripts/wallclock_lint.py` on 2026-09-17 (DN-108.D2, plan row P1.2: every gate becomes a `pharos check` module; the `source` family). A sweep of every live surface for the old spelling found three present-tense sentences in this ledger — the two comment-token census lines and the determinism-waiver-token sentence, each saying which live superproject gate READS the `DETERMINISM-ALLOW` token. Each now names the `wallclock` check module (spelled `./pharos check --module wallclock` from the superproject root). `random_determinism_lint.py` and `log_seat_routing_lint.py` on the same lines are repointed when those gates migrate, each in its own commit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…m_determinism_lint.py name the random_determinism check module The superproject deleted `scripts/random_determinism_lint.py` on 2026-09-17 (DN-108.D2, plan row P1.2: every gate becomes a `pharos check` module; the `source` family). The three present-tense sentences in this ledger naming it — the two comment-token census lines and the determinism-waiver-token sentence, each saying which live superproject gates READ the `DETERMINISM-ALLOW` token — now name the `random_determinism` and `wallclock` check modules (spelled `./pharos check --module random_determinism` from the superproject root). `log_seat_routing_lint.py` on the same lines is repointed when that gate migrates. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…t.py name the log_seat_routing check module The superproject deleted `scripts/log_seat_routing_lint.py` on 2026-09-17 (DN-108.D2, plan row P1.2: every gate becomes a `pharos check` module; the `source` family). The five present-tense sentences in this ledger naming it — the comment-token census lines and the marker-derivation sentences saying which live superproject gate reads `LOG-SEAT-ALLOW` — now name the `log_seat_routing` check module (spelled `./pharos check --module log_seat_routing` from the superproject root). With this, every gate of the `source` family's first half that these lines name is spelled as its module. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…ove onto da2abf63 Layer 3 (the last) of the malf-toolchain re-pin that unblocks the next CodeRoast release tag. THE DEFECT. The workspace pinned malf-toolchain at b5e15eee5e2cc9a2709309850f845b28ba8d9e58. The `malf` driver at that revision does `local pin="$MALF_WORKSPACE_ROOT/scripts/pin_coherence.py"` followed by `[[ -f "$pin" ]] || return 1`, in both `cut-verify` and `bump`. That superproject script no longer exists: the check became the Pharos check module `scripts/pharos/checks/pin_coherence.py` and its two producer verbs (`released` and `bump X.Y.Z`) moved to `scripts/version_line.py`. So the next `v*` tag would run `.github/workflows/cut-verify.yml`, which checks malf-toolchain out at the pinned revision and runs that checkout's `malf cut-verify`, which exits 1 on the missing file -- and every release job declaring `needs: [cut-verify, ...]` would be skipped. Measured: `git show b5e15eee:malf | grep -c pin_coherence` returns 6; `git show da2abf63:malf | grep -c pin_coherence` returns 2, and both survivors are correct (one comment and one `python3 "$pharos" check --module pin_coherence` invocation). THE TARGET IS NOT THE TOOLCHAIN'S main. `origin/main` is b62485cde9e1d5438b2c4ebabe86189a0ea7f028 and its count is also 6 -- main does not carry the fix. The target is da2abf639f64e1c1bca382aa7a973e9cc2f00412, the head of malf-toolchain's `claude/coderoast-claude-md-malf-p80u1w` branch, which is a strict fast-forward of main (7 commits ahead, 0 behind). That branch must be merged, not squashed, or every reference below would name a commit that no longer exists. WHY da2abf63 IS A LEGAL TARGET FOR EXTERNAL REFERENCES. The re-pin is layered because a commit may only pin edges whose TARGET it does not touch. Layer 1 (390108f5) moved malf-toolchain's 9 action->action refs onto the content head 5081176 and touched only 6 files under `.github/actions/`, none of them a target of those refs. Layer 2 (da2abf63) moved the 10 workflow->action refs onto layer 1 and touched only `.github/workflows/`, so all 10 target actions have identical bytes at layer 1 and at da2abf63. This layer touches no malf-toolchain file at all, so every workflow and every action a consumer executes has, at da2abf63, exactly the bytes it has at the revision this workspace pins. INV-17 (d) verifies that chain independently: each pinned SHA must be an ancestor of its successor differing by nothing but `uses:` lines. IN THIS REPOSITORY. 10 references move from b5e15eee to da2abf63: 8 `uses:` step(s) and 2 `actions/checkout` refs. Verified: every changed line is either a `uses: CodeRoasted/malf-toolchain/...@<40-hex>` step or the `ref:` of an `actions/checkout` whose `repository:` is `CodeRoasted/malf-toolchain`; every changed file parses under `python3 -c "import yaml; yaml.safe_load(open(f))"`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
coderoast-dev
added a commit
that referenced
this pull request
Oct 5, 2026
…ith no timed line has no envelope (DN-137.D1, DN-137.D2, DN-137.D6, DN-137.O1 producer half; N330). insight-canon: BSD syslog, logcat and Proxifier stamps, and BSD values in JSON/KV timestamp fields, parse into a yearless species (YearlessStamp, 8 bytes); the Tokenizer resolves it against the stream's previous event time (nearest of last/this/next year, the later year on a tie, Feb 29 only in a leap candidate), resets at construction and at every declare_context, and leaves it absent before any anchor; kDefaultReferenceYear and its never-built live-injection comment are deleted; CanonicalEvent::timestamp is std::optional, so a real 1970-01-01T00:00:00Z is a time. insight-eidos: presence is the optional's, and a window with no timed line reports no envelope instead of the epoch sentinel. insight-metalog: WindowBlock carries an optional envelope; start, end and duration_seconds, stability.previous_window_end, provenance and diff window bounds are omitted when absent; compose takes the envelope of the input that has one. coderoast-server: insight-mcp and server JSON omit the envelope when absent. Sift golden permutation_golden.json re-pinned: 24 diff windows 1970 -> {} and nothing else. Registered before this commit at coderoast-corpora a21ecc1 (R1 29 300 LogHub rows, R2 40 proof rows, R3 Sift 21 596 of 21 596 equal); spec text is metalog-spec PR #20 for the editor.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
2 participants
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.
No description provided.