Milestone 444 steps 1-2: an operator's ruling lives on the System it governs, and code is read as behaviour, not intent #193

2026-10-02T19:46:47-04:00

bvandeusen commented

2026-10-02 19:46:47 -04:00

Guidance only. No schema or server behaviour changes. One commit: 01d8a0b. CI run 7928 passed on dev.

writing-records.md has a new section, "A ruling goes on the System it governs". It defines a ruling with two tests: the operator decided it, and a later change could undo it. A ruling goes in a Rulings section at the end of the System description, one line each with who decided, when and the source record. The section holds what is in force, not history.
using-scribe:
- Reflex 1: code tells you what a thing does, not what was wanted.
- Reflex 9: points to the rulings section.
reporting-back: an option that carries existing behaviour says whose call it was. An assumption that contradicts a ruling is raised as a Conflict.
create_system / update_system docstrings describe the Rulings section. update_system notes that description replaces the whole text.
test_guidance_ownership: three new topics are pinned to their owners.
Plugin version: 2026.10.02.2259.

Why: a FabledLibrarian session contradicted a ruling the operator made 13 days earlier ("never give up on a book"). The ruling was kept only as a quote in a work log, beside a session's reading of it that capped replacements.

🤖 Generated with Claude Code

Guidance only. No schema or server behaviour changes. One commit: 01d8a0b. CI run 7928 passed on dev. - **writing-records.md** has a new section, "A ruling goes on the System it governs". It defines a ruling with two tests: the operator decided it, and a later change could undo it. A ruling goes in a `Rulings` section at the end of the System description, one line each with who decided, when and the source record. The section holds what is in force, not history. - **using-scribe:** - Reflex 1: code tells you what a thing does, not what was wanted. - Reflex 9: points to the rulings section. - **reporting-back:** an option that carries existing behaviour says whose call it was. An assumption that contradicts a ruling is raised as a Conflict. - **create_system / update_system docstrings** describe the Rulings section. `update_system` notes that `description` replaces the whole text. - **test_guidance_ownership:** three new topics are pinned to their owners. - **Plugin version:** 2026.10.02.2259. **Why:** a FabledLibrarian session contradicted a ruling the operator made 13 days earlier ("never give up on a book"). The ruling was kept only as a quote in a work log, beside a session's reading of it that capped replacements. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

bvandeusen added 1 commit 2026-10-02 19:46:47 -04:00

feat(guidance): an operator's ruling lives on the System it governs, and code is read as behaviour, not intent (milestone 444 steps 1-2, #4754 #4755 )

CI & Build / Python lint (push) Successful in 3s

Details

CI & Build / Plugin hooks (push) Successful in 12s

Details

CI & Build / TypeScript typecheck (push) Successful in 53s

Details

CI & Build / integration (push) Successful in 55s

Details

CI & Build / Python tests (push) Successful in 1m46s

Details

CI & Build / Build & push image (push) Successful in 56s

Details

01d8a0b9f1

A Librarian session contradicted a decision the operator had made 13 days
earlier. The ruling ("retry, then replace, never give up on a book") was
kept only as a quote in a work log, beside a session's reading of it that
capped replacements at 3. Three later sessions built on the reading, and one
carried the cap into an option as a "known cost", which the operator then
approved without being asked about it.

- writing-records.md: "A ruling goes on the System it governs". What a
  ruling is (the operator decided it; a later change could undo it), how it
  differs from a rule, and where it goes: a Rulings section at the end of
  the System description, one line each with who, when and the source
  record. Written the turn the operator decides; holds what is in force,
  not history; a charter line that contradicts a ruling is fixed in the
  same edit.
- using-scribe SKILL.md: reflex 1 says code tells you what a thing does,
  not what was wanted, and a limit read from code is unconfirmed until a
  System's Rulings says otherwise. Reflex 9 points to the ruling section.
- reporting-back: an option that carries existing behaviour says whose call
  it was (the operator's ruling, or a past session's never confirmed); one
  that contradicts a ruling is a Conflict.
- create_system / update_system docstrings: the Rulings section, and that
  description replaces the whole text.
- test_guidance_ownership: three topics pinned to their owners.
- Plugin version minted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

bvandeusen merged commit 6477c20664 into main

2026-10-02 19:46:50 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bvandeusen/FabledScribe#193