Benjamin_Boenisch/breakpilot-core
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(pipeline): use action_type-derived phase order in ontology generator

Browse Source 
LLM merge_key phases (e.g. "submission") don't always match PHASE_ORDER
keys. Derive phase order from action_type via get_phase_order() instead.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Benjamin Admin
2026-04-26 20:32:58 +02:00
parent 42ab5ead26
commit 96b8f25747
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
control-pipeline/services/dependency_generator.py
View File

@@ -26,7 +26,7 @@ logger = logging.getLogger(__name__)
# PHASE ORDERING (imported from ontology)
# ============================================================================
from services.control_ontology import PHASE_ORDER
from services.control_ontology import PHASE_ORDER, get_phase, get_phase_order
# ============================================================================
@@ -142,7 +142,8 @@ def generate_ontology_dependencies(controls: list[dict]) -> list[Dependency]:
obj = parsed["normalized_object"]
if obj:
ctrl["_parsed_mk"] = parsed
ctrl["_phase_order"] = PHASE_ORDER.get(parsed["phase"], 6)
# Use action_type to derive phase order (more reliable than LLM phase name)
ctrl["_phase_order"] = get_phase_order(parsed["action_type"])
groups[obj].append(ctrl)
dependencies: list[Dependency] = []