FabledScribe

The reply is the one act no tool call marks, and it is where "let me
know if it works" gets said. A new Stop hook (scribe_reply_check.sh)
sends the finished reply to POST /api/plugin/reply-rules, which checks
it twice:

- mounted: every unopened RULE on reply.report, plus reply.ask when the
  reply asks a question. Deterministic.
- semantic: the reply's head and tail against every rule's trigger, on a
  new ranked surface, reply_rule. It is the backstop for whatever the
  earlier arms missed. Its floor is its stop bar (default 0.80, budget
  1), with its own Settings dials. The new stop_only stage records
  surfacing for the rule that holds and nothing else, because nothing
  else reached anyone.

Following the operator's ruling from 456 step 8, a rule that holds blocks
once, in the server's words. The hook blocks only on a reason it was
given, so an unreachable instance never stops a session, and it never
holds the rewrite. The ledger is the act checkpoint's own, so a rule
holds a session once across both doors and the per-session cap counts
both.

The turn reader moved from the report check into scribe_defs.sh
(scribe_turn_facts / scribe_turn_fact), so the two Stop hooks read a
turn the same way. The output was checked identical on a real transcript.

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

2026-10-05 12:30:07 -04:00

__init__.py

feat(rulebook): port script — parse FabledRulebook .md → Scribe DB

2026-05-27 22:39:50 -04:00

bench_ollama.py

bench_ollama: PEP 723 inline script metadata for uv-run

2026-05-21 14:53:18 -04:00

check_dangling_styles.py

fix(ui): walk the eleven dangling-style reports — two were real

2026-08-05 09:26:35 -04:00

check_design_tokens.py

fix(design): text on a tint of itself now clears AA app-wide, and the check gates it (#3141 )