Skip to content

Commit c83b5c0

Browse files
committed
Define catalog routing regression scenario
1 parent 27c5c2d commit c83b5c0

1 file changed

Lines changed: 25 additions & 0 deletions

File tree

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# Catalog routing and boundary review
2+
3+
## Objective
4+
5+
Clarify canonical ownership and `Use when`/`Avoid when` boundaries without reducing discoverability or breaking repository validation.
6+
7+
## Baseline
8+
9+
- Repository validation: 39 catalogs and references pass.
10+
- Worktree: clean and synchronized with `origin/main`.
11+
- Existing routing covers probability/statistics and urban/territorial planning.
12+
13+
## Acceptance criteria
14+
15+
- Decision uncertainty routes to `08`; statistical/probabilistic inference routes to `37`.
16+
- Canonical owners and secondary specializations are explicit for representative cross-domain families.
17+
- Every method card retains a usable trigger and a concrete misuse boundary.
18+
- Crisis/continuity capabilities remain distinguishable by output and authority.
19+
- Validation, local-link checks, and diff checks pass.
20+
21+
## Adversarial checks
22+
23+
- A prompt containing only “uncertainty” must not be forced into one catalog without identifying the required output.
24+
- A domain specialization must not be treated as a second generic method.
25+
- `Avoid when` must not become a generic disadvantage list or a universal prohibition.

0 commit comments

Comments
 (0)