dbc1613a9752eec51e0806c7b131da18cd8a41b7
10
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 |
||
|
David F GliddenandClaude Opus 5
|
47ae108127 |
The fool is named Tarbuckle; the name recorded beside the bones with its provenance
Named by the steward from the bones, ratified by the jurist. Recorded in the same
file as the bones because the naming is the ONE step with no cryptographic guarantee
behind it: the beacon can be re-fetched by anyone and the seed recomputed from two
public values, but a name cannot be checked that way. The procedure is the only
evidence it was not steered, so the procedure is what gets written down.
Recorded as ATTESTATION, not as established fact. Fresh instance, bones only, one
generation kept, Thistleweld unread — these are the steward's words ratified by the
jurist. The executor did not observe the generation and cannot verify any row of
that table, and the record says so rather than laundering a report into a finding.
What the executor can attest first-hand is the part where it was the contamination
risk: it supplied no candidates, no criteria, no shortlist, no opinion, and knew the
peak was SUCCESSION when it could have offered them. That route was never opened.
Keeps the jurist's reasoning verbatim, because it ties the name to a structural
requirement rather than to taste: "Tarbuckle says" will never sit comfortably in a
PENDING entry, and §9's unfileability is eroded by prose habit rather than by
decision. A name that resists the citing sentence defends §9 where §9 actually breaks.
Also fixes §7's "the filed rule not edited", false since
|
||
|
David F GliddenandClaude Opus 5
|
42c461d71d |
[HARDENING] File PENDING-157: the deferral schema has no resolution state
The steward's scope point on yesterday's discharge, taken. Renaming the key closed one trigger; the next will need the same hand-rename by whoever is in session. If census 01 found decay is how gates fail here, a schema that cannot express "answered" is what produces the decay, and renaming keys one at a time is living with it. Filed while there is exactly ONE instance and three tracked deferrals remain. The window matters: once a second is renamed by habit the convention is established and the schema question stops being asked. Filed, not built — that was the direction. Carries a sharper half the rename surfaced: resolution must be unsatisfiable without a pointer, so a discharge that records THAT a gate closed but not WHAT closed it becomes impossible to express rather than merely discouraged. Plus two conditions on the recommendation (resolved blocks stay counted as a closed ledger; a dangling pointer is a register-integrity defect) and three required controls. Also writes the missing reverse pointer into FOOL-BONES §6. The discharge block already pointed at the derivation record and 06b3d8b's message named it; the record did not point back. Written at both ends now — one direction only is how a successor learns a gate was closed but never why. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf |
||
|
David F GliddenandClaude Opus 5
|
5737d4dff8 |
[FIX] 'abandonment' -> 'retirement' in the fool's doctrine; §6 was false as of today
The jurist owned this mismatch and scheduled it after the beacon so no edit would touch the filed rule before it fired. It fired at 12:00Z; this is that harmonization. v2 §4 step 3 said "Abandonment criterion" while §10 defined RETIREMENT. Censused before editing rather than sed'd. All 24 abandon* occurrences in the fool tree were counted and read in context: 9 were doctrine and changed; 13 in the trial-09 family were LEFT — that is the word §6 of the trial design owns, in its own sense about the jester form, and a blanket replace would have silently collided the two meanings it was supposed to separate. 1 in input-dependence-01 is ordinary English about the void of a numbering. 1 in FOOL-BONES is the dated record of what was owed. Prior wording preserved in place at every changed site. REVIEWED-125 ruled on the v2 draft's text; an untraceable edit drifts a ruling's subject away from its artifact, which is the PENDING-82/86 hazard this item's own record already notes recurring inside a ruling. The criterion is unchanged — only the word naming it. Separately, found while in the file: §6 "What has NOT happened" asserted the pulse had not been fetched and no bones derived. Both went false at 12:00Z today. Marked superseded in part, bullets struck rather than deleted since they are the pre-registration record, and pointed at FOOL-BONES for current state. A governance doc asserting stale current state is what Constraint 4 forbids. New §7 logs every post-beacon edit to the filed rule, so "filed and pushed before the beacon" stays auditable instead of eroding one silent correction at a time. Its claim that §1/§2/§2a/§3/§5/§5a are untouched was verified by reading the diff hunks against the pre-edit section map, not asserted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf |
||
|
David F GliddenandClaude Opus 5
|
5694b92539 |
[FIX] The bones are derived: beacon 2026-08-25T12:00:00Z, run once (PENDING-149)
Executes the standing run-once authorization filed in PENDING.md, against
FOOL-SEED-RULE.md at
|
||
|
David F GliddenandClaude Opus 5
|
d6377af572 |
[FIX] §2a records one ruling and one steward decision, not two rulings
The heading read "Two corrections to the v2 §6b block — RULED, no veto" while the ruling beneath it addressed only the retrieval URL. Its settling test — "could this correction have moved the outcome?" — returns no for the URL and YES for the provenance commit, since the provenance SHA is half the seed string. The heading therefore claimed a scope the ruling could not reach. Jurist confirmed 2026-08-23: "I ruled on one thing. The URL." The provenance commit was never a correction under veto — the steward selected a still-open value on the jurist's recommendation, before filing. It is now recorded as a steward decision of 2026-08-22, with its reasoning, because a value that moves the outcome must be attributable to the party entitled to choose it. Verified independently against git, not relayed: |
||
|
David F GliddenandClaude Opus 5
|
1e40b01d70 |
[FIX] Normalization tested at its single point; the dry run had bypassed it (PENDING-149)
The jurist's pre-25th condition: confirm lowercasing happens at exactly one point and is unit-tested against a known uppercase input. Single point confirmed at derive_fool.py:79 — the only .lower()/.upper()/ casefold in the file. Four checks added, including a negative control proving the test can fail. Selftest 16/16. Checking it found the defect the condition was aimed at, in my own work: the 2026-08-22 dry run lowercased the value OUTSIDE the code and passed it in already normalized, so the single normalization point was never exercised on uppercase input in the only end-to-end run. The test's subject was the pipeline; it excluded the step under scrutiny. Re-run with the raw uppercase value through the real path reproduces the same seed. Binding procedure added: on the 25th the outputValue is passed exactly as served. Jurist ruling on the URL correction recorded verbatim — no veto, with the reasoning, since it will be read later. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JQKeKY9T9d95KpvHwwok8T |
||
|
David F GliddenandClaude Opus 5
|
acfbb9fc0e |
[PROPOSAL] Fool seed rule filed before the beacon; two unresolvable values caught (PENDING-149)
§4 steps 1-4 discharged and pushed ahead of the 2026-08-25T12:00:00Z beacon: ratified axes recorded in writing, seed derivation rule filed, retirement and regeneration criteria filed, derivation implemented and self-tested. Two values in the jurist's §6b block did not resolve, and both are corrected in the open rather than absorbed: - the provenance commit's stated rationale was false. |