FabledScribe

The open-after-moment signal proposes a mount; nothing proposed taking one
off, so a wrong mount was noise at every occurrence until someone happened
to notice. rule_misfired(rule_id, moment, why, reached_by) records a report
against a MOUNTED pair, counted per distinct day (the MCP door carries no
session id) on a new rule_moment_judgments.misfire column (migration 0119,
backup v24). At three days the response carries a line asking the agent to
offer the operator the fix - reject takes the rule off, unmap_action stops
the action reaching the moment, confirm keeps the mount and stops the
asking - and Settings > Moments lists it as an unmount proposal with the
reasons and the actions that reached it. A re-mount clears the count.

Taught in moments.md, missed-retrieval.md and the reply hold's wording.

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

2026-10-05 18:19:59 -04:00

canonicalSystems.ts

feat(systems): the catalog reaches the moment a name is minted, and gets a face (#3028 , milestone 307 step 2)

2026-08-26 12:58:30 -04:00

client.ts

fix(frontend): every request carries a deadline, and expiry arrives as an error callers already handle (#3412 )

2026-09-02 14:59:41 -04:00

designSystems.ts

feat(design): a project reports drift in its own recorded components

2026-08-04 10:41:49 -04:00

inception.ts

feat(rules)!: retire rulebook subscriptions and per-project suppressions (#4052 )