feat(systems): a System names its files — path patterns stored, validated and matched (milestone 444 step 3, #4756)

A System gains path_patterns: globs relative to the repo root (* within one directory, ** across any depth, a plain directory covering everything under it). One service validates them for every door, so the web UI and MCP refuse the same bad pattern with the same message. systems_for_paths resolves paths to every active System that covers them, which step 4 (#4757) uses to deliver an area's rulings when its files are touched. - schema: systems.path_patterns JSONB NOT NULL default [] (migration 0113) - service: normalize_path_patterns, path_matches, systems_for_paths - routes + MCP create_system/update_system accept it; [] clears - web UI: a Files field in the create and edit forms, patterns on the card - backup carries it through export and restore - using-scribe reflex 7: tagging work keeps a System's files current Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-02 22:55:26 -04:00
parent 01d8a0b9f1
commit a113c72b4f
14 changed files with 435 additions and 17 deletions
@@ -198,6 +198,11 @@ Two constraints on *how* that's achieved:
   work-logs alike. Treat it as the tagging question asked at the moment of
   work: tag the record, create the missing System, or deliberately leave it.

+   A System also names its files: `path_patterns`, globs from the repo root.
+   When the work you are tagging touched files its System's patterns don't
+   cover, and they plainly belong to that area, add them with `update_system`
+   — which files are which area is your call, as naming the area was.
+
 8. **Name the record, never just its number.** Whenever you refer to a Scribe
   record — in a message to the operator, a commit message, a task body, a
   work-log — write the id *and* its title: `#3244 "the staleness signal"`,