FabledScribe

A System's rulings (the Rulings section of its description) now reach the
work by path, not by similarity. Both PreToolUse arms resolve the files a
command or edit names to the Systems whose path_patterns cover them, and the
first touch in a session shows each area's rulings in one line; a repeat is
a one-line reference. A lookup, so no floor, no budget, no retrieval_logs row.

- services/system_rulings: parse_rulings, command_paths (reads and writes,
  relative to the repo root from any cwd; flags, URLs, globs skipped),
  rulings_for_paths
- /tool-rules takes root, cwd and seen_ruling_systems; /prior-art takes
  seen_ruling_systems; both return ruling_system_ids
- hooks share <sid>.rulings.ids (cleared on compaction by the ledger naming
  convention); the Bash hook sends the repo root and cwd
- system_usage_events (migration 0114): surfacings by source, pulls from
  get_system; carried by backup (v20) through the system map
- writing-records: rulings also arrive when the area's files are touched

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

2026-10-02 23:08:32 -04:00

brainstorming

feat(plugin): add 4 Scribe-native process-skills (restore superpowers gap)

2026-06-13 20:52:34 -04:00

reporting-back

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 )

2026-10-02 18:59:36 -04:00

reusing-code

feat(shapes): the practice is written where it is read, and the coverage line measures the slip (milestone 439 step 6)

2026-10-01 08:46:58 -04:00

shape-accounting

feat(shapes): the practice is written where it is read, and the coverage line measures the slip (milestone 439 step 6)