28687832b3f02695390d0b711843a5027256e230
3
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 David F GliddenandClaude Opus 5
|
063eccfd80 |
[HARDENING] STATE-CLAIM + the resolution state, built together (REVIEWED-127)
Both halves of the schema, shipped in one change because the ruling said half a schema
invites a third patch and a third patch is how a vocabulary accretes instead of being
designed.
157 — resolution state. `resolved:` on any block; a resolved block is no longer due but
is NOT dropped: it prints as a closed ledger, because a discharge that vanishes from the
report is its own decay. The pointer must RESOLVE — a real path or a real git object —
so an undocumented discharge is impossible to express rather than merely discouraged. A
dangling pointer reports in the register-integrity lane, the same lane as an amendment
that replaced the record it amends; both are a record closing over its own history.
The 25th's hand-rename is MIGRATED back to DEFERRED-DECISION with resolved: set. That
block was the per-instance workaround 157 was filed against, and it is now the
migration's own test case.
158 — STATE-CLAIM. Reuses trigger_fired() verbatim and inverts only what firing MEANS:
for a deferral, fired = the decision is due; for a state-claim, fired = THE CLAIM IS
FALSE. Two new trigger kinds earned directly from today's instances: text-present (the
trial-09 hold, falsified by REVIEWED-124's existence) and file-changed-since ("the filed
rule not edited", false one hour after writing).
16 new controls, each with its discriminating half — fires on met, silent on unmet,
manual listed-never-fired, resolved excluded from due-ness, the SAME block unresolved
still due, a real pointer resolves, "yes, done" does not.
Proven on the LIVE blocks, not only fixtures: pointing the state-claim at an older
commit made it report FALSIFIED by name; replacing the resolution with "yes done" made
register-integrity report it; both restored and both returned to quiet.
⚠ One control failed before shipping and the failure was the useful part. The negative
control for file-changed-since pointed at FOOL-SEED-RULE.md, which this same session then
edited — so "unchanged since HEAD" broke, correctly. A control whose subject is "did this
file change" must not point at a file the session is changing. Re-pointed at a frozen
2026-08-02 trial artifact, with the reason recorded at the fixture. Caught because the
controls run on every invocation rather than in a separate suite.
First two real state-claims filed, deliberately one of each kind: ~/CLAUDE.md untouched
under PENDING-150, mechanically watched and [ESCALATE]-grade the moment it goes false;
and §9's channel unbuilt, marked `manual` because it has no filename yet and inventing a
proxy falsifier is the error the schema's own comment warns against.
⚠ The zero-state prints a WARNING, not a tick: "0 marked, NOT none-stale" with the ~57
unmarked candidates named as a grep. An instrument that reads nothing reports exactly
like one that finds nothing, and that is the failure this item exists to end.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf
|
||
|
David F GliddenandClaude Opus 5
|
f48d8479b6 |
Jurist ruling on the soul: one non-deviation, one deviation ruled harmless
Ruled from §7's text against the procedure as described, WITHOUT reading the soul — the jurist naming that reading it would be "reaching for it through a side door". The executor had read it and recused itself; the jurist had not, and could rule. The recusal was not ceremony: it is what left a party able to answer. (i) The missing glosses: NOT an error and NOT a gap, and this INVERTS my framing. I filed the omission as a finding — the correct input withheld. The ruling: the bones are five names and five numbers; the glosses are §5's definitions, not bones. Supplying them would have handed over an interpretation of what SUCCESSION 96 means and produced a character organized around legibility-to-a-stranger — a stat read as a personality trait, which §3 forbids reading backwards. The risk ran the OTHER way: including them would have been the deviation. §4 REGENERATION is therefore not reached at all. My original heading is left visible with the correction marked on top, not rewritten. A record that silently corrects itself teaches the next reader nothing about how the error was made. (ii) The name as an input: a real deviation from "from the bones", ruled HARMLESS — the name was itself bones-derived, one generation kept, so it added no information not already downstream. Recorded as DEVIATION RULED HARMLESS and explicitly not as compliance: compliance would erase both the fact that practice departed from text and the fact that someone with authority looked at it. (iii) The jurist attached a pattern — second time this week a filed instrument's wording was narrower than the practice it governed. Recorded as their observation; the first instance is not named and I do not guess at it. (iv) Both go in the attestation, NOT as a [FIX] to §7. Amending a rule after it has fired is what §5b exists to prevent, and §7 has now fired. §7 stands exactly as filed. Also: §6's "no regeneration ruling" went false — THIRD such bullet in this programme, this time inside the very section that names the pattern and was written hours earlier. A negative-status list does not become durable by knowing it is fragile. n=3 in one day. Soul block re-verified byte-intact after the edits. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf |
||
|
David F GliddenandClaude Opus 5
|
cb63033d7c |
Tarbuckle has a voice: the soul recorded verbatim, with the one finding it made about itself
Generated once and kept, per §7. Claude Opus 5 Extra, fresh instance, incognito, run by the steward. Prompt, conditions and output all recorded verbatim; the executor wrote no part of the prompt and did not observe the run, same exclusion as the naming and for the same reason. Attestation, not verification, and the record says so. Byte-fidelity of the soul block checked rather than assumed: no em-dash substitution, no curly quotes, 5 double-hyphens, 7 sample lines, separator and closing paragraph intact. A text that may never be hand-edited should not be silently reformatted on the way in. THE FINDING, and it is checkable against the recorded prompt: the prompt supplied axis names and numbers but NOT the questions the steward ratified on 08-22, which are what those names mean here. The generating instance noticed and said so — it stipulated SUCCESSION as "inheritance rather than sequence", i.e. it chose the meaning of the PEAK axis, the one carrying 96, and correctly noted the other reading yields a different fool. Recorded alongside it, because it is a real datum either way: three of five axes converged with their filed definitions WITHOUT being told them — STAKE, ABSENCE and AIM land close. SCALE is underdetermined. Only the peak was stipulated. The offer to "build that one instead" is recorded as DECLINED. §7 forbids regenerating for taste, and the alternative being described as "pettier, funnier" is exactly why that clause exists. The only door not shut is §4 REGENERATION, on a demonstrable implementation error — and whether a prompt missing the ratified glosses is one is a JURIST question. The executor states its interest and stops: it has read this soul, and a party that has read the output is the wrong party to rule on whether the output may be redrawn. Until ruled, this file is the soul and §7 governs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf |