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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,10 +28,11 @@ Before tuning `route_paraphrase_eval.py`:
28
28
29
29
1. Add fresh holdout phrases to `route-002-holdout-eval.yaml` and/or adversarial cases to `route-003-adversarial-eval.yaml`.
30
30
2. Run `make all` — `validate_route_fixture.py` enforces minimum fixture coverage.
31
-
3. When fixing review-vs-risk or plan-only boundaries, add holdout phrases **before** editing `route_paraphrase_eval.py` (see `ROUTING_CONTRACT.md` R8–R9).
32
-
3. Record governance-surface decisions in `PROJECT_KNOWLEDGE.md` Decision Index when routing contract changes.
31
+
3. When fixing routing boundaries, add holdout phrases **before** editing `route_paraphrase_eval.py` (see `ROUTING_CONTRACT.md` R8–R12).
32
+
4. When cheatsheet cues change, update exported probe tuples in `plans/tests/test_validate_route_fixture.py` and run `test_cheatsheet_*_parity.py` plus `test_cheatsheet_boundary_quick_cues.py`.
33
+
5. Record governance-surface decisions in `PROJECT_KNOWLEDGE.md` Decision Index when routing contract changes.
33
34
34
-
See [ROUTING_CONTRACT R8](reflective-prompt-library/plans/ROUTING_CONTRACT.md) and the [Governance Maintenance Playbook](reflective-prompt-library/GLOSSARY.md).
35
+
See [ROUTING_CONTRACT](reflective-prompt-library/plans/ROUTING_CONTRACT.md) (R8–R12) and the [Governance Maintenance Playbook](reflective-prompt-library/GLOSSARY.md).
Copy file name to clipboardExpand all lines: reflective-prompt-library/GLOSSARY.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -337,7 +337,7 @@ Curated top-of-cheatsheet summary of high-confusion routing traps (ROUTE-002 hol
337
337
338
338
## Governance Maintenance Playbook / 治理維護手冊
339
339
340
-
Ongoing upkeep after panel close (Rounds 1–66). Not agent instructions — operator checklist.
340
+
Ongoing upkeep after panel close (Rounds 1–67). Not agent instructions — operator checklist.
341
341
342
342
**Operational test:** Before router tuning, add fresh ROUTE-002/003 holdout phrases; run `make validate`; record decisions in `PROJECT_KNOWLEDGE.md` Decision Index when governance surface changes.
343
343
@@ -347,4 +347,5 @@ Ongoing upkeep after panel close (Rounds 1–66). Not agent instructions — ope
347
347
4. Keep manual `benchmark_tasks.py` runs optional — fixture gate only in CI.
348
348
5. Reject tenth skill / full `SKILL.md` i18n unless promotion gate met (panel A, Q, W, AJ).
349
349
6. When cheatsheet boundary quick cues change, update `BOUNDARY_QUICK_CUE_*` markers and probe snippets in `test_validate_route_fixture.py`; run `test_cheatsheet_boundary_quick_cues.py`.
350
+
7. Keep `CONTRIBUTING.md` Routing Maintenance aligned with `ROUTING_CONTRACT.md` R8–R12 when boundaries or cheatsheet parity steps change.
follows the same holdout-before-tune rule. No open implementation blockers from Rounds 8–20;
@@ -81,6 +81,7 @@ deferred promotions are recurrence-gated — see [panel backlog](plans/multi-age
81
81
- 2026-06-18 Adopt STORM's source-grounded perspective discovery as an optional `reflective-research` method, not a new skill → [record](plans/storm-perspective-discovery-reflection-2026-06-18.md)
82
82
- 2026-06-20 Synthesize external-adoption case studies, then correct the evidence and promotion-gate scope after the Test Plan routing counterexample → [record](plans/external-adoption-case-studies-2026-06-20.md)
83
83
- 2026-06-21 Evaluate Hyperplan / multi-agent adversarial planning — no change (runtime = non-goal; methodology overlaps; possible gaps not promoted) → [record](plans/external-adoption-case-studies-2026-06-20.md)
0 commit comments