You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Consumer entry: its protected_paths in the hooks' syntax #141
Part of the epic "Epic: slice 0, foundations. The repo holds the line, its context is tested, and the platform facts are recorded".
Follows "Kernel: a change to the Factory's own rules or a Lens's inputs needs a person" (#113), built by PR #135 (decision 0020): its working rulings named this as out of scope.
Why. The design gives a Consumer repo's entry a protected_paths. Since #113 the Factory's own list uses the hooks' syntax (a final / is everything below; * is part of one name; case ignored), matched by kernel/derive.py and tools/hooks/protected.py alike.
Done when
A Consumer entry's protected_paths uses the same syntax and the same matcher, with a schema and a counter-example.
Sequence (plan review, 2026-10-19). This waits on roles/ or a Consumer entry, which are slice 2's. It stays open under the slice-0 epic until the slice-2 epic is opened, then moves there. Nothing to build now.
Activity
don-petry commentedon Oct 19, 2026
Sequence (plan review, 2026-10-19). This waits on
roles/or a Consumer entry, which are slice 2's. It stays open under the slice-0 epic until the slice-2 epic is opened, then moves there. Nothing to build now.