fix(orchestration): preserve conditional knowledge escalation

Author: Ldsystem

references/assets/orchestration/contract/specification-v1.md

@@ -105,7 +105,7 @@ impact_decisions:
 
 Every material relation has exactly one `accepted | excluded | blocking` disposition. `projects_to` is required for accepted relations and must name stable requirements, constraints, interfaces, acceptance criteria, or validation targets. Excluded relations require evidence and a concise reason; "the user did not mention it" is not sufficient. Blocking relations create blocking Open Questions and keep the quality gate blocked.
 
-Use `none_relevant` only after a bounded scan finds no material relation and records its searched boundary, reason, and `stopping_reason`. Stop when every frontier relation is immaterial, already projected, excluded with evidence, or blocked for authority. Escalate to targeted Git history, prior work artifacts, or execution evidence only for contradictory current-state evidence, unresolved ownership, material regression/causality, or a suspected governing legacy decision; do not require full-history archaeology by default.
+Use `none_relevant` only after a bounded scan finds no material relation and records its searched boundary, reason, and `stopping_reason`. Stop when every frontier relation is immaterial, already projected, excluded with evidence, or blocked for authority. Escalate to targeted Git history, prior work artifacts, execution evidence, or durable knowledge only for contradictory current-state evidence, unresolved ownership, material regression/causality, or a suspected governing legacy decision; do not require full-history archaeology or broad knowledge retrieval by default.
 
 ## 5. Requirements, Constraints & Guidelines
 

references/assets/orchestration/workflow.md

@@ -114,7 +114,7 @@ Final review aggregates accepted task dispositions from execution and task-revie
 
 Only approved keep-summarizing owners write durable knowledge. Final orchestration review owns approved persistence delegation and may invoke that owner, then validate returned paths or an evidence-backed no-write result; executors and orchestration itself must not write knowledge directly.
 
-Specification authoring materializes `impact_decisions` from bounded current-state evidence about the requested surface, upstream/downstream relations, validation surfaces, and relevant dirty work. Each material relation is `accepted | excluded | blocking`: accepted relations use `projects_to` for stable specification IDs, excluded relations require evidence, and blocking relations prevent verification. A greenfield result may use `none_relevant` only with the searched boundary, reason, and `stopping_reason`. Targeted Git history, prior work artifacts, or execution evidence is an escalation for contradiction, unresolved ownership, material regression/causality, or suspected governing legacy decisions—not mandatory full-history archaeology. This impact-decision view is compared by semantic convergence; repository traversal remains owned by specification authoring.
+Specification authoring materializes `impact_decisions` from bounded current-state evidence about the requested surface, upstream/downstream relations, validation surfaces, and relevant dirty work. Each material relation is `accepted | excluded | blocking`: accepted relations use `projects_to` for stable specification IDs, excluded relations require evidence, and blocking relations prevent verification. A greenfield result may use `none_relevant` only with the searched boundary, reason, and `stopping_reason`. Targeted Git history, prior work artifacts, execution evidence, or durable knowledge is an escalation for contradiction, unresolved ownership, material regression/causality, or suspected governing legacy decisions—not mandatory full-history archaeology or broad knowledge retrieval. This impact-decision view is compared by semantic convergence; repository traversal remains owned by specification authoring.
 
 ## Lightweight development lane
 

skills/orch-create-specification/SKILL.md

@@ -16,7 +16,7 @@ Create the smallest authoritative specification under `.work-bundle/orchestratio
 3. Through `ks-what-is-helpful`, discover with polarity-neutral and stage/perspective/status-neutral query anchors. `implementation_spec` is classification and output-grouping intent, not a discovery-stage lifecycle filter.
 4. Classify results as authority, candidate, background, or blocked. Only authority shapes requirements and only accepted authority enters front-matter `source_knowledge` as `path` plus the already-reconciled `constraint`; keep candidate, background, blocked, superseded, supporting, opposing, constraining, unresolved/open-question, obsolete, and irrelevant-with-reason evidence in Source Context when material. Downstream planning allocates `AUTH-NNN` aliases from the accepted list so execution does not require `.work-bundle/knowledge/` reads or expose knowledge paths.
 5. Build one bounded current-state impact basis from the requested surface, material upstream dependencies or producers, downstream consumers, validation/test surfaces, and relevant dirty work. Record `impact_decisions` and give each material relation exactly one disposition: `accepted | excluded | blocking`. An accepted relation must use `projects_to` to name stable requirement, constraint, interface, acceptance-criterion, or validation-target IDs. An excluded relation requires evidence and a reason stronger than user omission. A blocking relation creates a blocking open question. When no material relation exists, record `none_relevant` with the searched boundary, reason, and `stopping_reason`.
-6. Stop current-state traversal when every frontier relation is immaterial, already projected to a stable ID, excluded with evidence, or blocked for authority. Escalate to targeted Git history, prior work artifacts, or execution evidence only when current-state evidence is contradictory, ownership is unresolved, regression or causality is material, or a governing legacy decision is suspected. Do not require full-history archaeology by default. For WorkBundle scope, include related active violations by ID, severity, deviation, scope, required resolution, and expected review closure. Exact-current-work conflicts may remain specification-owned.
+6. Stop current-state traversal when every frontier relation is immaterial, already projected to a stable ID, excluded with evidence, or blocked for authority. Escalate to targeted Git history, prior work artifacts, execution evidence, or durable knowledge only when current-state evidence is contradictory, ownership is unresolved, regression or causality is material, or a governing legacy decision is suspected. Do not require full-history archaeology or broad knowledge retrieval by default. For WorkBundle scope, include related active violations by ID, severity, deviation, scope, required resolution, and expected review closure. Exact-current-work conflicts may remain specification-owned.
 7. Ask Design Interrogation questions only for unresolved intent that changes requirements, architecture, workflow, API, persistence, validation, execution safety, or user purpose. Evidence class alone does not make an open question blocking.
 8. Normalize stable IDs, requirements, constraints, interfaces, acceptance criteria, decisions, open questions, and Knowledge Base Update disposition.
 9. Decide execution-workspace policy without provisioning it:

tests/test_orchestration_workflow_contracts.py

@@ -345,9 +345,14 @@ def test_specification_contract_requires_bounded_impact_decisions() -> None:
             "dirty work",
         ]:
             assert token in text
+        assert "durable knowledge" in text
+        assert "projects_to" in text and "stable" in text
+    for text in (contract, skill):
+        assert "blocking" in text and "open question" in text.lower()
+    assert "blocking relations prevent verification" in workflow
     assert "impact-decision view" in skill
     assert "keep repository traversal out of `dev-semantic-convergence`" in skill
-    assert "Git history, prior work artifacts, or execution evidence" in skill
+    assert "Git history, prior work artifacts, execution evidence, or durable knowledge" in skill
     assert "user did not mention" in contract
     assert "existing downstream consumer" in evals
     assert "greenfield isolated utility" in evals