Skip to content

feat(tri): tri skill claims -- the figures in the knowledge base, and what re-takes them - #3018

Merged
gHashTag merged 4 commits into
masterfrom
loop/skill-claims
Sep 3, 2026
Merged

feat(tri): tri skill claims -- the figures in the knowledge base, and what re-takes them#3018
gHashTag merged 4 commits into
masterfrom
loop/skill-claims

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 3, 2026

Copy link
Copy Markdown
Owner

The measurement

.claude/skills/ci-gates/SKILL.md is 11,389 lines and 409 numbered sections, and until now nothing had ever asked how many of its own claims a second reader could re-take.

SKILL.md files read           5
  NOT read (outside .claude/skills): .agents/skills/phi-loop/SKILL.md
  NOT read (outside .claude/skills): .agents/skills/tri-pipeline/SKILL.md
  NOT read (outside .claude/skills): .trinity/agents/AGENT_T_SKILL.md
numbered sections             409
stating a figure              121
of those, naming a command     40
of those, anchored (dated)      5
free to go stale              116

A figure with no command beside it is not wrong — it is unre-takeable by anyone but its author. That is the rot surface, and it is the first time it has been counted here. The three tracked SKILL.md files outside .claude/skills are named in the output rather than left silent: a count that quietly excludes part of its subject is the defect this page keeps recording.

Reuse, and the part that did not transfer

The population rule and the anchor rule are the ones tri issues numbers and tri issues dated already use, pointed at a second subject — an address is not a count in a skill either (#2994, Wave Loop 369, w699 are all over these headings), and a section that says "I published 268 and it was wrong in both directions" is history rather than a claim about the tree.

But the subject had to change with the rule. Read from section bodies the same matcher reports 404 of 409 — a matcher describing its input, since a section here is twenty-five lines of prose about numbers. Read from the heading, where the claim is actually made, it reports 121.

A rule written for a one-line claim does not transfer to a page of argument by being pointed at it.

Not resolved, and said rather than smoothed over

A throwaway probe over the same headings reports 123. Four attempts to locate the two-section gap failed — the comparison kept matching on truncated titles rather than on sections — and the shipped number is the one the tested matcher gives. Two readings of one population disagree by 2, the direction is not established, and §421 says what to do about it: report both and say which one the tool uses. That is in §446 and in this PR rather than absent.

Controls

check result
cargo test -p tri 471 passed, 0 failed
mutation: stop stripping addresses from the heading red
mutation: any backticked span counts as a command red
mutation: prose naming a tool counts as a command red
mutation: the preamble becomes a section red
mutation: sections never close at the next heading red

Also in here

cargo fmt sorted forty mod lines in main.rs that the change never touched — the trap already written down for a crate root, met inside the one file the change does edit, so git status showed exactly the two files I meant to touch and only git diff --stat gave it away (45 changed, 20 deletions, for a two-line wiring change). Reverted; the wiring is now 9 insertions, 0 deletions. §447.

Refs #2994

🤖 Generated with Claude Code

gHashTag and others added 3 commits September 3, 2026 18:18
… what re-takes them

409 numbered sections; 121 state a figure in their heading; 40 name a
command a second reader could run; 116 are free to go stale. That rot
surface has never been counted here.

The population and the anchor rule are the ones tri issues numbers and
tri issues dated already use, pointed at a second subject -- an address
is not a count in a skill either, and a section saying "I published 268
and it was wrong" is history rather than a claim about the tree.

But the SUBJECT had to change with it. Read from section BODIES the same
rule reports 404 of 409, which is a matcher describing its input: a
section is twenty-five lines of prose about numbers. Read from the
heading, where the claim is actually made, it reports 121. A rule written
for a one-line claim does not transfer to a page of argument by being
pointed at it.

Also names the three tracked SKILL.md files outside .claude/skills that
no command here reads, rather than leaving them out in silence.

Refs #2994

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
cargo fmt sorted forty mod lines this change never touched -- the trap
already written down for a crate root, met inside the one file the change
does edit. The diff here is now the two lines that wire the subcommand.

Refs #2994

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…er inside the edited file

446: the first count of this file's own rot surface. 409 sections, 121
stating a figure in the heading, 40 naming a command, 116 free to go
stale. Read from bodies the same rule reports 404 of 409 -- a matcher
describing its input. A second probe reports 123 and the two-section gap
is NOT resolved; both are stated.

447: cargo fmt sorted forty mod lines inside the file the change edits,
so git status looked correct and only the diff shape showed it.

Refs #2994

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-03 11:19:43 UTC

Summary

Status Count
Total Open PRs 12
PRs with Failing Checks 10
PRs with All Checks Green 2
READY 0
FAILING 10
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=2a95b1f73357 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-03 11:31:02 UTC

Summary

Status Count
Total Open PRs 11
PRs with Failing Checks 10
PRs with All Checks Green 1
READY 0
FAILING 10
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=a64be3550ca2 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag
gHashTag merged commit a43ebf8 into master Sep 3, 2026
36 checks passed
@gHashTag
gHashTag deleted the loop/skill-claims branch September 3, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant