From 8e42a59b981e7e8fd49e44197ef26c6972ece68d Mon Sep 17 00:00:00 2001 From: Alex Clarke Date: Sun, 13 Sep 2026 11:29:31 -0600 Subject: [PATCH] docs(adversary): fix mermaid node label and criterion_fault join edge Node B is the graph's `facts` node (script diff_facts.py), not a node named diff_facts. criterion_fault has no `next`; it reaches holistic through the map join, so draw it dashed like the other branch-terminal edges instead of as a solid successor edge. --- assets/agents/adversary/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/assets/agents/adversary/README.md b/assets/agents/adversary/README.md index 130cf92..3332c55 100644 --- a/assets/agents/adversary/README.md +++ b/assets/agents/adversary/README.md @@ -66,7 +66,7 @@ violation) and cites `file:line`. Vague complaints are not emitted. ```mermaid flowchart TD - A["parse (llm): extract acceptance criteria + declared verification commands"] --> B["diff_facts (script): resolve + bound the diff"] + A["parse (llm): extract acceptance criteria + declared verification commands"] --> B["facts (diff_facts.py): resolve + bound the diff"] B --> R["run_checks (script): run the declared verification commands ONCE, record results"] R --> C["map over criteria: one fresh-context branch each (parallel)"] C --> D["check_criterion (llm + fs/ast tools)"] @@ -79,7 +79,7 @@ flowchart TD B -. "fallback" .-> P R -. "fallback" .-> P D -. "fallback" .-> CF["criterion_fault (script): UNMET + PIPELINE-FAULT evidence for that ONE criterion"] - CF --> F + CF -. "map join" .-> F F -. "fallback" .-> G P --> G ```