Skip to content

tri rule-observance: measure the practice, not the seal (Refs #2622) - #2624

Merged
gHashTag merged 1 commit into
masterfrom
feat/rule-observance
Aug 23, 2026
Merged

tri rule-observance: measure the practice, not the seal (Refs #2622)#2624
gHashTag merged 1 commit into
masterfrom
feat/rule-observance

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

tri loop-rules checks docs/loop/LOOP-RULES.md against a sealed digest and passes. It closes with its own disclaimer:

"This certifies identity only. It does not certify that the rules are correct, nor that the tick obeyed them."

That is the file's own R6the seal certifies identity, not correctness — stated about the tool that enforces it. Nothing measured the second half.

Over the last 30 merged pull requests, every author [measured]:

clause (R11) observed
branch prefix w699-<topic> 0 of 30
provenance tag on a number 0 of 25 stating one
no Closes #N autoclose 30 of 30 ✓

The tag convention is alive elsewhere — [measured] appears 211 times in the theory document. It has never reached a pull request.

Two clauses at zero across every author is not one operator drifting. The file and the practice have parted, and the seal made the file look governed while nothing looked at the practice — a checksum over rules is exactly as strong as a green check over a gate that cannot fail.

Reports, does not gate

Two separable reasons:

  • Which way a drift resolves is not the measurer's call — practice to rule, rule to practice, or rule plus a gate. Encoding a preference decides it by default.
  • Most of the file is not mechanically checkable. "Your own instrument is the first suspect" is a judgement about a tick's content; a regex pretending to score it would make the unmeasured look measured, which is this campaign's whole subject.

Filed as #2622, including the clause I knowingly do not observe"merging is a human act" — which the owner authorised outside this file. The rule is not edited to match what I do: a rules file edited by the thing it governs is worth nothing.

And the smaller finding under it: R2 is "your own instrument is the first suspect." I have re-derived that from scratch five times this campaign while it sat written down, sealed, in a file I had never opened.

§104.

Refs #2622

`tri loop-rules` checks docs/loop/LOOP-RULES.md against a sealed digest
and passes. It closes with its own disclaimer: "This certifies identity
only. It does not certify that the rules are correct, nor that the tick
obeyed them."

That is the file's own R6 -- the seal certifies identity, not
correctness -- stated about the tool that enforces it. Nothing measured
the second half.

Over the last 30 merged pull requests, every author [measured]:

  branch prefix w699-<topic>        0 of 30
  provenance tag on a number        0 of 25 stating one
  no `Closes #N` autoclose         30 of 30

The tag convention is alive elsewhere: [measured] appears 211 times in
docs/theory/IGLA-FORMAL-RESULTS.md. It has never reached a pull
request.

Two clauses at zero across every author is not one operator drifting.
The file and the practice have parted, and the seal made the file look
governed while nothing looked at the practice -- a checksum over rules
is exactly as strong as a green check over a gate that cannot fail.

Reports, does not gate, for two separable reasons. Which way a drift
resolves -- practice to rule, rule to practice, or rule plus a gate --
belongs to whoever owns the file, and encoding a preference decides it
by default. And most of the file is not mechanically checkable: "your
own instrument is the first suspect" is a judgement about a tick's
content, and a regex pretending to score it would make the unmeasured
look measured.

Filed as #2622, including the clause I knowingly do not observe --
"merging is a human act" -- which the owner authorised outside this
file. The rule is NOT edited to match what I do: a rules file edited by
the thing it governs is worth nothing.

Refs #2622
@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

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

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-23 22:40:16 UTC

Summary

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e6333575ec10 != 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).

@gHashTag
gHashTag merged commit 6d94f30 into master Aug 23, 2026
23 of 24 checks passed
@gHashTag
gHashTag deleted the feat/rule-observance branch August 23, 2026 22:47
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