feat: Phase 2 - Normalisierung + Workflow Executor
Backend:
- normalization_engine.py (200 Zeilen): Synonym-Mapping, 5 Statuswerte
* normalize_decision_signal(): Kaskade (exact → case → synonym → invalid)
* apply_synonym_mapping(): DB-basierte Synonyme (case-insensitive)
* normalize_all_signals(): Batch-Processing gegen Katalog
* load_question_catalog(): Lädt normalization_rules aus DB
- workflow_executor.py (440 Zeilen): Sequenzielle Workflow-Ausführung
* execute_workflow(): Traversiert DAG in topologischer Reihenfolge
* execute_node(): Führt analysis nodes aus (start/end = no-op)
* aggregate_results(): Kombiniert analysis_core + normalized_signals
* save_execution_state(): Persistiert in workflow_executions
- workflow_models.py: Erweitert um Phase 2 Models
* SignalStatus Enum (valid, normalized, unclear, invalid, not_decidable)
* NormalizedSignal (question_type, raw_value, normalized_value, status)
* NodeExecutionState (node_id, status, analysis_core, normalized_signals)
* ExecutionResult (execution_id, workflow_id, status, node_states, aggregated_result)
- workflow_engine.py: Neue Funktion get_execution_order()
* Flattened topological sort für sequenzielle Execution
* Phase 7: Wird zu levels (parallele Execution)
- prompt_executor.py: execute_workflow_prompt() Implementierung
* Ruft workflow_executor.execute_workflow() auf
* Konvertiert ExecutionResult zu API-Response
- routers/workflows.py (230 Zeilen): Workflow Execution API
* POST /api/workflows/{id}/execute (mit enable_debug)
* GET /api/workflows/executions/{id} (lädt gespeicherten State)
* GET /api/workflows (listet alle aktiven Workflows)
* GET /api/workflows/{id} (lädt einzelnen Workflow mit Graph)
- main.py: Router-Registrierung (workflows.router)
Tests:
- test_phase2_normalization.py (17 Tests): Alle Normalisierungs-Szenarien
* Exact match, case-insensitive, synonym mapping, invalid, whitespace
* Batch-Normalisierung, not_in_catalog, mixed validity
- test_phase2_workflow_executor.py (10 Tests): Executor + Aggregation
* aggregate_results mit verschiedenen Konstellationen
* execute_node für start/end/analysis/unknown
* Integration mit question_augmenter + result_container_parser
Alle 27 Unit-Tests bestanden.
version: 0.9k (backend)
module: workflow 0.3.0
Konzept: .claude/task/Workflow_engine_prompting_engine/anforderungsanalyse_umsetzungsplan.md (Phase 2)
This commit is contained in:
1 parent
ca562b7130
commit
1f8791f4dd
10 files changed
+1591
-19
No files matched your search
@@ -391,3 +391,37 @@ def validate_workflow_graph(graph: WorkflowGraph) -> Tuple[bool, List[str]]:
|
||||
return False, errors
|
||||
except Exception as e:
|
||||
return False, [f"Unerwarteter Fehler: {str(e)}"]
|
||||
|
||||
|
||||
def get_execution_order(graph: WorkflowGraph) -> List[str]:
|
||||
"""
|
||||
Berechne sequenzielle Ausführungs-Reihenfolge (Phase 2).
|
||||
|
||||
Phase 2: Sequenziell (flattened topological sort).
|
||||
Phase 7: Parallele Execution (levels statt flat list).
|
||||
|
||||
Args:
|
||||
graph: Workflow-Graph
|
||||
|
||||
Returns:
|
||||
Liste von Knoten-IDs in Ausführungsreihenfolge
|
||||
Beispiel: ["start", "node_1", "node_2", "end"]
|
||||
|
||||
Raises:
|
||||
HTTPException: Bei ungültigem Graph
|
||||
|
||||
Beispiel:
|
||||
>>> from workflow_models import WorkflowGraph, WorkflowNode, WorkflowEdge
|
||||
>>> graph = WorkflowGraph(
|
||||
... nodes=[
|
||||
... WorkflowNode(id="start", type="start"),
|
||||
... WorkflowNode(id="end", type="end")
|
||||
... ],
|
||||
... edges=[WorkflowEdge(id="e1", from_node="start", to_node="end")]
|
||||
... )
|
||||
>>> get_execution_order(graph)
|
||||
['start', 'end']
|
||||
"""
|
||||
engine = WorkflowEngine(graph)
|
||||
# Nutze Validator's topological_order (flattened)
|
||||
return engine.validator.topological_order
|
||||
Reference in new issue
Block a user