diff --git a/edge-cases/edge-cases/missing-labels-workflow/README.md b/edge-cases/edge-cases/missing-labels-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..460683b49f7d964c2aeb94de6abc431847917b23
--- /dev/null
+++ b/edge-cases/edge-cases/missing-labels-workflow/README.md
@@ -0,0 +1,19 @@
+# Missing Labels Workflow
+
+This workflow models nodes without label parameters.
+
+**Template ID:** `missing-labels-workflow`  
+**Kind:** workflow  
+**Source domain:** edge-cases  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 4/5  
+**Nodes:** 13  
+**Lanes:** 4  
+**Tags:** [missing, labels, decision]  
+**Source path:** `edge-cases/missing-labels`  
+**Repo path:** `edge-cases/edge-cases/missing-labels-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/edge-cases/missing-labels-workflow/workflow.fz b/edge-cases/edge-cases/missing-labels-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..4ff3161af2c7536ec71c8c07a477bf0583329bbd
--- /dev/null
+++ b/edge-cases/edge-cases/missing-labels-workflow/workflow.fz
@@ -0,0 +1,38 @@
+laneA { # Lanea
+  n1: circle label:"Start Missing Labels"
+  n2: diamond
+  n5: rectangle label:"Missing Labels step 5"
+  n9: rectangle label:"Missing Labels step 9"
+  n13: circle label:"End Missing Labels"
+
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(bottom) -> laneC.n3.handle(top) [label="Yes/Approved"]
+  n2.handle(bottom) -> laneD.n4.handle(top) [label="No/Rejected"]
+  n5.handle(bottom) -> laneB.n6.handle(top)
+  n9.handle(bottom) -> laneB.n10.handle(top)
+}
+laneB { # Laneb
+  n6: rectangle label:"Missing Labels step 6"
+  n10: rectangle label:"Missing Labels step 10"
+
+  n6.handle(bottom) -> laneC.n7.handle(top)
+  n10.handle(bottom) -> laneC.n11.handle(top)
+}
+laneC { # Lanec
+  n3: rectangle
+  n7: rectangle label:"Missing Labels step 7"
+  n11: rectangle label:"Missing Labels step 11"
+
+  n3.handle(bottom) -> laneA.n5.handle(top)
+  n7.handle(bottom) -> laneD.n8.handle(top)
+  n11.handle(bottom) -> laneD.n12.handle(top)
+}
+laneD { # Laned
+  n4: rectangle label:"Missing Labels step 4"
+  n8: rectangle label:"Missing Labels step 8"
+  n12: rectangle label:"Missing Labels step 12"
+
+  n4.handle(bottom) -> laneA.n5.handle(top)
+  n8.handle(bottom) -> laneA.n9.handle(top)
+  n12.handle(bottom) -> laneA.n13.handle(top)
+}
\ No newline at end of file
diff --git a/edge-cases/edge-cases/orphan-node-workflow/README.md b/edge-cases/edge-cases/orphan-node-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..02c51bfa89f80c461f476fd69aae103396e4e330
--- /dev/null
+++ b/edge-cases/edge-cases/orphan-node-workflow/README.md
@@ -0,0 +1,19 @@
+# Orphan Node Workflow
+
+This workflow models a node with no connections.
+
+**Template ID:** `orphan-node-workflow`  
+**Kind:** workflow  
+**Source domain:** edge-cases  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 1/5  
+**Nodes:** 5  
+**Lanes:** 1  
+**Tags:** [orphan, node]  
+**Source path:** `edge-cases/orphan-node`  
+**Repo path:** `edge-cases/edge-cases/orphan-node-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/edge-cases/orphan-node-workflow/metadata.json b/edge-cases/edge-cases/orphan-node-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..ce049a936bbccab036e1a04e8ddf90a00471a2b9
--- /dev/null
+++ b/edge-cases/edge-cases/orphan-node-workflow/metadata.json
@@ -0,0 +1,22 @@
+{
+  "template_id": "orphan-node-workflow",
+  "workflow_id": "orphan-node",
+  "title": "Orphan Node Workflow",
+  "kind": "workflow",
+  "source_domain": "edge-cases",
+  "primary_use_case": "edge-cases",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "edge-cases"
+  ],
+  "complexity": 1,
+  "num_nodes": 5,
+  "num_lanes": 1,
+  "tags": [
+    "orphan",
+    "node"
+  ],
+  "description": "This workflow models a node with no connections.",
+  "source_path": "edge-cases/orphan-node",
+  "repo_path": "edge-cases/edge-cases/orphan-node-workflow"
+}
diff --git a/edge-cases/edge-cases/orphan-node-workflow/workflow.fz b/edge-cases/edge-cases/orphan-node-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..a23da3ee63e2877c08b7ffea0cd7b7579fa71d86
--- /dev/null
+++ b/edge-cases/edge-cases/orphan-node-workflow/workflow.fz
@@ -0,0 +1,13 @@
+laneA { # Lanea
+  n1: circle label:"Start Orphan Node"
+  n2: rectangle label:"Orphan Node step 2"
+  n3: diamond label:"Orphan Node step 3"
+  n4: rectangle label:"Orphan Node step 4"
+  n5: circle label:"End Orphan Node"
+
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left) [label="Next"]
+  n3.handle(right) -> n4.handle(left)
+  n3.handle(bottom) -> n2.handle(bottom) [label="Retry/Rejected"]
+  n4.handle(right) -> n5.handle(left)
+}
\ No newline at end of file
diff --git a/edge-cases/edge-cases/sql-injection-label-workflow/README.md b/edge-cases/edge-cases/sql-injection-label-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..9bd9b7a59e6e3f2985381c5fdaf7ffdca2cf0086
--- /dev/null
+++ b/edge-cases/edge-cases/sql-injection-label-workflow/README.md
@@ -0,0 +1,19 @@
+# Sql Injection Label Workflow
+
+This workflow models a label that looks like an SQL injection attempt.
+
+**Template ID:** `sql-injection-label-workflow`  
+**Kind:** workflow  
+**Source domain:** edge-cases  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 2/5  
+**Nodes:** 7  
+**Lanes:** 2  
+**Tags:** [sql, injection, label]  
+**Source path:** `edge-cases/sql-injection-label`  
+**Repo path:** `edge-cases/edge-cases/sql-injection-label-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/edge-cases/sql-injection-label-workflow/metadata.json b/edge-cases/edge-cases/sql-injection-label-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..c2cdfa4686c56dd2e096311293d47ec9a7776fc9
--- /dev/null
+++ b/edge-cases/edge-cases/sql-injection-label-workflow/metadata.json
@@ -0,0 +1,23 @@
+{
+  "template_id": "sql-injection-label-workflow",
+  "workflow_id": "sql-injection-label",
+  "title": "Sql Injection Label Workflow",
+  "kind": "workflow",
+  "source_domain": "edge-cases",
+  "primary_use_case": "edge-cases",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "edge-cases"
+  ],
+  "complexity": 2,
+  "num_nodes": 7,
+  "num_lanes": 2,
+  "tags": [
+    "sql",
+    "injection",
+    "label"
+  ],
+  "description": "This workflow models a label that looks like an SQL injection attempt.",
+  "source_path": "edge-cases/sql-injection-label",
+  "repo_path": "edge-cases/edge-cases/sql-injection-label-workflow"
+}
diff --git a/edge-cases/edge-cases/sql-injection-label-workflow/workflow.fz b/edge-cases/edge-cases/sql-injection-label-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..1c8deae05fb5e7b1ede067fd4aaa1aa6b70021dd
--- /dev/null
+++ b/edge-cases/edge-cases/sql-injection-label-workflow/workflow.fz
@@ -0,0 +1,19 @@
+laneA { # Lanea
+  n1: circle label:"Start Sql Injection Label"
+  n3: rectangle label:"Sql Injection Label step 3"
+  n5: rectangle label:"Sql Injection Label step 5"
+  n7: circle label:"End Sql Injection Label"
+
+  n1.handle(bottom) -> laneB.n2.handle(top)
+  n3.handle(bottom) -> laneB.n4.handle(top) [label="Processed"]
+  n5.handle(bottom) -> laneB.n6.handle(top)
+}
+laneB { # Laneb
+  n2: rectangle label:"SELECT * FROM users WHERE name='admin' OR 1=1; --"
+  n4: rectangle label:"Sql Injection Label step 4"
+  n6: rectangle label:"Sql Injection Label step 6"
+
+  n2.handle(bottom) -> laneA.n3.handle(top)
+  n4.handle(bottom) -> laneA.n5.handle(top)
+  n6.handle(bottom) -> laneA.n7.handle(top) [label="Success"]
+}
\ No newline at end of file
diff --git a/edge-cases/edge-cases/unicode-labels-workflow/README.md b/edge-cases/edge-cases/unicode-labels-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..96cad6d4557062d60b7c57cd9aef22c988c8dc29
--- /dev/null
+++ b/edge-cases/edge-cases/unicode-labels-workflow/README.md
@@ -0,0 +1,19 @@
+# Unicode Labels Workflow
+
+This workflow models emoji and international characters in labels.
+
+**Template ID:** `unicode-labels-workflow`  
+**Kind:** workflow  
+**Source domain:** edge-cases  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 1/5  
+**Nodes:** 5  
+**Lanes:** 1  
+**Tags:** [unicode, labels]  
+**Source path:** `edge-cases/unicode-labels`  
+**Repo path:** `edge-cases/edge-cases/unicode-labels-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/edge-cases/unicode-labels-workflow/metadata.json b/edge-cases/edge-cases/unicode-labels-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..fe0431ace0e7d4d81c2fa9ddf427be2f6a307467
--- /dev/null
+++ b/edge-cases/edge-cases/unicode-labels-workflow/metadata.json
@@ -0,0 +1,22 @@
+{
+  "template_id": "unicode-labels-workflow",
+  "workflow_id": "unicode-labels",
+  "title": "Unicode Labels Workflow",
+  "kind": "workflow",
+  "source_domain": "edge-cases",
+  "primary_use_case": "edge-cases",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "edge-cases"
+  ],
+  "complexity": 1,
+  "num_nodes": 5,
+  "num_lanes": 1,
+  "tags": [
+    "unicode",
+    "labels"
+  ],
+  "description": "This workflow models emoji and international characters in labels.",
+  "source_path": "edge-cases/unicode-labels",
+  "repo_path": "edge-cases/edge-cases/unicode-labels-workflow"
+}
diff --git a/edge-cases/edge-cases/unicode-labels-workflow/workflow.fz b/edge-cases/edge-cases/unicode-labels-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..0b6d52c171b088cca5b4ba403e9c716cb9f441d1
--- /dev/null
+++ b/edge-cases/edge-cases/unicode-labels-workflow/workflow.fz
@@ -0,0 +1,12 @@
+laneA { # Lanea
+  n1: circle label:"Start Unicode Labels"
+  n2: rectangle label:"Unicode label (rocket)"
+  n3: rectangle label:"多言語ラベル"
+  n4: rectangle label:"Unicode Labels step 4"
+  n5: circle label:"End Unicode Labels"
+
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left) [label="Next"]
+  n3.handle(right) -> n4.handle(left)
+  n4.handle(right) -> n5.handle(left)
+}
\ No newline at end of file
diff --git a/edge-cases/edge-cases/very-long-label-workflow/README.md b/edge-cases/edge-cases/very-long-label-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..daeb839a67aaa12ac759388c30fa8763077ebdec
--- /dev/null
+++ b/edge-cases/edge-cases/very-long-label-workflow/README.md
@@ -0,0 +1,19 @@
+# Very Long Label Workflow
+
+This workflow models labels with very long text.
+
+**Template ID:** `very-long-label-workflow`  
+**Kind:** workflow  
+**Source domain:** edge-cases  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 1/5  
+**Nodes:** 5  
+**Lanes:** 1  
+**Tags:** [very, long, label, decision, loop]  
+**Source path:** `edge-cases/very-long-label`  
+**Repo path:** `edge-cases/edge-cases/very-long-label-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/edge-cases/very-long-label-workflow/metadata.json b/edge-cases/edge-cases/very-long-label-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..d1acc76ea1e1eae819146ea03669125848249173
--- /dev/null
+++ b/edge-cases/edge-cases/very-long-label-workflow/metadata.json
@@ -0,0 +1,25 @@
+{
+  "template_id": "very-long-label-workflow",
+  "workflow_id": "very-long-label",
+  "title": "Very Long Label Workflow",
+  "kind": "workflow",
+  "source_domain": "edge-cases",
+  "primary_use_case": "edge-cases",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "edge-cases"
+  ],
+  "complexity": 1,
+  "num_nodes": 5,
+  "num_lanes": 1,
+  "tags": [
+    "very",
+    "long",
+    "label",
+    "decision",
+    "loop"
+  ],
+  "description": "This workflow models labels with very long text.",
+  "source_path": "edge-cases/very-long-label",
+  "repo_path": "edge-cases/edge-cases/very-long-label-workflow"
+}
diff --git a/edge-cases/edge-cases/very-long-label-workflow/workflow.fz b/edge-cases/edge-cases/very-long-label-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..19cf0b3289f8a210f2730e35f9257dc1af84eedb
--- /dev/null
+++ b/edge-cases/edge-cases/very-long-label-workflow/workflow.fz
@@ -0,0 +1,14 @@
+laneA { # Lanea
+  n1: circle label:"Start Very Long Label"
+  n2: diamond label:"Very long label for demonstration for demonstration for demonstration for demonstration for demonstration for demonstration for demonstration for demonstration "
+  n3: rectangle label:"Very Long Label step 3"
+  n4: rectangle label:"Very Long Label step 4"
+  n5: circle label:"End Very Long Label"
+
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left) [label="Yes/Approved"]
+  n2.handle(bottom) -> n4.handle(top) [label="No/Rejected"]
+  n3.handle(right) -> n5.handle(left)
+  n4.handle(right) -> n5.handle(left)
+  loop [retry until success] n2 n3 n4
+}
\ No newline at end of file
diff --git a/edge-cases/edge-cases/xml-in-label-workflow/README.md b/edge-cases/edge-cases/xml-in-label-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..c144a5181f37a70a845ca592c6122ddd9d2c004c
--- /dev/null
+++ b/edge-cases/edge-cases/xml-in-label-workflow/README.md
@@ -0,0 +1,19 @@
+# Xml In Label Workflow
+
+This workflow models a label that contains XML text.
+
+**Template ID:** `xml-in-label-workflow`  
+**Kind:** workflow  
+**Source domain:** edge-cases  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 5/5  
+**Nodes:** 16  
+**Lanes:** 4  
+**Tags:** [xml, in, label]  
+**Source path:** `edge-cases/xml-in-label`  
+**Repo path:** `edge-cases/edge-cases/xml-in-label-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/edge-cases/xml-in-label-workflow/metadata.json b/edge-cases/edge-cases/xml-in-label-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..3df88cac460bbbc2f3f9c0b6ea92ad928d320e27
--- /dev/null
+++ b/edge-cases/edge-cases/xml-in-label-workflow/metadata.json
@@ -0,0 +1,23 @@
+{
+  "template_id": "xml-in-label-workflow",
+  "workflow_id": "xml-in-label",
+  "title": "Xml In Label Workflow",
+  "kind": "workflow",
+  "source_domain": "edge-cases",
+  "primary_use_case": "edge-cases",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "edge-cases"
+  ],
+  "complexity": 5,
+  "num_nodes": 16,
+  "num_lanes": 4,
+  "tags": [
+    "xml",
+    "in",
+    "label"
+  ],
+  "description": "This workflow models a label that contains XML text.",
+  "source_path": "edge-cases/xml-in-label",
+  "repo_path": "edge-cases/edge-cases/xml-in-label-workflow"
+}
diff --git a/edge-cases/edge-cases/xml-in-label-workflow/workflow.fz b/edge-cases/edge-cases/xml-in-label-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..ed74b623f673f8c1d7516e6151e1ad262dca9e4c
--- /dev/null
+++ b/edge-cases/edge-cases/xml-in-label-workflow/workflow.fz
@@ -0,0 +1,44 @@
+laneA { # Lanea
+  n1: circle label:"Start Xml In Label"
+  n5: rectangle label:"Xml In Label step 5"
+  n9: rectangle label:"Xml In Label step 9"
+  n13: rectangle label:"Xml In Label step 13"
+
+  n1.handle(bottom) -> laneB.n2.handle(top) [label="Success"]
+  n5.handle(bottom) -> laneB.n6.handle(top)
+  n9.handle(bottom) -> laneB.n10.handle(top)
+  n13.handle(bottom) -> laneB.n14.handle(top) [label="Processed"]
+}
+laneB { # Laneb
+  n2: rectangle label:"<note><to>User</to><body>Example</body></note>"
+  n6: rectangle label:"Xml In Label step 6"
+  n10: rectangle label:"Xml In Label step 10"
+  n14: rectangle label:"Xml In Label step 14"
+
+  n2.handle(bottom) -> laneC.n3.handle(top)
+  n6.handle(bottom) -> laneC.n7.handle(top)
+  n10.handle(bottom) -> laneC.n11.handle(top) [label="Done"]
+  n14.handle(bottom) -> laneC.n15.handle(top)
+}
+laneC { # Lanec
+  n3: rectangle label:"Xml In Label step 3"
+  n7: rectangle label:"Xml In Label step 7"
+  n11: rectangle label:"Xml In Label step 11"
+  n15: rectangle label:"Xml In Label step 15"
+
+  n3.handle(bottom) -> laneD.n4.handle(top)
+  n7.handle(bottom) -> laneD.n8.handle(top) [label="Next"]
+  n11.handle(bottom) -> laneD.n12.handle(top)
+  n15.handle(bottom) -> laneD.n16.handle(top)
+}
+laneD { # Laned
+  n4: rectangle label:"Xml In Label step 4"
+  n8: diamond label:"Xml In Label step 8"
+  n12: rectangle label:"Xml In Label step 12"
+  n16: circle label:"End Xml In Label"
+
+  n4.handle(bottom) -> laneA.n5.handle(top) [label="Valid"]
+  n8.handle(bottom) -> laneA.n9.handle(top)
+  n8.handle(right) -> laneC.n7.handle(right) [label="Retry/Rejected"]
+  n12.handle(bottom) -> laneA.n13.handle(top)
+}
\ No newline at end of file
diff --git a/edge-cases/edge-cases/xss-label-workflow/README.md b/edge-cases/edge-cases/xss-label-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f3d232d5a6bfbafb61a6562c0818db58cc09052
--- /dev/null
+++ b/edge-cases/edge-cases/xss-label-workflow/README.md
@@ -0,0 +1,19 @@
+# Xss Label Workflow
+
+This workflow models a label that looks like an XSS script.
+
+**Template ID:** `xss-label-workflow`  
+**Kind:** workflow  
+**Source domain:** edge-cases  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [xss, label]  
+**Source path:** `edge-cases/xss-label`  
+**Repo path:** `edge-cases/edge-cases/xss-label-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/edge-cases/xss-label-workflow/metadata.json b/edge-cases/edge-cases/xss-label-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..d702c02462a5d29ebe28856d2997e73e29f9aa5a
--- /dev/null
+++ b/edge-cases/edge-cases/xss-label-workflow/metadata.json
@@ -0,0 +1,22 @@
+{
+  "template_id": "xss-label-workflow",
+  "workflow_id": "xss-label",
+  "title": "Xss Label Workflow",
+  "kind": "workflow",
+  "source_domain": "edge-cases",
+  "primary_use_case": "edge-cases",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "edge-cases"
+  ],
+  "complexity": 3,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "xss",
+    "label"
+  ],
+  "description": "This workflow models a label that looks like an XSS script.",
+  "source_path": "edge-cases/xss-label",
+  "repo_path": "edge-cases/edge-cases/xss-label-workflow"
+}
diff --git a/edge-cases/edge-cases/xss-label-workflow/workflow.fz b/edge-cases/edge-cases/xss-label-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..4728565c950ad057f72ec687047c44acec6e8a78
--- /dev/null
+++ b/edge-cases/edge-cases/xss-label-workflow/workflow.fz
@@ -0,0 +1,29 @@
+laneA { # Lanea
+  n1: circle label:"Start Xss Label"
+  n4: rectangle label:"Xss Label step 4"
+  n7: diamond label:"Xss Label step 7"
+  n10: circle label:"End Xss Label"
+
+  n1.handle(bottom) -> laneB.n2.handle(top) [label="Success"]
+  n4.handle(bottom) -> laneB.n5.handle(top) [label="Valid"]
+  n7.handle(bottom) -> laneB.n8.handle(top) [label="Next"]
+  n7.handle(right) -> laneC.n6.handle(right) [label="Retry/Rejected"]
+}
+laneB { # Laneb
+  n2: rectangle label:"<script>alert('xss')</script>"
+  n5: rectangle label:"Xss Label step 5"
+  n8: rectangle label:"Xss Label step 8"
+
+  n2.handle(bottom) -> laneC.n3.handle(top)
+  n5.handle(bottom) -> laneC.n6.handle(top)
+  n8.handle(bottom) -> laneC.n9.handle(top)
+}
+laneC { # Lanec
+  n3: rectangle label:"Xss Label step 3"
+  n6: rectangle label:"Xss Label step 6"
+  n9: rectangle label:"Xss Label step 9"
+
+  n3.handle(bottom) -> laneA.n4.handle(top)
+  n6.handle(bottom) -> laneA.n7.handle(top)
+  n9.handle(bottom) -> laneA.n10.handle(top)
+}
\ No newline at end of file
diff --git a/edge-cases/syntax-primitives/16-max-nodes-workflow/README.md b/edge-cases/syntax-primitives/16-max-nodes-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..ffd361ec6e275752d7cf2ea4750a6f7c108bf15b
--- /dev/null
+++ b/edge-cases/syntax-primitives/16-max-nodes-workflow/README.md
@@ -0,0 +1,19 @@
+# 16 Max Nodes Workflow
+
+This workflow models 50 nodes in one lane as a stress test.
+
+**Template ID:** `16-max-nodes-workflow`  
+**Kind:** workflow  
+**Source domain:** syntax-primitives  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 2/5  
+**Nodes:** 50  
+**Lanes:** 2  
+**Tags:** [16, max, nodes]  
+**Source path:** `syntax-primitives/16-max-nodes`  
+**Repo path:** `edge-cases/syntax-primitives/16-max-nodes-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/syntax-primitives/16-max-nodes-workflow/metadata.json b/edge-cases/syntax-primitives/16-max-nodes-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..1eb157c510c187254f953f91b4766a11e7576f92
--- /dev/null
+++ b/edge-cases/syntax-primitives/16-max-nodes-workflow/metadata.json
@@ -0,0 +1,23 @@
+{
+  "template_id": "16-max-nodes-workflow",
+  "workflow_id": "16-max-nodes",
+  "title": "16 Max Nodes Workflow",
+  "kind": "workflow",
+  "source_domain": "syntax-primitives",
+  "primary_use_case": "edge-cases",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "edge-cases"
+  ],
+  "complexity": 2,
+  "num_nodes": 50,
+  "num_lanes": 2,
+  "tags": [
+    "16",
+    "max",
+    "nodes"
+  ],
+  "description": "This workflow models 50 nodes in one lane as a stress test.",
+  "source_path": "syntax-primitives/16-max-nodes",
+  "repo_path": "edge-cases/syntax-primitives/16-max-nodes-workflow"
+}
diff --git a/edge-cases/syntax-primitives/16-max-nodes-workflow/workflow.fz b/edge-cases/syntax-primitives/16-max-nodes-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..23770289943742ec87d84982ebd68131c9a43868
--- /dev/null
+++ b/edge-cases/syntax-primitives/16-max-nodes-workflow/workflow.fz
@@ -0,0 +1,104 @@
+laneA { # Lane A
+  n1: circle label:"Start 16 Max Nodes"
+  n3: rectangle label:"16 Max Nodes step 3"
+  n5: rectangle label:"16 Max Nodes step 5"
+  n7: rectangle label:"16 Max Nodes step 7"
+  n9: rectangle label:"16 Max Nodes step 9"
+  n11: rectangle label:"16 Max Nodes step 11"
+  n13: rectangle label:"16 Max Nodes step 13"
+  n15: rectangle label:"16 Max Nodes step 15"
+  n17: rectangle label:"16 Max Nodes step 17"
+  n19: rectangle label:"16 Max Nodes step 19"
+  n21: rectangle label:"16 Max Nodes step 21"
+  n23: rectangle label:"16 Max Nodes step 23"
+  n25: rectangle label:"16 Max Nodes step 25"
+  n27: rectangle label:"16 Max Nodes step 27"
+  n29: rectangle label:"16 Max Nodes step 29"
+  n31: rectangle label:"16 Max Nodes step 31"
+  n33: rectangle label:"16 Max Nodes step 33"
+  n35: rectangle label:"16 Max Nodes step 35"
+  n37: rectangle label:"16 Max Nodes step 37"
+  n39: rectangle label:"16 Max Nodes step 39"
+  n41: rectangle label:"16 Max Nodes step 41"
+  n43: rectangle label:"16 Max Nodes step 43"
+  n45: rectangle label:"16 Max Nodes step 45"
+  n47: rectangle label:"16 Max Nodes step 47"
+  n49: rectangle label:"16 Max Nodes step 49"
+  n1.handle(bottom) -> laneB.n2.handle(top)
+  n3.handle(bottom) -> laneB.n4.handle(top)
+  n5.handle(bottom) -> laneB.n6.handle(top)
+  n7.handle(bottom) -> laneB.n8.handle(top)
+  n9.handle(bottom) -> laneB.n10.handle(top)
+  n11.handle(bottom) -> laneB.n12.handle(top)
+  n13.handle(bottom) -> laneB.n14.handle(top)
+  n15.handle(bottom) -> laneB.n16.handle(top)
+  n17.handle(bottom) -> laneB.n18.handle(top)
+  n19.handle(bottom) -> laneB.n20.handle(top)
+  n21.handle(bottom) -> laneB.n22.handle(top)
+  n23.handle(bottom) -> laneB.n24.handle(top)
+  n25.handle(bottom) -> laneB.n26.handle(top)
+  n27.handle(bottom) -> laneB.n28.handle(top)
+  n29.handle(bottom) -> laneB.n30.handle(top)
+  n31.handle(bottom) -> laneB.n32.handle(top)
+  n33.handle(bottom) -> laneB.n34.handle(top)
+  n35.handle(bottom) -> laneB.n36.handle(top)
+  n37.handle(bottom) -> laneB.n38.handle(top)
+  n39.handle(bottom) -> laneB.n40.handle(top)
+  n41.handle(bottom) -> laneB.n42.handle(top)
+  n43.handle(bottom) -> laneB.n44.handle(top)
+  n45.handle(bottom) -> laneB.n46.handle(top)
+  n47.handle(bottom) -> laneB.n48.handle(top)
+  n49.handle(bottom) -> laneB.n50.handle(top)
+}
+
+laneB { # Lane B
+  n2: rectangle label:"16 Max Nodes step 2"
+  n4: rectangle label:"16 Max Nodes step 4"
+  n6: rectangle label:"16 Max Nodes step 6"
+  n8: rectangle label:"16 Max Nodes step 8"
+  n10: rectangle label:"16 Max Nodes step 10"
+  n12: rectangle label:"16 Max Nodes step 12"
+  n14: rectangle label:"16 Max Nodes step 14"
+  n16: rectangle label:"16 Max Nodes step 16"
+  n18: rectangle label:"16 Max Nodes step 18"
+  n20: rectangle label:"16 Max Nodes step 20"
+  n22: rectangle label:"16 Max Nodes step 22"
+  n24: rectangle label:"16 Max Nodes step 24"
+  n26: rectangle label:"16 Max Nodes step 26"
+  n28: rectangle label:"16 Max Nodes step 28"
+  n30: rectangle label:"16 Max Nodes step 30"
+  n32: rectangle label:"16 Max Nodes step 32"
+  n34: rectangle label:"16 Max Nodes step 34"
+  n36: rectangle label:"16 Max Nodes step 36"
+  n38: rectangle label:"16 Max Nodes step 38"
+  n40: rectangle label:"16 Max Nodes step 40"
+  n42: rectangle label:"16 Max Nodes step 42"
+  n44: rectangle label:"16 Max Nodes step 44"
+  n46: rectangle label:"16 Max Nodes step 46"
+  n48: rectangle label:"16 Max Nodes step 48"
+  n50: circle label:"End 16 Max Nodes"
+  n2.handle(right) -> laneA.n3.handle(left)
+  n4.handle(right) -> laneA.n5.handle(left)
+  n6.handle(right) -> laneA.n7.handle(left)
+  n8.handle(right) -> laneA.n9.handle(left)
+  n10.handle(right) -> laneA.n11.handle(left)
+  n12.handle(right) -> laneA.n13.handle(left)
+  n14.handle(right) -> laneA.n15.handle(left)
+  n16.handle(right) -> laneA.n17.handle(left)
+  n18.handle(right) -> laneA.n19.handle(left)
+  n20.handle(right) -> laneA.n21.handle(left)
+  n22.handle(right) -> laneA.n23.handle(left)
+  n24.handle(right) -> laneA.n25.handle(left)
+  n26.handle(right) -> laneA.n27.handle(left)
+  n28.handle(right) -> laneA.n29.handle(left)
+  n30.handle(right) -> laneA.n31.handle(left)
+  n32.handle(right) -> laneA.n33.handle(left)
+  n34.handle(right) -> laneA.n35.handle(left)
+  n36.handle(right) -> laneA.n37.handle(left)
+  n38.handle(right) -> laneA.n39.handle(left)
+  n40.handle(right) -> laneA.n41.handle(left)
+  n42.handle(right) -> laneA.n43.handle(left)
+  n44.handle(right) -> laneA.n45.handle(left)
+  n46.handle(right) -> laneA.n47.handle(left)
+  n48.handle(right) -> laneA.n49.handle(left)
+}
diff --git a/edge-cases/syntax-primitives/19-label-escaping-workflow/README.md b/edge-cases/syntax-primitives/19-label-escaping-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..acc3445d3c762e34d4a6999c4cf7d1eb9bd28d8b
--- /dev/null
+++ b/edge-cases/syntax-primitives/19-label-escaping-workflow/README.md
@@ -0,0 +1,19 @@
+# 19 Label Escaping Workflow
+
+This workflow models labels that include quotes and special characters.
+
+**Template ID:** `19-label-escaping-workflow`  
+**Kind:** workflow  
+**Source domain:** syntax-primitives  
+**Primary use case:** edge-cases  
+**Secondary use cases:** None  
+**Complexity:** 2/5  
+**Nodes:** 7  
+**Lanes:** 2  
+**Tags:** [19, label, escaping]  
+**Source path:** `syntax-primitives/19-label-escaping`  
+**Repo path:** `edge-cases/syntax-primitives/19-label-escaping-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/edge-cases/syntax-primitives/19-label-escaping-workflow/metadata.json b/edge-cases/syntax-primitives/19-label-escaping-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..a91d535cb391cbd4b8cfdddfc15633c5ff0dd0c2
--- /dev/null
+++ b/edge-cases/syntax-primitives/19-label-escaping-workflow/metadata.json
@@ -0,0 +1,23 @@
+{
+  "template_id": "19-label-escaping-workflow",
+  "workflow_id": "19-label-escaping",
+  "title": "19 Label Escaping Workflow",
+  "kind": "workflow",
+  "source_domain": "syntax-primitives",
+  "primary_use_case": "edge-cases",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "edge-cases"
+  ],
+  "complexity": 2,
+  "num_nodes": 7,
+  "num_lanes": 2,
+  "tags": [
+    "19",
+    "label",
+    "escaping"
+  ],
+  "description": "This workflow models labels that include quotes and special characters.",
+  "source_path": "syntax-primitives/19-label-escaping",
+  "repo_path": "edge-cases/syntax-primitives/19-label-escaping-workflow"
+}
diff --git a/edge-cases/syntax-primitives/19-label-escaping-workflow/workflow.fz b/edge-cases/syntax-primitives/19-label-escaping-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..c8dae4819435c96d723a7ef4b73757b4204e45c8
--- /dev/null
+++ b/edge-cases/syntax-primitives/19-label-escaping-workflow/workflow.fz
@@ -0,0 +1,18 @@
+laneA { # Lane A
+  n1: circle label:"Start 19 Label Escaping"
+  n3: rectangle label:"19 Label Escaping step 3"
+  n5: rectangle label:"19 Label Escaping step 5"
+  n7: circle label:"End 19 Label Escaping"
+  n1.handle(bottom) -> laneB.n2.handle(top)
+  n3.handle(bottom) -> laneB.n4.handle(top)
+  n5.handle(bottom) -> laneB.n6.handle(top)
+}
+
+laneB { # Lane B
+  n2: rectangle label:"19 Label Escaping step 2"
+  n4: rectangle label:"19 Label Escaping step 4"
+  n6: rectangle label:"19 Label Escaping step 6"
+  n2.handle(right) -> laneA.n3.handle(left)
+  n4.handle(right) -> laneA.n5.handle(left)
+  n6.handle(right) -> laneA.n7.handle(left)
+}
diff --git a/handoff/architecture/bulkhead-isolation-architecture/README.md b/handoff/architecture/bulkhead-isolation-architecture/README.md
index e45011924ce64aff5e4caf5f6d3d293b6920beac..ea7c8f89d3f6344f6d7fb99727934d6945bf700e 100644
--- a/handoff/architecture/bulkhead-isolation-architecture/README.md
+++ b/handoff/architecture/bulkhead-isolation-architecture/README.md
@@ -6,7 +6,7 @@ A bulkhead isolation architecture diagram with separate thread pools for critica
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** handoff  
-**Secondary use cases:** None  
+**Secondary use cases:** patterns  
 **Complexity:** 4/5  
 **Nodes:** 18  
 **Lanes:** 4  
diff --git a/handoff/architecture/bulkhead-isolation-architecture/metadata.json b/handoff/architecture/bulkhead-isolation-architecture/metadata.json
index ec76a7ba7dfac52fae2857ad47ec7ce1f415bf07..d9ee95f82aa6e069e6515d38dcad7b381df57cee 100644
--- a/handoff/architecture/bulkhead-isolation-architecture/metadata.json
+++ b/handoff/architecture/bulkhead-isolation-architecture/metadata.json
@@ -5,9 +5,12 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "handoff",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "patterns"
+  ],
   "use_cases": [
-    "handoff"
+    "handoff",
+    "patterns"
   ],
   "complexity": 4,
   "num_nodes": 18,
diff --git a/handoff/architecture/bulkhead-isolation-architecture/workflow.fz b/handoff/architecture/bulkhead-isolation-architecture/workflow.fz
index 4a2d49cbf615f0fe7b2e7b4a1c6af39df417d433..7aa216093c96fb8441ece73cb149c1517adcc38c 100644
--- a/handoff/architecture/bulkhead-isolation-architecture/workflow.fz
+++ b/handoff/architecture/bulkhead-isolation-architecture/workflow.fz
@@ -1,43 +1,43 @@
-Gateway { # API Gateway
-n1: circle label:"Incoming Request"
-n2: rectangle label:"Classify Request Type"
-n3: diamond label:"Request Category?"
-n4: rectangle label:"Route to Critical Pool"
-n5: rectangle label:"Route to Standard Pool"
-n6: rectangle label:"Route to Batch Pool"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(right) -> n4.handle(left) [label="Critical"]
-n3.handle(bottom) -> n5.handle(top) [label="Standard"]
-n3.handle(left) -> n6.handle(right) [label="Batch"]
-n4.handle(bottom) -> CriticalPool.n7.handle(top) [label="Priority"]
-n5.handle(bottom) -> StandardPool.n11.handle(top) [label="Normal"]
-n6.handle(bottom) -> BatchPool.n15.handle(top) [label="Low Priority"]
-}
-CriticalPool { # Critical Thread Pool (10 threads)
-n7: rectangle label:"Dedicated Connection Pool"
-n8: diamond label:"Pool Exhausted?"
-n9: rectangle label:"Process Payment Request"
-n10: rectangle label:"Queue with Timeout"
-n7.handle(right) -> n8.handle(left) [label="Check"]
-n8.handle(right) -> n9.handle(left) [label="Available"]
-n8.handle(bottom) -> n10.handle(top) [label="Exhausted"]
-}
-StandardPool { # Standard Thread Pool (20 threads)
-n11: rectangle label:"Shared Connection Pool"
-n12: diamond label:"Pool Exhausted?"
-n13: rectangle label:"Process API Request"
-n14: rectangle label:"Return 503 Service Unavailable"
-n11.handle(right) -> n12.handle(left) [label="Check"]
-n12.handle(right) -> n13.handle(left) [label="Available"]
-n12.handle(bottom) -> n14.handle(top) [label="Exhausted"]
-}
-BatchPool { # Batch Thread Pool (5 threads)
-n15: rectangle label:"Rate-Limited Pool"
-n16: diamond label:"Pool Exhausted?"
-n17: rectangle label:"Process Batch Job"
-n18: rectangle label:"Backpressure: Delay Retry"
-n15.handle(right) -> n16.handle(left) [label="Check"]
-n16.handle(right) -> n17.handle(left) [label="Available"]
-n16.handle(bottom) -> n18.handle(top) [label="Exhausted"]
-}
+Gateway { # API Gateway
+n1: circle label:"Incoming Request"
+n2: rectangle label:"Classify Request Type"
+n3: diamond label:"Request Category?"
+n4: rectangle label:"Route to Critical Pool"
+n5: rectangle label:"Route to Standard Pool"
+n6: rectangle label:"Route to Batch Pool"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(right) -> n4.handle(left) [label="Critical"]
+n3.handle(bottom) -> n5.handle(top) [label="Standard"]
+n3.handle(left) -> n6.handle(right) [label="Batch"]
+n4.handle(bottom) -> CriticalPool.n7.handle(top) [label="Priority"]
+n5.handle(bottom) -> StandardPool.n11.handle(top) [label="Normal"]
+n6.handle(bottom) -> BatchPool.n15.handle(top) [label="Low Priority"]
+}
+CriticalPool { # Critical Thread Pool (10 threads)
+n7: rectangle label:"Dedicated Connection Pool"
+n8: diamond label:"Pool Exhausted?"
+n9: rectangle label:"Process Payment Request"
+n10: rectangle label:"Queue with Timeout"
+n7.handle(right) -> n8.handle(left) [label="Check"]
+n8.handle(right) -> n9.handle(left) [label="Available"]
+n8.handle(bottom) -> n10.handle(top) [label="Exhausted"]
+}
+StandardPool { # Standard Thread Pool (20 threads)
+n11: rectangle label:"Shared Connection Pool"
+n12: diamond label:"Pool Exhausted?"
+n13: rectangle label:"Process API Request"
+n14: rectangle label:"Return 503 Service Unavailable"
+n11.handle(right) -> n12.handle(left) [label="Check"]
+n12.handle(right) -> n13.handle(left) [label="Available"]
+n12.handle(bottom) -> n14.handle(top) [label="Exhausted"]
+}
+BatchPool { # Batch Thread Pool (5 threads)
+n15: rectangle label:"Rate-Limited Pool"
+n16: diamond label:"Pool Exhausted?"
+n17: rectangle label:"Process Batch Job"
+n18: rectangle label:"Backpressure: Delay Retry"
+n15.handle(right) -> n16.handle(left) [label="Check"]
+n16.handle(right) -> n17.handle(left) [label="Available"]
+n16.handle(bottom) -> n18.handle(top) [label="Exhausted"]
+}
diff --git a/handoff/architecture/cell-based-architecture/workflow.fz b/handoff/architecture/cell-based-architecture/workflow.fz
index 491599d74608f8cb0dd1942e1a65a42336197db4..66a37944886738bf850073e7be5565569682b731 100644
--- a/handoff/architecture/cell-based-architecture/workflow.fz
+++ b/handoff/architecture/cell-based-architecture/workflow.fz
@@ -1,48 +1,48 @@
-GlobalRouter { # Global Router
-n1: circle label:"User Request"
-n2: rectangle label:"Geographic Routing"
-n3: diamond label:"User Cell Assignment?"
-n4: rectangle label:"Route to Cell A"
-n5: rectangle label:"Route to Cell B"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(right) -> n4.handle(left) [label="US-East"]
-n3.handle(bottom) -> n5.handle(top) [label="EU-West"]
-n4.handle(bottom) -> CellA.n6.handle(top) [label="Forward"]
-n5.handle(bottom) -> CellB.n12.handle(top) [label="Forward"]
-}
-CellA { # Cell A (US-East)
-n6: rectangle label:"Cell Gateway"
-n7: rectangle label:"Compute Layer"
-n8: rectangle label:"Cell Database"
-n9: rectangle label:"Cell Cache"
-n10: rectangle label:"Cell Message Queue"
-n11: circle label:"Cell Response"
-n6.handle(right) -> n7.handle(left) [label="Process"]
-n7.handle(right) -> n8.handle(left) [label="Read/Write"]
-n7.handle(bottom) -> n9.handle(top) [label="Cache"]
-n7.handle(bottom) -> n10.handle(top) [label="Async"]
-n8.handle(right) -> n11.handle(left)
-n8.handle(bottom) -> SharedServices.n18.handle(top) [label="Replicate"]
-}
-CellB { # Cell B (EU-West)
-n12: rectangle label:"Cell Gateway"
-n13: rectangle label:"Compute Layer"
-n14: rectangle label:"Cell Database"
-n15: rectangle label:"Cell Cache"
-n16: rectangle label:"Cell Message Queue"
-n17: circle label:"Cell Response"
-n12.handle(right) -> n13.handle(left) [label="Process"]
-n13.handle(right) -> n14.handle(left) [label="Read/Write"]
-n13.handle(bottom) -> n15.handle(top) [label="Cache"]
-n13.handle(bottom) -> n16.handle(top) [label="Async"]
-n14.handle(right) -> n17.handle(left)
-n14.handle(bottom) -> SharedServices.n18.handle(top) [label="Replicate"]
-}
-SharedServices { # Shared Services (Cross-Cell)
-n18: rectangle label:"Cross-Cell Replication"
-n19: rectangle label:"Global Config Service"
-n20: rectangle label:"Monitoring and Alerting"
-n18.handle(right) -> n19.handle(left) [label="Sync Config"]
-n19.handle(right) -> n20.handle(left) [label="Health"]
-}
+GlobalRouter { # Global Router
+n1: circle label:"User Request"
+n2: rectangle label:"Geographic Routing"
+n3: diamond label:"User Cell Assignment?"
+n4: rectangle label:"Route to Cell A"
+n5: rectangle label:"Route to Cell B"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(right) -> n4.handle(left) [label="US-East"]
+n3.handle(bottom) -> n5.handle(top) [label="EU-West"]
+n4.handle(bottom) -> CellA.n6.handle(top) [label="Forward"]
+n5.handle(bottom) -> CellB.n12.handle(top) [label="Forward"]
+}
+CellA { # Cell A (US-East)
+n6: rectangle label:"Cell Gateway"
+n7: rectangle label:"Compute Layer"
+n8: rectangle label:"Cell Database"
+n9: rectangle label:"Cell Cache"
+n10: rectangle label:"Cell Message Queue"
+n11: circle label:"Cell Response"
+n6.handle(right) -> n7.handle(left) [label="Process"]
+n7.handle(right) -> n8.handle(left) [label="Read/Write"]
+n7.handle(bottom) -> n9.handle(top) [label="Cache"]
+n7.handle(bottom) -> n10.handle(top) [label="Async"]
+n8.handle(right) -> n11.handle(left)
+n8.handle(bottom) -> SharedServices.n18.handle(top) [label="Replicate"]
+}
+CellB { # Cell B (EU-West)
+n12: rectangle label:"Cell Gateway"
+n13: rectangle label:"Compute Layer"
+n14: rectangle label:"Cell Database"
+n15: rectangle label:"Cell Cache"
+n16: rectangle label:"Cell Message Queue"
+n17: circle label:"Cell Response"
+n12.handle(right) -> n13.handle(left) [label="Process"]
+n13.handle(right) -> n14.handle(left) [label="Read/Write"]
+n13.handle(bottom) -> n15.handle(top) [label="Cache"]
+n13.handle(bottom) -> n16.handle(top) [label="Async"]
+n14.handle(right) -> n17.handle(left)
+n14.handle(bottom) -> SharedServices.n18.handle(top) [label="Replicate"]
+}
+SharedServices { # Shared Services (Cross-Cell)
+n18: rectangle label:"Cross-Cell Replication"
+n19: rectangle label:"Global Config Service"
+n20: rectangle label:"Monitoring and Alerting"
+n18.handle(right) -> n19.handle(left) [label="Sync Config"]
+n19.handle(right) -> n20.handle(left) [label="Health"]
+}
diff --git a/handoff/architecture/microservices-service-discovery-architecture/README.md b/handoff/architecture/microservices-service-discovery-architecture/README.md
index e4530e366e1f280e84714f9694f1d2df775c50e3..e467a93b398a3e093f900fdafb6168d0e90f7d45 100644
--- a/handoff/architecture/microservices-service-discovery-architecture/README.md
+++ b/handoff/architecture/microservices-service-discovery-architecture/README.md
@@ -6,7 +6,7 @@ A service discovery architecture diagram with Consul or Eureka registry, client-
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** handoff  
-**Secondary use cases:** None  
+**Secondary use cases:** architecture  
 **Complexity:** 3/5  
 **Nodes:** 16  
 **Lanes:** 3  
diff --git a/handoff/architecture/microservices-service-discovery-architecture/metadata.json b/handoff/architecture/microservices-service-discovery-architecture/metadata.json
index f923ff79c2de92757511485798b467ce9aeabe95..00c54a4043e74680a0d984dc93a5ecb72b01af0e 100644
--- a/handoff/architecture/microservices-service-discovery-architecture/metadata.json
+++ b/handoff/architecture/microservices-service-discovery-architecture/metadata.json
@@ -5,9 +5,12 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "handoff",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "architecture"
+  ],
   "use_cases": [
-    "handoff"
+    "handoff",
+    "architecture"
   ],
   "complexity": 3,
   "num_nodes": 16,
diff --git a/handoff/architecture/microservices-service-discovery-architecture/workflow.fz b/handoff/architecture/microservices-service-discovery-architecture/workflow.fz
index c3cbaf4d7dac8ecfe54afa571f6850f69fc1cf7c..35dc02f76834a9552266dc0cf5553af10921a4e3 100644
--- a/handoff/architecture/microservices-service-discovery-architecture/workflow.fz
+++ b/handoff/architecture/microservices-service-discovery-architecture/workflow.fz
@@ -1,59 +1,59 @@
-Client { # Client Service
-n1: circle label:"Service Call Needed"
-n2: rectangle label:"Query Service Registry"
-n8: rectangle label:"Client-Side Load Balance"
-n9: rectangle label:"Send Request to Instance"
-n14: rectangle label:"Receive Response"
-n15: rectangle label:"Process Result"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Registry.n3.handle(top) [label="Lookup"]
-n8.handle(right) -> n9.handle(left)
-n9.handle(bottom) -> Target.n10.handle(top) [label="HTTP/gRPC"]
-n14.handle(right) -> n15.handle(left)
-}
-Registry { # Service Registry (Consul/Eureka)
-n3: rectangle label:"Receive Lookup Request"
-n4: rectangle label:"Check Health Status"
-n5: diamond label:"Healthy Instances?"
-n6: rectangle label:"Return Instance List"
-n7: rectangle label:"Return Service Unavailable"
-n18: rectangle label:"Receive Heartbeat"
-n19: rectangle label:"Send Registration Ack"
-n21: rectangle label:"Receive Ready Signal"
-n22: rectangle label:"Send Health Ping"
-n24: rectangle label:"Update Health Status"
-n27: rectangle label:"Process Removal"
-n3.handle(right) -> n4.handle(left)
-n4.handle(right) -> n5.handle(left)
-n5.handle(right) -> n6.handle(left) [label="Yes"]
-n5.handle(bottom) -> n7.handle(top) [label="No"]
-n6.handle(top) -> Client.n8.handle(bottom) [label="Endpoints"]
-n7.handle(top) -> Client.n14.handle(bottom) [label="503"]
-n18.handle(right) -> n19.handle(left)
-n19.handle(bottom) -> Target.n20.handle(top) [label="Registered OK"]
-n21.handle(right) -> n22.handle(left)
-n22.handle(bottom) -> Target.n23.handle(top) [label="Ping"]
-}
-Target { # Target Service
-n10: rectangle label:"Instance A (Primary)"
-n11: rectangle label:"Instance B (Replica)"
-n12: rectangle label:"Instance C (Replica)"
-n13: rectangle label:"Send Response"
-n16: rectangle label:"Register on Startup"
-n17: rectangle label:"Send Heartbeat"
-n20: rectangle label:"Receive Registration Ack"
-n23: rectangle label:"Respond to Ping"
-n25: rectangle label:"Service Running"
-n26: rectangle label:"Deregister on Shutdown"
-n10.handle(right) -> n11.handle(left) [label="Replicate"]
-n11.handle(right) -> n12.handle(left) [label="Replicate"]
-n12.handle(right) -> n13.handle(left)
-n13.handle(top) -> Client.n14.handle(bottom) [label="Response"]
-n16.handle(right) -> n17.handle(left)
-n17.handle(top) -> Registry.n18.handle(bottom) [label="Heartbeat"]
-n20.handle(top) -> Registry.n21.handle(bottom) [label="Ready for Ping"]
-n23.handle(top) -> Registry.n24.handle(bottom) [label="Healthy"]
-n23.handle(right) -> n25.handle(left)
-n25.handle(right) -> n26.handle(left) [label="Shutdown"]
-n26.handle(top) -> Registry.n27.handle(bottom) [label="Remove"]
-}
+Client { # Client Service
+n1: circle label:"Service Call Needed"
+n2: rectangle label:"Query Service Registry"
+n8: rectangle label:"Client-Side Load Balance"
+n9: rectangle label:"Send Request to Instance"
+n14: rectangle label:"Receive Response"
+n15: rectangle label:"Process Result"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Registry.n3.handle(top) [label="Lookup"]
+n8.handle(right) -> n9.handle(left)
+n9.handle(bottom) -> Target.n10.handle(top) [label="HTTP/gRPC"]
+n14.handle(right) -> n15.handle(left)
+}
+Registry { # Service Registry (Consul/Eureka)
+n3: rectangle label:"Receive Lookup Request"
+n4: rectangle label:"Check Health Status"
+n5: diamond label:"Healthy Instances?"
+n6: rectangle label:"Return Instance List"
+n7: rectangle label:"Return Service Unavailable"
+n18: rectangle label:"Receive Heartbeat"
+n19: rectangle label:"Send Registration Ack"
+n21: rectangle label:"Receive Ready Signal"
+n22: rectangle label:"Send Health Ping"
+n24: rectangle label:"Update Health Status"
+n27: rectangle label:"Process Removal"
+n3.handle(right) -> n4.handle(left)
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left) [label="Yes"]
+n5.handle(bottom) -> n7.handle(top) [label="No"]
+n6.handle(top) -> Client.n8.handle(bottom) [label="Endpoints"]
+n7.handle(top) -> Client.n14.handle(bottom) [label="503"]
+n18.handle(right) -> n19.handle(left)
+n19.handle(bottom) -> Target.n20.handle(top) [label="Registered OK"]
+n21.handle(right) -> n22.handle(left)
+n22.handle(bottom) -> Target.n23.handle(top) [label="Ping"]
+}
+Target { # Target Service
+n10: rectangle label:"Instance A (Primary)"
+n11: rectangle label:"Instance B (Replica)"
+n12: rectangle label:"Instance C (Replica)"
+n13: rectangle label:"Send Response"
+n16: rectangle label:"Register on Startup"
+n17: rectangle label:"Send Heartbeat"
+n20: rectangle label:"Receive Registration Ack"
+n23: rectangle label:"Respond to Ping"
+n25: rectangle label:"Service Running"
+n26: rectangle label:"Deregister on Shutdown"
+n10.handle(right) -> n11.handle(left) [label="Replicate"]
+n11.handle(right) -> n12.handle(left) [label="Replicate"]
+n12.handle(right) -> n13.handle(left)
+n13.handle(top) -> Client.n14.handle(bottom) [label="Response"]
+n16.handle(right) -> n17.handle(left)
+n17.handle(top) -> Registry.n18.handle(bottom) [label="Heartbeat"]
+n20.handle(top) -> Registry.n21.handle(bottom) [label="Ready for Ping"]
+n23.handle(top) -> Registry.n24.handle(bottom) [label="Healthy"]
+n23.handle(right) -> n25.handle(left)
+n25.handle(right) -> n26.handle(left) [label="Shutdown"]
+n26.handle(top) -> Registry.n27.handle(bottom) [label="Remove"]
+}
diff --git a/handoff/architecture/serverless-edge-computing-architecture/README.md b/handoff/architecture/serverless-edge-computing-architecture/README.md
index 51bd694c69433223c7c2dab3a5db2a1e0570e306..fe666bb324738415c03cbabe0c218b15ed1e08f7 100644
--- a/handoff/architecture/serverless-edge-computing-architecture/README.md
+++ b/handoff/architecture/serverless-edge-computing-architecture/README.md
@@ -6,7 +6,7 @@ A serverless edge computing architecture diagram with CloudFront or Cloudflare e
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** handoff  
-**Secondary use cases:** None  
+**Secondary use cases:** architecture  
 **Complexity:** 3/5  
 **Nodes:** 15  
 **Lanes:** 3  
diff --git a/handoff/architecture/serverless-edge-computing-architecture/metadata.json b/handoff/architecture/serverless-edge-computing-architecture/metadata.json
index d2e45d79019aea2e1082e815747715c6fb8b8676..06cdabd2a8760dc3023985397c6b5a9ccd1b917d 100644
--- a/handoff/architecture/serverless-edge-computing-architecture/metadata.json
+++ b/handoff/architecture/serverless-edge-computing-architecture/metadata.json
@@ -5,9 +5,12 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "handoff",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "architecture"
+  ],
   "use_cases": [
-    "handoff"
+    "handoff",
+    "architecture"
   ],
   "complexity": 3,
   "num_nodes": 15,
diff --git a/handoff/architecture/serverless-edge-computing-architecture/workflow.fz b/handoff/architecture/serverless-edge-computing-architecture/workflow.fz
index 13ef0ce9de4267862fab32b6c9b2f09fdb17f32d..048197b964a1e755e227568f46f1d15f785f58c6 100644
--- a/handoff/architecture/serverless-edge-computing-architecture/workflow.fz
+++ b/handoff/architecture/serverless-edge-computing-architecture/workflow.fz
@@ -1,51 +1,51 @@
-User { # End User
-n1: circle label:"Browser Request"
-n2: rectangle label:"DNS Resolution (Route 53)"
-n21: rectangle label:"Receive Optimized Response"
-n22: circle label:"Page Rendered"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Edge.n3.handle(top) [label="Nearest PoP"]
-n21.handle(right) -> n22.handle(left)
-}
-Edge { # Edge Network (CloudFront/Cloudflare)
-n3: rectangle label:"Edge Location PoP"
-n4: diamond label:"Cache Hit?"
-n5: rectangle label:"Return Cached Response"
-n6: rectangle label:"Edge Function (Lambda@Edge)"
-n7: rectangle label:"A/B Test Routing"
-n8: rectangle label:"Geo-Based Personalization"
-n19: rectangle label:"Cache and Forward Response"
-n20: rectangle label:"Send to User"
-n3.handle(right) -> n4.handle(left)
-n4.handle(right) -> n5.handle(left) [label="HIT"]
-n4.handle(bottom) -> n6.handle(top) [label="MISS"]
-n5.handle(top) -> User.n21.handle(bottom) [label="Fast Response"]
-n6.handle(right) -> n7.handle(left) [label="Modify Request"]
-n7.handle(right) -> n8.handle(left) [label="Personalize"]
-n8.handle(bottom) -> Origin.n9.handle(top) [label="Forward"]
-n19.handle(right) -> n20.handle(left)
-n20.handle(top) -> User.n21.handle(bottom) [label="Response"]
-}
-Origin { # Origin Services
-n9: rectangle label:"Origin Shield"
-n10: rectangle label:"Application Load Balancer"
-n11: rectangle label:"Serverless API"
-n12: rectangle label:"Static Asset Store (S3)"
-n13: rectangle label:"Generate Response"
-n14: rectangle label:"Prepare Origin Response"
-n15: rectangle label:"Package Response"
-n16: rectangle label:"Forward Origin Response"
-n17: rectangle label:"Send Cached Response"
-n18: rectangle label:"Deliver to Edge"
-n9.handle(right) -> n10.handle(left) [label="Collapse Requests"]
-n10.handle(right) -> n11.handle(left) [label="Dynamic"]
-n10.handle(bottom) -> n12.handle(top) [label="Static"]
-n11.handle(right) -> n13.handle(left) [label="Compute"]
-n12.handle(right) -> n13.handle(left) [label="Assets"]
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left)
-n16.handle(right) -> n17.handle(left)
-n17.handle(right) -> n18.handle(left)
-n18.handle(top) -> Edge.n19.handle(bottom) [label="Cache + Return"]
-}
+User { # End User
+n1: circle label:"Browser Request"
+n2: rectangle label:"DNS Resolution (Route 53)"
+n21: rectangle label:"Receive Optimized Response"
+n22: circle label:"Page Rendered"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Edge.n3.handle(top) [label="Nearest PoP"]
+n21.handle(right) -> n22.handle(left)
+}
+Edge { # Edge Network (CloudFront/Cloudflare)
+n3: rectangle label:"Edge Location PoP"
+n4: diamond label:"Cache Hit?"
+n5: rectangle label:"Return Cached Response"
+n6: rectangle label:"Edge Function (Lambda@Edge)"
+n7: rectangle label:"A/B Test Routing"
+n8: rectangle label:"Geo-Based Personalization"
+n19: rectangle label:"Cache and Forward Response"
+n20: rectangle label:"Send to User"
+n3.handle(right) -> n4.handle(left)
+n4.handle(right) -> n5.handle(left) [label="HIT"]
+n4.handle(bottom) -> n6.handle(top) [label="MISS"]
+n5.handle(top) -> User.n21.handle(bottom) [label="Fast Response"]
+n6.handle(right) -> n7.handle(left) [label="Modify Request"]
+n7.handle(right) -> n8.handle(left) [label="Personalize"]
+n8.handle(bottom) -> Origin.n9.handle(top) [label="Forward"]
+n19.handle(right) -> n20.handle(left)
+n20.handle(top) -> User.n21.handle(bottom) [label="Response"]
+}
+Origin { # Origin Services
+n9: rectangle label:"Origin Shield"
+n10: rectangle label:"Application Load Balancer"
+n11: rectangle label:"Serverless API"
+n12: rectangle label:"Static Asset Store (S3)"
+n13: rectangle label:"Generate Response"
+n14: rectangle label:"Prepare Origin Response"
+n15: rectangle label:"Package Response"
+n16: rectangle label:"Forward Origin Response"
+n17: rectangle label:"Send Cached Response"
+n18: rectangle label:"Deliver to Edge"
+n9.handle(right) -> n10.handle(left) [label="Collapse Requests"]
+n10.handle(right) -> n11.handle(left) [label="Dynamic"]
+n10.handle(bottom) -> n12.handle(top) [label="Static"]
+n11.handle(right) -> n13.handle(left) [label="Compute"]
+n12.handle(right) -> n13.handle(left) [label="Assets"]
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left)
+n17.handle(right) -> n18.handle(left)
+n18.handle(top) -> Edge.n19.handle(bottom) [label="Cache + Return"]
+}
diff --git a/handoff/architecture/serverless-multi-cloud-architecture/README.md b/handoff/architecture/serverless-multi-cloud-architecture/README.md
index 54d8ca5b6b9a9d41420d843e7c9fb059586d25fa..86baea2a17e267adb7ab40b57a4faaab25849653 100644
--- a/handoff/architecture/serverless-multi-cloud-architecture/README.md
+++ b/handoff/architecture/serverless-multi-cloud-architecture/README.md
@@ -6,7 +6,7 @@ A multi-cloud serverless architecture diagram with DNS-based traffic routing bet
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** handoff  
-**Secondary use cases:** None  
+**Secondary use cases:** platform-reliability, architecture  
 **Complexity:** 4/5  
 **Nodes:** 18  
 **Lanes:** 4  
diff --git a/handoff/architecture/serverless-multi-cloud-architecture/metadata.json b/handoff/architecture/serverless-multi-cloud-architecture/metadata.json
index 946892481eca55bcfb425f7b7ac1e6c873e8ce28..50f9964c6777b9dc88961b5a8a3f892d7da2f90a 100644
--- a/handoff/architecture/serverless-multi-cloud-architecture/metadata.json
+++ b/handoff/architecture/serverless-multi-cloud-architecture/metadata.json
@@ -5,9 +5,14 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "handoff",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "platform-reliability",
+    "architecture"
+  ],
   "use_cases": [
-    "handoff"
+    "handoff",
+    "platform-reliability",
+    "architecture"
   ],
   "complexity": 4,
   "num_nodes": 18,
diff --git a/handoff/architecture/serverless-multi-cloud-architecture/workflow.fz b/handoff/architecture/serverless-multi-cloud-architecture/workflow.fz
index ee4287d2b1cc8b73932742ed82928a4c43b99393..211e2527eafe54caabc6926478508d906f44ded9 100644
--- a/handoff/architecture/serverless-multi-cloud-architecture/workflow.fz
+++ b/handoff/architecture/serverless-multi-cloud-architecture/workflow.fz
@@ -1,55 +1,55 @@
-TrafficManager { # Global Traffic Manager
-n1: circle label:"User Request"
-n2: rectangle label:"DNS-Based Routing"
-n3: diamond label:"Primary Cloud Healthy?"
-n4: rectangle label:"Route to Primary (AWS)"
-n5: rectangle label:"Failover to Secondary (Azure)"
-n20: rectangle label:"Receive Cloud Response"
-n21: circle label:"Return to User"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(right) -> n4.handle(left) [label="Healthy"]
-n3.handle(bottom) -> n5.handle(top) [label="Unhealthy"]
-n4.handle(bottom) -> AWS.n6.handle(top) [label="Forward"]
-n5.handle(bottom) -> Azure.n13.handle(top) [label="Forward"]
-n20.handle(right) -> n21.handle(left)
-}
-AWS { # AWS Region
-n6: rectangle label:"API Gateway"
-n7: rectangle label:"Lambda Functions"
-n8: rectangle label:"DynamoDB"
-n9: rectangle label:"S3 Storage"
-n10: rectangle label:"CloudWatch Monitoring"
-n11: rectangle label:"Prepare Response"
-n12: rectangle label:"Return to TrafficManager"
-n6.handle(right) -> n7.handle(left) [label="Invoke"]
-n7.handle(right) -> n8.handle(left) [label="Read/Write"]
-n7.handle(bottom) -> n9.handle(top) [label="Store"]
-n8.handle(right) -> n10.handle(left) [label="Monitor"]
-n10.handle(right) -> n11.handle(left)
-n11.handle(right) -> n12.handle(left)
-n12.handle(top) -> TrafficManager.n20.handle(bottom) [label="AWS Response"]
-}
-Azure { # Azure Region
-n13: rectangle label:"Azure API Management"
-n14: rectangle label:"Azure Functions"
-n15: rectangle label:"Cosmos DB"
-n16: rectangle label:"Blob Storage"
-n17: rectangle label:"Azure Monitor"
-n18: rectangle label:"Prepare Response"
-n19: rectangle label:"Return to TrafficManager"
-n13.handle(right) -> n14.handle(left) [label="Invoke"]
-n14.handle(right) -> n15.handle(left) [label="Read/Write"]
-n14.handle(bottom) -> n16.handle(top) [label="Store"]
-n15.handle(right) -> n17.handle(left) [label="Monitor"]
-n17.handle(right) -> n18.handle(left)
-n18.handle(right) -> n19.handle(left)
-n19.handle(top) -> TrafficManager.n20.handle(bottom) [label="Azure Response"]
-}
-DataSync { # Cross-Cloud Sync
-n22: rectangle label:"Event Bridge"
-n23: rectangle label:"Bi-Directional Replication"
-n24: rectangle label:"Conflict Resolution"
-n22.handle(right) -> n23.handle(left) [label="CDC Events"]
-n23.handle(right) -> n24.handle(left) [label="Last-Write-Wins"]
-}
+TrafficManager { # Global Traffic Manager
+n1: circle label:"User Request"
+n2: rectangle label:"DNS-Based Routing"
+n3: diamond label:"Primary Cloud Healthy?"
+n4: rectangle label:"Route to Primary (AWS)"
+n5: rectangle label:"Failover to Secondary (Azure)"
+n20: rectangle label:"Receive Cloud Response"
+n21: circle label:"Return to User"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(right) -> n4.handle(left) [label="Healthy"]
+n3.handle(bottom) -> n5.handle(top) [label="Unhealthy"]
+n4.handle(bottom) -> AWS.n6.handle(top) [label="Forward"]
+n5.handle(bottom) -> Azure.n13.handle(top) [label="Forward"]
+n20.handle(right) -> n21.handle(left)
+}
+AWS { # AWS Region
+n6: rectangle label:"API Gateway"
+n7: rectangle label:"Lambda Functions"
+n8: rectangle label:"DynamoDB"
+n9: rectangle label:"S3 Storage"
+n10: rectangle label:"CloudWatch Monitoring"
+n11: rectangle label:"Prepare Response"
+n12: rectangle label:"Return to TrafficManager"
+n6.handle(right) -> n7.handle(left) [label="Invoke"]
+n7.handle(right) -> n8.handle(left) [label="Read/Write"]
+n7.handle(bottom) -> n9.handle(top) [label="Store"]
+n8.handle(right) -> n10.handle(left) [label="Monitor"]
+n10.handle(right) -> n11.handle(left)
+n11.handle(right) -> n12.handle(left)
+n12.handle(top) -> TrafficManager.n20.handle(bottom) [label="AWS Response"]
+}
+Azure { # Azure Region
+n13: rectangle label:"Azure API Management"
+n14: rectangle label:"Azure Functions"
+n15: rectangle label:"Cosmos DB"
+n16: rectangle label:"Blob Storage"
+n17: rectangle label:"Azure Monitor"
+n18: rectangle label:"Prepare Response"
+n19: rectangle label:"Return to TrafficManager"
+n13.handle(right) -> n14.handle(left) [label="Invoke"]
+n14.handle(right) -> n15.handle(left) [label="Read/Write"]
+n14.handle(bottom) -> n16.handle(top) [label="Store"]
+n15.handle(right) -> n17.handle(left) [label="Monitor"]
+n17.handle(right) -> n18.handle(left)
+n18.handle(right) -> n19.handle(left)
+n19.handle(top) -> TrafficManager.n20.handle(bottom) [label="Azure Response"]
+}
+DataSync { # Cross-Cloud Sync
+n22: rectangle label:"Event Bridge"
+n23: rectangle label:"Bi-Directional Replication"
+n24: rectangle label:"Conflict Resolution"
+n22.handle(right) -> n23.handle(left) [label="CDC Events"]
+n23.handle(right) -> n24.handle(left) [label="Last-Write-Wins"]
+}
diff --git a/handoff/business-operations/support-ticket-workflow/workflow.fz b/handoff/business-operations/support-ticket-workflow/workflow.fz
index a183a677934c7f561ae2bd4a3e9a02ad3033fdb6..6e96234caf3710e8497a2c9a8c7d52ad29537d66 100644
--- a/handoff/business-operations/support-ticket-workflow/workflow.fz
+++ b/handoff/business-operations/support-ticket-workflow/workflow.fz
@@ -1,50 +1,50 @@
-Customer { # Customer
-n1: circle label:"Start"
-n2: rectangle label:"Submit support request"
-n3: rectangle label:"Receive ticket number"
-n4: rectangle label:"Provide additional info"
-n5: rectangle label:"Rate support experience"
-n6: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Triage.n7.handle(top) [label="Create ticket"]
-n3.handle(bottom) -> Agent.n14.handle(top) [label="Reply"]
-n4.handle(bottom) -> Agent.n14.handle(top) [label="Update"]
-n5.handle(right) -> n6.handle(left)
-}
-Triage { # Triage System
-n7: rectangle label:"Parse ticket content"
-n8: rectangle label:"Classify by category"
-n9: diamond label:"Priority level?"
-n10: rectangle label:"Route to L1 queue"
-n11: rectangle label:"Route to L2 queue"
-n12: rectangle label:"Escalate to L3"
-n13: rectangle label:"Send confirmation email"
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left)
-n9.handle(right) -> n10.handle(left) [label="Low/Medium"]
-n9.handle(bottom) -> n11.handle(top) [label="High"]
-n9.handle(left) -> n12.handle(top) [label="Critical"]
-n10.handle(bottom) -> Agent.n14.handle(top) [label="Assign"]
-n11.handle(bottom) -> Agent.n14.handle(top) [label="Assign"]
-n12.handle(bottom) -> Agent.n14.handle(top) [label="Assign"]
-n13.handle(top) -> Customer.n3.handle(bottom) [label="Ticket created"]
-}
-Agent { # Support Agent
-n14: rectangle label:"Review ticket details"
-n15: diamond label:"Can resolve?"
-n16: rectangle label:"Provide solution"
-n17: rectangle label:"Request more info"
-n18: rectangle label:"Escalate to specialist"
-n19: diamond label:"Customer satisfied?"
-n20: rectangle label:"Close ticket"
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left) [label="Yes"]
-n15.handle(bottom) -> n17.handle(top) [label="Need info"]
-n15.handle(left) -> n18.handle(top) [label="No - Complex"]
-n16.handle(right) -> n19.handle(left)
-n17.handle(top) -> Customer.n4.handle(bottom) [label="Request sent"]
-n18.handle(bottom) -> Triage.n12.handle(bottom) [label="Escalate"]
-n19.handle(right) -> n20.handle(left) [label="Yes"]
-n19.handle(bottom) -> n14.handle(bottom) [label="No - Reopen"]
-n20.handle(top) -> Customer.n5.handle(bottom) [label="Survey sent"]
+Customer { # Customer
+n1: circle label:"Start"
+n2: rectangle label:"Submit support request"
+n3: rectangle label:"Receive ticket number"
+n4: rectangle label:"Provide additional info"
+n5: rectangle label:"Rate support experience"
+n6: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Triage.n7.handle(top) [label="Create ticket"]
+n3.handle(bottom) -> Agent.n14.handle(top) [label="Reply"]
+n4.handle(bottom) -> Agent.n14.handle(top) [label="Update"]
+n5.handle(right) -> n6.handle(left)
+}
+Triage { # Triage System
+n7: rectangle label:"Parse ticket content"
+n8: rectangle label:"Classify by category"
+n9: diamond label:"Priority level?"
+n10: rectangle label:"Route to L1 queue"
+n11: rectangle label:"Route to L2 queue"
+n12: rectangle label:"Escalate to L3"
+n13: rectangle label:"Send confirmation email"
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left) [label="Low/Medium"]
+n9.handle(bottom) -> n11.handle(top) [label="High"]
+n9.handle(left) -> n12.handle(top) [label="Critical"]
+n10.handle(bottom) -> Agent.n14.handle(top) [label="Assign"]
+n11.handle(bottom) -> Agent.n14.handle(top) [label="Assign"]
+n12.handle(bottom) -> Agent.n14.handle(top) [label="Assign"]
+n13.handle(top) -> Customer.n3.handle(bottom) [label="Ticket created"]
+}
+Agent { # Support Agent
+n14: rectangle label:"Review ticket details"
+n15: diamond label:"Can resolve?"
+n16: rectangle label:"Provide solution"
+n17: rectangle label:"Request more info"
+n18: rectangle label:"Escalate to specialist"
+n19: diamond label:"Customer satisfied?"
+n20: rectangle label:"Close ticket"
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left) [label="Yes"]
+n15.handle(bottom) -> n17.handle(top) [label="Need info"]
+n15.handle(left) -> n18.handle(top) [label="No - Complex"]
+n16.handle(right) -> n19.handle(left)
+n17.handle(top) -> Customer.n4.handle(bottom) [label="Request sent"]
+n18.handle(bottom) -> Triage.n12.handle(bottom) [label="Escalate"]
+n19.handle(right) -> n20.handle(left) [label="Yes"]
+n19.handle(bottom) -> n14.handle(bottom) [label="No - Reopen"]
+n20.handle(top) -> Customer.n5.handle(bottom) [label="Survey sent"]
 }
\ No newline at end of file
diff --git a/handoff/commerce-automation/ai-order-routing-workflow/README.md b/handoff/commerce-automation/ai-order-routing-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..d2bd81b1ae000e1ad0b2604d454f7f44f6489e79
--- /dev/null
+++ b/handoff/commerce-automation/ai-order-routing-workflow/README.md
@@ -0,0 +1,19 @@
+# AI Order Routing Workflow
+
+Order routing where an AI decision engine classifies each order, auto-processes the clean ones and sends the rest to a backorder queue before operations completes it.
+
+**Template ID:** `ai-order-routing-workflow`  
+**Kind:** workflow  
+**Source domain:** Commerce Automation  
+**Primary use case:** handoff  
+**Secondary use cases:** commerce-automation  
+**Complexity:** 3/5  
+**Nodes:** 14  
+**Lanes:** 3  
+**Tags:** [n8n, order-routing, ai-decision, backorder, fulfillment]  
+**Source path:** ``  
+**Repo path:** `handoff/commerce-automation/ai-order-routing-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/handoff/commerce-automation/ai-order-routing-workflow/metadata.json b/handoff/commerce-automation/ai-order-routing-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..bf7cef4d13fd0be05a8c3cf09fdfa881adc24777
--- /dev/null
+++ b/handoff/commerce-automation/ai-order-routing-workflow/metadata.json
@@ -0,0 +1,28 @@
+{
+  "template_id": "ai-order-routing-workflow",
+  "workflow_id": "ai-order-routing",
+  "title": "AI Order Routing Workflow",
+  "kind": "workflow",
+  "source_domain": "Commerce Automation",
+  "primary_use_case": "handoff",
+  "secondary_use_cases": [
+    "commerce-automation"
+  ],
+  "use_cases": [
+    "handoff",
+    "commerce-automation"
+  ],
+  "complexity": 3,
+  "num_nodes": 14,
+  "num_lanes": 3,
+  "tags": [
+    "n8n",
+    "order-routing",
+    "ai-decision",
+    "backorder",
+    "fulfillment"
+  ],
+  "description": "Order routing where an AI decision engine classifies each order, auto-processes the clean ones and sends the rest to a backorder queue before operations completes it.",
+  "source_path": "",
+  "repo_path": "handoff/commerce-automation/ai-order-routing-workflow"
+}
diff --git a/handoff/commerce-automation/ai-order-routing-workflow/workflow.fz b/handoff/commerce-automation/ai-order-routing-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..62b8f3b4e37bcfe66ce7d8f5f384e363dc48b69c
--- /dev/null
+++ b/handoff/commerce-automation/ai-order-routing-workflow/workflow.fz
@@ -0,0 +1,37 @@
+channels { # Sales Channels
+  n1: rectangle label:"Order Received"
+  n2: diamond label:"Platform?"
+  n3: rectangle label:"Unified Order Payload"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(bottom) -> n3.handle(top)
+  n3.handle(right) -> agent.n4.handle(left) [label="new order"]
+}
+
+agent { # AI Decision Engine
+  n4: rectangle label:"AI: Classify Order"
+  n5: diamond label:"Risk Score?"
+  n6: rectangle label:"Auto-Process"
+  n7: rectangle label:"Flag for Review"
+  n8: diamond label:"Inventory Check"
+  n9: rectangle label:"Route to Warehouse"
+  n10: rectangle label:"Backorder Queue"
+  n4.handle(left) -> channels.n3.handle(right) [label="ack"]
+  n4.handle(right) -> n5.handle(left)
+  n5.handle(right) -> n6.handle(left) [label="low"]
+  n5.handle(bottom) -> n7.handle(top) [label="high"]
+  n6.handle(right) -> n8.handle(left)
+  n8.handle(right) -> n9.handle(left) [label="in stock"]
+  n8.handle(bottom) -> n10.handle(top) [label="none"]
+  n9.handle(right) -> ops.n11.handle(left) [label="dispatch"]
+}
+
+ops { # Operations
+  n11: rectangle label:"OMS / ERP Write"
+  n12: rectangle label:"Shipment Created"
+  n13: rectangle label:"Notify Customer"
+  n14: circle label:"Complete"
+  n11.handle(left) -> agent.n9.handle(right) [label="confirmed"]
+  n11.handle(right) -> n12.handle(left)
+  n12.handle(right) -> n13.handle(left)
+  n13.handle(right) -> n14.handle(left)
+}
diff --git a/handoff/devops/mcp-tool-router/workflow.fz b/handoff/devops/mcp-tool-router/workflow.fz
index e7128471664f7d1013048d1102741b3e1f51a3b3..007cfc9b21a824724cf6242fadb61be9948073c8 100644
--- a/handoff/devops/mcp-tool-router/workflow.fz
+++ b/handoff/devops/mcp-tool-router/workflow.fz
@@ -1,41 +1,41 @@
-Host {
-  n1: circle label="User sends prompt"
-  n2: rectangle label="Agent extracts intent"
-  n3: rectangle label="Send intent to router"
-  n4: rectangle label="Receive routed result"
-  n5: rectangle label="Agent responds to user"
-  n1.handle(right) -> n2.handle(left)
-  n2.handle(right) -> n3.handle(left)
-  n3.handle(bottom) -> Router.n6.handle(top) [label="Intent + tool request"]
-  n4.handle(right) -> n5.handle(left)
-}
-
-Router {
-  n6: rectangle label="Receive intent"
-  n7: rectangle label="Semantic match via embeddings"
-  n8: diamond label="Which MCP server?"
-  n9: rectangle label="Forward to Server A"
-  n10: rectangle label="Forward to Server B"
-  n11: rectangle label="Normalize and return result"
-  n6.handle(right) -> n7.handle(left)
-  n7.handle(right) -> n8.handle(left)
-  n8.handle(bottom) -> n9.handle(top) [label="Route A"]
-  n8.handle(right) -> n10.handle(left) [label="Route B"]
-  n9.handle(bottom) -> ServerA.n12.handle(top) [label="Call Server A"]
-  n10.handle(bottom) -> ServerB.n14.handle(top) [label="Call Server B"]
-  n11.handle(top) -> Host.n4.handle(bottom) [label="Final result"]
-}
-
-ServerA {
-  n12: rectangle label="Execute tool A"
-  n13: rectangle label="Return A result"
-  n12.handle(right) -> n13.handle(left)
-  n13.handle(top) -> Router.n11.handle(bottom) [label="Result A"]
-}
-
-ServerB {
-  n14: rectangle label="Execute tool B"
-  n15: rectangle label="Return B result"
-  n14.handle(right) -> n15.handle(left)
-  n15.handle(top) -> Router.n11.handle(left) [label="Result B"]
-}
+Host {
+  n1: circle label="User sends prompt"
+  n2: rectangle label="Agent extracts intent"
+  n3: rectangle label="Send intent to router"
+  n4: rectangle label="Receive routed result"
+  n5: rectangle label="Agent responds to user"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left)
+  n3.handle(bottom) -> Router.n6.handle(top) [label="Intent + tool request"]
+  n4.handle(right) -> n5.handle(left)
+}
+
+Router {
+  n6: rectangle label="Receive intent"
+  n7: rectangle label="Semantic match via embeddings"
+  n8: diamond label="Which MCP server?"
+  n9: rectangle label="Forward to Server A"
+  n10: rectangle label="Forward to Server B"
+  n11: rectangle label="Normalize and return result"
+  n6.handle(right) -> n7.handle(left)
+  n7.handle(right) -> n8.handle(left)
+  n8.handle(bottom) -> n9.handle(top) [label="Route A"]
+  n8.handle(right) -> n10.handle(left) [label="Route B"]
+  n9.handle(bottom) -> ServerA.n12.handle(top) [label="Call Server A"]
+  n10.handle(bottom) -> ServerB.n14.handle(top) [label="Call Server B"]
+  n11.handle(top) -> Host.n4.handle(bottom) [label="Final result"]
+}
+
+ServerA {
+  n12: rectangle label="Execute tool A"
+  n13: rectangle label="Return A result"
+  n12.handle(right) -> n13.handle(left)
+  n13.handle(top) -> Router.n11.handle(bottom) [label="Result A"]
+}
+
+ServerB {
+  n14: rectangle label="Execute tool B"
+  n15: rectangle label="Return B result"
+  n14.handle(right) -> n15.handle(left)
+  n15.handle(top) -> Router.n11.handle(left) [label="Result B"]
+}
diff --git a/handoff/devops/on-call-rotation-workflow/workflow.fz b/handoff/devops/on-call-rotation-workflow/workflow.fz
index d5753194616a51d94a96ad4ea87bd32106dbd876..50a36d6a3f64b2931a0a3fae2b2d6e903e7c8369 100644
--- a/handoff/devops/on-call-rotation-workflow/workflow.fz
+++ b/handoff/devops/on-call-rotation-workflow/workflow.fz
@@ -1,47 +1,47 @@
-Scheduler { # On-Call Scheduler
-n1: circle label:"Start"
-n2: rectangle label:"Load rotation schedule"
-n3: rectangle label:"Determine current on-call"
-n4: rectangle label:"Complete handoff"
-n5: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(bottom) -> Handoff.n6.handle(top) [label="Rotation due"]
-n4.handle(right) -> n5.handle(left)
-}
-Handoff { # Handoff Process
-n6: rectangle label:"Notify outgoing engineer"
-n7: rectangle label:"Notify incoming engineer"
-n8: diamond label:"Handoff acknowledged?"
-n9: rectangle label:"Transfer pager access"
-n10: rectangle label:"Escalate to manager"
-n11: rectangle label:"Update PagerDuty schedule"
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left) [label="Yes"]
-n8.handle(bottom) -> n10.handle(top) [label="No"]
-n9.handle(right) -> n11.handle(left)
-n10.handle(right) -> n9.handle(top)
-n11.handle(bottom) -> Alerting.n12.handle(top) [label="Active"]
-}
-Alerting { # Alert Routing
-n12: rectangle label:"Receive incoming alert"
-n13: diamond label:"Severity level?"
-n14: rectangle label:"Page on-call immediately"
-n15: rectangle label:"Send Slack notification"
-n16: rectangle label:"Queue for review"
-n17: diamond label:"Acknowledged in 5 min?"
-n18: rectangle label:"Escalate to backup"
-n19: rectangle label:"Log acknowledgment"
-n12.handle(right) -> n13.handle(left)
-n13.handle(right) -> n14.handle(left) [label="Critical"]
-n13.handle(bottom) -> n15.handle(top) [label="Warning"]
-n13.handle(left) -> n16.handle(top) [label="Info"]
-n14.handle(right) -> n17.handle(left)
-n15.handle(right) -> n19.handle(left)
-n16.handle(right) -> n19.handle(top)
-n17.handle(right) -> n19.handle(left) [label="Yes"]
-n17.handle(bottom) -> n18.handle(top) [label="No"]
-n18.handle(right) -> n17.handle(top)
-n19.handle(top) -> Scheduler.n4.handle(bottom) [label="Handled"]
-}
+Scheduler { # On-Call Scheduler
+n1: circle label:"Start"
+n2: rectangle label:"Load rotation schedule"
+n3: rectangle label:"Determine current on-call"
+n4: rectangle label:"Complete handoff"
+n5: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(bottom) -> Handoff.n6.handle(top) [label="Rotation due"]
+n4.handle(right) -> n5.handle(left)
+}
+Handoff { # Handoff Process
+n6: rectangle label:"Notify outgoing engineer"
+n7: rectangle label:"Notify incoming engineer"
+n8: diamond label:"Handoff acknowledged?"
+n9: rectangle label:"Transfer pager access"
+n10: rectangle label:"Escalate to manager"
+n11: rectangle label:"Update PagerDuty schedule"
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left) [label="Yes"]
+n8.handle(bottom) -> n10.handle(top) [label="No"]
+n9.handle(right) -> n11.handle(left)
+n10.handle(right) -> n9.handle(top)
+n11.handle(bottom) -> Alerting.n12.handle(top) [label="Active"]
+}
+Alerting { # Alert Routing
+n12: rectangle label:"Receive incoming alert"
+n13: diamond label:"Severity level?"
+n14: rectangle label:"Page on-call immediately"
+n15: rectangle label:"Send Slack notification"
+n16: rectangle label:"Queue for review"
+n17: diamond label:"Acknowledged in 5 min?"
+n18: rectangle label:"Escalate to backup"
+n19: rectangle label:"Log acknowledgment"
+n12.handle(right) -> n13.handle(left)
+n13.handle(right) -> n14.handle(left) [label="Critical"]
+n13.handle(bottom) -> n15.handle(top) [label="Warning"]
+n13.handle(left) -> n16.handle(top) [label="Info"]
+n14.handle(right) -> n17.handle(left)
+n15.handle(right) -> n19.handle(left)
+n16.handle(right) -> n19.handle(top)
+n17.handle(right) -> n19.handle(left) [label="Yes"]
+n17.handle(bottom) -> n18.handle(top) [label="No"]
+n18.handle(right) -> n17.handle(top)
+n19.handle(top) -> Scheduler.n4.handle(bottom) [label="Handled"]
+}
diff --git a/handoff/finance/payment-run-workflow/workflow.fz b/handoff/finance/payment-run-workflow/workflow.fz
index c57f27846ea2976d1006702b9e1573fb8528288b..df711c74751cc81874ae722d914124806db1ca1e 100644
--- a/handoff/finance/payment-run-workflow/workflow.fz
+++ b/handoff/finance/payment-run-workflow/workflow.fz
@@ -1,44 +1,44 @@
-APClerk { # AP Clerk
-n1: circle label:"Start"
-n2: rectangle label:"Select invoices for payment"
-n3: rectangle label:"Create payment batch"
-n4: rectangle label:"Confirm payments sent"
-n5: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(bottom) -> Approval.n6.handle(top) [label="Submit"]
-n4.handle(right) -> n5.handle(left)
-}
-Approval { # Payment Approval
-n6: rectangle label:"Review payment batch"
-n7: diamond label:"Batch amount?"
-n8: rectangle label:"Single approver"
-n9: rectangle label:"Dual approval required"
-n10: diamond label:"Approved?"
-n11: rectangle label:"Return for correction"
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n8.handle(left) [label="< $50K"]
-n7.handle(bottom) -> n9.handle(top) [label=">= $50K"]
-n8.handle(right) -> n10.handle(left)
-n9.handle(right) -> n10.handle(top)
-n10.handle(right) -> Banking.n12.handle(left) [label="Yes"]
-n10.handle(bottom) -> n11.handle(top) [label="No"]
-n11.handle(top) -> APClerk.n2.handle(bottom) [label="Revise"]
-}
-Banking { # Banking System
-n12: rectangle label:"Generate ACH file"
-n13: rectangle label:"Generate check run"
-n14: diamond label:"Payment method?"
-n15: rectangle label:"Submit to bank"
-n16: rectangle label:"Print checks"
-n17: rectangle label:"Confirm transmission"
-n18: rectangle label:"Update vendor records"
-n12.handle(right) -> n14.handle(left)
-n13.handle(right) -> n14.handle(top)
-n14.handle(right) -> n15.handle(left) [label="ACH"]
-n14.handle(bottom) -> n16.handle(top) [label="Check"]
-n15.handle(right) -> n17.handle(left)
-n16.handle(right) -> n17.handle(top)
-n17.handle(right) -> n18.handle(left)
-n18.handle(top) -> APClerk.n4.handle(bottom) [label="Complete"]
-}
+APClerk { # AP Clerk
+n1: circle label:"Start"
+n2: rectangle label:"Select invoices for payment"
+n3: rectangle label:"Create payment batch"
+n4: rectangle label:"Confirm payments sent"
+n5: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(bottom) -> Approval.n6.handle(top) [label="Submit"]
+n4.handle(right) -> n5.handle(left)
+}
+Approval { # Payment Approval
+n6: rectangle label:"Review payment batch"
+n7: diamond label:"Batch amount?"
+n8: rectangle label:"Single approver"
+n9: rectangle label:"Dual approval required"
+n10: diamond label:"Approved?"
+n11: rectangle label:"Return for correction"
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left) [label="< $50K"]
+n7.handle(bottom) -> n9.handle(top) [label=">= $50K"]
+n8.handle(right) -> n10.handle(left)
+n9.handle(right) -> n10.handle(top)
+n10.handle(right) -> Banking.n12.handle(left) [label="Yes"]
+n10.handle(bottom) -> n11.handle(top) [label="No"]
+n11.handle(top) -> APClerk.n2.handle(bottom) [label="Revise"]
+}
+Banking { # Banking System
+n12: rectangle label:"Generate ACH file"
+n13: rectangle label:"Generate check run"
+n14: diamond label:"Payment method?"
+n15: rectangle label:"Submit to bank"
+n16: rectangle label:"Print checks"
+n17: rectangle label:"Confirm transmission"
+n18: rectangle label:"Update vendor records"
+n12.handle(right) -> n14.handle(left)
+n13.handle(right) -> n14.handle(top)
+n14.handle(right) -> n15.handle(left) [label="ACH"]
+n14.handle(bottom) -> n16.handle(top) [label="Check"]
+n15.handle(right) -> n17.handle(left)
+n16.handle(right) -> n17.handle(top)
+n17.handle(right) -> n18.handle(left)
+n18.handle(top) -> APClerk.n4.handle(bottom) [label="Complete"]
+}
diff --git a/handoff/hr/offboarding-workflow/workflow.fz b/handoff/hr/offboarding-workflow/workflow.fz
index c227cec825b29cc9d9fcbbbfceefd2c9c780bbe0..06077f3b6f3f411103be326fc4cda2232945562a 100644
--- a/handoff/hr/offboarding-workflow/workflow.fz
+++ b/handoff/hr/offboarding-workflow/workflow.fz
@@ -1,55 +1,55 @@
-DepartingEmployee { # Departing Employee
-n1: circle label:"Start"
-n2: rectangle label:"Submit resignation"
-n3: rectangle label:"Complete exit interview"
-n4: rectangle label:"Return company equipment"
-n5: rectangle label:"Receive final paycheck"
-n6: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> HR.n7.handle(top) [label="Resignation"]
-n3.handle(bottom) -> HR.n14.handle(top) [label="Feedback"]
-n4.handle(bottom) -> IT.n18.handle(top) [label="Equipment"]
-n5.handle(right) -> n6.handle(left)
-}
-HR { # Human Resources
-n7: rectangle label:"Process resignation"
-n8: rectangle label:"Calculate last working day"
-n9: rectangle label:"Notify payroll"
-n10: rectangle label:"Schedule exit interview"
-n11: diamond label:"Notice period waived?"
-n12: rectangle label:"Process immediate departure"
-n13: rectangle label:"Standard notice period"
-n14: rectangle label:"Conduct exit interview"
-n15: rectangle label:"Document feedback"
-n16: rectangle label:"Calculate final pay"
-n17: rectangle label:"Process severance if applicable"
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left)
-n9.handle(right) -> n10.handle(left)
-n10.handle(right) -> n11.handle(left)
-n11.handle(right) -> n12.handle(left) [label="Yes"]
-n11.handle(bottom) -> n13.handle(top) [label="No"]
-n12.handle(top) -> DepartingEmployee.n3.handle(bottom) [label="Exit now"]
-n13.handle(top) -> DepartingEmployee.n3.handle(bottom) [label="Work notice"]
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left)
-n16.handle(right) -> n17.handle(left)
-n17.handle(top) -> DepartingEmployee.n5.handle(bottom) [label="Pay ready"]
-}
-IT { # IT Department
-n18: rectangle label:"Revoke system access"
-n19: rectangle label:"Disable email account"
-n20: rectangle label:"Backup user data"
-n21: rectangle label:"Collect laptop and badge"
-n22: diamond label:"All equipment returned?"
-n23: rectangle label:"Clear security checklist"
-n24: rectangle label:"Charge for missing items"
-n18.handle(right) -> n19.handle(left)
-n19.handle(right) -> n20.handle(left)
-n20.handle(right) -> n21.handle(left)
-n21.handle(right) -> n22.handle(left)
-n22.handle(right) -> n23.handle(left) [label="Yes"]
-n22.handle(bottom) -> n24.handle(top) [label="No"]
-n23.handle(top) -> DepartingEmployee.n4.handle(bottom) [label="Cleared"]
-n24.handle(top) -> DepartingEmployee.n4.handle(bottom) [label="Deducted"]
-}
+DepartingEmployee { # Departing Employee
+n1: circle label:"Start"
+n2: rectangle label:"Submit resignation"
+n3: rectangle label:"Complete exit interview"
+n4: rectangle label:"Return company equipment"
+n5: rectangle label:"Receive final paycheck"
+n6: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> HR.n7.handle(top) [label="Resignation"]
+n3.handle(bottom) -> HR.n14.handle(top) [label="Feedback"]
+n4.handle(bottom) -> IT.n18.handle(top) [label="Equipment"]
+n5.handle(right) -> n6.handle(left)
+}
+HR { # Human Resources
+n7: rectangle label:"Process resignation"
+n8: rectangle label:"Calculate last working day"
+n9: rectangle label:"Notify payroll"
+n10: rectangle label:"Schedule exit interview"
+n11: diamond label:"Notice period waived?"
+n12: rectangle label:"Process immediate departure"
+n13: rectangle label:"Standard notice period"
+n14: rectangle label:"Conduct exit interview"
+n15: rectangle label:"Document feedback"
+n16: rectangle label:"Calculate final pay"
+n17: rectangle label:"Process severance if applicable"
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left)
+n10.handle(right) -> n11.handle(left)
+n11.handle(right) -> n12.handle(left) [label="Yes"]
+n11.handle(bottom) -> n13.handle(top) [label="No"]
+n12.handle(top) -> DepartingEmployee.n3.handle(bottom) [label="Exit now"]
+n13.handle(top) -> DepartingEmployee.n3.handle(bottom) [label="Work notice"]
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left)
+n17.handle(top) -> DepartingEmployee.n5.handle(bottom) [label="Pay ready"]
+}
+IT { # IT Department
+n18: rectangle label:"Revoke system access"
+n19: rectangle label:"Disable email account"
+n20: rectangle label:"Backup user data"
+n21: rectangle label:"Collect laptop and badge"
+n22: diamond label:"All equipment returned?"
+n23: rectangle label:"Clear security checklist"
+n24: rectangle label:"Charge for missing items"
+n18.handle(right) -> n19.handle(left)
+n19.handle(right) -> n20.handle(left)
+n20.handle(right) -> n21.handle(left)
+n21.handle(right) -> n22.handle(left)
+n22.handle(right) -> n23.handle(left) [label="Yes"]
+n22.handle(bottom) -> n24.handle(top) [label="No"]
+n23.handle(top) -> DepartingEmployee.n4.handle(bottom) [label="Cleared"]
+n24.handle(top) -> DepartingEmployee.n4.handle(bottom) [label="Deducted"]
+}
diff --git a/handoff/llm-operations/dynamic-tool-schema-selection-workflow/README.md b/handoff/llm-operations/dynamic-tool-schema-selection-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..c4d917472a127d82f7c4a0221611173b0da36a44
--- /dev/null
+++ b/handoff/llm-operations/dynamic-tool-schema-selection-workflow/README.md
@@ -0,0 +1,19 @@
+# Dynamic Tool Schema Selection Workflow
+
+Instead of loading all 50 tool schemas into every request, the agent analyses the step, queries the MCP tool registry and injects only the two schemas it needs.
+
+**Template ID:** `dynamic-tool-schema-selection-workflow`  
+**Kind:** workflow  
+**Source domain:** LLM Operations  
+**Primary use case:** handoff  
+**Secondary use cases:** mcp, llm-operations  
+**Complexity:** 2/5  
+**Nodes:** 8  
+**Lanes:** 3  
+**Tags:** [token-optimization, mcp, tool-schemas, tool-routing, llmops]  
+**Source path:** ``  
+**Repo path:** `handoff/llm-operations/dynamic-tool-schema-selection-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/handoff/llm-operations/dynamic-tool-schema-selection-workflow/metadata.json b/handoff/llm-operations/dynamic-tool-schema-selection-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..4a2943d8bafb7256caf7cbf52f139bbb9d120847
--- /dev/null
+++ b/handoff/llm-operations/dynamic-tool-schema-selection-workflow/metadata.json
@@ -0,0 +1,30 @@
+{
+  "template_id": "dynamic-tool-schema-selection-workflow",
+  "workflow_id": "dynamic-tool-schema-selection",
+  "title": "Dynamic Tool Schema Selection Workflow",
+  "kind": "workflow",
+  "source_domain": "LLM Operations",
+  "primary_use_case": "handoff",
+  "secondary_use_cases": [
+    "mcp",
+    "llm-operations"
+  ],
+  "use_cases": [
+    "handoff",
+    "mcp",
+    "llm-operations"
+  ],
+  "complexity": 2,
+  "num_nodes": 8,
+  "num_lanes": 3,
+  "tags": [
+    "token-optimization",
+    "mcp",
+    "tool-schemas",
+    "tool-routing",
+    "llmops"
+  ],
+  "description": "Instead of loading all 50 tool schemas into every request, the agent analyses the step, queries the MCP tool registry and injects only the two schemas it needs.",
+  "source_path": "",
+  "repo_path": "handoff/llm-operations/dynamic-tool-schema-selection-workflow"
+}
diff --git a/handoff/llm-operations/dynamic-tool-schema-selection-workflow/workflow.fz b/handoff/llm-operations/dynamic-tool-schema-selection-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..7d187b2545259a638950f955280d1e4d1f209cf2
--- /dev/null
+++ b/handoff/llm-operations/dynamic-tool-schema-selection-workflow/workflow.fz
@@ -0,0 +1,23 @@
+agent { # AI Agent
+n1: circle label:"New objective"
+n2: rectangle label:"Analyze required capabilities"
+n5: rectangle label:"Construct prompt with 2 schemas"
+n8: circle label:"Execute step"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> registry.n3.handle(top) [label="Request tools by intent"]
+n5.handle(bottom) -> llm.n6.handle(top) [label="Send lean request"]
+}
+
+registry { # MCP Tool Registry
+n3: diamond label:"Match intent to tools"
+n4: rectangle label:"Extract specific schemas (not all 50)"
+n3.handle(right) -> n4.handle(left)
+n4.handle(top) -> agent.n5.handle(bottom) [label="Return 2 schemas"]
+}
+
+llm { # Model API
+n6: rectangle label:"Process 500 tool tokens (not 10k)"
+n7: rectangle label:"Select tool to call"
+n6.handle(right) -> n7.handle(left)
+n7.handle(top) -> agent.n8.handle(bottom) [label="Return tool call"]
+}
diff --git a/handoff/llm-operations/llm-model-router-cost-aware-routing/README.md b/handoff/llm-operations/llm-model-router-cost-aware-routing/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..39fe700e06f1334875f0640a0d89d353598e9926
--- /dev/null
+++ b/handoff/llm-operations/llm-model-router-cost-aware-routing/README.md
@@ -0,0 +1,19 @@
+# LLM Model Router — Cost-Aware Routing
+
+An LLM gateway that reads the token budget, extracts intent and length, then routes the call to the cheap model or the premium one before delivering the response.
+
+**Template ID:** `llm-model-router-cost-aware-routing`  
+**Kind:** workflow  
+**Source domain:** LLM Operations  
+**Primary use case:** handoff  
+**Secondary use cases:** mcp, llm-operations  
+**Complexity:** 2/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [token-optimization, model-routing, llm-gateway, cost, llmops]  
+**Source path:** ``  
+**Repo path:** `handoff/llm-operations/llm-model-router-cost-aware-routing`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/handoff/llm-operations/llm-model-router-cost-aware-routing/metadata.json b/handoff/llm-operations/llm-model-router-cost-aware-routing/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..6ae27d12d4b96dbd4b359b5df1685ab8aa690257
--- /dev/null
+++ b/handoff/llm-operations/llm-model-router-cost-aware-routing/metadata.json
@@ -0,0 +1,30 @@
+{
+  "template_id": "llm-model-router-cost-aware-routing",
+  "workflow_id": "llm-model-router-cost-aware-routing",
+  "title": "LLM Model Router — Cost-Aware Routing",
+  "kind": "workflow",
+  "source_domain": "LLM Operations",
+  "primary_use_case": "handoff",
+  "secondary_use_cases": [
+    "mcp",
+    "llm-operations"
+  ],
+  "use_cases": [
+    "handoff",
+    "mcp",
+    "llm-operations"
+  ],
+  "complexity": 2,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "token-optimization",
+    "model-routing",
+    "llm-gateway",
+    "cost",
+    "llmops"
+  ],
+  "description": "An LLM gateway that reads the token budget, extracts intent and length, then routes the call to the cheap model or the premium one before delivering the response.",
+  "source_path": "",
+  "repo_path": "handoff/llm-operations/llm-model-router-cost-aware-routing"
+}
diff --git a/handoff/llm-operations/llm-model-router-cost-aware-routing/workflow.fz b/handoff/llm-operations/llm-model-router-cost-aware-routing/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..8ca984d2e5c45ee397705bf6504607656aab94e3
--- /dev/null
+++ b/handoff/llm-operations/llm-model-router-cost-aware-routing/workflow.fz
@@ -0,0 +1,28 @@
+client { # Application
+n1: circle label:"User request"
+n10: circle label:"Deliver response"
+n1.handle(bottom) -> gateway.n2.handle(top) [label="Query"]
+}
+
+gateway { # LLM Gateway
+n2: rectangle label:"Extract intent & length"
+n3: diamond label:"Requires heavy reasoning?"
+n4: rectangle label:"Select Flash / Haiku"
+n5: rectangle label:"Select Pro / Opus"
+n8: rectangle label:"Normalize response"
+n9: rectangle label:"Log token metrics"
+n2.handle(right) -> n3.handle(left)
+n3.handle(bottom) -> n4.handle(top) [label="No"]
+n3.handle(right) -> n5.handle(left) [label="Yes"]
+n4.handle(bottom) -> providers.n6.handle(top) [label="Call budget API"]
+n5.handle(bottom) -> providers.n7.handle(top) [label="Call premium API"]
+n8.handle(right) -> n9.handle(left)
+n9.handle(top) -> client.n10.handle(bottom) [label="Final result"]
+}
+
+providers { # Model APIs
+n6: rectangle label:"Process fast"
+n7: rectangle label:"Process deep reasoning"
+n6.handle(top) -> gateway.n8.handle(bottom) [label="Return answer"]
+n7.handle(top) -> gateway.n8.handle(bottom) [label="Return answer"]
+}
diff --git a/handoff/logistics/stock-transfer-workflow/workflow.fz b/handoff/logistics/stock-transfer-workflow/workflow.fz
index 668b091248b908bb5ffc3c4ebefb58d23159f3af..82ceb461e46044541f80babb83055eafdb1fc8f6 100644
--- a/handoff/logistics/stock-transfer-workflow/workflow.fz
+++ b/handoff/logistics/stock-transfer-workflow/workflow.fz
@@ -1,28 +1,28 @@
-supplier { # Supplier
-  n1: circle label:"Start Stock Transfer"
-  n4: rectangle label:"Make Stock Transfer decision"
-  n7: rectangle label:"Continue Stock Transfer process"
-  n10: circle label:"End Stock Transfer"
-  n1.handle(bottom) -> warehouse.n2.handle(top)
-  n4.handle(bottom) -> warehouse.n5.handle(top)
-  n7.handle(bottom) -> warehouse.n8.handle(top)
-}
-
-warehouse { # Warehouse
-  n2: rectangle label:"Receive Stock Transfer request"
-  n5: rectangle label:"Update records for Stock Transfer"
-  n8: rectangle label:"Continue Stock Transfer process"
-  n2.handle(bottom) -> iot_sensor.n3.handle(top) [label="Next"]
-  n5.handle(bottom) -> iot_sensor.n6.handle(top) [label="Done"]
-  n8.handle(bottom) -> iot_sensor.n9.handle(top) [label="Processed"]
-}
-
-iot_sensor { # Iot_Sensor
-  n3: rectangle label:"Review Stock Transfer details"
-  n6: rectangle label:"Continue Stock Transfer process"
-  n9: diamond label:"Continue Stock Transfer process"
-  n9.handle(right) -> supplier.n10.handle(bottom)
-  n9.handle(left) -> warehouse.n8.handle(left) [label="Retry/Rejected"]
-  n3.handle(right) -> supplier.n4.handle(left)
-  n6.handle(right) -> supplier.n7.handle(left)
-}
+supplier { # Supplier
+  n1: circle label:"Start Stock Transfer"
+  n4: rectangle label:"Make Stock Transfer decision"
+  n7: rectangle label:"Continue Stock Transfer process"
+  n10: circle label:"End Stock Transfer"
+  n1.handle(bottom) -> warehouse.n2.handle(top)
+  n4.handle(bottom) -> warehouse.n5.handle(top)
+  n7.handle(bottom) -> warehouse.n8.handle(top)
+}
+
+warehouse { # Warehouse
+  n2: rectangle label:"Receive Stock Transfer request"
+  n5: rectangle label:"Update records for Stock Transfer"
+  n8: rectangle label:"Continue Stock Transfer process"
+  n2.handle(bottom) -> iot_sensor.n3.handle(top) [label="Next"]
+  n5.handle(bottom) -> iot_sensor.n6.handle(top) [label="Done"]
+  n8.handle(bottom) -> iot_sensor.n9.handle(top) [label="Processed"]
+}
+
+iot_sensor { # Iot_Sensor
+  n3: rectangle label:"Review Stock Transfer details"
+  n6: rectangle label:"Continue Stock Transfer process"
+  n9: diamond label:"Continue Stock Transfer process"
+  n9.handle(right) -> supplier.n10.handle(bottom)
+  n9.handle(left) -> warehouse.n8.handle(left) [label="Retry/Rejected"]
+  n3.handle(right) -> supplier.n4.handle(left)
+  n6.handle(right) -> supplier.n7.handle(left)
+}
diff --git a/handoff/logistics/warehouse-transfer-workflow/workflow.fz b/handoff/logistics/warehouse-transfer-workflow/workflow.fz
index 3e04513b6c2224e5dee5de9ecdd8ee65b949e328..2c16c917823ae2c8a331950c3aa0902540a0ed05 100644
--- a/handoff/logistics/warehouse-transfer-workflow/workflow.fz
+++ b/handoff/logistics/warehouse-transfer-workflow/workflow.fz
@@ -1,27 +1,27 @@
-supplier { # Supplier
-  n1: circle label:"Start Warehouse Transfer"
-  n4: rectangle label:"Make Warehouse Transfer decision"
-  n7: rectangle label:"Continue Warehouse Transfer process"
-  n10: circle label:"End Warehouse Transfer"
-  n1.handle(bottom) -> warehouse.n2.handle(top)
-  n4.handle(bottom) -> warehouse.n5.handle(top)
-  n7.handle(bottom) -> warehouse.n8.handle(top)
-}
-
-warehouse { # Warehouse
-  n2: rectangle label:"Receive Warehouse Transfer request"
-  n5: rectangle label:"Update records for Warehouse Transfer"
-  n8: rectangle label:"Continue Warehouse Transfer process"
-  n2.handle(bottom) -> iot_sensor.n3.handle(top) [label="Next"]
-  n5.handle(bottom) -> iot_sensor.n6.handle(top) [label="Done"]
-  n8.handle(bottom) -> iot_sensor.n9.handle(top) [label="Processed"]
-}
-
-iot_sensor { # Iot Sensor
-  n3: rectangle label:"Review Warehouse Transfer details"
-  n6: rectangle label:"Continue Warehouse Transfer process"
-  n9: rectangle label:"Continue Warehouse Transfer process"
-  n9.handle(right) -> supplier.n10.handle(bottom)
-  n6.handle(right) -> supplier.n7.handle(left)
-  n3.handle(right) -> supplier.n4.handle(left)
-}
+supplier { # Supplier
+  n1: circle label:"Start Warehouse Transfer"
+  n4: rectangle label:"Make Warehouse Transfer decision"
+  n7: rectangle label:"Continue Warehouse Transfer process"
+  n10: circle label:"End Warehouse Transfer"
+  n1.handle(bottom) -> warehouse.n2.handle(top)
+  n4.handle(bottom) -> warehouse.n5.handle(top)
+  n7.handle(bottom) -> warehouse.n8.handle(top)
+}
+
+warehouse { # Warehouse
+  n2: rectangle label:"Receive Warehouse Transfer request"
+  n5: rectangle label:"Update records for Warehouse Transfer"
+  n8: rectangle label:"Continue Warehouse Transfer process"
+  n2.handle(bottom) -> iot_sensor.n3.handle(top) [label="Next"]
+  n5.handle(bottom) -> iot_sensor.n6.handle(top) [label="Done"]
+  n8.handle(bottom) -> iot_sensor.n9.handle(top) [label="Processed"]
+}
+
+iot_sensor { # Iot Sensor
+  n3: rectangle label:"Review Warehouse Transfer details"
+  n6: rectangle label:"Continue Warehouse Transfer process"
+  n9: rectangle label:"Continue Warehouse Transfer process"
+  n9.handle(right) -> supplier.n10.handle(bottom)
+  n6.handle(right) -> supplier.n7.handle(left)
+  n3.handle(right) -> supplier.n4.handle(left)
+}
diff --git a/handoff/patterns/api-gateway-workflow/README.md b/handoff/patterns/api-gateway-workflow/README.md
index aade7ccd87519a768f4bc9f0d68b2df59c27124f..861ab71cf03c0e0825900292bca4800c342786f4 100644
--- a/handoff/patterns/api-gateway-workflow/README.md
+++ b/handoff/patterns/api-gateway-workflow/README.md
@@ -6,7 +6,7 @@ API Gateway pattern with request authentication, rate limiting, request routing
 **Kind:** workflow  
 **Source domain:** patterns  
 **Primary use case:** handoff  
-**Secondary use cases:** security, mcp  
+**Secondary use cases:** security, mcp, architecture, patterns  
 **Complexity:** 3/5  
 **Nodes:** 7  
 **Lanes:** 2  
diff --git a/handoff/patterns/api-gateway-workflow/metadata.json b/handoff/patterns/api-gateway-workflow/metadata.json
index 4453dbbca1b616740898b6ba3a8d58e98edeebd9..177248457e656195f597cd5258d4cad8d080a273 100644
--- a/handoff/patterns/api-gateway-workflow/metadata.json
+++ b/handoff/patterns/api-gateway-workflow/metadata.json
@@ -7,12 +7,16 @@
   "primary_use_case": "handoff",
   "secondary_use_cases": [
     "security",
-    "mcp"
+    "mcp",
+    "architecture",
+    "patterns"
   ],
   "use_cases": [
     "handoff",
     "security",
-    "mcp"
+    "mcp",
+    "architecture",
+    "patterns"
   ],
   "complexity": 3,
   "num_nodes": 7,
diff --git a/handoff/patterns/api-gateway-workflow/workflow.fz b/handoff/patterns/api-gateway-workflow/workflow.fz
index 918d6ef86e76ba782f31a3efe0b17acb66b33d0e..91648224e89210bba7e371c6d37867edc2295664 100644
--- a/handoff/patterns/api-gateway-workflow/workflow.fz
+++ b/handoff/patterns/api-gateway-workflow/workflow.fz
@@ -1,44 +1,44 @@
-Client { # Client
-n1: circle label:"Start"
-n2: rectangle label:"Send API request"
-n3: rectangle label:"Receive response"
-n4: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Gateway.n5.handle(top) [label="HTTP Request"]
-n3.handle(right) -> n4.handle(left)
-}
-Gateway { # API Gateway
-n5: rectangle label:"Receive incoming request"
-n6: rectangle label:"Validate API key"
-n7: diamond label:"Authenticated?"
-n8: rectangle label:"Check rate limits"
-n9: rectangle label:"Return 401 Unauthorized"
-n10: diamond label:"Within rate limit?"
-n11: rectangle label:"Route to service"
-n12: rectangle label:"Return 429 Too Many Requests"
-n13: rectangle label:"Transform response"
-n5.handle(right) -> n6.handle(left)
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n8.handle(left) [label="Yes"]
-n7.handle(bottom) -> n9.handle(top) [label="No"]
-n8.handle(right) -> n10.handle(left)
-n9.handle(top) -> Client.n3.handle(bottom) [label="401"]
-n10.handle(right) -> n11.handle(left) [label="Yes"]
-n10.handle(bottom) -> n12.handle(top) [label="No"]
-n11.handle(bottom) -> Backend.n14.handle(top) [label="Forward"]
-n12.handle(top) -> Client.n3.handle(bottom) [label="429"]
-n13.handle(top) -> Client.n3.handle(bottom) [label="Response"]
-}
-Backend { # Backend Service
-n14: rectangle label:"Process request"
-n15: diamond label:"Request valid?"
-n16: rectangle label:"Execute business logic"
-n17: rectangle label:"Return error response"
-n18: rectangle label:"Return success response"
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left) [label="Yes"]
-n15.handle(bottom) -> n17.handle(top) [label="No"]
-n16.handle(right) -> n18.handle(left)
-n17.handle(top) -> Gateway.n13.handle(bottom) [label="Error"]
-n18.handle(top) -> Gateway.n13.handle(bottom) [label="Success"]
-}
+Client { # Client
+n1: circle label:"Start"
+n2: rectangle label:"Send API request"
+n3: rectangle label:"Receive response"
+n4: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Gateway.n5.handle(top) [label="HTTP Request"]
+n3.handle(right) -> n4.handle(left)
+}
+Gateway { # API Gateway
+n5: rectangle label:"Receive incoming request"
+n6: rectangle label:"Validate API key"
+n7: diamond label:"Authenticated?"
+n8: rectangle label:"Check rate limits"
+n9: rectangle label:"Return 401 Unauthorized"
+n10: diamond label:"Within rate limit?"
+n11: rectangle label:"Route to service"
+n12: rectangle label:"Return 429 Too Many Requests"
+n13: rectangle label:"Transform response"
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left) [label="Yes"]
+n7.handle(bottom) -> n9.handle(top) [label="No"]
+n8.handle(right) -> n10.handle(left)
+n9.handle(top) -> Client.n3.handle(bottom) [label="401"]
+n10.handle(right) -> n11.handle(left) [label="Yes"]
+n10.handle(bottom) -> n12.handle(top) [label="No"]
+n11.handle(bottom) -> Backend.n14.handle(top) [label="Forward"]
+n12.handle(top) -> Client.n3.handle(bottom) [label="429"]
+n13.handle(top) -> Client.n3.handle(bottom) [label="Response"]
+}
+Backend { # Backend Service
+n14: rectangle label:"Process request"
+n15: diamond label:"Request valid?"
+n16: rectangle label:"Execute business logic"
+n17: rectangle label:"Return error response"
+n18: rectangle label:"Return success response"
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left) [label="Yes"]
+n15.handle(bottom) -> n17.handle(top) [label="No"]
+n16.handle(right) -> n18.handle(left)
+n17.handle(top) -> Gateway.n13.handle(bottom) [label="Error"]
+n18.handle(top) -> Gateway.n13.handle(bottom) [label="Success"]
+}
diff --git a/handoff/patterns/escalation-pattern-workflow/README.md b/handoff/patterns/escalation-pattern-workflow/README.md
index 52a4d9ea143585930b270b87d6fa07e75a106d73..4bddb20411503cf215b580075958ad11aab4dfd1 100644
--- a/handoff/patterns/escalation-pattern-workflow/README.md
+++ b/handoff/patterns/escalation-pattern-workflow/README.md
@@ -6,7 +6,7 @@ This workflow models escalating issues to higher authority when needed.
 **Kind:** workflow  
 **Source domain:** patterns  
 **Primary use case:** handoff  
-**Secondary use cases:** None  
+**Secondary use cases:** patterns  
 **Complexity:** 3/5  
 **Nodes:** 10  
 **Lanes:** 3  
diff --git a/handoff/patterns/escalation-pattern-workflow/metadata.json b/handoff/patterns/escalation-pattern-workflow/metadata.json
index 3b73435bd5d059fabd8f7495fffa927af133fda8..5e10fd6cfddc4c5e766866465cfdb4c31367ec3f 100644
--- a/handoff/patterns/escalation-pattern-workflow/metadata.json
+++ b/handoff/patterns/escalation-pattern-workflow/metadata.json
@@ -5,9 +5,12 @@
   "kind": "workflow",
   "source_domain": "patterns",
   "primary_use_case": "handoff",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "patterns"
+  ],
   "use_cases": [
-    "handoff"
+    "handoff",
+    "patterns"
   ],
   "complexity": 3,
   "num_nodes": 10,
diff --git a/handoff/patterns/escalation-pattern-workflow/workflow.fz b/handoff/patterns/escalation-pattern-workflow/workflow.fz
index ed93834e42dfd379da68eb693bfcc83089bdf74c..8a2cbbd48f1c457e7b95a98a7630827561cf3469 100644
--- a/handoff/patterns/escalation-pattern-workflow/workflow.fz
+++ b/handoff/patterns/escalation-pattern-workflow/workflow.fz
@@ -1,28 +1,28 @@
-user { # User
-  n1: circle label:"Start Escalation Pattern"
-  n4: rectangle label:"Execute Escalation Pattern action"
-  n7: rectangle label:"Monitor Escalation Pattern status"
-  n10: circle label:"End Escalation Pattern"
-  n1.handle(bottom) -> app.n2.handle(top)
-  n4.handle(bottom) -> app.n5.handle(top)
-  n7.handle(bottom) -> app.n8.handle(top)
-}
-
-app { # App
-  n2: rectangle label:"Receive Escalation Pattern event"
-  n5: rectangle label:"Record Escalation Pattern outcome"
-  n8: rectangle label:"Monitor Escalation Pattern status"
-  n2.handle(bottom) -> service.n3.handle(top)
-  n5.handle(bottom) -> service.n6.handle(top)
-  n8.handle(bottom) -> service.n9.handle(top)
-}
-
-service { # Service
-  n3: rectangle label:"Validate Escalation Pattern conditions"
-  n6: rectangle label:"Monitor Escalation Pattern status"
-  n9: diamond label:"Monitor Escalation Pattern status"
-  n3.handle(right) -> user.n4.handle(left) [label="Processed"]
-  n9.handle(left) -> app.n8.handle(left) [label="Retry/Rejected"]
-  n9.handle(right) -> user.n10.handle(bottom) [label="Valid"]
-  n6.handle(right) -> user.n7.handle(left) [label="Success"]
-}
+user { # User
+  n1: circle label:"Start Escalation Pattern"
+  n4: rectangle label:"Execute Escalation Pattern action"
+  n7: rectangle label:"Monitor Escalation Pattern status"
+  n10: circle label:"End Escalation Pattern"
+  n1.handle(bottom) -> app.n2.handle(top)
+  n4.handle(bottom) -> app.n5.handle(top)
+  n7.handle(bottom) -> app.n8.handle(top)
+}
+
+app { # App
+  n2: rectangle label:"Receive Escalation Pattern event"
+  n5: rectangle label:"Record Escalation Pattern outcome"
+  n8: rectangle label:"Monitor Escalation Pattern status"
+  n2.handle(bottom) -> service.n3.handle(top)
+  n5.handle(bottom) -> service.n6.handle(top)
+  n8.handle(bottom) -> service.n9.handle(top)
+}
+
+service { # Service
+  n3: rectangle label:"Validate Escalation Pattern conditions"
+  n6: rectangle label:"Monitor Escalation Pattern status"
+  n9: diamond label:"Monitor Escalation Pattern status"
+  n3.handle(right) -> user.n4.handle(left) [label="Processed"]
+  n9.handle(left) -> app.n8.handle(left) [label="Retry/Rejected"]
+  n9.handle(right) -> user.n10.handle(bottom) [label="Valid"]
+  n6.handle(right) -> user.n7.handle(left) [label="Success"]
+}
diff --git a/handoff/patterns/routing-slip-workflow/README.md b/handoff/patterns/routing-slip-workflow/README.md
index 46b7d74d54985286882b6063a15f390f757e8c6a..5f2847159657ad8e07f2c9dabdb1a0caf8de78a6 100644
--- a/handoff/patterns/routing-slip-workflow/README.md
+++ b/handoff/patterns/routing-slip-workflow/README.md
@@ -6,7 +6,7 @@ This workflow models having messages carry their own routing instructions.
 **Kind:** workflow  
 **Source domain:** patterns  
 **Primary use case:** handoff  
-**Secondary use cases:** None  
+**Secondary use cases:** patterns  
 **Complexity:** 4/5  
 **Nodes:** 13  
 **Lanes:** 4  
diff --git a/handoff/patterns/routing-slip-workflow/metadata.json b/handoff/patterns/routing-slip-workflow/metadata.json
index 736c4cac486eea8517fd882eba4679d90094bf7f..f311d83278bff35661fe9b3f418563273f7a042c 100644
--- a/handoff/patterns/routing-slip-workflow/metadata.json
+++ b/handoff/patterns/routing-slip-workflow/metadata.json
@@ -5,9 +5,12 @@
   "kind": "workflow",
   "source_domain": "patterns",
   "primary_use_case": "handoff",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "patterns"
+  ],
   "use_cases": [
-    "handoff"
+    "handoff",
+    "patterns"
   ],
   "complexity": 4,
   "num_nodes": 13,
diff --git a/handoff/patterns/routing-slip-workflow/workflow.fz b/handoff/patterns/routing-slip-workflow/workflow.fz
index 0b9615ee72bfd217cb7ea2fd2e6b25454d2d696d..690e26edcf4a97d80dfa3773e9fd48991ad42a67 100644
--- a/handoff/patterns/routing-slip-workflow/workflow.fz
+++ b/handoff/patterns/routing-slip-workflow/workflow.fz
@@ -1,38 +1,38 @@
-user { # User
-  n1: circle label:"Start Routing Slip"
-  n5: rectangle label:"Record Routing Slip outcome"
-  n9: rectangle label:"Monitor Routing Slip status"
-  n13: circle label:"End Routing Slip"
-  n1.handle(bottom) -> app.n2.handle(top)
-  n5.handle(bottom) -> app.n6.handle(top) [label="Done"]
-  n9.handle(bottom) -> app.n10.handle(top)
-}
-
-app { # App
-  n2: rectangle label:"Receive Routing Slip event"
-  n6: rectangle label:"Monitor Routing Slip status"
-  n10: rectangle label:"Monitor Routing Slip status"
-  n2.handle(bottom) -> service.n3.handle(top) [label="Next"]
-  n6.handle(bottom) -> service.n7.handle(top)
-  n10.handle(bottom) -> service.n11.handle(top)
-}
-
-service { # Service
-  n3: rectangle label:"Validate Routing Slip conditions"
-  n7: rectangle label:"Monitor Routing Slip status"
-  n11: rectangle label:"Monitor Routing Slip status"
-  n3.handle(bottom) -> database.n4.handle(top)
-  n7.handle(bottom) -> database.n8.handle(top)
-  n11.handle(bottom) -> database.n12.handle(top) [label="Success"]
-}
-
-database { # Database
-  n4: diamond label:"Execute Routing Slip action"
-  n8: rectangle label:"Monitor Routing Slip status"
-  n12: diamond label:"Monitor Routing Slip status"
-  n12.handle(left) -> service.n11.handle(left) [label="Retry/Rejected"]
-  n12.handle(right) -> user.n13.handle(bottom)
-  n8.handle(right) -> user.n9.handle(left) [label="Processed"]
-  n4.handle(left) -> service.n3.handle(left) [label="Retry/Rejected"]
-  n4.handle(right) -> user.n5.handle(left)
-}
+user { # User
+  n1: circle label:"Start Routing Slip"
+  n5: rectangle label:"Record Routing Slip outcome"
+  n9: rectangle label:"Monitor Routing Slip status"
+  n13: circle label:"End Routing Slip"
+  n1.handle(bottom) -> app.n2.handle(top)
+  n5.handle(bottom) -> app.n6.handle(top) [label="Done"]
+  n9.handle(bottom) -> app.n10.handle(top)
+}
+
+app { # App
+  n2: rectangle label:"Receive Routing Slip event"
+  n6: rectangle label:"Monitor Routing Slip status"
+  n10: rectangle label:"Monitor Routing Slip status"
+  n2.handle(bottom) -> service.n3.handle(top) [label="Next"]
+  n6.handle(bottom) -> service.n7.handle(top)
+  n10.handle(bottom) -> service.n11.handle(top)
+}
+
+service { # Service
+  n3: rectangle label:"Validate Routing Slip conditions"
+  n7: rectangle label:"Monitor Routing Slip status"
+  n11: rectangle label:"Monitor Routing Slip status"
+  n3.handle(bottom) -> database.n4.handle(top)
+  n7.handle(bottom) -> database.n8.handle(top)
+  n11.handle(bottom) -> database.n12.handle(top) [label="Success"]
+}
+
+database { # Database
+  n4: diamond label:"Execute Routing Slip action"
+  n8: rectangle label:"Monitor Routing Slip status"
+  n12: diamond label:"Monitor Routing Slip status"
+  n12.handle(left) -> service.n11.handle(left) [label="Retry/Rejected"]
+  n12.handle(right) -> user.n13.handle(bottom)
+  n8.handle(right) -> user.n9.handle(left) [label="Processed"]
+  n4.handle(left) -> service.n3.handle(left) [label="Retry/Rejected"]
+  n4.handle(right) -> user.n5.handle(left)
+}
diff --git a/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/README.md b/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..c76549d7617c563a0958163cd19b09298c3bad8e
--- /dev/null
+++ b/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/README.md
@@ -0,0 +1,19 @@
+# Customer Onboarding & Sales Handoff Workflow
+
+Three-lane onboarding workflow where the sales team hands the closed deal to the onboarding specialist, who runs the kickoff and setup tasks with the customer.
+
+**Template ID:** `customer-onboarding-sales-handoff-workflow`  
+**Kind:** workflow  
+**Source domain:** Process Mapping  
+**Primary use case:** handoff  
+**Secondary use cases:** onboarding, process-mapping  
+**Complexity:** 3/5  
+**Nodes:** 19  
+**Lanes:** 3  
+**Tags:** [process-mapping, customer-onboarding, handoff, sales, kickoff]  
+**Source path:** ``  
+**Repo path:** `handoff/process-mapping/customer-onboarding-sales-handoff-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/metadata.json b/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..9ad62fab1a2587258747183c0c3e4d8971ae7b6b
--- /dev/null
+++ b/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/metadata.json
@@ -0,0 +1,30 @@
+{
+  "template_id": "customer-onboarding-sales-handoff-workflow",
+  "workflow_id": "customer-onboarding-sales-handoff",
+  "title": "Customer Onboarding & Sales Handoff Workflow",
+  "kind": "workflow",
+  "source_domain": "Process Mapping",
+  "primary_use_case": "handoff",
+  "secondary_use_cases": [
+    "onboarding",
+    "process-mapping"
+  ],
+  "use_cases": [
+    "handoff",
+    "onboarding",
+    "process-mapping"
+  ],
+  "complexity": 3,
+  "num_nodes": 19,
+  "num_lanes": 3,
+  "tags": [
+    "process-mapping",
+    "customer-onboarding",
+    "handoff",
+    "sales",
+    "kickoff"
+  ],
+  "description": "Three-lane onboarding workflow where the sales team hands the closed deal to the onboarding specialist, who runs the kickoff and setup tasks with the customer.",
+  "source_path": "",
+  "repo_path": "handoff/process-mapping/customer-onboarding-sales-handoff-workflow"
+}
diff --git a/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/workflow.fz b/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..dc7924df415b28f7b84726b5881efd718d833f8f
--- /dev/null
+++ b/handoff/process-mapping/customer-onboarding-sales-handoff-workflow/workflow.fz
@@ -0,0 +1,49 @@
+sales { # Sales Team
+n1: circle label:"Start"
+n2: rectangle label:"Send Welcome Email & Contract"
+n3: rectangle label:"Receive Signed Contract"
+n4: rectangle label:"Create Internal Ticket"
+n5: circle label:"Handoff"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(right) -> n4.handle(left)
+n4.handle(right) -> n5.handle(left)
+n5.handle(bottom) -> onboarding.n6.handle(top) [label="Ticket Created"]
+}
+
+onboarding { # Onboarding Specialist
+n6: rectangle label:"Review Client Info & Goals"
+n7: rectangle label:"Schedule Kickoff Call"
+n8: rectangle label:"Conduct Kickoff Meeting"
+n9: rectangle label:"Configure Account"
+n10: rectangle label:"Prepare Training Materials"
+n11: rectangle label:"Grant System Access"
+n12: circle label:"Complete"
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left)
+n10.handle(right) -> n11.handle(left)
+n11.handle(right) -> n12.handle(left)
+n7.handle(bottom) -> customer.n13.handle(top) [label="Sends Invite"]
+n8.handle(bottom) -> customer.n14.handle(top) [label="Holds Meeting"]
+n11.handle(bottom) -> customer.n15.handle(top) [label="Sends Credentials"]
+}
+
+customer { # Customer
+n13: rectangle label:"Receive Meeting Invite"
+n14: rectangle label:"Attend Kickoff Meeting"
+n15: rectangle label:"Receive Login & Materials"
+n16: diamond label:"First Login Successful?"
+n17: rectangle label:"Complete Setup Tasks"
+n18: rectangle label:"Confirm Go-Live"
+n19: circle label:"Onboarded!"
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left) [label="Yes"]
+n17.handle(right) -> n18.handle(left)
+n18.handle(right) -> n19.handle(left)
+n16.handle(top) -> onboarding.n11.handle(bottom) [label="No - Needs help"]
+n18.handle(top) -> onboarding.n12.handle(bottom) [label="Notify Success"]
+}
diff --git a/handoff/process-mapping/customer-service-escalation-workflow/README.md b/handoff/process-mapping/customer-service-escalation-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd876f063f4464313d89fb0f54619c061de79d5a
--- /dev/null
+++ b/handoff/process-mapping/customer-service-escalation-workflow/README.md
@@ -0,0 +1,19 @@
+# Customer Service Escalation Workflow
+
+Customer support workflow that applies the standard greeting and service protocol, then escalates to tier 2 when the standard path cannot resolve the request.
+
+**Template ID:** `customer-service-escalation-workflow`  
+**Kind:** workflow  
+**Source domain:** Process Mapping  
+**Primary use case:** handoff  
+**Secondary use cases:** support, process-mapping  
+**Complexity:** 2/5  
+**Nodes:** 11  
+**Lanes:** 2  
+**Tags:** [process-mapping, support, escalation, service, tier-2]  
+**Source path:** ``  
+**Repo path:** `handoff/process-mapping/customer-service-escalation-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/handoff/process-mapping/customer-service-escalation-workflow/metadata.json b/handoff/process-mapping/customer-service-escalation-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..538ea1a88f3f50c98712c6616a497be5bef5f308
--- /dev/null
+++ b/handoff/process-mapping/customer-service-escalation-workflow/metadata.json
@@ -0,0 +1,30 @@
+{
+  "template_id": "customer-service-escalation-workflow",
+  "workflow_id": "customer-service-escalation",
+  "title": "Customer Service Escalation Workflow",
+  "kind": "workflow",
+  "source_domain": "Process Mapping",
+  "primary_use_case": "handoff",
+  "secondary_use_cases": [
+    "support",
+    "process-mapping"
+  ],
+  "use_cases": [
+    "handoff",
+    "support",
+    "process-mapping"
+  ],
+  "complexity": 2,
+  "num_nodes": 11,
+  "num_lanes": 2,
+  "tags": [
+    "process-mapping",
+    "support",
+    "escalation",
+    "service",
+    "tier-2"
+  ],
+  "description": "Customer support workflow that applies the standard greeting and service protocol, then escalates to tier 2 when the standard path cannot resolve the request.",
+  "source_path": "",
+  "repo_path": "handoff/process-mapping/customer-service-escalation-workflow"
+}
diff --git a/handoff/process-mapping/customer-service-escalation-workflow/workflow.fz b/handoff/process-mapping/customer-service-escalation-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..c89991169786b7c082dbf00691b5b51a3717cfae
--- /dev/null
+++ b/handoff/process-mapping/customer-service-escalation-workflow/workflow.fz
@@ -0,0 +1,28 @@
+CustomerInitiation { # CustomerInitiation
+  n1: circle label:"Customer Contact Initiated"
+  n2: rectangle label:"Follow Standard Greeting Protocol"
+  n3: rectangle label:"Identify Customer Needs"
+  n4: diamond label:"Standard Service Path?"
+  n5: rectangle label:"Route to Specialized Team"
+  n6: circle label:"Service Path Defined"
+  n4.handle(right) -> n6.handle(left) [label="Yes"]
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left)
+  n3.handle(right) -> n4.handle(left)
+  n5.handle(right) -> n6.handle(bottom)
+  n4.handle(bottom) -> n5.handle(left) [label="No"]
+  n6.handle(right) -> ServiceExecution.n7.handle(left)
+}
+
+ServiceExecution { # ServiceExecution
+  n7: rectangle label:"Execute Standard Service Protocol"
+  n8: rectangle label:"Log All Interactions & Outcomes"
+  n9: diamond label:"Issue Resolved?"
+  n10: rectangle label:"Escalate to Tier 2 Support"
+  n11: circle label:"Service Complete"
+  n9.handle(right) -> n11.handle(left) [label="Yes"]
+  n9.handle(bottom) -> n10.handle(top) [label="No"]
+  n8.handle(right) -> n9.handle(left)
+  n10.handle(left) -> n8.handle(bottom)
+  n7.handle(right) -> n8.handle(left)
+}
diff --git a/handoff/process-mapping/handoff-readiness-checklist-workflow/README.md b/handoff/process-mapping/handoff-readiness-checklist-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..2f95e9dcab09c218e165a2d5729927a3fdabba2a
--- /dev/null
+++ b/handoff/process-mapping/handoff-readiness-checklist-workflow/README.md
@@ -0,0 +1,19 @@
+# Handoff Readiness Checklist Workflow
+
+Handoff workflow with a completeness gate: the handoff checklist must be fully met before the receiving team approves and work moves forward.
+
+**Template ID:** `handoff-readiness-checklist-workflow`  
+**Kind:** workflow  
+**Source domain:** Process Mapping  
+**Primary use case:** handoff  
+**Secondary use cases:** approval, process-mapping  
+**Complexity:** 2/5  
+**Nodes:** 10  
+**Lanes:** 2  
+**Tags:** [process-mapping, handoff, checklist, approval, transition]  
+**Source path:** ``  
+**Repo path:** `handoff/process-mapping/handoff-readiness-checklist-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/handoff/process-mapping/handoff-readiness-checklist-workflow/metadata.json b/handoff/process-mapping/handoff-readiness-checklist-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..b83f87aa4614545a5612233254b3c1ddeacfc6e0
--- /dev/null
+++ b/handoff/process-mapping/handoff-readiness-checklist-workflow/metadata.json
@@ -0,0 +1,30 @@
+{
+  "template_id": "handoff-readiness-checklist-workflow",
+  "workflow_id": "handoff-readiness-checklist",
+  "title": "Handoff Readiness Checklist Workflow",
+  "kind": "workflow",
+  "source_domain": "Process Mapping",
+  "primary_use_case": "handoff",
+  "secondary_use_cases": [
+    "approval",
+    "process-mapping"
+  ],
+  "use_cases": [
+    "handoff",
+    "approval",
+    "process-mapping"
+  ],
+  "complexity": 2,
+  "num_nodes": 10,
+  "num_lanes": 2,
+  "tags": [
+    "process-mapping",
+    "handoff",
+    "checklist",
+    "approval",
+    "transition"
+  ],
+  "description": "Handoff workflow with a completeness gate: the handoff checklist must be fully met before the receiving team approves and work moves forward.",
+  "source_path": "",
+  "repo_path": "handoff/process-mapping/handoff-readiness-checklist-workflow"
+}
diff --git a/handoff/process-mapping/handoff-readiness-checklist-workflow/workflow.fz b/handoff/process-mapping/handoff-readiness-checklist-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..df2448e2dff8a6dfabcd7f3c38c0715e0480ee61
--- /dev/null
+++ b/handoff/process-mapping/handoff-readiness-checklist-workflow/workflow.fz
@@ -0,0 +1,26 @@
+PreparationPhase { # PreparationPhase
+  n1: circle label:"Work Ready for Handoff"
+  n2: rectangle label:"Complete Handoff Checklist"
+  n3: diamond label:"All Requirements Met?"
+  n4: rectangle label:"Revise Work Package"
+  n5: circle label:"Handoff Approved"
+  n3.handle(right) -> n5.handle(left) [label="Yes"]
+  n3.handle(bottom) -> n4.handle(top) [label="No"]
+  n2.handle(right) -> n3.handle(left)
+  n4.handle(left) -> n2.handle(bottom)
+  n1.handle(right) -> n2.handle(left)
+  n5.handle(right) -> ReceivingPhase.n6.handle(left)
+}
+
+ReceivingPhase { # ReceivingPhase
+  n6: circle label:"Work Received"
+  n7: rectangle label:"Review Work Against Checklist"
+  n8: diamond label:"Work Accepted?"
+  n9: circle label:"Handoff Complete"
+  n10: rectangle label:"Request Clarification"
+  n8.handle(right) -> n9.handle(left) [label="Yes"]
+  n6.handle(right) -> n7.handle(left)
+  n7.handle(right) -> n8.handle(left)
+  n10.handle(top) -> n4.handle(bottom)
+  n8.handle(top) -> n10.handle(bottom) [label="No"]
+}
diff --git a/handoff/process-mapping/ownership-assignment-escalation-workflow/README.md b/handoff/process-mapping/ownership-assignment-escalation-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..b70d595491195f60e0b6fe48a17f307343a76809
--- /dev/null
+++ b/handoff/process-mapping/ownership-assignment-escalation-workflow/README.md
@@ -0,0 +1,19 @@
+# Ownership Assignment & Escalation Workflow
+
+Work assignment workflow that names an accountable owner, checks for blockers, escalates to the manager and confirms the assignment with everyone involved.
+
+**Template ID:** `ownership-assignment-escalation-workflow`  
+**Kind:** workflow  
+**Source domain:** Process Mapping  
+**Primary use case:** handoff  
+**Secondary use cases:** process-mapping  
+**Complexity:** 2/5  
+**Nodes:** 12  
+**Lanes:** 2  
+**Tags:** [process-mapping, ownership, escalation, assignment, blockers]  
+**Source path:** ``  
+**Repo path:** `handoff/process-mapping/ownership-assignment-escalation-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/handoff/process-mapping/ownership-assignment-escalation-workflow/metadata.json b/handoff/process-mapping/ownership-assignment-escalation-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..17cbc63205d15b45ca13777fb2770acd245615f8
--- /dev/null
+++ b/handoff/process-mapping/ownership-assignment-escalation-workflow/metadata.json
@@ -0,0 +1,28 @@
+{
+  "template_id": "ownership-assignment-escalation-workflow",
+  "workflow_id": "ownership-assignment-escalation",
+  "title": "Ownership Assignment & Escalation Workflow",
+  "kind": "workflow",
+  "source_domain": "Process Mapping",
+  "primary_use_case": "handoff",
+  "secondary_use_cases": [
+    "process-mapping"
+  ],
+  "use_cases": [
+    "handoff",
+    "process-mapping"
+  ],
+  "complexity": 2,
+  "num_nodes": 12,
+  "num_lanes": 2,
+  "tags": [
+    "process-mapping",
+    "ownership",
+    "escalation",
+    "assignment",
+    "blockers"
+  ],
+  "description": "Work assignment workflow that names an accountable owner, checks for blockers, escalates to the manager and confirms the assignment with everyone involved.",
+  "source_path": "",
+  "repo_path": "handoff/process-mapping/ownership-assignment-escalation-workflow"
+}
diff --git a/handoff/process-mapping/ownership-assignment-escalation-workflow/workflow.fz b/handoff/process-mapping/ownership-assignment-escalation-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..17b67e07f04f5afeb0d24b55d34bd896c8f079b6
--- /dev/null
+++ b/handoff/process-mapping/ownership-assignment-escalation-workflow/workflow.fz
@@ -0,0 +1,31 @@
+TaskAssignment { # TaskAssignment
+  n1: circle label:"Work Request Initiated"
+  n2: rectangle label:"Review Scope and Requirements"
+  n3: diamond label:"Owner Clearly Defined?"
+  n4: rectangle label:"Assign Accountable Owner"
+  n5: rectangle label:"Communicate Assignment"
+  n6: circle label:"Work Begins"
+  n3.handle(right) -> n5.handle(left) [label="Yes"]
+  n5.handle(right) -> n6.handle(left)
+  n3.handle(bottom) -> n4.handle(left) [label="No"]
+  n2.handle(right) -> n3.handle(left)
+  n1.handle(right) -> n2.handle(left)
+  n4.handle(top) -> n5.handle(bottom)
+  n6.handle(right) -> ExecutionTracking.n7.handle(left)
+}
+
+ExecutionTracking { # ExecutionTracking
+  n7: rectangle label:"Execute Assigned Work"
+  n8: diamond label:"Support Required?"
+  n9: rectangle label:"Provide Assistance"
+  n10: diamond label:"Blockers Identified?"
+  n11: rectangle label:"Escalate to Manager"
+  n12: circle label:"Work Complete"
+  n7.handle(right) -> n8.handle(left)
+  n8.handle(top) -> n12.handle(top) [label="No"]
+  n8.handle(right) -> n9.handle(left) [label="Yes"]
+  n9.handle(right) -> n10.handle(left)
+  n10.handle(right) -> n12.handle(left) [label="No"]
+  n10.handle(bottom) -> n11.handle(left) [label="Yes"]
+  n11.handle(right) -> n12.handle(bottom)
+}
diff --git a/incident/architecture/api-composition-pattern-architecture/README.md b/incident/architecture/api-composition-pattern-architecture/README.md
index 1c109016a117199e972b3bb23ed2cf5305d93c9e..3cb338c0aca9b3b1d521715ca24b38f4089bf7a6 100644
--- a/incident/architecture/api-composition-pattern-architecture/README.md
+++ b/incident/architecture/api-composition-pattern-architecture/README.md
@@ -6,7 +6,7 @@ An API composition architecture diagram with a composer service that fans out pa
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** incident  
-**Secondary use cases:** None  
+**Secondary use cases:** architecture, patterns  
 **Complexity:** 3/5  
 **Nodes:** 16  
 **Lanes:** 3  
diff --git a/incident/architecture/api-composition-pattern-architecture/metadata.json b/incident/architecture/api-composition-pattern-architecture/metadata.json
index f0c57f4032d8740d909e058c678fcbe7c67a3036..85b0ee9d2de1ebaf8e0e632b7a8e19a2eb1ae1f8 100644
--- a/incident/architecture/api-composition-pattern-architecture/metadata.json
+++ b/incident/architecture/api-composition-pattern-architecture/metadata.json
@@ -5,9 +5,14 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "incident",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "architecture",
+    "patterns"
+  ],
   "use_cases": [
-    "incident"
+    "incident",
+    "architecture",
+    "patterns"
   ],
   "complexity": 3,
   "num_nodes": 16,
diff --git a/incident/architecture/api-composition-pattern-architecture/workflow.fz b/incident/architecture/api-composition-pattern-architecture/workflow.fz
index 7ead7012e8cc86210c17e05cbb3910d401d02eff..dd1807bf2d44ad8af0830859d26fa8aa5080ad44 100644
--- a/incident/architecture/api-composition-pattern-architecture/workflow.fz
+++ b/incident/architecture/api-composition-pattern-architecture/workflow.fz
@@ -1,44 +1,44 @@
-Client { # Client Application
-n1: circle label:"Complex Query Request"
-n2: rectangle label:"API Composer Service"
-n19: rectangle label:"Receive Composed Response"
-n20: circle label:"Display Result"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Composer.n3.handle(top) [label="Compose"]
-n19.handle(right) -> n20.handle(left)
-}
-Composer { # API Composition Layer
-n3: rectangle label:"Parse Query Requirements"
-n4: rectangle label:"Fan-Out Parallel Requests"
-n13: rectangle label:"Collect Responses"
-n14: diamond label:"All Responses Received?"
-n15: rectangle label:"Merge and Transform"
-n16: rectangle label:"Return Partial with Fallback"
-n3.handle(right) -> n4.handle(left) [label="Decompose"]
-n4.handle(bottom) -> Services.n5.handle(top) [label="GET /users"]
-n4.handle(bottom) -> Services.n7.handle(top) [label="GET /orders"]
-n4.handle(bottom) -> Services.n9.handle(top) [label="GET /products"]
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left) [label="Yes"]
-n14.handle(bottom) -> n16.handle(top) [label="Timeout"]
-n15.handle(top) -> Client.n19.handle(bottom) [label="Composed JSON"]
-n16.handle(top) -> Client.n19.handle(bottom) [label="Partial JSON"]
-}
-Services { # Microservices
-n5: rectangle label:"User Service"
-n6: rectangle label:"User Response"
-n7: rectangle label:"Order Service"
-n8: rectangle label:"Order Response"
-n9: rectangle label:"Product Service"
-n10: rectangle label:"Product Response"
-n11: rectangle label:"Aggregate Results"
-n12: rectangle label:"Send to Composer"
-n5.handle(right) -> n6.handle(left) [label="Query"]
-n7.handle(right) -> n8.handle(left) [label="Query"]
-n9.handle(right) -> n10.handle(left) [label="Query"]
-n6.handle(bottom) -> n11.handle(top) [label="User Data"]
-n8.handle(bottom) -> n11.handle(top) [label="Order Data"]
-n10.handle(right) -> n11.handle(left) [label="Product Data"]
-n11.handle(right) -> n12.handle(left)
-n12.handle(top) -> Composer.n13.handle(bottom) [label="All Data"]
-}
+Client { # Client Application
+n1: circle label:"Complex Query Request"
+n2: rectangle label:"API Composer Service"
+n19: rectangle label:"Receive Composed Response"
+n20: circle label:"Display Result"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Composer.n3.handle(top) [label="Compose"]
+n19.handle(right) -> n20.handle(left)
+}
+Composer { # API Composition Layer
+n3: rectangle label:"Parse Query Requirements"
+n4: rectangle label:"Fan-Out Parallel Requests"
+n13: rectangle label:"Collect Responses"
+n14: diamond label:"All Responses Received?"
+n15: rectangle label:"Merge and Transform"
+n16: rectangle label:"Return Partial with Fallback"
+n3.handle(right) -> n4.handle(left) [label="Decompose"]
+n4.handle(bottom) -> Services.n5.handle(top) [label="GET /users"]
+n4.handle(bottom) -> Services.n7.handle(top) [label="GET /orders"]
+n4.handle(bottom) -> Services.n9.handle(top) [label="GET /products"]
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left) [label="Yes"]
+n14.handle(bottom) -> n16.handle(top) [label="Timeout"]
+n15.handle(top) -> Client.n19.handle(bottom) [label="Composed JSON"]
+n16.handle(top) -> Client.n19.handle(bottom) [label="Partial JSON"]
+}
+Services { # Microservices
+n5: rectangle label:"User Service"
+n6: rectangle label:"User Response"
+n7: rectangle label:"Order Service"
+n8: rectangle label:"Order Response"
+n9: rectangle label:"Product Service"
+n10: rectangle label:"Product Response"
+n11: rectangle label:"Aggregate Results"
+n12: rectangle label:"Send to Composer"
+n5.handle(right) -> n6.handle(left) [label="Query"]
+n7.handle(right) -> n8.handle(left) [label="Query"]
+n9.handle(right) -> n10.handle(left) [label="Query"]
+n6.handle(bottom) -> n11.handle(top) [label="User Data"]
+n8.handle(bottom) -> n11.handle(top) [label="Order Data"]
+n10.handle(right) -> n11.handle(left) [label="Product Data"]
+n11.handle(right) -> n12.handle(left)
+n12.handle(top) -> Composer.n13.handle(bottom) [label="All Data"]
+}
diff --git a/incident/architecture/event-driven-dead-letter-queue-architecture/README.md b/incident/architecture/event-driven-dead-letter-queue-architecture/README.md
index 3c262780084307ddc99868d71434bb44fd8f0de2..595a7e0a8d5502b54409d05103881e7ee100433a 100644
--- a/incident/architecture/event-driven-dead-letter-queue-architecture/README.md
+++ b/incident/architecture/event-driven-dead-letter-queue-architecture/README.md
@@ -6,7 +6,7 @@ A dead letter queue architecture diagram with retry policies, exponential backof
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** incident  
-**Secondary use cases:** compliance  
+**Secondary use cases:** compliance, architecture, patterns  
 **Complexity:** 3/5  
 **Nodes:** 16  
 **Lanes:** 3  
diff --git a/incident/architecture/event-driven-dead-letter-queue-architecture/metadata.json b/incident/architecture/event-driven-dead-letter-queue-architecture/metadata.json
index 6dc8e79678d51ff1b55374a7a00ba2efbc5a09b6..c15a439ddb5887dda824bd1ea1995dfd50e71087 100644
--- a/incident/architecture/event-driven-dead-letter-queue-architecture/metadata.json
+++ b/incident/architecture/event-driven-dead-letter-queue-architecture/metadata.json
@@ -6,11 +6,15 @@
   "source_domain": "Architecture",
   "primary_use_case": "incident",
   "secondary_use_cases": [
-    "compliance"
+    "compliance",
+    "architecture",
+    "patterns"
   ],
   "use_cases": [
     "incident",
-    "compliance"
+    "compliance",
+    "architecture",
+    "patterns"
   ],
   "complexity": 3,
   "num_nodes": 16,
diff --git a/incident/architecture/event-driven-dead-letter-queue-architecture/workflow.fz b/incident/architecture/event-driven-dead-letter-queue-architecture/workflow.fz
index dd65e31c5df35be9c337ce5fc8e3f54c6ae79004..92edd67f08d1da7940efda08385e12054091a9e6 100644
--- a/incident/architecture/event-driven-dead-letter-queue-architecture/workflow.fz
+++ b/incident/architecture/event-driven-dead-letter-queue-architecture/workflow.fz
@@ -1,39 +1,39 @@
-Producer { # Message Producer
-n1: circle label:"Publish Message"
-n2: rectangle label:"Serialize Payload"
-n3: rectangle label:"Send to Main Queue"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left) [label="Enqueue"]
-n3.handle(bottom) -> MainQueue.n4.handle(top) [label="Deliver"]
-}
-MainQueue { # Main Processing Queue
-n4: rectangle label:"Receive Message"
-n5: rectangle label:"Attempt Processing"
-n6: diamond label:"Processing Succeeded?"
-n7: rectangle label:"Acknowledge Message"
-n8: rectangle label:"Increment Retry Count"
-n9: diamond label:"Max Retries Exceeded?"
-n10: rectangle label:"Schedule Retry"
-n4.handle(right) -> n5.handle(left)
-n5.handle(right) -> n6.handle(left)
-n6.handle(right) -> n7.handle(left) [label="Yes"]
-n6.handle(bottom) -> n8.handle(top) [label="No"]
-n8.handle(right) -> n9.handle(left)
-n9.handle(right) -> n10.handle(left) [label="Retry"]
-n9.handle(bottom) -> DLQ.n11.handle(top) [label="Exceeded"]
-}
-DLQ { # Dead Letter Queue
-n11: rectangle label:"Route to DLQ"
-n12: rectangle label:"Store Failed Message"
-n13: rectangle label:"Alert Operations Team"
-n14: rectangle label:"Manual Review Dashboard"
-n15: diamond label:"Reprocessable?"
-n16: rectangle label:"Requeue to Main"
-n17: rectangle label:"Archive and Close"
-n11.handle(right) -> n12.handle(left) [label="Preserve Context"]
-n12.handle(right) -> n13.handle(left) [label="PagerDuty"]
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left) [label="Investigate"]
-n15.handle(right) -> n16.handle(left) [label="Yes"]
-n15.handle(bottom) -> n17.handle(top) [label="No"]
-}
+Producer { # Message Producer
+n1: circle label:"Publish Message"
+n2: rectangle label:"Serialize Payload"
+n3: rectangle label:"Send to Main Queue"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left) [label="Enqueue"]
+n3.handle(bottom) -> MainQueue.n4.handle(top) [label="Deliver"]
+}
+MainQueue { # Main Processing Queue
+n4: rectangle label:"Receive Message"
+n5: rectangle label:"Attempt Processing"
+n6: diamond label:"Processing Succeeded?"
+n7: rectangle label:"Acknowledge Message"
+n8: rectangle label:"Increment Retry Count"
+n9: diamond label:"Max Retries Exceeded?"
+n10: rectangle label:"Schedule Retry"
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left) [label="Yes"]
+n6.handle(bottom) -> n8.handle(top) [label="No"]
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left) [label="Retry"]
+n9.handle(bottom) -> DLQ.n11.handle(top) [label="Exceeded"]
+}
+DLQ { # Dead Letter Queue
+n11: rectangle label:"Route to DLQ"
+n12: rectangle label:"Store Failed Message"
+n13: rectangle label:"Alert Operations Team"
+n14: rectangle label:"Manual Review Dashboard"
+n15: diamond label:"Reprocessable?"
+n16: rectangle label:"Requeue to Main"
+n17: rectangle label:"Archive and Close"
+n11.handle(right) -> n12.handle(left) [label="Preserve Context"]
+n12.handle(right) -> n13.handle(left) [label="PagerDuty"]
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left) [label="Investigate"]
+n15.handle(right) -> n16.handle(left) [label="Yes"]
+n15.handle(bottom) -> n17.handle(top) [label="No"]
+}
diff --git a/incident/architecture/health-check-pattern-architecture/README.md b/incident/architecture/health-check-pattern-architecture/README.md
index 89b1c8331106049b8b20d6f8c063141a3cf1dca1..90e0120299a1d90ffe8c5cf866fc6c825f8a09fc 100644
--- a/incident/architecture/health-check-pattern-architecture/README.md
+++ b/incident/architecture/health-check-pattern-architecture/README.md
@@ -6,7 +6,7 @@ A health check pattern architecture diagram with load balancer probes, deep heal
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** incident  
-**Secondary use cases:** security  
+**Secondary use cases:** security, patterns  
 **Complexity:** 3/5  
 **Nodes:** 19  
 **Lanes:** 4  
diff --git a/incident/architecture/health-check-pattern-architecture/metadata.json b/incident/architecture/health-check-pattern-architecture/metadata.json
index b2a43b3809d453274e562afef40873ba66ffcaaa..a28289a14bc5f86964b659db83ceccafb4d7308c 100644
--- a/incident/architecture/health-check-pattern-architecture/metadata.json
+++ b/incident/architecture/health-check-pattern-architecture/metadata.json
@@ -6,11 +6,13 @@
   "source_domain": "Architecture",
   "primary_use_case": "incident",
   "secondary_use_cases": [
-    "security"
+    "security",
+    "patterns"
   ],
   "use_cases": [
     "incident",
-    "security"
+    "security",
+    "patterns"
   ],
   "complexity": 3,
   "num_nodes": 19,
diff --git a/incident/architecture/health-check-pattern-architecture/workflow.fz b/incident/architecture/health-check-pattern-architecture/workflow.fz
index 4716ed83bfc46cb2c7c60965a2cda5a582194ae7..4a153cbda3904be5f0b0a6da9498a7bf618cdcb9 100644
--- a/incident/architecture/health-check-pattern-architecture/workflow.fz
+++ b/incident/architecture/health-check-pattern-architecture/workflow.fz
@@ -1,59 +1,59 @@
-LoadBalancer { # Load Balancer
-n1: circle label:"Health Check Timer"
-n2: rectangle label:"Send Health Probe"
-n17: rectangle label:"Evaluate Response"
-n18: diamond label:"Instance Healthy?"
-n19: rectangle label:"Keep in Rotation"
-n20: rectangle label:"Remove from Rotation"
-n21: rectangle label:"Update Routing Table"
-n1.handle(right) -> n2.handle(left) [label="Every 10s"]
-n2.handle(bottom) -> ServiceA.n3.handle(top) [label="GET /health"]
-n2.handle(bottom) -> ServiceB.n10.handle(top) [label="GET /health"]
-n17.handle(right) -> n18.handle(left)
-n18.handle(right) -> n19.handle(left) [label="200 OK"]
-n18.handle(bottom) -> n20.handle(top) [label="Timeout/5xx"]
-n19.handle(right) -> n21.handle(left)
-n20.handle(right) -> n21.handle(left)
-n21.handle(bottom) -> Alerting.n22.handle(top) [label="Status Change"]
-}
-ServiceA { # Service A
-n3: rectangle label:"Check Database Connection"
-n4: rectangle label:"Check Redis Connection"
-n5: rectangle label:"Check Disk Space"
-n6: rectangle label:"Return Health Status"
-n7: rectangle label:"Send Status to LB"
-n8: rectangle label:"Forward Service A Status"
-n9: rectangle label:"Deliver A Result"
-n3.handle(right) -> n4.handle(left) [label="DB OK"]
-n4.handle(right) -> n5.handle(left) [label="Cache OK"]
-n5.handle(right) -> n6.handle(left) [label="Disk OK"]
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left)
-n9.handle(top) -> LoadBalancer.n17.handle(bottom) [label="Status JSON"]
-}
-ServiceB { # Service B
-n10: rectangle label:"Check API Dependencies"
-n11: rectangle label:"Check Message Queue"
-n12: rectangle label:"Check Memory Usage"
-n13: rectangle label:"Return Health Status"
-n14: rectangle label:"Send Status to LB"
-n15: rectangle label:"Forward Service B Status"
-n16: rectangle label:"Deliver B Result"
-n10.handle(right) -> n11.handle(left) [label="APIs OK"]
-n11.handle(right) -> n12.handle(left) [label="Queue OK"]
-n12.handle(right) -> n13.handle(left) [label="Disk OK"]
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left)
-n16.handle(top) -> LoadBalancer.n17.handle(bottom) [label="Status JSON"]
-}
-Alerting { # Alerting System
-n22: rectangle label:"Monitor Health Trends"
-n23: diamond label:"Consecutive Failures?"
-n24: rectangle label:"Send PagerDuty Alert"
-n25: rectangle label:"Log Health Metric"
-n22.handle(right) -> n23.handle(left)
-n23.handle(right) -> n24.handle(left) [label="3+ Failures"]
-n23.handle(bottom) -> n25.handle(top) [label="Below Threshold"]
-}
+LoadBalancer { # Load Balancer
+n1: circle label:"Health Check Timer"
+n2: rectangle label:"Send Health Probe"
+n17: rectangle label:"Evaluate Response"
+n18: diamond label:"Instance Healthy?"
+n19: rectangle label:"Keep in Rotation"
+n20: rectangle label:"Remove from Rotation"
+n21: rectangle label:"Update Routing Table"
+n1.handle(right) -> n2.handle(left) [label="Every 10s"]
+n2.handle(bottom) -> ServiceA.n3.handle(top) [label="GET /health"]
+n2.handle(bottom) -> ServiceB.n10.handle(top) [label="GET /health"]
+n17.handle(right) -> n18.handle(left)
+n18.handle(right) -> n19.handle(left) [label="200 OK"]
+n18.handle(bottom) -> n20.handle(top) [label="Timeout/5xx"]
+n19.handle(right) -> n21.handle(left)
+n20.handle(right) -> n21.handle(left)
+n21.handle(bottom) -> Alerting.n22.handle(top) [label="Status Change"]
+}
+ServiceA { # Service A
+n3: rectangle label:"Check Database Connection"
+n4: rectangle label:"Check Redis Connection"
+n5: rectangle label:"Check Disk Space"
+n6: rectangle label:"Return Health Status"
+n7: rectangle label:"Send Status to LB"
+n8: rectangle label:"Forward Service A Status"
+n9: rectangle label:"Deliver A Result"
+n3.handle(right) -> n4.handle(left) [label="DB OK"]
+n4.handle(right) -> n5.handle(left) [label="Cache OK"]
+n5.handle(right) -> n6.handle(left) [label="Disk OK"]
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left)
+n9.handle(top) -> LoadBalancer.n17.handle(bottom) [label="Status JSON"]
+}
+ServiceB { # Service B
+n10: rectangle label:"Check API Dependencies"
+n11: rectangle label:"Check Message Queue"
+n12: rectangle label:"Check Memory Usage"
+n13: rectangle label:"Return Health Status"
+n14: rectangle label:"Send Status to LB"
+n15: rectangle label:"Forward Service B Status"
+n16: rectangle label:"Deliver B Result"
+n10.handle(right) -> n11.handle(left) [label="APIs OK"]
+n11.handle(right) -> n12.handle(left) [label="Queue OK"]
+n12.handle(right) -> n13.handle(left) [label="Disk OK"]
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left)
+n16.handle(top) -> LoadBalancer.n17.handle(bottom) [label="Status JSON"]
+}
+Alerting { # Alerting System
+n22: rectangle label:"Monitor Health Trends"
+n23: diamond label:"Consecutive Failures?"
+n24: rectangle label:"Send PagerDuty Alert"
+n25: rectangle label:"Log Health Metric"
+n22.handle(right) -> n23.handle(left)
+n23.handle(right) -> n24.handle(left) [label="3+ Failures"]
+n23.handle(bottom) -> n25.handle(top) [label="Below Threshold"]
+}
diff --git a/incident/architecture/serverless-step-functions-orchestration-architecture/README.md b/incident/architecture/serverless-step-functions-orchestration-architecture/README.md
index 6674cdfe4dbb66469a073c90cad7f10a6a0686b5..b3554886d2877acf7f1b83a9bc25762027b2d8d3 100644
--- a/incident/architecture/serverless-step-functions-orchestration-architecture/README.md
+++ b/incident/architecture/serverless-step-functions-orchestration-architecture/README.md
@@ -6,7 +6,7 @@ An AWS Step Functions orchestration architecture diagram with state machine work
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** incident  
-**Secondary use cases:** ai-orchestration  
+**Secondary use cases:** ai-orchestration, architecture, patterns  
 **Complexity:** 4/5  
 **Nodes:** 17  
 **Lanes:** 3  
diff --git a/incident/architecture/serverless-step-functions-orchestration-architecture/metadata.json b/incident/architecture/serverless-step-functions-orchestration-architecture/metadata.json
index 49f5b3986ca30e026cf7dd3d3d836757394aae91..cbf6102ad84c49905c5a3f249be3401c2c747e21 100644
--- a/incident/architecture/serverless-step-functions-orchestration-architecture/metadata.json
+++ b/incident/architecture/serverless-step-functions-orchestration-architecture/metadata.json
@@ -6,11 +6,15 @@
   "source_domain": "Architecture",
   "primary_use_case": "incident",
   "secondary_use_cases": [
-    "ai-orchestration"
+    "ai-orchestration",
+    "architecture",
+    "patterns"
   ],
   "use_cases": [
     "incident",
-    "ai-orchestration"
+    "ai-orchestration",
+    "architecture",
+    "patterns"
   ],
   "complexity": 4,
   "num_nodes": 17,
diff --git a/incident/architecture/serverless-step-functions-orchestration-architecture/workflow.fz b/incident/architecture/serverless-step-functions-orchestration-architecture/workflow.fz
index 808bfdd3bc0dad79217f0a03425725a019de3561..17257aff1d0e957f01a3406c1ea4cd69cace3b34 100644
--- a/incident/architecture/serverless-step-functions-orchestration-architecture/workflow.fz
+++ b/incident/architecture/serverless-step-functions-orchestration-architecture/workflow.fz
@@ -1,53 +1,53 @@
-Trigger { # Trigger
-n1: circle label:"Start Execution"
-n2: rectangle label:"API Gateway / EventBridge"
-n3: rectangle label:"Invoke Step Function"
-n22: rectangle label:"Receive Execution Result"
-n23: circle label:"Execution Complete"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left) [label="StartExecution"]
-n3.handle(bottom) -> StateMachine.n4.handle(top) [label="Input JSON"]
-n22.handle(right) -> n23.handle(left)
-}
-StateMachine { # AWS Step Functions
-n4: rectangle label:"Validate Input (Task)"
-n5: diamond label:"Order Type?"
-n6: rectangle label:"Standard Order Path"
-n7: rectangle label:"Express Order Path"
-n8: rectangle label:"Parallel Processing"
-n20: rectangle label:"Receive Lambda Results"
-n9: rectangle label:"Wait for Approval"
-n10: diamond label:"Approved?"
-n11: rectangle label:"Execute Final Step"
-n12: rectangle label:"Compensation Rollback"
-n13: rectangle label:"Report to Trigger"
-n21: rectangle label:"Send Execution Result"
-n4.handle(right) -> n5.handle(left)
-n5.handle(right) -> n6.handle(left) [label="Standard"]
-n5.handle(bottom) -> n7.handle(top) [label="Express"]
-n6.handle(right) -> n8.handle(left)
-n7.handle(right) -> n8.handle(left)
-n8.handle(bottom) -> Lambdas.n14.handle(top) [label="Invoke"]
-n20.handle(right) -> n9.handle(left) [label="Map State"]
-n9.handle(right) -> n10.handle(left) [label="Callback"]
-n10.handle(right) -> n11.handle(left) [label="Yes"]
-n10.handle(bottom) -> n12.handle(top) [label="No"]
-n11.handle(right) -> n13.handle(left)
-n12.handle(right) -> n13.handle(left) [label="Rolled Back"]
-n13.handle(right) -> n21.handle(left)
-n21.handle(top) -> Trigger.n22.handle(bottom) [label="Result"]
-}
-Lambdas { # Lambda Functions
-n14: rectangle label:"Payment Lambda"
-n15: rectangle label:"Inventory Lambda"
-n16: rectangle label:"Notification Lambda"
-n17: rectangle label:"Error Catcher Lambda"
-n18: rectangle label:"Collect Lambda Results"
-n19: rectangle label:"Return to State Machine"
-n14.handle(right) -> n15.handle(left) [label="Charge"]
-n15.handle(right) -> n16.handle(left) [label="Reserve"]
-n16.handle(right) -> n17.handle(left)
-n17.handle(right) -> n18.handle(left)
-n18.handle(right) -> n19.handle(left)
-n19.handle(top) -> StateMachine.n20.handle(bottom) [label="Lambda Results"]
-}
+Trigger { # Trigger
+n1: circle label:"Start Execution"
+n2: rectangle label:"API Gateway / EventBridge"
+n3: rectangle label:"Invoke Step Function"
+n22: rectangle label:"Receive Execution Result"
+n23: circle label:"Execution Complete"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left) [label="StartExecution"]
+n3.handle(bottom) -> StateMachine.n4.handle(top) [label="Input JSON"]
+n22.handle(right) -> n23.handle(left)
+}
+StateMachine { # AWS Step Functions
+n4: rectangle label:"Validate Input (Task)"
+n5: diamond label:"Order Type?"
+n6: rectangle label:"Standard Order Path"
+n7: rectangle label:"Express Order Path"
+n8: rectangle label:"Parallel Processing"
+n20: rectangle label:"Receive Lambda Results"
+n9: rectangle label:"Wait for Approval"
+n10: diamond label:"Approved?"
+n11: rectangle label:"Execute Final Step"
+n12: rectangle label:"Compensation Rollback"
+n13: rectangle label:"Report to Trigger"
+n21: rectangle label:"Send Execution Result"
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left) [label="Standard"]
+n5.handle(bottom) -> n7.handle(top) [label="Express"]
+n6.handle(right) -> n8.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(bottom) -> Lambdas.n14.handle(top) [label="Invoke"]
+n20.handle(right) -> n9.handle(left) [label="Map State"]
+n9.handle(right) -> n10.handle(left) [label="Callback"]
+n10.handle(right) -> n11.handle(left) [label="Yes"]
+n10.handle(bottom) -> n12.handle(top) [label="No"]
+n11.handle(right) -> n13.handle(left)
+n12.handle(right) -> n13.handle(left) [label="Rolled Back"]
+n13.handle(right) -> n21.handle(left)
+n21.handle(top) -> Trigger.n22.handle(bottom) [label="Result"]
+}
+Lambdas { # Lambda Functions
+n14: rectangle label:"Payment Lambda"
+n15: rectangle label:"Inventory Lambda"
+n16: rectangle label:"Notification Lambda"
+n17: rectangle label:"Error Catcher Lambda"
+n18: rectangle label:"Collect Lambda Results"
+n19: rectangle label:"Return to State Machine"
+n14.handle(right) -> n15.handle(left) [label="Charge"]
+n15.handle(right) -> n16.handle(left) [label="Reserve"]
+n16.handle(right) -> n17.handle(left)
+n17.handle(right) -> n18.handle(left)
+n18.handle(right) -> n19.handle(left)
+n19.handle(top) -> StateMachine.n20.handle(bottom) [label="Lambda Results"]
+}
diff --git a/incident/devops/deployment-rollback-workflow/workflow.fz b/incident/devops/deployment-rollback-workflow/workflow.fz
index c0ecd75fe653b00a2d9d16df398fdafccd272618..ff54e8c817776d172162695f995b6a1d5808dae5 100644
--- a/incident/devops/deployment-rollback-workflow/workflow.fz
+++ b/incident/devops/deployment-rollback-workflow/workflow.fz
@@ -1,52 +1,52 @@
-AlertSystem { # Alert System
-n1: circle label:"Start"
-n2: rectangle label:"Detect anomaly in metrics"
-n3: rectangle label:"Trigger rollback alert"
-n4: rectangle label:"Notify on-call engineer"
-n5: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(bottom) -> Orchestrator.n6.handle(top) [label="Initiate rollback"]
-n4.handle(right) -> n5.handle(left)
-}
-Orchestrator { # Deployment Orchestrator
-n6: rectangle label:"Identify current version"
-n7: rectangle label:"Fetch previous stable version"
-n8: diamond label:"Previous version available?"
-n9: rectangle label:"Prepare rollback manifest"
-n10: rectangle label:"Halt manual rollback"
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left) [label="Yes"]
-n8.handle(bottom) -> n10.handle(top) [label="No"]
-n9.handle(bottom) -> Kubernetes.n11.handle(top) [label="Apply"]
-n10.handle(top) -> AlertSystem.n4.handle(bottom) [label="Manual needed"]
-}
-Kubernetes { # Kubernetes Cluster
-n11: rectangle label:"Scale down new pods"
-n12: rectangle label:"Deploy previous image"
-n13: rectangle label:"Wait for pods ready"
-n14: diamond label:"All pods healthy?"
-n15: rectangle label:"Update service selector"
-n16: rectangle label:"Mark rollback failed"
-n11.handle(right) -> n12.handle(left)
-n12.handle(right) -> n13.handle(left)
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left) [label="Yes"]
-n14.handle(bottom) -> n16.handle(top) [label="No"]
-n15.handle(bottom) -> Verification.n17.handle(top) [label="Traffic shifted"]
-n16.handle(top) -> AlertSystem.n4.handle(bottom) [label="Failed"]
-}
-Verification { # Verification
-n17: rectangle label:"Run smoke tests"
-n18: diamond label:"Tests passing?"
-n19: rectangle label:"Update deployment status"
-n20: rectangle label:"Cleanup old resources"
-n21: rectangle label:"Escalate to team lead"
-n17.handle(right) -> n18.handle(left)
-n18.handle(right) -> n19.handle(left) [label="Yes"]
-n18.handle(bottom) -> n21.handle(top) [label="No"]
-n19.handle(right) -> n20.handle(left)
-n20.handle(top) -> AlertSystem.n4.handle(bottom) [label="Rollback complete"]
-n21.handle(top) -> AlertSystem.n4.handle(bottom) [label="Needs attention"]
-}
+AlertSystem { # Alert System
+n1: circle label:"Start"
+n2: rectangle label:"Detect anomaly in metrics"
+n3: rectangle label:"Trigger rollback alert"
+n4: rectangle label:"Notify on-call engineer"
+n5: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(bottom) -> Orchestrator.n6.handle(top) [label="Initiate rollback"]
+n4.handle(right) -> n5.handle(left)
+}
+Orchestrator { # Deployment Orchestrator
+n6: rectangle label:"Identify current version"
+n7: rectangle label:"Fetch previous stable version"
+n8: diamond label:"Previous version available?"
+n9: rectangle label:"Prepare rollback manifest"
+n10: rectangle label:"Halt manual rollback"
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left) [label="Yes"]
+n8.handle(bottom) -> n10.handle(top) [label="No"]
+n9.handle(bottom) -> Kubernetes.n11.handle(top) [label="Apply"]
+n10.handle(top) -> AlertSystem.n4.handle(bottom) [label="Manual needed"]
+}
+Kubernetes { # Kubernetes Cluster
+n11: rectangle label:"Scale down new pods"
+n12: rectangle label:"Deploy previous image"
+n13: rectangle label:"Wait for pods ready"
+n14: diamond label:"All pods healthy?"
+n15: rectangle label:"Update service selector"
+n16: rectangle label:"Mark rollback failed"
+n11.handle(right) -> n12.handle(left)
+n12.handle(right) -> n13.handle(left)
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left) [label="Yes"]
+n14.handle(bottom) -> n16.handle(top) [label="No"]
+n15.handle(bottom) -> Verification.n17.handle(top) [label="Traffic shifted"]
+n16.handle(top) -> AlertSystem.n4.handle(bottom) [label="Failed"]
+}
+Verification { # Verification
+n17: rectangle label:"Run smoke tests"
+n18: diamond label:"Tests passing?"
+n19: rectangle label:"Update deployment status"
+n20: rectangle label:"Cleanup old resources"
+n21: rectangle label:"Escalate to team lead"
+n17.handle(right) -> n18.handle(left)
+n18.handle(right) -> n19.handle(left) [label="Yes"]
+n18.handle(bottom) -> n21.handle(top) [label="No"]
+n19.handle(right) -> n20.handle(left)
+n20.handle(top) -> AlertSystem.n4.handle(bottom) [label="Rollback complete"]
+n21.handle(top) -> AlertSystem.n4.handle(bottom) [label="Needs attention"]
+}
diff --git a/incident/devops/incident-response-workflow/workflow.fz b/incident/devops/incident-response-workflow/workflow.fz
index 930bee544df85d9adaf13e813fe7de407b86ce79..6c0166702f5ab616bdb5f6fbfdd161070f781dfb 100644
--- a/incident/devops/incident-response-workflow/workflow.fz
+++ b/incident/devops/incident-response-workflow/workflow.fz
@@ -1,56 +1,56 @@
-Monitoring { # Monitoring System
-n1: circle label:"Start"
-n2: rectangle label:"Alert triggered"
-n3: rectangle label:"Page on-call responder"
-n4: rectangle label:"Log incident timeline"
-n5: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> OnCall.n6.handle(top) [label="SEV-1 Alert"]
-n3.handle(bottom) -> OnCall.n6.handle(top) [label="Paged"]
-n4.handle(right) -> n5.handle(left)
-}
-OnCall { # On-Call Responder
-n6: rectangle label:"Acknowledge incident"
-n7: rectangle label:"Assess severity and impact"
-n8: diamond label:"Severity level?"
-n9: rectangle label:"Declare major incident"
-n10: rectangle label:"Begin troubleshooting"
-n11: rectangle label:"Escalate to team lead"
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left) [label="SEV-1/2"]
-n8.handle(bottom) -> n10.handle(top) [label="SEV-3/4"]
-n9.handle(bottom) -> IncidentCommand.n12.handle(top) [label="Open bridge"]
-n10.handle(bottom) -> Resolution.n18.handle(top) [label="Investigate"]
-n11.handle(bottom) -> IncidentCommand.n12.handle(top) [label="Needs help"]
-}
-IncidentCommand { # Incident Command
-n12: rectangle label:"Open war room bridge"
-n13: rectangle label:"Assign incident commander"
-n14: rectangle label:"Coordinate response teams"
-n15: rectangle label:"Communicate status updates"
-n16: diamond label:"Customer impact?"
-n17: rectangle label:"Notify customer success"
-n12.handle(right) -> n13.handle(left)
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left)
-n16.handle(right) -> n17.handle(left) [label="Yes"]
-n16.handle(bottom) -> Resolution.n18.handle(top) [label="No"]
-n17.handle(bottom) -> Resolution.n18.handle(top) [label="Notified"]
-}
-Resolution { # Resolution
-n18: rectangle label:"Identify root cause"
-n19: rectangle label:"Implement fix"
-n20: diamond label:"Issue resolved?"
-n21: rectangle label:"Verify recovery"
-n22: rectangle label:"Close incident"
-n23: rectangle label:"Schedule postmortem"
-n18.handle(right) -> n19.handle(left)
-n19.handle(right) -> n20.handle(left)
-n20.handle(right) -> n21.handle(left) [label="Yes"]
-n20.handle(bottom) -> n18.handle(bottom) [label="No - Continue"]
-n21.handle(right) -> n22.handle(left)
-n22.handle(right) -> n23.handle(left)
-n23.handle(top) -> Monitoring.n4.handle(bottom) [label="Complete"]
-}
+Monitoring { # Monitoring System
+n1: circle label:"Start"
+n2: rectangle label:"Alert triggered"
+n3: rectangle label:"Page on-call responder"
+n4: rectangle label:"Log incident timeline"
+n5: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> OnCall.n6.handle(top) [label="SEV-1 Alert"]
+n3.handle(bottom) -> OnCall.n6.handle(top) [label="Paged"]
+n4.handle(right) -> n5.handle(left)
+}
+OnCall { # On-Call Responder
+n6: rectangle label:"Acknowledge incident"
+n7: rectangle label:"Assess severity and impact"
+n8: diamond label:"Severity level?"
+n9: rectangle label:"Declare major incident"
+n10: rectangle label:"Begin troubleshooting"
+n11: rectangle label:"Escalate to team lead"
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left) [label="SEV-1/2"]
+n8.handle(bottom) -> n10.handle(top) [label="SEV-3/4"]
+n9.handle(bottom) -> IncidentCommand.n12.handle(top) [label="Open bridge"]
+n10.handle(bottom) -> Resolution.n18.handle(top) [label="Investigate"]
+n11.handle(bottom) -> IncidentCommand.n12.handle(top) [label="Needs help"]
+}
+IncidentCommand { # Incident Command
+n12: rectangle label:"Open war room bridge"
+n13: rectangle label:"Assign incident commander"
+n14: rectangle label:"Coordinate response teams"
+n15: rectangle label:"Communicate status updates"
+n16: diamond label:"Customer impact?"
+n17: rectangle label:"Notify customer success"
+n12.handle(right) -> n13.handle(left)
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left) [label="Yes"]
+n16.handle(bottom) -> Resolution.n18.handle(top) [label="No"]
+n17.handle(bottom) -> Resolution.n18.handle(top) [label="Notified"]
+}
+Resolution { # Resolution
+n18: rectangle label:"Identify root cause"
+n19: rectangle label:"Implement fix"
+n20: diamond label:"Issue resolved?"
+n21: rectangle label:"Verify recovery"
+n22: rectangle label:"Close incident"
+n23: rectangle label:"Schedule postmortem"
+n18.handle(right) -> n19.handle(left)
+n19.handle(right) -> n20.handle(left)
+n20.handle(right) -> n21.handle(left) [label="Yes"]
+n20.handle(bottom) -> n18.handle(bottom) [label="No - Continue"]
+n21.handle(right) -> n22.handle(left)
+n22.handle(right) -> n23.handle(left)
+n23.handle(top) -> Monitoring.n4.handle(bottom) [label="Complete"]
+}
diff --git a/incident/devops/monitoring-alert-workflow/workflow.fz b/incident/devops/monitoring-alert-workflow/workflow.fz
index e1639b319920f291066fc151ae03de1168a163b7..1a75a200116d42c2660a3f1002a35d0ec1ee7b24 100644
--- a/incident/devops/monitoring-alert-workflow/workflow.fz
+++ b/incident/devops/monitoring-alert-workflow/workflow.fz
@@ -1,45 +1,45 @@
-Prometheus { # Prometheus
-n1: circle label:"Start"
-n2: rectangle label:"Scrape metrics endpoint"
-n3: rectangle label:"Evaluate alert rules"
-n4: diamond label:"Threshold breached?"
-n5: rectangle label:"Fire alert to Alertmanager"
-n6: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(right) -> n4.handle(left)
-n4.handle(right) -> n5.handle(left) [label="Yes"]
-n4.handle(bottom) -> n6.handle(top) [label="No"]
-n5.handle(bottom) -> Alertmanager.n7.handle(top) [label="Alert fired"]
-}
-Alertmanager { # Alertmanager
-n7: rectangle label:"Receive alert"
-n8: rectangle label:"Deduplicate alerts"
-n9: rectangle label:"Group related alerts"
-n10: diamond label:"Silenced or inhibited?"
-n11: rectangle label:"Route to receiver"
-n12: rectangle label:"Drop alert"
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left)
-n9.handle(right) -> n10.handle(left)
-n10.handle(right) -> n11.handle(left) [label="No"]
-n10.handle(bottom) -> n12.handle(top) [label="Yes"]
-n11.handle(bottom) -> Notification.n13.handle(top) [label="Notify"]
-n12.handle(top) -> Prometheus.n6.handle(bottom) [label="Suppressed"]
-}
-Notification { # Notification Channels
-n13: rectangle label:"Format alert message"
-n14: diamond label:"Channel type?"
-n15: rectangle label:"Send to Slack"
-n16: rectangle label:"Send to PagerDuty"
-n17: rectangle label:"Send email"
-n18: rectangle label:"Log delivery status"
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left) [label="Slack"]
-n14.handle(bottom) -> n16.handle(top) [label="PagerDuty"]
-n14.handle(left) -> n17.handle(top) [label="Email"]
-n15.handle(bottom) -> n18.handle(top)
-n16.handle(right) -> n18.handle(left)
-n17.handle(bottom) -> n18.handle(left)
-n18.handle(top) -> Prometheus.n6.handle(bottom) [label="Delivered"]
-}
+Prometheus { # Prometheus
+n1: circle label:"Start"
+n2: rectangle label:"Scrape metrics endpoint"
+n3: rectangle label:"Evaluate alert rules"
+n4: diamond label:"Threshold breached?"
+n5: rectangle label:"Fire alert to Alertmanager"
+n6: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(right) -> n4.handle(left)
+n4.handle(right) -> n5.handle(left) [label="Yes"]
+n4.handle(bottom) -> n6.handle(top) [label="No"]
+n5.handle(bottom) -> Alertmanager.n7.handle(top) [label="Alert fired"]
+}
+Alertmanager { # Alertmanager
+n7: rectangle label:"Receive alert"
+n8: rectangle label:"Deduplicate alerts"
+n9: rectangle label:"Group related alerts"
+n10: diamond label:"Silenced or inhibited?"
+n11: rectangle label:"Route to receiver"
+n12: rectangle label:"Drop alert"
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left)
+n10.handle(right) -> n11.handle(left) [label="No"]
+n10.handle(bottom) -> n12.handle(top) [label="Yes"]
+n11.handle(bottom) -> Notification.n13.handle(top) [label="Notify"]
+n12.handle(top) -> Prometheus.n6.handle(bottom) [label="Suppressed"]
+}
+Notification { # Notification Channels
+n13: rectangle label:"Format alert message"
+n14: diamond label:"Channel type?"
+n15: rectangle label:"Send to Slack"
+n16: rectangle label:"Send to PagerDuty"
+n17: rectangle label:"Send email"
+n18: rectangle label:"Log delivery status"
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left) [label="Slack"]
+n14.handle(bottom) -> n16.handle(top) [label="PagerDuty"]
+n14.handle(left) -> n17.handle(top) [label="Email"]
+n15.handle(bottom) -> n18.handle(top)
+n16.handle(right) -> n18.handle(left)
+n17.handle(bottom) -> n18.handle(left)
+n18.handle(top) -> Prometheus.n6.handle(bottom) [label="Delivered"]
+}
diff --git a/incident/logistics/cold-chain-monitoring-workflow/workflow.fz b/incident/logistics/cold-chain-monitoring-workflow/workflow.fz
index e49183301a3df03293feb585ef62dad5e990fb26..98ba02bf52514af8188319b416b42b3aba2270cb 100644
--- a/incident/logistics/cold-chain-monitoring-workflow/workflow.fz
+++ b/incident/logistics/cold-chain-monitoring-workflow/workflow.fz
@@ -1,22 +1,22 @@
-supplier { # Supplier
-  n1: circle label:"Start Cold Chain Monitoring"
-  n3: rectangle label:"Review Cold Chain Monitoring details"
-  n5: rectangle label:"Update records for Cold Chain Monitoring"
-  n7: circle label:"End Cold Chain Monitoring"
-  n1.handle(bottom) -> warehouse.n2.handle(top)
-  n1.handle(right) -> n3.handle(left)
-  n1.handle(bottom) -> warehouse.n4.handle(top)
-  n1.handle(right) -> n5.handle(left)
-  n1.handle(bottom) -> warehouse.n6.handle(top)
-  n5.handle(right) -> n7.handle(left)
-  n3.handle(right) -> n7.handle(top)
-}
-
-warehouse { # Warehouse
-  n2: rectangle label:"Receive Cold Chain Monitoring request"
-  n4: rectangle label:"Make Cold Chain Monitoring decision"
-  n6: diamond label:"Continue Cold Chain Monitoring process"
-  n6.handle(right) -> supplier.n7.handle(bottom)
-  n4.handle(right) -> supplier.n7.handle(bottom)
-  n2.handle(right) -> supplier.n7.handle(bottom)
-}
+supplier { # Supplier
+  n1: circle label:"Start Cold Chain Monitoring"
+  n3: rectangle label:"Review Cold Chain Monitoring details"
+  n5: rectangle label:"Update records for Cold Chain Monitoring"
+  n7: circle label:"End Cold Chain Monitoring"
+  n1.handle(bottom) -> warehouse.n2.handle(top)
+  n1.handle(right) -> n3.handle(left)
+  n1.handle(bottom) -> warehouse.n4.handle(top)
+  n1.handle(right) -> n5.handle(left)
+  n1.handle(bottom) -> warehouse.n6.handle(top)
+  n5.handle(right) -> n7.handle(left)
+  n3.handle(right) -> n7.handle(top)
+}
+
+warehouse { # Warehouse
+  n2: rectangle label:"Receive Cold Chain Monitoring request"
+  n4: rectangle label:"Make Cold Chain Monitoring decision"
+  n6: diamond label:"Continue Cold Chain Monitoring process"
+  n6.handle(right) -> supplier.n7.handle(bottom)
+  n4.handle(right) -> supplier.n7.handle(bottom)
+  n2.handle(right) -> supplier.n7.handle(bottom)
+}
diff --git a/incident/logistics/hazmat-handling-workflow/workflow.fz b/incident/logistics/hazmat-handling-workflow/workflow.fz
index 574c151899f34c0d59c8703678c8c86bd5439b8e..f00df5f9dc7822ab1313175b7b3424c35bc96f8e 100644
--- a/incident/logistics/hazmat-handling-workflow/workflow.fz
+++ b/incident/logistics/hazmat-handling-workflow/workflow.fz
@@ -1,28 +1,28 @@
-supplier { # Supplier
-  n1: circle label:"Start Hazmat Handling"
-  n2: diamond label:"Receive Hazmat Handling request"
-  n4: rectangle label:"Make Hazmat Handling decision"
-  n7: rectangle label:"Continue Hazmat Handling process"
-  n10: circle label:"End Hazmat Handling"
-  n1.handle(right) -> n2.handle(left)
-  n2.handle(bottom) -> iot_sensor.n3.handle(top) [label="Yes/Approved"]
-  n4.handle(bottom) -> warehouse.n5.handle(top)
-  n7.handle(bottom) -> warehouse.n8.handle(top)
-  n2.handle(top) -> n4.handle(top) [label="No/Rejected"]
-}
-
-warehouse { # Warehouse
-  n5: rectangle label:"Update records for Hazmat Handling"
-  n8: rectangle label:"Continue Hazmat Handling process"
-  n5.handle(bottom) -> iot_sensor.n6.handle(top)
-  n8.handle(bottom) -> iot_sensor.n9.handle(top)
-}
-
-iot_sensor { # Iot_Sensor
-  n3: rectangle label:"Review Hazmat Handling details"
-  n6: rectangle label:"Continue Hazmat Handling process"
-  n9: rectangle label:"Continue Hazmat Handling process"
-  n9.handle(right) -> supplier.n10.handle(bottom)
-  n6.handle(right) -> supplier.n7.handle(left)
-  n3.handle(left) -> warehouse.n5.handle(left)
-}
+supplier { # Supplier
+  n1: circle label:"Start Hazmat Handling"
+  n2: diamond label:"Receive Hazmat Handling request"
+  n4: rectangle label:"Make Hazmat Handling decision"
+  n7: rectangle label:"Continue Hazmat Handling process"
+  n10: circle label:"End Hazmat Handling"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(bottom) -> iot_sensor.n3.handle(top) [label="Yes/Approved"]
+  n4.handle(bottom) -> warehouse.n5.handle(top)
+  n7.handle(bottom) -> warehouse.n8.handle(top)
+  n2.handle(top) -> n4.handle(top) [label="No/Rejected"]
+}
+
+warehouse { # Warehouse
+  n5: rectangle label:"Update records for Hazmat Handling"
+  n8: rectangle label:"Continue Hazmat Handling process"
+  n5.handle(bottom) -> iot_sensor.n6.handle(top)
+  n8.handle(bottom) -> iot_sensor.n9.handle(top)
+}
+
+iot_sensor { # Iot_Sensor
+  n3: rectangle label:"Review Hazmat Handling details"
+  n6: rectangle label:"Continue Hazmat Handling process"
+  n9: rectangle label:"Continue Hazmat Handling process"
+  n9.handle(right) -> supplier.n10.handle(bottom)
+  n6.handle(right) -> supplier.n7.handle(left)
+  n3.handle(left) -> warehouse.n5.handle(left)
+}
diff --git a/incident/patterns/canary-deploy-workflow/README.md b/incident/patterns/canary-deploy-workflow/README.md
index 9828a44c6b337996fe85322993fcaf0e66d60414..b74128c45acf694a24313d87636048c36adcf2a0 100644
--- a/incident/patterns/canary-deploy-workflow/README.md
+++ b/incident/patterns/canary-deploy-workflow/README.md
@@ -6,7 +6,7 @@ Canary deployment pattern with gradual traffic shifting, real-time metrics monit
 **Kind:** workflow  
 **Source domain:** patterns  
 **Primary use case:** incident  
-**Secondary use cases:** delivery  
+**Secondary use cases:** delivery, patterns  
 **Complexity:** 3/5  
 **Nodes:** 7  
 **Lanes:** 2  
diff --git a/incident/patterns/canary-deploy-workflow/metadata.json b/incident/patterns/canary-deploy-workflow/metadata.json
index 4ced77082dbeb882a4ce483318051f956b669d78..c96ab52ff15cccc22ccfd6dd2ec049b89d545611 100644
--- a/incident/patterns/canary-deploy-workflow/metadata.json
+++ b/incident/patterns/canary-deploy-workflow/metadata.json
@@ -6,11 +6,13 @@
   "source_domain": "patterns",
   "primary_use_case": "incident",
   "secondary_use_cases": [
-    "delivery"
+    "delivery",
+    "patterns"
   ],
   "use_cases": [
     "incident",
-    "delivery"
+    "delivery",
+    "patterns"
   ],
   "complexity": 3,
   "num_nodes": 7,
diff --git a/incident/patterns/canary-deploy-workflow/workflow.fz b/incident/patterns/canary-deploy-workflow/workflow.fz
index 38a79115b647dc389f29fe657611a7565f75e582..d161ea791a52533b7fbb7a8a46e3bb24335796ff 100644
--- a/incident/patterns/canary-deploy-workflow/workflow.fz
+++ b/incident/patterns/canary-deploy-workflow/workflow.fz
@@ -1,48 +1,48 @@
-Deployment { # Deployment Pipeline
-n1: circle label:"Start"
-n2: rectangle label:"Build container image"
-n3: rectangle label:"Push to registry"
-n4: rectangle label:"Complete rollout"
-n5: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(bottom) -> CanaryController.n6.handle(top) [label="Deploy canary"]
-n4.handle(right) -> n5.handle(left)
-}
-CanaryController { # Canary Controller
-n6: rectangle label:"Deploy to 5% of pods"
-n7: rectangle label:"Configure traffic split"
-n8: rectangle label:"Wait observation period"
-n9: diamond label:"Metrics healthy?"
-n10: rectangle label:"Increase to 25%"
-n11: rectangle label:"Rollback canary"
-n12: diamond label:"Still healthy?"
-n13: rectangle label:"Increase to 50%"
-n14: rectangle label:"Full rollout 100%"
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left)
-n9.handle(right) -> n10.handle(left) [label="Yes"]
-n9.handle(bottom) -> n11.handle(top) [label="No"]
-n10.handle(right) -> n12.handle(left)
-n11.handle(top) -> Deployment.n4.handle(bottom) [label="Aborted"]
-n12.handle(right) -> n13.handle(left) [label="Yes"]
-n12.handle(bottom) -> n11.handle(top) [label="No"]
-n13.handle(right) -> n14.handle(left)
-n14.handle(bottom) -> Monitoring.n15.handle(top) [label="Monitor"]
-}
-Monitoring { # Monitoring
-n15: rectangle label:"Track error rate"
-n16: rectangle label:"Measure latency p99"
-n17: rectangle label:"Check resource usage"
-n18: diamond label:"All metrics pass?"
-n19: rectangle label:"Mark deployment success"
-n20: rectangle label:"Trigger automatic rollback"
-n15.handle(right) -> n16.handle(left)
-n16.handle(right) -> n17.handle(left)
-n17.handle(right) -> n18.handle(left)
-n18.handle(right) -> n19.handle(left) [label="Yes"]
-n18.handle(bottom) -> n20.handle(top) [label="No"]
-n19.handle(top) -> Deployment.n4.handle(bottom) [label="Success"]
-n20.handle(top) -> Deployment.n4.handle(bottom) [label="Rolled back"]
-}
+Deployment { # Deployment Pipeline
+n1: circle label:"Start"
+n2: rectangle label:"Build container image"
+n3: rectangle label:"Push to registry"
+n4: rectangle label:"Complete rollout"
+n5: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(bottom) -> CanaryController.n6.handle(top) [label="Deploy canary"]
+n4.handle(right) -> n5.handle(left)
+}
+CanaryController { # Canary Controller
+n6: rectangle label:"Deploy to 5% of pods"
+n7: rectangle label:"Configure traffic split"
+n8: rectangle label:"Wait observation period"
+n9: diamond label:"Metrics healthy?"
+n10: rectangle label:"Increase to 25%"
+n11: rectangle label:"Rollback canary"
+n12: diamond label:"Still healthy?"
+n13: rectangle label:"Increase to 50%"
+n14: rectangle label:"Full rollout 100%"
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left) [label="Yes"]
+n9.handle(bottom) -> n11.handle(top) [label="No"]
+n10.handle(right) -> n12.handle(left)
+n11.handle(top) -> Deployment.n4.handle(bottom) [label="Aborted"]
+n12.handle(right) -> n13.handle(left) [label="Yes"]
+n12.handle(bottom) -> n11.handle(top) [label="No"]
+n13.handle(right) -> n14.handle(left)
+n14.handle(bottom) -> Monitoring.n15.handle(top) [label="Monitor"]
+}
+Monitoring { # Monitoring
+n15: rectangle label:"Track error rate"
+n16: rectangle label:"Measure latency p99"
+n17: rectangle label:"Check resource usage"
+n18: diamond label:"All metrics pass?"
+n19: rectangle label:"Mark deployment success"
+n20: rectangle label:"Trigger automatic rollback"
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left)
+n17.handle(right) -> n18.handle(left)
+n18.handle(right) -> n19.handle(left) [label="Yes"]
+n18.handle(bottom) -> n20.handle(top) [label="No"]
+n19.handle(top) -> Deployment.n4.handle(bottom) [label="Success"]
+n20.handle(top) -> Deployment.n4.handle(bottom) [label="Rolled back"]
+}
diff --git a/incident/platform-reliability/gcp-account-suspension-outage-cascade/README.md b/incident/platform-reliability/gcp-account-suspension-outage-cascade/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..dcb4276ba4f73f41809b04ab8571713e36714009
--- /dev/null
+++ b/incident/platform-reliability/gcp-account-suspension-outage-cascade/README.md
@@ -0,0 +1,19 @@
+# GCP Account Suspension Outage Cascade
+
+How a single account suspension cascades into an 8-hour platform outage: control plane offline, API down, caches expiring, workloads returning 404 and OAuth throttled.
+
+**Template ID:** `gcp-account-suspension-outage-cascade`  
+**Kind:** workflow  
+**Source domain:** Platform Reliability  
+**Primary use case:** incident  
+**Secondary use cases:** platform-reliability  
+**Complexity:** 2/5  
+**Nodes:** 8  
+**Lanes:** 1  
+**Tags:** [multi-cloud, outage, cascade, resilience, gcp]  
+**Source path:** ``  
+**Repo path:** `incident/platform-reliability/gcp-account-suspension-outage-cascade`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/incident/platform-reliability/gcp-account-suspension-outage-cascade/metadata.json b/incident/platform-reliability/gcp-account-suspension-outage-cascade/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..ec5e2a1cae7b10fcf107daef98627f1b00333c34
--- /dev/null
+++ b/incident/platform-reliability/gcp-account-suspension-outage-cascade/metadata.json
@@ -0,0 +1,28 @@
+{
+  "template_id": "gcp-account-suspension-outage-cascade",
+  "workflow_id": "gcp-account-suspension-outage-cascade",
+  "title": "GCP Account Suspension Outage Cascade",
+  "kind": "workflow",
+  "source_domain": "Platform Reliability",
+  "primary_use_case": "incident",
+  "secondary_use_cases": [
+    "platform-reliability"
+  ],
+  "use_cases": [
+    "incident",
+    "platform-reliability"
+  ],
+  "complexity": 2,
+  "num_nodes": 8,
+  "num_lanes": 1,
+  "tags": [
+    "multi-cloud",
+    "outage",
+    "cascade",
+    "resilience",
+    "gcp"
+  ],
+  "description": "How a single account suspension cascades into an 8-hour platform outage: control plane offline, API down, caches expiring, workloads returning 404 and OAuth throttled.",
+  "source_path": "",
+  "repo_path": "incident/platform-reliability/gcp-account-suspension-outage-cascade"
+}
diff --git a/incident/platform-reliability/gcp-account-suspension-outage-cascade/workflow.fz b/incident/platform-reliability/gcp-account-suspension-outage-cascade/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..54efb4c3308ee4723c209189f4fe22475ce0e430
--- /dev/null
+++ b/incident/platform-reliability/gcp-account-suspension-outage-cascade/workflow.fz
@@ -0,0 +1,19 @@
+outage { # GCP Suspension → Full Outage Cascade
+  n1: circle label:"GCP suspends account (22:20 UTC)"
+  n2: rectangle label:"Control plane offline"
+  n3: rectangle label:"Dashboard / API down"
+  n4: rectangle label:"Route caches expire (~15 min)"
+  n5: rectangle label:"Metal workloads → 404"
+  n6: rectangle label:"AWS workloads → 404"
+  n7: rectangle label:"GitHub OAuth rate-limited"
+  n8: circle label:"~8 hr platform outage"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(top) -> n4.handle(top) [label="immediate"]
+  n2.handle(right) -> n3.handle(left) [label="immediate"]
+  n4.handle(top) -> n6.handle(top) [label="cache expiry"]
+  n4.handle(right) -> n5.handle(left) [label="cache expiry"]
+  n3.handle(top) -> n7.handle(top) [label="retry burst"]
+  n5.handle(bottom) -> n8.handle(bottom)
+  n7.handle(right) -> n8.handle(left)
+  n6.handle(top) -> n8.handle(top)
+}
diff --git a/incident/process-mapping/incident-root-cause-prevention-workflow/README.md b/incident/process-mapping/incident-root-cause-prevention-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..852c879c640701e03caff4b0d02e92a33ccf3f45
--- /dev/null
+++ b/incident/process-mapping/incident-root-cause-prevention-workflow/README.md
@@ -0,0 +1,19 @@
+# Incident Root Cause & Prevention Workflow
+
+Incident response workflow that documents the current state, traces the root cause, validates controls and creates a prevention protocol before the case is closed.
+
+**Template ID:** `incident-root-cause-prevention-workflow`  
+**Kind:** workflow  
+**Source domain:** Process Mapping  
+**Primary use case:** incident  
+**Secondary use cases:** compliance, process-mapping  
+**Complexity:** 2/5  
+**Nodes:** 10  
+**Lanes:** 2  
+**Tags:** [process-mapping, incident, root-cause, prevention, controls]  
+**Source path:** ``  
+**Repo path:** `incident/process-mapping/incident-root-cause-prevention-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/incident/process-mapping/incident-root-cause-prevention-workflow/metadata.json b/incident/process-mapping/incident-root-cause-prevention-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..6c55b4d28630f0ae2208714153fcd1afb0375047
--- /dev/null
+++ b/incident/process-mapping/incident-root-cause-prevention-workflow/metadata.json
@@ -0,0 +1,30 @@
+{
+  "template_id": "incident-root-cause-prevention-workflow",
+  "workflow_id": "incident-root-cause-prevention",
+  "title": "Incident Root Cause & Prevention Workflow",
+  "kind": "workflow",
+  "source_domain": "Process Mapping",
+  "primary_use_case": "incident",
+  "secondary_use_cases": [
+    "compliance",
+    "process-mapping"
+  ],
+  "use_cases": [
+    "incident",
+    "compliance",
+    "process-mapping"
+  ],
+  "complexity": 2,
+  "num_nodes": 10,
+  "num_lanes": 2,
+  "tags": [
+    "process-mapping",
+    "incident",
+    "root-cause",
+    "prevention",
+    "controls"
+  ],
+  "description": "Incident response workflow that documents the current state, traces the root cause, validates controls and creates a prevention protocol before the case is closed.",
+  "source_path": "",
+  "repo_path": "incident/process-mapping/incident-root-cause-prevention-workflow"
+}
diff --git a/incident/process-mapping/incident-root-cause-prevention-workflow/workflow.fz b/incident/process-mapping/incident-root-cause-prevention-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..7c7a3bb423b320e4f8bdc67551e1100535f2d783
--- /dev/null
+++ b/incident/process-mapping/incident-root-cause-prevention-workflow/workflow.fz
@@ -0,0 +1,26 @@
+InitialIncident { # InitialIncident
+  n1: circle label:"Incident Detected"
+  n2: rectangle label:"Document Current State"
+  n3: diamond label:"Root Cause Identified?"
+  n4: rectangle label:"Conduct Root Cause Analysis"
+  n5: rectangle label:"Create Prevention Protocol"
+  n6: rectangle label:"Monitor Implementation"
+  n3.handle(right) -> n5.handle(left) [label="Yes - Proceed"]
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left)
+  n5.handle(right) -> n6.handle(left)
+  n6.handle(right) -> PreventionImplementation.n7.handle(left)
+  n3.handle(top) -> n4.handle(left) [label="No - Investigate"]
+  n4.handle(bottom) -> n5.handle(top)
+}
+
+PreventionImplementation { # PreventionImplementation
+  n7: rectangle label:"Update Standard Procedures"
+  n8: rectangle label:"Train Affected Staff"
+  n9: diamond label:"Controls Effective?"
+  n10: circle label:"Incident Prevented"
+  n9.handle(right) -> n10.handle(left) [label="Yes"]
+  n7.handle(right) -> n8.handle(left)
+  n9.handle(bottom) -> n7.handle(bottom) [label="No - Revise"]
+  n8.handle(right) -> n9.handle(left)
+}
diff --git a/llm-operations/llm-operations/structured-output-validation-workflow/README.md b/llm-operations/llm-operations/structured-output-validation-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..f22963f85f548beb7ce9ec8e54269e4fe4054593
--- /dev/null
+++ b/llm-operations/llm-operations/structured-output-validation-workflow/README.md
@@ -0,0 +1,19 @@
+# Structured Output Validation Workflow
+
+Output on a leash: the model generates against an output schema, the orchestrator validates that it parses as JSON or a diff, and regenerates or formats when it does not.
+
+**Template ID:** `structured-output-validation-workflow`  
+**Kind:** workflow  
+**Source domain:** LLM Operations  
+**Primary use case:** llm-operations  
+**Secondary use cases:** None  
+**Complexity:** 2/5  
+**Nodes:** 8  
+**Lanes:** 2  
+**Tags:** [token-optimization, structured-output, validation, json-schema, llmops]  
+**Source path:** ``  
+**Repo path:** `llm-operations/llm-operations/structured-output-validation-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/llm-operations/llm-operations/structured-output-validation-workflow/metadata.json b/llm-operations/llm-operations/structured-output-validation-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..de9495e1561e4d03f3d8bee34949d8f623fc5976
--- /dev/null
+++ b/llm-operations/llm-operations/structured-output-validation-workflow/metadata.json
@@ -0,0 +1,25 @@
+{
+  "template_id": "structured-output-validation-workflow",
+  "workflow_id": "structured-output-validation",
+  "title": "Structured Output Validation Workflow",
+  "kind": "workflow",
+  "source_domain": "LLM Operations",
+  "primary_use_case": "llm-operations",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "llm-operations"
+  ],
+  "complexity": 2,
+  "num_nodes": 8,
+  "num_lanes": 2,
+  "tags": [
+    "token-optimization",
+    "structured-output",
+    "validation",
+    "json-schema",
+    "llmops"
+  ],
+  "description": "Output on a leash: the model generates against an output schema, the orchestrator validates that it parses as JSON or a diff, and regenerates or formats when it does not.",
+  "source_path": "",
+  "repo_path": "llm-operations/llm-operations/structured-output-validation-workflow"
+}
diff --git a/llm-operations/llm-operations/structured-output-validation-workflow/workflow.fz b/llm-operations/llm-operations/structured-output-validation-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..f6084f4c1d78bb3f3f08564d705bccf8c4411969
--- /dev/null
+++ b/llm-operations/llm-operations/structured-output-validation-workflow/workflow.fz
@@ -0,0 +1,21 @@
+app { # Orchestrator
+n1: circle label:"Task initiated"
+n2: rectangle label:"Apply output schema (JSON, Diff)"
+n3: rectangle label:"Set max_tokens=500"
+n6: diamond label:"Parses correctly?"
+n7: rectangle label:"Tighten system prompt"
+n8: circle label:"Proceed to next step"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(bottom) -> provider.n4.handle(top) [label="Strict constraints"]
+n6.handle(right) -> n8.handle(left) [label="Yes"]
+n6.handle(bottom) -> n7.handle(top) [label="No"]
+n7.handle(left) -> n2.handle(bottom) [label="Retry with penalties"]
+}
+
+provider { # LLM API
+n4: rectangle label:"Process request"
+n5: rectangle label:"Generate formatted output"
+n4.handle(right) -> n5.handle(left)
+n5.handle(top) -> app.n6.handle(bottom) [label="Returns exact shape"]
+}
diff --git a/mcp/architecture/ambassador-pattern-architecture/README.md b/mcp/architecture/ambassador-pattern-architecture/README.md
index cb21d6b644c063183ca35b35f06bc763be5f937b..d0b0df0d970dfc2685d02e755b84273c4cd3c6d5 100644
--- a/mcp/architecture/ambassador-pattern-architecture/README.md
+++ b/mcp/architecture/ambassador-pattern-architecture/README.md
@@ -6,7 +6,7 @@ An ambassador pattern architecture diagram with a local proxy sidecar handling a
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** mcp  
-**Secondary use cases:** None  
+**Secondary use cases:** patterns  
 **Complexity:** 3/5  
 **Nodes:** 15  
 **Lanes:** 3  
diff --git a/mcp/architecture/ambassador-pattern-architecture/metadata.json b/mcp/architecture/ambassador-pattern-architecture/metadata.json
index 76600a152bd0417381e85d4d5a6be17214e41805..87ed56008ec39e6cf72f7c8fd9af421fdbc74ab7 100644
--- a/mcp/architecture/ambassador-pattern-architecture/metadata.json
+++ b/mcp/architecture/ambassador-pattern-architecture/metadata.json
@@ -5,9 +5,12 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "mcp",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "patterns"
+  ],
   "use_cases": [
-    "mcp"
+    "mcp",
+    "patterns"
   ],
   "complexity": 3,
   "num_nodes": 15,
diff --git a/mcp/architecture/ambassador-pattern-architecture/workflow.fz b/mcp/architecture/ambassador-pattern-architecture/workflow.fz
index 3cde1928544601e3ba5f986e52069110a096cec9..8b2b0fc1fe41d0eff19a876618a7648b20c8dc84 100644
--- a/mcp/architecture/ambassador-pattern-architecture/workflow.fz
+++ b/mcp/architecture/ambassador-pattern-architecture/workflow.fz
@@ -1,36 +1,36 @@
-Application { # Application Container
-n1: circle label:"Outbound Request"
-n2: rectangle label:"Application Code"
-n3: rectangle label:"Ambassador Proxy"
-n14: rectangle label:"Receive Proxied Response"
-n15: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left) [label="localhost:9000"]
-n3.handle(bottom) -> AmbassadorLogic.n4.handle(top) [label="Intercept"]
-n14.handle(right) -> n15.handle(left)
-}
-AmbassadorLogic { # Ambassador Logic
-n4: rectangle label:"Add Auth Headers"
-n5: rectangle label:"Apply Circuit Breaker"
-n6: diamond label:"Circuit Open?"
-n7: rectangle label:"Enable Retry Logic"
-n8: rectangle label:"Return Cached Fallback"
-n12: rectangle label:"Collect Metrics"
-n13: rectangle label:"Forward Response"
-n4.handle(right) -> n5.handle(left) [label="Bearer Token"]
-n5.handle(right) -> n6.handle(left)
-n6.handle(right) -> n7.handle(left) [label="Closed"]
-n6.handle(bottom) -> n8.handle(top) [label="Open"]
-n7.handle(bottom) -> ExternalService.n9.handle(top) [label="HTTPS + Retry"]
-n8.handle(top) -> Application.n14.handle(bottom) [label="Fallback"]
-n12.handle(right) -> n13.handle(left)
-n13.handle(top) -> Application.n14.handle(bottom) [label="Proxied Response"]
-}
-ExternalService { # External API
-n9: rectangle label:"Third-Party API"
-n10: rectangle label:"Process Request"
-n11: rectangle label:"Return Response"
-n9.handle(right) -> n10.handle(left)
-n10.handle(right) -> n11.handle(left)
-n11.handle(top) -> AmbassadorLogic.n12.handle(bottom) [label="Response + Metrics"]
-}
+Application { # Application Container
+n1: circle label:"Outbound Request"
+n2: rectangle label:"Application Code"
+n3: rectangle label:"Ambassador Proxy"
+n14: rectangle label:"Receive Proxied Response"
+n15: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left) [label="localhost:9000"]
+n3.handle(bottom) -> AmbassadorLogic.n4.handle(top) [label="Intercept"]
+n14.handle(right) -> n15.handle(left)
+}
+AmbassadorLogic { # Ambassador Logic
+n4: rectangle label:"Add Auth Headers"
+n5: rectangle label:"Apply Circuit Breaker"
+n6: diamond label:"Circuit Open?"
+n7: rectangle label:"Enable Retry Logic"
+n8: rectangle label:"Return Cached Fallback"
+n12: rectangle label:"Collect Metrics"
+n13: rectangle label:"Forward Response"
+n4.handle(right) -> n5.handle(left) [label="Bearer Token"]
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left) [label="Closed"]
+n6.handle(bottom) -> n8.handle(top) [label="Open"]
+n7.handle(bottom) -> ExternalService.n9.handle(top) [label="HTTPS + Retry"]
+n8.handle(top) -> Application.n14.handle(bottom) [label="Fallback"]
+n12.handle(right) -> n13.handle(left)
+n13.handle(top) -> Application.n14.handle(bottom) [label="Proxied Response"]
+}
+ExternalService { # External API
+n9: rectangle label:"Third-Party API"
+n10: rectangle label:"Process Request"
+n11: rectangle label:"Return Response"
+n9.handle(right) -> n10.handle(left)
+n10.handle(right) -> n11.handle(left)
+n11.handle(top) -> AmbassadorLogic.n12.handle(bottom) [label="Response + Metrics"]
+}
diff --git a/mcp/architecture/circuit-breaker-resilience-architecture/README.md b/mcp/architecture/circuit-breaker-resilience-architecture/README.md
index 010420b597c2ce10ccc29ec2b55e3fbc0e609b69..3971e053f67246c4e1c6940563c477988a7d0f95 100644
--- a/mcp/architecture/circuit-breaker-resilience-architecture/README.md
+++ b/mcp/architecture/circuit-breaker-resilience-architecture/README.md
@@ -6,7 +6,7 @@ A circuit breaker resilience architecture diagram showing the complete state mac
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** mcp  
-**Secondary use cases:** None  
+**Secondary use cases:** patterns  
 **Complexity:** 4/5  
 **Nodes:** 18  
 **Lanes:** 3  
diff --git a/mcp/architecture/circuit-breaker-resilience-architecture/metadata.json b/mcp/architecture/circuit-breaker-resilience-architecture/metadata.json
index 3f9c9ada8b8329257b639eaad9ea7b58ac9c9375..d70cd1aa64f2f27bcbce8eb3d29b7eaafc72e658 100644
--- a/mcp/architecture/circuit-breaker-resilience-architecture/metadata.json
+++ b/mcp/architecture/circuit-breaker-resilience-architecture/metadata.json
@@ -5,9 +5,12 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "mcp",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "patterns"
+  ],
   "use_cases": [
-    "mcp"
+    "mcp",
+    "patterns"
   ],
   "complexity": 4,
   "num_nodes": 18,
diff --git a/mcp/architecture/circuit-breaker-resilience-architecture/workflow.fz b/mcp/architecture/circuit-breaker-resilience-architecture/workflow.fz
index bf3619f098da490fb867d4cc93effc07ae48181a..e269e5b0d8f27e5f5587900dd6e81e641d42519b 100644
--- a/mcp/architecture/circuit-breaker-resilience-architecture/workflow.fz
+++ b/mcp/architecture/circuit-breaker-resilience-architecture/workflow.fz
@@ -1,52 +1,52 @@
-Client { # Client Service
-n1: circle label:"Service Call"
-n2: rectangle label:"Circuit Breaker Proxy"
-n21: rectangle label:"Receive Response"
-n22: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Breaker.n3.handle(top) [label="Check State"]
-n21.handle(right) -> n22.handle(left)
-}
-Breaker { # Circuit Breaker
-n3: diamond label:"Circuit State?"
-n4: rectangle label:"Forward Request (Closed)"
-n5: rectangle label:"Return Fallback (Open)"
-n6: rectangle label:"Test Request (Half-Open)"
-n13: rectangle label:"Track Success"
-n14: rectangle label:"Track Failure"
-n15: diamond label:"Failure Threshold?"
-n16: rectangle label:"Trip Circuit Open"
-n17: rectangle label:"Reset to Closed"
-n18: rectangle label:"Start Recovery Timer"
-n19: rectangle label:"Forward Success Response"
-n20: rectangle label:"Forward Error Response"
-n3.handle(right) -> n4.handle(left) [label="Closed"]
-n3.handle(bottom) -> n5.handle(top) [label="Open"]
-n3.handle(left) -> n6.handle(right) [label="Half-Open"]
-n4.handle(bottom) -> Downstream.n7.handle(top) [label="Forward"]
-n5.handle(top) -> Client.n21.handle(bottom) [label="Cached/Default"]
-n6.handle(bottom) -> Downstream.n7.handle(top) [label="Probe"]
-n13.handle(right) -> n17.handle(left) [label="Healthy"]
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left) [label="Exceeded"]
-n16.handle(right) -> n18.handle(left) [label="Cooldown"]
-n17.handle(right) -> n19.handle(left)
-n19.handle(top) -> Client.n21.handle(bottom) [label="Success"]
-n18.handle(right) -> n20.handle(left)
-n20.handle(top) -> Client.n21.handle(bottom) [label="Error"]
-}
-Downstream { # Downstream Service
-n7: rectangle label:"Process Request"
-n8: diamond label:"Response OK?"
-n9: rectangle label:"Return Success"
-n10: rectangle label:"Return Error/Timeout"
-n11: rectangle label:"Send Success Signal"
-n12: rectangle label:"Send Failure Signal"
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left) [label="200"]
-n8.handle(bottom) -> n10.handle(top) [label="5xx/Timeout"]
-n9.handle(right) -> n11.handle(left)
-n10.handle(right) -> n12.handle(left)
-n11.handle(top) -> Breaker.n13.handle(bottom) [label="Success"]
-n12.handle(top) -> Breaker.n14.handle(bottom) [label="Failure"]
-}
+Client { # Client Service
+n1: circle label:"Service Call"
+n2: rectangle label:"Circuit Breaker Proxy"
+n21: rectangle label:"Receive Response"
+n22: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Breaker.n3.handle(top) [label="Check State"]
+n21.handle(right) -> n22.handle(left)
+}
+Breaker { # Circuit Breaker
+n3: diamond label:"Circuit State?"
+n4: rectangle label:"Forward Request (Closed)"
+n5: rectangle label:"Return Fallback (Open)"
+n6: rectangle label:"Test Request (Half-Open)"
+n13: rectangle label:"Track Success"
+n14: rectangle label:"Track Failure"
+n15: diamond label:"Failure Threshold?"
+n16: rectangle label:"Trip Circuit Open"
+n17: rectangle label:"Reset to Closed"
+n18: rectangle label:"Start Recovery Timer"
+n19: rectangle label:"Forward Success Response"
+n20: rectangle label:"Forward Error Response"
+n3.handle(right) -> n4.handle(left) [label="Closed"]
+n3.handle(bottom) -> n5.handle(top) [label="Open"]
+n3.handle(left) -> n6.handle(right) [label="Half-Open"]
+n4.handle(bottom) -> Downstream.n7.handle(top) [label="Forward"]
+n5.handle(top) -> Client.n21.handle(bottom) [label="Cached/Default"]
+n6.handle(bottom) -> Downstream.n7.handle(top) [label="Probe"]
+n13.handle(right) -> n17.handle(left) [label="Healthy"]
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left) [label="Exceeded"]
+n16.handle(right) -> n18.handle(left) [label="Cooldown"]
+n17.handle(right) -> n19.handle(left)
+n19.handle(top) -> Client.n21.handle(bottom) [label="Success"]
+n18.handle(right) -> n20.handle(left)
+n20.handle(top) -> Client.n21.handle(bottom) [label="Error"]
+}
+Downstream { # Downstream Service
+n7: rectangle label:"Process Request"
+n8: diamond label:"Response OK?"
+n9: rectangle label:"Return Success"
+n10: rectangle label:"Return Error/Timeout"
+n11: rectangle label:"Send Success Signal"
+n12: rectangle label:"Send Failure Signal"
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left) [label="200"]
+n8.handle(bottom) -> n10.handle(top) [label="5xx/Timeout"]
+n9.handle(right) -> n11.handle(left)
+n10.handle(right) -> n12.handle(left)
+n11.handle(top) -> Breaker.n13.handle(bottom) [label="Success"]
+n12.handle(top) -> Breaker.n14.handle(bottom) [label="Failure"]
+}
diff --git a/mcp/architecture/graphql-federation-architecture/workflow.fz b/mcp/architecture/graphql-federation-architecture/workflow.fz
index 170679688e4e42dd7840e2caea71ba00f51647dd..1609e411d9b161b0341297d77ee9a6555c8e47ba 100644
--- a/mcp/architecture/graphql-federation-architecture/workflow.fz
+++ b/mcp/architecture/graphql-federation-architecture/workflow.fz
@@ -1,51 +1,51 @@
-Client { # Client Application
-n1: circle label:"GraphQL Query"
-n2: rectangle label:"Send to Gateway"
-n21: rectangle label:"Receive Unified Response"
-n22: circle label:"Render UI"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Gateway.n3.handle(top) [label="POST /graphql"]
-n21.handle(right) -> n22.handle(left)
-}
-Gateway { # Apollo Federation Gateway
-n3: rectangle label:"Parse GraphQL Query"
-n4: rectangle label:"Build Query Plan"
-n5: rectangle label:"Fan-Out to Subgraphs"
-n18: rectangle label:"Merge Responses"
-n19: rectangle label:"Return Unified Result"
-n20: rectangle label:"Send to Client"
-n3.handle(right) -> n4.handle(left) [label="AST"]
-n4.handle(right) -> n5.handle(left) [label="Execution Plan"]
-n5.handle(bottom) -> Subgraphs.n6.handle(top) [label="User Fields"]
-n5.handle(bottom) -> Subgraphs.n8.handle(top) [label="Product Fields"]
-n5.handle(bottom) -> Subgraphs.n10.handle(top) [label="Review Fields"]
-n18.handle(right) -> n19.handle(left) [label="Stitched"]
-n19.handle(right) -> n20.handle(left)
-n20.handle(top) -> Client.n21.handle(bottom) [label="JSON"]
-}
-Subgraphs { # Federated Subgraphs
-n6: rectangle label:"User Subgraph"
-n7: rectangle label:"User Database"
-n8: rectangle label:"Product Subgraph"
-n9: rectangle label:"Product Database"
-n10: rectangle label:"Review Subgraph"
-n11: rectangle label:"Review Database"
-n12: rectangle label:"Collect User Data"
-n13: rectangle label:"Collect Product Data"
-n14: rectangle label:"Collect Review Data"
-n15: rectangle label:"Aggregate All Results"
-n16: rectangle label:"Prepare Response"
-n17: rectangle label:"Send Combined Data"
-n6.handle(right) -> n7.handle(left) [label="Query"]
-n8.handle(right) -> n9.handle(left) [label="Query"]
-n10.handle(right) -> n11.handle(left) [label="Query"]
-n7.handle(right) -> n12.handle(left)
-n9.handle(right) -> n13.handle(left)
-n11.handle(right) -> n14.handle(left)
-n12.handle(bottom) -> n15.handle(top) [label="User Data"]
-n13.handle(bottom) -> n15.handle(top) [label="Product Data"]
-n14.handle(right) -> n15.handle(left) [label="Review Data"]
-n15.handle(right) -> n16.handle(left)
-n16.handle(right) -> n17.handle(left)
-n17.handle(top) -> Gateway.n18.handle(bottom) [label="All Data"]
-}
+Client { # Client Application
+n1: circle label:"GraphQL Query"
+n2: rectangle label:"Send to Gateway"
+n21: rectangle label:"Receive Unified Response"
+n22: circle label:"Render UI"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Gateway.n3.handle(top) [label="POST /graphql"]
+n21.handle(right) -> n22.handle(left)
+}
+Gateway { # Apollo Federation Gateway
+n3: rectangle label:"Parse GraphQL Query"
+n4: rectangle label:"Build Query Plan"
+n5: rectangle label:"Fan-Out to Subgraphs"
+n18: rectangle label:"Merge Responses"
+n19: rectangle label:"Return Unified Result"
+n20: rectangle label:"Send to Client"
+n3.handle(right) -> n4.handle(left) [label="AST"]
+n4.handle(right) -> n5.handle(left) [label="Execution Plan"]
+n5.handle(bottom) -> Subgraphs.n6.handle(top) [label="User Fields"]
+n5.handle(bottom) -> Subgraphs.n8.handle(top) [label="Product Fields"]
+n5.handle(bottom) -> Subgraphs.n10.handle(top) [label="Review Fields"]
+n18.handle(right) -> n19.handle(left) [label="Stitched"]
+n19.handle(right) -> n20.handle(left)
+n20.handle(top) -> Client.n21.handle(bottom) [label="JSON"]
+}
+Subgraphs { # Federated Subgraphs
+n6: rectangle label:"User Subgraph"
+n7: rectangle label:"User Database"
+n8: rectangle label:"Product Subgraph"
+n9: rectangle label:"Product Database"
+n10: rectangle label:"Review Subgraph"
+n11: rectangle label:"Review Database"
+n12: rectangle label:"Collect User Data"
+n13: rectangle label:"Collect Product Data"
+n14: rectangle label:"Collect Review Data"
+n15: rectangle label:"Aggregate All Results"
+n16: rectangle label:"Prepare Response"
+n17: rectangle label:"Send Combined Data"
+n6.handle(right) -> n7.handle(left) [label="Query"]
+n8.handle(right) -> n9.handle(left) [label="Query"]
+n10.handle(right) -> n11.handle(left) [label="Query"]
+n7.handle(right) -> n12.handle(left)
+n9.handle(right) -> n13.handle(left)
+n11.handle(right) -> n14.handle(left)
+n12.handle(bottom) -> n15.handle(top) [label="User Data"]
+n13.handle(bottom) -> n15.handle(top) [label="Product Data"]
+n14.handle(right) -> n15.handle(left) [label="Review Data"]
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left)
+n17.handle(top) -> Gateway.n18.handle(bottom) [label="All Data"]
+}
diff --git a/mcp/architecture/microservices-service-mesh-architecture/README.md b/mcp/architecture/microservices-service-mesh-architecture/README.md
index 1acbb8c6574a82fcbd42795da98ec8dafd9ea780..c8100e2e46c5ce59dd3cf6062376521b0b577084 100644
--- a/mcp/architecture/microservices-service-mesh-architecture/README.md
+++ b/mcp/architecture/microservices-service-mesh-architecture/README.md
@@ -6,7 +6,7 @@ A service mesh architecture diagram with Istio or Linkerd sidecar proxies handli
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** mcp  
-**Secondary use cases:** None  
+**Secondary use cases:** architecture  
 **Complexity:** 4/5  
 **Nodes:** 18  
 **Lanes:** 3  
diff --git a/mcp/architecture/microservices-service-mesh-architecture/metadata.json b/mcp/architecture/microservices-service-mesh-architecture/metadata.json
index c01cf00de33a3b4aaba9f8c2f0f71732273bcbf6..253415dbb296e4c5daf0d101530accbfc8282f9a 100644
--- a/mcp/architecture/microservices-service-mesh-architecture/metadata.json
+++ b/mcp/architecture/microservices-service-mesh-architecture/metadata.json
@@ -5,9 +5,12 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "mcp",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "architecture"
+  ],
   "use_cases": [
-    "mcp"
+    "mcp",
+    "architecture"
   ],
   "complexity": 4,
   "num_nodes": 18,
diff --git a/mcp/architecture/microservices-service-mesh-architecture/workflow.fz b/mcp/architecture/microservices-service-mesh-architecture/workflow.fz
index 2931fe2e4c7c543a41b98438fe3f1d5af5caab59..f467b371c30316135d986d745d7fca5c745ca00b 100644
--- a/mcp/architecture/microservices-service-mesh-architecture/workflow.fz
+++ b/mcp/architecture/microservices-service-mesh-architecture/workflow.fz
@@ -1,52 +1,52 @@
-Ingress { # Ingress Controller
-n1: circle label:"External Traffic"
-n2: rectangle label:"TLS Termination"
-n3: rectangle label:"Route to Service Mesh"
-n22: rectangle label:"Receive Mesh Response"
-n23: circle label:"Response to Client"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(bottom) -> Mesh.n4.handle(top) [label="Enter Mesh"]
-n22.handle(right) -> n23.handle(left)
-}
-Mesh { # Service Mesh (Istio/Linkerd)
-n4: rectangle label:"Sidecar Proxy Intercept"
-n5: rectangle label:"mTLS Encryption"
-n6: rectangle label:"Traffic Policy Check"
-n7: diamond label:"Circuit Breaker Open?"
-n8: rectangle label:"Load Balance Request"
-n9: rectangle label:"Return Fallback"
-n18: rectangle label:"Receive Service Response"
-n19: rectangle label:"Collect Telemetry"
-n20: rectangle label:"Distributed Tracing"
-n21: rectangle label:"Forward to Ingress"
-n4.handle(right) -> n5.handle(left)
-n5.handle(right) -> n6.handle(left)
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n8.handle(left) [label="Closed"]
-n7.handle(bottom) -> n9.handle(top) [label="Open"]
-n8.handle(bottom) -> Services.n10.handle(top) [label="Forward"]
-n9.handle(bottom) -> Services.n16.handle(top) [label="Fallback"]
-n18.handle(right) -> n19.handle(left)
-n19.handle(right) -> n20.handle(left)
-n20.handle(right) -> n21.handle(left)
-n21.handle(top) -> Ingress.n22.handle(bottom) [label="Mesh Response"]
-}
-Services { # Backend Services
-n10: rectangle label:"Product Catalog Service"
-n11: rectangle label:"Pricing Service"
-n12: rectangle label:"Recommendation Engine"
-n13: rectangle label:"Response Aggregation"
-n14: rectangle label:"Sidecar Proxy Egress"
-n15: rectangle label:"Return to Mesh"
-n16: rectangle label:"Cached Fallback Response"
-n17: rectangle label:"Return Fallback to Mesh"
-n10.handle(right) -> n11.handle(left) [label="Get Prices"]
-n11.handle(right) -> n12.handle(left) [label="Enrich"]
-n12.handle(right) -> n13.handle(left)
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left)
-n15.handle(top) -> Mesh.n18.handle(bottom) [label="Service Response"]
-n16.handle(right) -> n17.handle(left) [label="Stale Data"]
-n17.handle(top) -> Mesh.n18.handle(bottom) [label="Fallback Response"]
-}
+Ingress { # Ingress Controller
+n1: circle label:"External Traffic"
+n2: rectangle label:"TLS Termination"
+n3: rectangle label:"Route to Service Mesh"
+n22: rectangle label:"Receive Mesh Response"
+n23: circle label:"Response to Client"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(bottom) -> Mesh.n4.handle(top) [label="Enter Mesh"]
+n22.handle(right) -> n23.handle(left)
+}
+Mesh { # Service Mesh (Istio/Linkerd)
+n4: rectangle label:"Sidecar Proxy Intercept"
+n5: rectangle label:"mTLS Encryption"
+n6: rectangle label:"Traffic Policy Check"
+n7: diamond label:"Circuit Breaker Open?"
+n8: rectangle label:"Load Balance Request"
+n9: rectangle label:"Return Fallback"
+n18: rectangle label:"Receive Service Response"
+n19: rectangle label:"Collect Telemetry"
+n20: rectangle label:"Distributed Tracing"
+n21: rectangle label:"Forward to Ingress"
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left) [label="Closed"]
+n7.handle(bottom) -> n9.handle(top) [label="Open"]
+n8.handle(bottom) -> Services.n10.handle(top) [label="Forward"]
+n9.handle(bottom) -> Services.n16.handle(top) [label="Fallback"]
+n18.handle(right) -> n19.handle(left)
+n19.handle(right) -> n20.handle(left)
+n20.handle(right) -> n21.handle(left)
+n21.handle(top) -> Ingress.n22.handle(bottom) [label="Mesh Response"]
+}
+Services { # Backend Services
+n10: rectangle label:"Product Catalog Service"
+n11: rectangle label:"Pricing Service"
+n12: rectangle label:"Recommendation Engine"
+n13: rectangle label:"Response Aggregation"
+n14: rectangle label:"Sidecar Proxy Egress"
+n15: rectangle label:"Return to Mesh"
+n16: rectangle label:"Cached Fallback Response"
+n17: rectangle label:"Return Fallback to Mesh"
+n10.handle(right) -> n11.handle(left) [label="Get Prices"]
+n11.handle(right) -> n12.handle(left) [label="Enrich"]
+n12.handle(right) -> n13.handle(left)
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left)
+n15.handle(top) -> Mesh.n18.handle(bottom) [label="Service Response"]
+n16.handle(right) -> n17.handle(left) [label="Stale Data"]
+n17.handle(top) -> Mesh.n18.handle(bottom) [label="Fallback Response"]
+}
diff --git a/mcp/architecture/microservices-sidecar-pattern-architecture/README.md b/mcp/architecture/microservices-sidecar-pattern-architecture/README.md
index 52a6595e4ecbed9ecf2c19c0bf4dd8c868b566c8..06c0d70f9be4f3b842cfd93c30270dea2abde712 100644
--- a/mcp/architecture/microservices-sidecar-pattern-architecture/README.md
+++ b/mcp/architecture/microservices-sidecar-pattern-architecture/README.md
@@ -6,7 +6,7 @@ A sidecar pattern architecture diagram showing Envoy proxy, log collector, and c
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** mcp  
-**Secondary use cases:** None  
+**Secondary use cases:** architecture, patterns  
 **Complexity:** 4/5  
 **Nodes:** 13  
 **Lanes:** 3  
diff --git a/mcp/architecture/microservices-sidecar-pattern-architecture/metadata.json b/mcp/architecture/microservices-sidecar-pattern-architecture/metadata.json
index 4b8a0eba546a10af9a8a33513bdf926b17cd1dba..5b6abb469cea773e6ef1df8ca48fcdfb80ec507b 100644
--- a/mcp/architecture/microservices-sidecar-pattern-architecture/metadata.json
+++ b/mcp/architecture/microservices-sidecar-pattern-architecture/metadata.json
@@ -5,9 +5,14 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "mcp",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "architecture",
+    "patterns"
+  ],
   "use_cases": [
-    "mcp"
+    "mcp",
+    "architecture",
+    "patterns"
   ],
   "complexity": 4,
   "num_nodes": 13,
diff --git a/mcp/architecture/microservices-sidecar-pattern-architecture/workflow.fz b/mcp/architecture/microservices-sidecar-pattern-architecture/workflow.fz
index 320fd8d28d5bc378f1b3dc32434ae83f8c8401b6..a84e901cc155eea925b59fb4aa538ed98fec76bb 100644
--- a/mcp/architecture/microservices-sidecar-pattern-architecture/workflow.fz
+++ b/mcp/architecture/microservices-sidecar-pattern-architecture/workflow.fz
@@ -1,37 +1,37 @@
-ControlPlane { # Control Plane
-n1: rectangle label:"Service Mesh Control Plane"
-n2: rectangle label:"Push Configuration"
-n3: rectangle label:"Certificate Authority"
-n15: rectangle label:"Receive Config Ack"
-n16: rectangle label:"Config Confirmed"
-n1.handle(right) -> n2.handle(left) [label="Policy"]
-n2.handle(bottom) -> Pod.n4.handle(top) [label="xDS Config"]
-n3.handle(bottom) -> Pod.n4.handle(top) [label="mTLS Cert"]
-n15.handle(right) -> n16.handle(left)
-}
-Pod { # Kubernetes Pod
-n4: rectangle label:"Envoy Sidecar Proxy"
-n5: rectangle label:"Config Watcher Sidecar"
-n6: rectangle label:"Application Container"
-n7: rectangle label:"Log Collector Sidecar"
-n8: rectangle label:"Send Log Batch"
-n13: rectangle label:"Receive Log Ack"
-n14: rectangle label:"Acknowledge Config"
-n4.handle(right) -> n5.handle(left)
-n5.handle(right) -> n6.handle(left) [label="Config Applied"]
-n6.handle(right) -> n7.handle(left) [label="Logs"]
-n7.handle(right) -> n8.handle(left)
-n8.handle(bottom) -> Observability.n9.handle(top) [label="Ship Logs"]
-n13.handle(right) -> n14.handle(left)
-n14.handle(top) -> ControlPlane.n15.handle(bottom) [label="Config Ack"]
-}
-Observability { # Observability Stack
-n9: rectangle label:"ELK Log Aggregation"
-n10: rectangle label:"Prometheus Metrics"
-n11: rectangle label:"Jaeger Tracing"
-n12: rectangle label:"Return Log Ack"
-n9.handle(right) -> n10.handle(left)
-n10.handle(right) -> n11.handle(left) [label="Traces"]
-n11.handle(right) -> n12.handle(left)
-n12.handle(top) -> Pod.n13.handle(bottom) [label="Logs Received"]
-}
+ControlPlane { # Control Plane
+n1: rectangle label:"Service Mesh Control Plane"
+n2: rectangle label:"Push Configuration"
+n3: rectangle label:"Certificate Authority"
+n15: rectangle label:"Receive Config Ack"
+n16: rectangle label:"Config Confirmed"
+n1.handle(right) -> n2.handle(left) [label="Policy"]
+n2.handle(bottom) -> Pod.n4.handle(top) [label="xDS Config"]
+n3.handle(bottom) -> Pod.n4.handle(top) [label="mTLS Cert"]
+n15.handle(right) -> n16.handle(left)
+}
+Pod { # Kubernetes Pod
+n4: rectangle label:"Envoy Sidecar Proxy"
+n5: rectangle label:"Config Watcher Sidecar"
+n6: rectangle label:"Application Container"
+n7: rectangle label:"Log Collector Sidecar"
+n8: rectangle label:"Send Log Batch"
+n13: rectangle label:"Receive Log Ack"
+n14: rectangle label:"Acknowledge Config"
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left) [label="Config Applied"]
+n6.handle(right) -> n7.handle(left) [label="Logs"]
+n7.handle(right) -> n8.handle(left)
+n8.handle(bottom) -> Observability.n9.handle(top) [label="Ship Logs"]
+n13.handle(right) -> n14.handle(left)
+n14.handle(top) -> ControlPlane.n15.handle(bottom) [label="Config Ack"]
+}
+Observability { # Observability Stack
+n9: rectangle label:"ELK Log Aggregation"
+n10: rectangle label:"Prometheus Metrics"
+n11: rectangle label:"Jaeger Tracing"
+n12: rectangle label:"Return Log Ack"
+n9.handle(right) -> n10.handle(left)
+n10.handle(right) -> n11.handle(left) [label="Traces"]
+n11.handle(right) -> n12.handle(left)
+n12.handle(top) -> Pod.n13.handle(bottom) [label="Logs Received"]
+}
diff --git a/mcp/architecture/serverless-api-backend-architecture/README.md b/mcp/architecture/serverless-api-backend-architecture/README.md
index aef554506d6af653525c54b26bf40ae86c73d6bc..a8d5ab8864f4a9a2d2d002a62176e2b856f07bb0 100644
--- a/mcp/architecture/serverless-api-backend-architecture/README.md
+++ b/mcp/architecture/serverless-api-backend-architecture/README.md
@@ -6,7 +6,7 @@ A serverless API backend architecture diagram with API Gateway, Lambda authorize
 **Kind:** architecture  
 **Source domain:** Architecture  
 **Primary use case:** mcp  
-**Secondary use cases:** None  
+**Secondary use cases:** architecture  
 **Complexity:** 3/5  
 **Nodes:** 15  
 **Lanes:** 3  
diff --git a/mcp/architecture/serverless-api-backend-architecture/metadata.json b/mcp/architecture/serverless-api-backend-architecture/metadata.json
index 580f9be2ac77ce77918048d119566ecf121a784f..4e916c263fbb4817d62090290ae7f2ef733261d1 100644
--- a/mcp/architecture/serverless-api-backend-architecture/metadata.json
+++ b/mcp/architecture/serverless-api-backend-architecture/metadata.json
@@ -5,9 +5,12 @@
   "kind": "architecture",
   "source_domain": "Architecture",
   "primary_use_case": "mcp",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "architecture"
+  ],
   "use_cases": [
-    "mcp"
+    "mcp",
+    "architecture"
   ],
   "complexity": 3,
   "num_nodes": 15,
diff --git a/mcp/architecture/serverless-api-backend-architecture/workflow.fz b/mcp/architecture/serverless-api-backend-architecture/workflow.fz
index 6730eb6984b7b9e03ae55d84e4bc11544318bae7..179b96a0d249f5b134b1d102f7cbc164a8ba7359 100644
--- a/mcp/architecture/serverless-api-backend-architecture/workflow.fz
+++ b/mcp/architecture/serverless-api-backend-architecture/workflow.fz
@@ -1,39 +1,39 @@
-Client { # Client Application
-n1: circle label:"API Request"
-n2: rectangle label:"API Gateway (AWS/Azure)"
-n16: rectangle label:"Receive Response"
-n17: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Functions.n3.handle(top) [label="Invoke Lambda"]
-n16.handle(right) -> n17.handle(left)
-}
-Functions { # Serverless Functions
-n3: rectangle label:"Auth Authorizer Lambda"
-n4: diamond label:"Token Valid?"
-n5: rectangle label:"Business Logic Lambda"
-n6: rectangle label:"Return 401"
-n13: rectangle label:"Receive Data"
-n14: rectangle label:"Data Validation Lambda"
-n15: rectangle label:"Response Formatter"
-n3.handle(right) -> n4.handle(left)
-n4.handle(right) -> n5.handle(left) [label="Authorized"]
-n4.handle(bottom) -> n6.handle(top) [label="Denied"]
-n5.handle(bottom) -> ManagedServices.n7.handle(top) [label="Read/Write"]
-n6.handle(top) -> Client.n16.handle(bottom) [label="401"]
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left) [label="Validated"]
-n15.handle(top) -> Client.n16.handle(bottom) [label="200 JSON"]
-}
-ManagedServices { # Managed Cloud Services
-n7: rectangle label:"DynamoDB / CosmosDB"
-n8: rectangle label:"S3 Object Storage"
-n9: rectangle label:"SQS Message Queue"
-n10: rectangle label:"SNS Notification"
-n11: rectangle label:"CloudWatch Logs"
-n12: rectangle label:"Return Data"
-n7.handle(right) -> n8.handle(left) [label="Store Assets"]
-n9.handle(right) -> n10.handle(left) [label="Trigger"]
-n10.handle(right) -> n11.handle(left) [label="Log"]
-n11.handle(right) -> n12.handle(left)
-n12.handle(top) -> Functions.n13.handle(bottom) [label="Data Response"]
-}
+Client { # Client Application
+n1: circle label:"API Request"
+n2: rectangle label:"API Gateway (AWS/Azure)"
+n16: rectangle label:"Receive Response"
+n17: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Functions.n3.handle(top) [label="Invoke Lambda"]
+n16.handle(right) -> n17.handle(left)
+}
+Functions { # Serverless Functions
+n3: rectangle label:"Auth Authorizer Lambda"
+n4: diamond label:"Token Valid?"
+n5: rectangle label:"Business Logic Lambda"
+n6: rectangle label:"Return 401"
+n13: rectangle label:"Receive Data"
+n14: rectangle label:"Data Validation Lambda"
+n15: rectangle label:"Response Formatter"
+n3.handle(right) -> n4.handle(left)
+n4.handle(right) -> n5.handle(left) [label="Authorized"]
+n4.handle(bottom) -> n6.handle(top) [label="Denied"]
+n5.handle(bottom) -> ManagedServices.n7.handle(top) [label="Read/Write"]
+n6.handle(top) -> Client.n16.handle(bottom) [label="401"]
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left) [label="Validated"]
+n15.handle(top) -> Client.n16.handle(bottom) [label="200 JSON"]
+}
+ManagedServices { # Managed Cloud Services
+n7: rectangle label:"DynamoDB / CosmosDB"
+n8: rectangle label:"S3 Object Storage"
+n9: rectangle label:"SQS Message Queue"
+n10: rectangle label:"SNS Notification"
+n11: rectangle label:"CloudWatch Logs"
+n12: rectangle label:"Return Data"
+n7.handle(right) -> n8.handle(left) [label="Store Assets"]
+n9.handle(right) -> n10.handle(left) [label="Trigger"]
+n10.handle(right) -> n11.handle(left) [label="Log"]
+n11.handle(right) -> n12.handle(left)
+n12.handle(top) -> Functions.n13.handle(bottom) [label="Data Response"]
+}
diff --git a/mcp/devops/mcp-circuit-breaker/README.md b/mcp/devops/mcp-circuit-breaker/README.md
index 128d7367b398bed16b8d4738a442da4538c6189c..966d5b342d8b744e5321f68df8747975fc0c373c 100644
--- a/mcp/devops/mcp-circuit-breaker/README.md
+++ b/mcp/devops/mcp-circuit-breaker/README.md
@@ -6,7 +6,7 @@ A resilience pattern that wraps MCP calls with health-aware gates using three st
 **Kind:** architecture  
 **Source domain:** DevOps  
 **Primary use case:** mcp  
-**Secondary use cases:** None  
+**Secondary use cases:** patterns  
 **Complexity:** 3/5  
 **Nodes:** 9  
 **Lanes:** 3  
diff --git a/mcp/devops/mcp-circuit-breaker/metadata.json b/mcp/devops/mcp-circuit-breaker/metadata.json
index b6935b8c9e2e379193979f17866732c74a08c223..b0f87e2d36bc0fa3445d3af13c50b606b0c78158 100644
--- a/mcp/devops/mcp-circuit-breaker/metadata.json
+++ b/mcp/devops/mcp-circuit-breaker/metadata.json
@@ -5,9 +5,12 @@
   "kind": "architecture",
   "source_domain": "DevOps",
   "primary_use_case": "mcp",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "patterns"
+  ],
   "use_cases": [
-    "mcp"
+    "mcp",
+    "patterns"
   ],
   "complexity": 3,
   "num_nodes": 9,
diff --git a/mcp/devops/mcp-circuit-breaker/workflow.fz b/mcp/devops/mcp-circuit-breaker/workflow.fz
index e88a866acdfca618eb99fa22c76bb3c890b519bd..b0bfadc18df8d8f7c42dd2e5e69ce4469c6ef27e 100644
--- a/mcp/devops/mcp-circuit-breaker/workflow.fz
+++ b/mcp/devops/mcp-circuit-breaker/workflow.fz
@@ -1,37 +1,37 @@
-Host { # Host Application
-  n1: circle label="User sends prompt"
-  n2: rectangle label="Agent prepares MCP call"
-  n3: rectangle label="Pass call to circuit breaker"
-  n4: rectangle label="Receive result or error"
-  n5: rectangle label="Agent responds to user"
-  n1.handle(right) -> n2.handle(left)
-  n2.handle(right) -> n3.handle(left)
-  n3.handle(bottom) -> CB.n6.handle(top) [label="MCP tool call"]
-  n4.handle(right) -> n5.handle(left)
-}
-
-CB { # Circuit Breaker
-  n6: rectangle label="Check circuit state"
-  n7: diamond label="Circuit open?"
-  n8: rectangle label="Forward to MCP server"
-  n9: rectangle label="Fast-fail with error"
-  n10: diamond label="Call succeeded?"
-  n11: rectangle label="Record success"
-  n12: rectangle label="Record failure and check threshold"
-  n6.handle(right) -> n7.handle(left)
-  n7.handle(right) -> n8.handle(left) [label="Closed"]
-  n7.handle(bottom) -> n9.handle(top) [label="Open"]
-  n8.handle(bottom) -> MCPServer.n13.handle(top) [label="Forward request"]
-  n9.handle(top) -> Host.n4.handle(bottom) [label="CircuitOpenError"]
-  n10.handle(right) -> n11.handle(left) [label="Yes"]
-  n10.handle(bottom) -> n12.handle(top) [label="No"]
-  n11.handle(top) -> Host.n4.handle(left) [label="Return result"]
-  n12.handle(top) -> Host.n4.handle(right) [label="Return error"]
-}
-
-MCPServer { # MCP Server
-  n13: rectangle label="Attempt tool execution"
-  n14: rectangle label="Return result or error"
-  n13.handle(right) -> n14.handle(left)
-  n14.handle(top) -> CB.n10.handle(bottom) [label="Execution outcome"]
-}
+Host { # Host Application
+  n1: circle label="User sends prompt"
+  n2: rectangle label="Agent prepares MCP call"
+  n3: rectangle label="Pass call to circuit breaker"
+  n4: rectangle label="Receive result or error"
+  n5: rectangle label="Agent responds to user"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left)
+  n3.handle(bottom) -> CB.n6.handle(top) [label="MCP tool call"]
+  n4.handle(right) -> n5.handle(left)
+}
+
+CB { # Circuit Breaker
+  n6: rectangle label="Check circuit state"
+  n7: diamond label="Circuit open?"
+  n8: rectangle label="Forward to MCP server"
+  n9: rectangle label="Fast-fail with error"
+  n10: diamond label="Call succeeded?"
+  n11: rectangle label="Record success"
+  n12: rectangle label="Record failure and check threshold"
+  n6.handle(right) -> n7.handle(left)
+  n7.handle(right) -> n8.handle(left) [label="Closed"]
+  n7.handle(bottom) -> n9.handle(top) [label="Open"]
+  n8.handle(bottom) -> MCPServer.n13.handle(top) [label="Forward request"]
+  n9.handle(top) -> Host.n4.handle(bottom) [label="CircuitOpenError"]
+  n10.handle(right) -> n11.handle(left) [label="Yes"]
+  n10.handle(bottom) -> n12.handle(top) [label="No"]
+  n11.handle(top) -> Host.n4.handle(left) [label="Return result"]
+  n12.handle(top) -> Host.n4.handle(right) [label="Return error"]
+}
+
+MCPServer { # MCP Server
+  n13: rectangle label="Attempt tool execution"
+  n14: rectangle label="Return result or error"
+  n13.handle(right) -> n14.handle(left)
+  n14.handle(top) -> CB.n10.handle(bottom) [label="Execution outcome"]
+}
diff --git a/mcp/devops/mcp-context-proxy/workflow.fz b/mcp/devops/mcp-context-proxy/workflow.fz
index 0c1c794d8f7cbcb0574d3a863d9a0665c7d13100..e3792d9f0157d848227bd518dec3fccaba144452 100644
--- a/mcp/devops/mcp-context-proxy/workflow.fz
+++ b/mcp/devops/mcp-context-proxy/workflow.fz
@@ -1,32 +1,32 @@
-Host { # Host Application
-  n1: circle label="User sends prompt"
-  n2: rectangle label="Agent requests context"
-  n3: rectangle label="Receive context"
-  n4: rectangle label="Agent responds to user"
-  n1.handle(right) -> n2.handle(left)
-  n2.handle(bottom) -> Proxy.n5.handle(top) [label="Context request"]
-  n3.handle(right) -> n4.handle(left)
-}
-
-Proxy { # Context Proxy
-  n5: rectangle label="Receive context request"
-  n6: rectangle label="Check cache with TTL"
-  n7: diamond label="Cache hit?"
-  n8: rectangle label="Return cached context"
-  n9: rectangle label="Fetch fresh from MCP server"
-  n10: rectangle label="Compress and cache response"
-  n5.handle(right) -> n6.handle(left)
-  n6.handle(right) -> n7.handle(left)
-  n7.handle(right) -> n8.handle(left) [label="Hit"]
-  n7.handle(bottom) -> n9.handle(top) [label="Miss"]
-  n8.handle(top) -> Host.n3.handle(bottom) [label="Cached context"]
-  n9.handle(bottom) -> MCPServer.n11.handle(top) [label="Fetch request"]
-  n10.handle(top) -> Host.n3.handle(left) [label="Fresh context"]
-}
-
-MCPServer { # MCP Server
-  n11: rectangle label="Fetch full context"
-  n12: rectangle label="Return fresh data"
-  n11.handle(right) -> n12.handle(left)
-  n12.handle(top) -> Proxy.n10.handle(bottom) [label="Fresh data"]
-}
+Host { # Host Application
+  n1: circle label="User sends prompt"
+  n2: rectangle label="Agent requests context"
+  n3: rectangle label="Receive context"
+  n4: rectangle label="Agent responds to user"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(bottom) -> Proxy.n5.handle(top) [label="Context request"]
+  n3.handle(right) -> n4.handle(left)
+}
+
+Proxy { # Context Proxy
+  n5: rectangle label="Receive context request"
+  n6: rectangle label="Check cache with TTL"
+  n7: diamond label="Cache hit?"
+  n8: rectangle label="Return cached context"
+  n9: rectangle label="Fetch fresh from MCP server"
+  n10: rectangle label="Compress and cache response"
+  n5.handle(right) -> n6.handle(left)
+  n6.handle(right) -> n7.handle(left)
+  n7.handle(right) -> n8.handle(left) [label="Hit"]
+  n7.handle(bottom) -> n9.handle(top) [label="Miss"]
+  n8.handle(top) -> Host.n3.handle(bottom) [label="Cached context"]
+  n9.handle(bottom) -> MCPServer.n11.handle(top) [label="Fetch request"]
+  n10.handle(top) -> Host.n3.handle(left) [label="Fresh context"]
+}
+
+MCPServer { # MCP Server
+  n11: rectangle label="Fetch full context"
+  n12: rectangle label="Return fresh data"
+  n11.handle(right) -> n12.handle(left)
+  n12.handle(top) -> Proxy.n10.handle(bottom) [label="Fresh data"]
+}
diff --git a/mcp/devops/mcp-direct-connect/workflow.fz b/mcp/devops/mcp-direct-connect/workflow.fz
index d15e9edd65a81146fcfc56ca58e4aaaa99c2100f..7bb53133a5859927204b66da941e632056de349a 100644
--- a/mcp/devops/mcp-direct-connect/workflow.fz
+++ b/mcp/devops/mcp-direct-connect/workflow.fz
@@ -1,20 +1,20 @@
-Host { # Host Application
-  n1: circle label="User sends prompt"
-  n2: rectangle label="Agent builds JSON-RPC request"
-  n3: rectangle label="Send request via stdio"
-  n4: rectangle label="Receive JSON-RPC result"
-  n5: rectangle label="Agent responds to user"
-  n1.handle(right) -> n2.handle(left)
-  n2.handle(right) -> n3.handle(left)
-  n3.handle(bottom) -> MCPServer.n6.handle(top) [label="JSON-RPC request"]
-  n4.handle(right) -> n5.handle(left)
-}
-
-MCPServer { # MCP Server
-  n6: rectangle label="Parse incoming request"
-  n7: rectangle label="Execute tool or resource"
-  n8: rectangle label="Build JSON-RPC response"
-  n6.handle(right) -> n7.handle(left)
-  n7.handle(right) -> n8.handle(left)
-  n8.handle(top) -> Host.n4.handle(bottom) [label="JSON-RPC response"]
-}
+Host { # Host Application
+  n1: circle label="User sends prompt"
+  n2: rectangle label="Agent builds JSON-RPC request"
+  n3: rectangle label="Send request via stdio"
+  n4: rectangle label="Receive JSON-RPC result"
+  n5: rectangle label="Agent responds to user"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left)
+  n3.handle(bottom) -> MCPServer.n6.handle(top) [label="JSON-RPC request"]
+  n4.handle(right) -> n5.handle(left)
+}
+
+MCPServer { # MCP Server
+  n6: rectangle label="Parse incoming request"
+  n7: rectangle label="Execute tool or resource"
+  n8: rectangle label="Build JSON-RPC response"
+  n6.handle(right) -> n7.handle(left)
+  n7.handle(right) -> n8.handle(left)
+  n8.handle(top) -> Host.n4.handle(bottom) [label="JSON-RPC response"]
+}
diff --git a/mcp/llm-operations/context-compaction-gateway-workflow/README.md b/mcp/llm-operations/context-compaction-gateway-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ff88540086a2c695865e29b29ca70279865e5bc
--- /dev/null
+++ b/mcp/llm-operations/context-compaction-gateway-workflow/README.md
@@ -0,0 +1,19 @@
+# Context Compaction Gateway Workflow
+
+A context gateway that assembles raw context from the vector store and logs, compacts 100k tokens down to 15k and only then builds the final prompt.
+
+**Template ID:** `context-compaction-gateway-workflow`  
+**Kind:** workflow  
+**Source domain:** LLM Operations  
+**Primary use case:** mcp  
+**Secondary use cases:** context-management, llm-operations  
+**Complexity:** 2/5  
+**Nodes:** 12  
+**Lanes:** 4  
+**Tags:** [token-optimization, context-management, compaction, rag, llmops]  
+**Source path:** ``  
+**Repo path:** `mcp/llm-operations/context-compaction-gateway-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/mcp/llm-operations/context-compaction-gateway-workflow/metadata.json b/mcp/llm-operations/context-compaction-gateway-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..a5633afcb8b4d41d297037ddff293127af003728
--- /dev/null
+++ b/mcp/llm-operations/context-compaction-gateway-workflow/metadata.json
@@ -0,0 +1,30 @@
+{
+  "template_id": "context-compaction-gateway-workflow",
+  "workflow_id": "context-compaction-gateway",
+  "title": "Context Compaction Gateway Workflow",
+  "kind": "workflow",
+  "source_domain": "LLM Operations",
+  "primary_use_case": "mcp",
+  "secondary_use_cases": [
+    "context-management",
+    "llm-operations"
+  ],
+  "use_cases": [
+    "mcp",
+    "context-management",
+    "llm-operations"
+  ],
+  "complexity": 2,
+  "num_nodes": 12,
+  "num_lanes": 4,
+  "tags": [
+    "token-optimization",
+    "context-management",
+    "compaction",
+    "rag",
+    "llmops"
+  ],
+  "description": "A context gateway that assembles raw context from the vector store and logs, compacts 100k tokens down to 15k and only then builds the final prompt.",
+  "source_path": "",
+  "repo_path": "mcp/llm-operations/context-compaction-gateway-workflow"
+}
diff --git a/mcp/llm-operations/context-compaction-gateway-workflow/workflow.fz b/mcp/llm-operations/context-compaction-gateway-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..39a2a931004a9dcd9709c17b1b7f55d35aea8aae
--- /dev/null
+++ b/mcp/llm-operations/context-compaction-gateway-workflow/workflow.fz
@@ -0,0 +1,34 @@
+agent { # AI Orchestrator
+n1: circle label:"Task triggered"
+n4: rectangle label:"Assemble raw context"
+n9: rectangle label:"Build final prompt"
+n12: circle label:"Parse result"
+n1.handle(bottom) -> datastore.n2.handle(top) [label="Fetch history & docs"]
+n4.handle(bottom) -> compactor.n5.handle(top) [label="100k tokens"]
+n9.handle(bottom) -> llm.n10.handle(top) [label="Send 15k tokens"]
+}
+
+datastore { # Vector DB & Logs
+n2: rectangle label:"Retrieve chunks"
+n3: rectangle label:"Package records"
+n2.handle(right) -> n3.handle(left)
+n3.handle(top) -> agent.n4.handle(bottom) [label="Return matches"]
+}
+
+compactor { # Context Gateway
+n5: rectangle label:"Parse AST & blocks"
+n6: rectangle label:"Drop stale / duplicate info"
+n7: rectangle label:"Rank by query relevance"
+n8: rectangle label:"Pack remaining context"
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(top) -> agent.n9.handle(bottom) [label="Compacted 15k tokens"]
+}
+
+llm { # Model API
+n10: rectangle label:"Process lean prompt"
+n11: rectangle label:"Generate answer"
+n10.handle(right) -> n11.handle(left)
+n11.handle(top) -> agent.n12.handle(bottom) [label="Deliver response"]
+}
diff --git a/mcp/patterns/circuit-breaker-workflow/README.md b/mcp/patterns/circuit-breaker-workflow/README.md
index ba37bade3157c5cfb8f2f044cfc22b5c459fe1c4..640bebe22aa1e3110187c2fb0a25e94292893e95 100644
--- a/mcp/patterns/circuit-breaker-workflow/README.md
+++ b/mcp/patterns/circuit-breaker-workflow/README.md
@@ -6,7 +6,7 @@ Circuit breaker resilience pattern with closed, open, and half-open states for p
 **Kind:** workflow  
 **Source domain:** patterns  
 **Primary use case:** mcp  
-**Secondary use cases:** None  
+**Secondary use cases:** architecture, patterns  
 **Complexity:** 4/5  
 **Nodes:** 19  
 **Lanes:** 3  
diff --git a/mcp/patterns/circuit-breaker-workflow/metadata.json b/mcp/patterns/circuit-breaker-workflow/metadata.json
index 3a7da86c70fefba166315c1783c90f72faee0c02..0a11030811490079422cff14eeb8a5e1a73a0712 100644
--- a/mcp/patterns/circuit-breaker-workflow/metadata.json
+++ b/mcp/patterns/circuit-breaker-workflow/metadata.json
@@ -5,9 +5,14 @@
   "kind": "workflow",
   "source_domain": "patterns",
   "primary_use_case": "mcp",
-  "secondary_use_cases": [],
+  "secondary_use_cases": [
+    "architecture",
+    "patterns"
+  ],
   "use_cases": [
-    "mcp"
+    "mcp",
+    "architecture",
+    "patterns"
   ],
   "complexity": 4,
   "num_nodes": 19,
diff --git a/mcp/patterns/circuit-breaker-workflow/workflow.fz b/mcp/patterns/circuit-breaker-workflow/workflow.fz
index e347a51239333b7ae013b9ac2c0b10b597271f1e..b6b6c9c92b78b99a94ae964f5911c4ebbfccaff4 100644
--- a/mcp/patterns/circuit-breaker-workflow/workflow.fz
+++ b/mcp/patterns/circuit-breaker-workflow/workflow.fz
@@ -1,43 +1,43 @@
-Client { # Client Application
-n1: circle label:"Start"
-n2: rectangle label:"Initiate service call"
-n3: rectangle label:"Receive response"
-n4: rectangle label:"Process fallback response"
-n5: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> CircuitBreaker.n6.handle(top) [label="Request"]
-n3.handle(right) -> n5.handle(left)
-n4.handle(right) -> n5.handle(left)
-}
-CircuitBreaker { # Circuit Breaker
-n6: diamond label:"Circuit state?"
-n7: rectangle label:"Allow request through"
-n8: rectangle label:"Return cached fallback"
-n9: rectangle label:"Increment failure count"
-n10: diamond label:"Failure threshold reached?"
-n11: rectangle label:"Open circuit"
-n12: rectangle label:"Reset failure count"
-n13: rectangle label:"Start half-open timer"
-n6.handle(right) -> n7.handle(left) [label="Closed"]
-n6.handle(bottom) -> n8.handle(top) [label="Open"]
-n6.handle(left) -> n7.handle(top) [label="Half-Open"]
-n7.handle(bottom) -> ExternalService.n14.handle(top) [label="Forward"]
-n8.handle(top) -> Client.n4.handle(bottom) [label="Fallback"]
-n9.handle(right) -> n10.handle(left)
-n10.handle(right) -> n11.handle(left) [label="Yes"]
-n10.handle(bottom) -> n12.handle(top) [label="No"]
-n11.handle(right) -> n13.handle(left)
-n12.handle(top) -> Client.n3.handle(bottom) [label="Success"]
-n13.handle(top) -> Client.n4.handle(bottom) [label="Tripped"]
-}
-ExternalService { # External Service
-n14: rectangle label:"Process request"
-n15: diamond label:"Request successful?"
-n16: rectangle label:"Return success response"
-n17: rectangle label:"Return error response"
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left) [label="Yes"]
-n15.handle(bottom) -> n17.handle(top) [label="No"]
-n16.handle(top) -> CircuitBreaker.n12.handle(bottom) [label="OK"]
-n17.handle(top) -> CircuitBreaker.n9.handle(bottom) [label="Error"]
-}
+Client { # Client Application
+n1: circle label:"Start"
+n2: rectangle label:"Initiate service call"
+n3: rectangle label:"Receive response"
+n4: rectangle label:"Process fallback response"
+n5: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> CircuitBreaker.n6.handle(top) [label="Request"]
+n3.handle(right) -> n5.handle(left)
+n4.handle(right) -> n5.handle(left)
+}
+CircuitBreaker { # Circuit Breaker
+n6: diamond label:"Circuit state?"
+n7: rectangle label:"Allow request through"
+n8: rectangle label:"Return cached fallback"
+n9: rectangle label:"Increment failure count"
+n10: diamond label:"Failure threshold reached?"
+n11: rectangle label:"Open circuit"
+n12: rectangle label:"Reset failure count"
+n13: rectangle label:"Start half-open timer"
+n6.handle(right) -> n7.handle(left) [label="Closed"]
+n6.handle(bottom) -> n8.handle(top) [label="Open"]
+n6.handle(left) -> n7.handle(top) [label="Half-Open"]
+n7.handle(bottom) -> ExternalService.n14.handle(top) [label="Forward"]
+n8.handle(top) -> Client.n4.handle(bottom) [label="Fallback"]
+n9.handle(right) -> n10.handle(left)
+n10.handle(right) -> n11.handle(left) [label="Yes"]
+n10.handle(bottom) -> n12.handle(top) [label="No"]
+n11.handle(right) -> n13.handle(left)
+n12.handle(top) -> Client.n3.handle(bottom) [label="Success"]
+n13.handle(top) -> Client.n4.handle(bottom) [label="Tripped"]
+}
+ExternalService { # External Service
+n14: rectangle label:"Process request"
+n15: diamond label:"Request successful?"
+n16: rectangle label:"Return success response"
+n17: rectangle label:"Return error response"
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left) [label="Yes"]
+n15.handle(bottom) -> n17.handle(top) [label="No"]
+n16.handle(top) -> CircuitBreaker.n12.handle(bottom) [label="OK"]
+n17.handle(top) -> CircuitBreaker.n9.handle(bottom) [label="Error"]
+}
diff --git a/metadata.csv b/metadata.csv
index e24c96575d0ec0c76a311582d969286dcae6baee..9704b1afb75b5cb96ee86f1adbfac35e20a13463 100644
--- a/metadata.csv
+++ b/metadata.csv
@@ -1,75 +1,103 @@
 template_id,workflow_id,title,kind,source_domain,primary_use_case,secondary_use_cases,use_cases,complexity,num_nodes,num_lanes,tags,description,source_path,repo_path
-a-b-testing-workflow,a-b-testing,A B Testing Workflow,workflow,patterns,uncategorized,,,3,10,3,a;b;testing;patterns,This workflow models comparing two versions to see which performs better.,patterns/a-b-testing,uncategorized/patterns/a-b-testing-workflow
+01-basic-lane-workflow,01-basic-lane,01 Basic Lane Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,1,01;basic;lane,This workflow models two connected nodes in a single lane showing basic flow.,syntax-primitives/01-basic-lane,syntax-primitives/syntax-primitives/01-basic-lane-workflow
+02-handle-positions-workflow,02-handle-positions,02 Handle Positions Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,1,02;handle;positions,"This workflow models nodes with explicit top, bottom, left, and right handle connections.",syntax-primitives/02-handle-positions,syntax-primitives/syntax-primitives/02-handle-positions-workflow
+03-all-shapes-workflow,03-all-shapes,03 All Shapes Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,1,03;all;shapes,"This workflow models a workflow that demonstrates circle, rectangle, diamond, and taskbox shapes.",syntax-primitives/03-all-shapes,syntax-primitives/syntax-primitives/03-all-shapes-workflow
+04-labeled-arrows-workflow,04-labeled-arrows,04 Labeled Arrows Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,1,04;labeled;arrows,This workflow models connections with descriptive labels between nodes.,syntax-primitives/04-labeled-arrows,syntax-primitives/syntax-primitives/04-labeled-arrows-workflow
+05-multiple-lanes-workflow,05-multiple-lanes,05 Multiple Lanes Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,3,05;multiple;lanes,This workflow models three lanes with cross-lane communication.,syntax-primitives/05-multiple-lanes,syntax-primitives/syntax-primitives/05-multiple-lanes-workflow
+06-nested-lanes-workflow,06-nested-lanes,06 Nested Lanes Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,3,06;nested;lanes,This workflow models lanes that conceptually contain other lanes.,syntax-primitives/06-nested-lanes,syntax-primitives/syntax-primitives/06-nested-lanes-workflow
+07-unicode-labels-workflow,07-unicode-labels,07 Unicode Labels Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,1,07;unicode;labels,This workflow models a workflow with emoji and international characters in labels.,syntax-primitives/07-unicode-labels,syntax-primitives/syntax-primitives/07-unicode-labels-workflow
+08-empty-lane-workflow,08-empty-lane,08 Empty Lane Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,1,08;empty;lane,This workflow models a lane with no nodes to test empty-lane handling.,syntax-primitives/08-empty-lane,syntax-primitives/syntax-primitives/08-empty-lane-workflow
+09-cross-lane-circular-workflow,09-cross-lane-circular,09 Cross Lane Circular Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,1,09;cross;lane;circular,This workflow models an arrow that loops back across lanes in a circular fashion.,syntax-primitives/09-cross-lane-circular,syntax-primitives/syntax-primitives/09-cross-lane-circular-workflow
+10-long-labels-workflow,10-long-labels,10 Long Labels Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,1,5,1,10;long;labels,This workflow models labels with extra-long descriptive text.,syntax-primitives/10-long-labels,syntax-primitives/syntax-primitives/10-long-labels-workflow
+11-taskbox-complete-workflow,11-taskbox-complete,11 Taskbox Complete Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,2,7,2,11;taskbox;complete,"This workflow models a taskbox with owner, description, and system parameters.",syntax-primitives/11-taskbox-complete,syntax-primitives/syntax-primitives/11-taskbox-complete-workflow
+12-bidirectional-arrows-workflow,12-bidirectional-arrows,12 Bidirectional Arrows Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,2,7,2,12;bidirectional;arrows,This workflow models two-way connections between the same pair of nodes.,syntax-primitives/12-bidirectional-arrows,syntax-primitives/syntax-primitives/12-bidirectional-arrows-workflow
+13-parallel-flows-workflow,13-parallel-flows,13 Parallel Flows Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,2,7,2,13;parallel;flows,This workflow models one node splitting into three parallel tasks.,syntax-primitives/13-parallel-flows,syntax-primitives/syntax-primitives/13-parallel-flows-workflow
+14-error-handling-workflow,14-error-handling,14 Error Handling Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,2,7,2,14;error;handling,This workflow models a try and retry style pattern for handling errors.,syntax-primitives/14-error-handling,syntax-primitives/syntax-primitives/14-error-handling-workflow
+15-optional-parameters-workflow,15-optional-parameters,15 Optional Parameters Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,2,7,2,15;optional;parameters,This workflow models a taskbox with some optional fields left out.,syntax-primitives/15-optional-parameters,syntax-primitives/syntax-primitives/15-optional-parameters-workflow
+16-max-nodes-workflow,16-max-nodes,16 Max Nodes Workflow,workflow,syntax-primitives,edge-cases,,edge-cases,2,50,2,16;max;nodes,This workflow models 50 nodes in one lane as a stress test.,syntax-primitives/16-max-nodes,edge-cases/syntax-primitives/16-max-nodes-workflow
+17-minimal-nodes-workflow,17-minimal-nodes,17 Minimal Nodes Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,2,1,1,17;minimal;nodes,This workflow models a workflow with a single start node only.,syntax-primitives/17-minimal-nodes,syntax-primitives/syntax-primitives/17-minimal-nodes-workflow
+18-complex-handles-workflow,18-complex-handles,18 Complex Handles Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,2,7,2,18;complex;handles,This workflow models a workflow that uses every handle position in one diagram.,syntax-primitives/18-complex-handles,syntax-primitives/syntax-primitives/18-complex-handles-workflow
+19-label-escaping-workflow,19-label-escaping,19 Label Escaping Workflow,workflow,syntax-primitives,edge-cases,,edge-cases,2,7,2,19;label;escaping,This workflow models labels that include quotes and special characters.,syntax-primitives/19-label-escaping,edge-cases/syntax-primitives/19-label-escaping-workflow
+20-syntax-complete-workflow,20-syntax-complete,20 Syntax Complete Workflow,workflow,syntax-primitives,syntax-primitives,,syntax-primitives,2,7,3,20;syntax;complete,This workflow models one workflow using most available language features.,syntax-primitives/20-syntax-complete,syntax-primitives/syntax-primitives/20-syntax-complete-workflow
+a-b-testing-workflow,a-b-testing,A B Testing Workflow,workflow,patterns,patterns,,patterns,3,10,3,a;b;testing;patterns,This workflow models comparing two versions to see which performs better.,patterns/a-b-testing,patterns/patterns/a-b-testing-workflow
 ab-test-setup-workflow,ab-test-setup,Ab Test Setup Workflow,workflow,business-operations,onboarding,,onboarding,3,10,3,ab-testing;experimentation;split-testing;statistical-significance;conversion-optimization;optimizely,"A/B test setup workflow with hypothesis definition, variant creation, traffic allocation, statistical analysis, and winner deployment.",business-operations/ab-test-setup,onboarding/business-operations/ab-test-setup-workflow
 access-review-workflow,access-review,Access Review Workflow,workflow,devops,approval,compliance,approval;compliance,4,18,3,access-review;user-access-certification;quarterly-review;manager-approval;compliance;sod-violations;audit,"Quarterly user access review workflow with manager certification, separation of duties validation, remediation tracking, and compliance reporting for audit purposes.",devops/access-review,approval/devops/access-review-workflow
 account-deletion-workflow,account-deletion,Account Deletion Workflow,workflow,business-operations,offboarding,billing,offboarding;billing,3,7,2,account-deletion;user-offboarding;data-cleanup;subscription-cancel;retention-offer;exit-survey,"Account deletion workflow with cancellation reason capture, retention offer, subscription termination, data cleanup, and confirmation email.",business-operations/account-deletion,offboarding/business-operations/account-deletion-workflow
-api-gateway-workflow,api-gateway,Api Gateway Workflow,workflow,patterns,handoff,security;mcp,handoff;security;mcp,3,7,2,api-gateway;microservices;rate-limiting;request-routing;authentication;load-balancing,"API Gateway pattern with request authentication, rate limiting, request routing to backend services, response aggregation, and error handling.",patterns/api-gateway,handoff/patterns/api-gateway-workflow
+api-gateway-workflow,api-gateway,Api Gateway Workflow,workflow,patterns,handoff,security;mcp;architecture;patterns,handoff;security;mcp;architecture;patterns,3,7,2,api-gateway;microservices;rate-limiting;request-routing;authentication;load-balancing,"API Gateway pattern with request authentication, rate limiting, request routing to backend services, response aggregation, and error handling.",patterns/api-gateway,handoff/patterns/api-gateway-workflow
 api-key-rotation-workflow,api-key-rotation,Api Key Rotation Workflow,workflow,business-operations,security,compliance,security;compliance,3,10,3,api-key-rotation;security;credential-management;zero-downtime;secrets-manager;compliance,"API key rotation workflow with new key generation, dual-key transition period, client notification, old key deprecation, and audit logging.",business-operations/api-key-rotation,security/business-operations/api-key-rotation-workflow
-audit-trail-workflow,audit-trail,Audit Trail Workflow,workflow,patterns,compliance,,compliance,4,13,4,audit;trail;patterns;decision;loop,This workflow models logging all important actions for compliance.,patterns/audit-trail,compliance/patterns/audit-trail-workflow
-authentication-flow-workflow,authentication-flow,Authentication Flow Workflow,workflow,patterns,security,,security,3,7,2,authentication;login;jwt;oauth;mfa;session-management,"User authentication workflow with credential validation, MFA challenge, JWT token generation, session creation, and failed attempt tracking.",patterns/authentication-flow,security/patterns/authentication-flow-workflow
-authorization-flow-workflow,authorization-flow,Authorization Flow Workflow,workflow,patterns,approval,security,approval;security,3,10,3,authorization;flow;patterns,This workflow models checking user permissions before actions run.,patterns/authorization-flow,approval/patterns/authorization-flow-workflow
+audit-trail-workflow,audit-trail,Audit Trail Workflow,workflow,patterns,compliance,patterns,compliance;patterns,4,13,4,audit;trail;patterns;decision;loop,This workflow models logging all important actions for compliance.,patterns/audit-trail,compliance/patterns/audit-trail-workflow
+authentication-flow-workflow,authentication-flow,Authentication Flow Workflow,workflow,patterns,security,patterns,security;patterns,3,7,2,authentication;login;jwt;oauth;mfa;session-management,"User authentication workflow with credential validation, MFA challenge, JWT token generation, session creation, and failed attempt tracking.",patterns/authentication-flow,security/patterns/authentication-flow-workflow
+authorization-flow-workflow,authorization-flow,Authorization Flow Workflow,workflow,patterns,approval,security;patterns,approval;security;patterns,3,10,3,authorization;flow;patterns,This workflow models checking user permissions before actions run.,patterns/authorization-flow,approval/patterns/authorization-flow-workflow
 background-check-workflow,background-check,Background Check Workflow,workflow,hr,uncategorized,,,3,7,2,background-check;pre-employment;criminal-history;employment-verification;education-verification;drug-screening,"Pre-employment background check workflow with criminal history search, employment verification, education verification, and drug screening coordination.",hr/background-check,uncategorized/hr/background-check-workflow
 backup-restore-workflow,backup-restore,Backup Restore Workflow,workflow,devops,delivery,,delivery,3,10,3,backup-restore;disaster-recovery;rpo-rto;snapshot;data-protection;recovery-testing,"Backup and restore workflow with scheduled backups, offsite replication, retention policy enforcement, restore testing, and RTO/RPO validation.",devops/backup-restore,delivery/devops/backup-restore-workflow
 bank-reconciliation-workflow,bank-reconciliation,Bank Reconciliation Workflow,workflow,finance,uncategorized,,,4,18,3,bank-reconciliation;gl-matching;variance-analysis;journal-entries;auto-matching;discrepancy-resolution,"Bank reconciliation workflow with automated transaction matching, variance reporting, discrepancy research, and journal entry creation for timing differences and bank errors.",finance/bank-reconciliation,uncategorized/finance/bank-reconciliation-workflow
-batch-processing-workflow,batch-processing,Batch Processing Workflow,workflow,patterns,uncategorized,,,3,7,2,batch-processing;scheduled-jobs;bulk-operations;etl;chunk-processing;job-scheduler,"Batch processing pattern with job scheduling, chunk-based processing, checkpoint/restart capability, error handling, and completion reporting.",patterns/batch-processing,uncategorized/patterns/batch-processing-workflow
-billing-dispute-workflow,billing-dispute,Billing Dispute Workflow,workflow,business-operations,approval,billing,approval;billing,4,13,4,billing-dispute;chargeback;refund-request;dispute-resolution;fraud-review;stripe,"Billing dispute workflow with dispute intake, transaction review, fraud analysis, resolution decision, and chargeback response handling.",business-operations/billing-dispute,approval/business-operations/billing-dispute-workflow
-blue-green-deploy-workflow,blue-green-deploy,Blue Green Deploy Workflow,workflow,patterns,delivery,,delivery,4,13,4,blue-green-deployment;zero-downtime;traffic-switching;rollback;load-balancer;release-management,"Blue-green deployment pattern with parallel environment setup, smoke testing, load balancer traffic switch, and instant rollback capability.",patterns/blue-green-deploy,delivery/patterns/blue-green-deploy-workflow
+batch-processing-workflow,batch-processing,Batch Processing Workflow,workflow,patterns,patterns,,patterns,3,7,2,batch-processing;scheduled-jobs;bulk-operations;etl;chunk-processing;job-scheduler,"Batch processing pattern with job scheduling, chunk-based processing, checkpoint/restart capability, error handling, and completion reporting.",patterns/batch-processing,patterns/patterns/batch-processing-workflow
+bidirectional-loop-workflow,bidirectional-loop,Bidirectional Loop Workflow,workflow,edge-cases,edge-cases,,edge-cases,5,16,4,bidirectional;loop;decision,This workflow models circular references between nodes in both directions.,edge-cases/bidirectional-loop,edge-cases/edge-cases/bidirectional-loop-workflow
+billing-dispute-workflow,billing-dispute,Billing Dispute Workflow,workflow,business-operations,approval,billing;commerce-automation,approval;billing;commerce-automation,4,13,4,billing-dispute;chargeback;refund-request;dispute-resolution;fraud-review;stripe,"Billing dispute workflow with dispute intake, transaction review, fraud analysis, resolution decision, and chargeback response handling.",business-operations/billing-dispute,approval/business-operations/billing-dispute-workflow
+blue-green-deploy-workflow,blue-green-deploy,Blue Green Deploy Workflow,workflow,patterns,delivery,patterns,delivery;patterns,4,13,4,blue-green-deployment;zero-downtime;traffic-switching;rollback;load-balancer;release-management,"Blue-green deployment pattern with parallel environment setup, smoke testing, load balancer traffic switch, and instant rollback capability.",patterns/blue-green-deploy,delivery/patterns/blue-green-deploy-workflow
 bonus-allocation-workflow,bonus-allocation,Bonus Allocation Workflow,workflow,hr,uncategorized,,,3,7,2,bonus-allocation;annual-bonus;performance-bonus;budget-pool;calibration;payout,"Annual bonus allocation workflow with budget pool distribution, performance-based calculation, manager calibration, executive approval, and payroll processing.",hr/bonus-allocation,uncategorized/hr/bonus-allocation-workflow
 budget-approval-workflow,budget-approval,Budget Approval Workflow,workflow,finance,approval,,approval,4,19,3,budget-approval;financial-planning;tiered-approval;cfo-approval;ceo-approval;board-approval;fund-allocation,"Corporate budget approval workflow with tiered approval routing based on amount thresholds (CFO < $100K, CEO $100K-$1M, Board > $1M), prior year comparison, and fund allocation.",finance/budget-approval,approval/finance/budget-approval-workflow
-cache-aside-workflow,cache-aside,Cache Aside Workflow,workflow,patterns,uncategorized,,,3,10,3,cache-aside;lazy-loading;cache-miss;cache-invalidation;redis;performance,"Cache-aside pattern with cache lookup, database fallback on miss, cache population, TTL-based expiration, and write-through invalidation.",patterns/cache-aside,uncategorized/patterns/cache-aside-workflow
-callback-pattern-workflow,callback-pattern,Callback Pattern Workflow,workflow,patterns,uncategorized,,,3,10,3,callback;pattern;patterns;decision;loop,This workflow models an async operation that notifies a callback when done.,patterns/callback-pattern,uncategorized/patterns/callback-pattern-workflow
-canary-deploy-workflow,canary-deploy,Canary Deploy Workflow,workflow,patterns,incident,delivery,incident;delivery,3,7,2,canary-deployment;progressive-rollout;traffic-splitting;metrics-monitoring;gradual-release;feature-flags,"Canary deployment pattern with gradual traffic shifting, real-time metrics monitoring, automatic rollback triggers, and progressive rollout to full production.",patterns/canary-deploy,incident/patterns/canary-deploy-workflow
+cache-aside-workflow,cache-aside,Cache Aside Workflow,workflow,patterns,patterns,,patterns,3,10,3,cache-aside;lazy-loading;cache-miss;cache-invalidation;redis;performance,"Cache-aside pattern with cache lookup, database fallback on miss, cache population, TTL-based expiration, and write-through invalidation.",patterns/cache-aside,patterns/patterns/cache-aside-workflow
+callback-pattern-workflow,callback-pattern,Callback Pattern Workflow,workflow,patterns,patterns,,patterns,3,10,3,callback;pattern;patterns;decision;loop,This workflow models an async operation that notifies a callback when done.,patterns/callback-pattern,patterns/patterns/callback-pattern-workflow
+canary-deploy-workflow,canary-deploy,Canary Deploy Workflow,workflow,patterns,incident,delivery;patterns,incident;delivery;patterns,3,7,2,canary-deployment;progressive-rollout;traffic-splitting;metrics-monitoring;gradual-release;feature-flags,"Canary deployment pattern with gradual traffic shifting, real-time metrics monitoring, automatic rollback triggers, and progressive rollout to full production.",patterns/canary-deploy,incident/patterns/canary-deploy-workflow
 candidate-rejection-workflow,candidate-rejection,Candidate Rejection Workflow,workflow,hr,uncategorized,,,3,10,3,candidate-rejection;hiring-decision;rejection-letter;talent-pool;candidate-experience;ats-update,"Candidate rejection workflow with stage-appropriate messaging, personalized rejection letters, talent pool consideration, ATS status update, and candidate experience feedback.",hr/candidate-rejection,uncategorized/hr/candidate-rejection-workflow
 carrier-selection-workflow,carrier-selection,Carrier Selection Workflow,workflow,logistics,uncategorized,,,3,10,3,carrier-selection;rate-shopping;transit-time;service-level;tms;freight-optimization,"Carrier selection workflow with rate shopping, transit time comparison, service level matching, carrier performance scoring, and optimal carrier assignment.",logistics/carrier-selection,uncategorized/logistics/carrier-selection-workflow
 cash-flow-forecast-workflow,cash-flow-forecast,Cash Flow Forecast Workflow,workflow,finance,uncategorized,,,3,7,2,cash-flow-forecast;liquidity-planning;working-capital;ar-collections;ap-disbursements;treasury,"Cash flow forecasting workflow with AR/AP projections, working capital analysis, liquidity gap identification, and short-term financing recommendations.",finance/cash-flow-forecast,uncategorized/finance/cash-flow-forecast-workflow
 certificate-renewal-workflow,certificate-renewal,Certificate Renewal Workflow,workflow,devops,security,,security,4,19,3,ssl-certificate;tls-renewal;lets-encrypt;certificate-authority;domain-validation;load-balancer;health-check,"SSL/TLS certificate renewal workflow with expiration monitoring, certificate request by type (DV/OV/EV), domain validation, deployment to load balancers, and health check verification with rollback.",devops/certificate-renewal,security/devops/certificate-renewal-workflow
 chaos-engineering-workflow,chaos-engineering,Chaos Engineering Workflow,workflow,devops,uncategorized,,,4,13,4,chaos-engineering;fault-injection;resilience-testing;game-day;blast-radius;steady-state,"Chaos engineering workflow with hypothesis definition, steady-state monitoring, controlled fault injection, blast radius limitation, and resilience validation.",devops/chaos-engineering,uncategorized/devops/chaos-engineering-workflow
 ci-cd-pipeline-workflow,ci-cd-pipeline,Ci Cd Pipeline Workflow,workflow,devops,delivery,,delivery,4,22,3,ci-cd;continuous-integration;continuous-deployment;github-actions;artifact-registry;staging;production;rollback,"Full CI/CD pipeline with code checkout, linting, unit tests, artifact building, staging deployment, smoke tests, production deployment, and automatic rollback on failure.",devops/ci-cd-pipeline,delivery/devops/ci-cd-pipeline-workflow
-circuit-breaker-workflow,circuit-breaker,Circuit Breaker Workflow,workflow,patterns,mcp,,mcp,4,19,3,circuit-breaker;resilience;fault-tolerance;microservices;hystrix;half-open;fallback,"Circuit breaker resilience pattern with closed, open, and half-open states for protecting services from cascading failures with automatic recovery testing.",patterns/circuit-breaker,mcp/patterns/circuit-breaker-workflow
-claim-check-workflow,claim-check,Claim Check Workflow,workflow,patterns,uncategorized,,,2,7,2,claim;check;patterns,This workflow models keeping large payloads external and only passing references.,patterns/claim-check,uncategorized/patterns/claim-check-workflow
+circuit-breaker-workflow,circuit-breaker,Circuit Breaker Workflow,workflow,patterns,mcp,architecture;patterns,mcp;architecture;patterns,4,19,3,circuit-breaker;resilience;fault-tolerance;microservices;hystrix;half-open;fallback,"Circuit breaker resilience pattern with closed, open, and half-open states for protecting services from cascading failures with automatic recovery testing.",patterns/circuit-breaker,mcp/patterns/circuit-breaker-workflow
+claim-check-workflow,claim-check,Claim Check Workflow,workflow,patterns,patterns,,patterns,2,7,2,claim;check;patterns,This workflow models keeping large payloads external and only passing references.,patterns/claim-check,patterns/patterns/claim-check-workflow
 cohort-analysis-workflow,cohort-analysis,Cohort Analysis Workflow,workflow,business-operations,uncategorized,,,4,13,4,cohort-analysis;retention-analysis;user-behavior;ltv;churn-prediction;analytics,"Cohort analysis workflow with user segmentation by signup date, retention curve calculation, LTV projection, and behavioral pattern identification.",business-operations/cohort-analysis,uncategorized/business-operations/cohort-analysis-workflow
 cold-chain-monitoring-workflow,cold-chain-monitoring,Cold Chain Monitoring Workflow,workflow,logistics,incident,,incident,3,7,2,cold-chain;temperature-monitoring;iot-sensors;excursion-alert;pharmaceutical;perishables,"Cold chain monitoring workflow with IoT temperature sensors, real-time alerts, excursion documentation, corrective action triggers, and compliance reporting.",logistics/cold-chain-monitoring,incident/logistics/cold-chain-monitoring-workflow
+comment-like-labels-workflow,comment-like-labels,Comment Like Labels Workflow,workflow,edge-cases,edge-cases,,edge-cases,1,5,1,comment;like;labels,This workflow models labels that look like code comments.,edge-cases/comment-like-labels,edge-cases/edge-cases/comment-like-labels-workflow
 community-moderation-workflow,community-moderation,Community Moderation Workflow,workflow,business-operations,uncategorized,,,3,7,2,community-moderation;content-moderation;user-reports;trust-safety;ai-moderation;appeals,"Community content moderation workflow with AI auto-flagging, user reports, human review queue, action enforcement, and appeals handling.",business-operations/community-moderation,uncategorized/business-operations/community-moderation-workflow
-compensation-transaction-workflow,compensation-transaction,Compensation Transaction Workflow,workflow,patterns,uncategorized,,,2,7,2,compensation;transaction;patterns;decision;loop,This workflow models rolling back work when a later step fails.,patterns/compensation-transaction,uncategorized/patterns/compensation-transaction-workflow
+compensation-transaction-workflow,compensation-transaction,Compensation Transaction Workflow,workflow,patterns,patterns,,patterns,2,7,2,compensation;transaction;patterns;decision;loop,This workflow models rolling back work when a later step fails.,patterns/compensation-transaction,patterns/patterns/compensation-transaction-workflow
 conflict-resolution-workflow,conflict-resolution,Conflict Resolution Workflow,workflow,hr,billing,,billing,4,10,3,conflict-resolution;workplace-dispute;mediation;hr-investigation;employee-relations;grievance,"Workplace conflict resolution workflow with complaint intake, HR investigation, mediation sessions, resolution documentation, and follow-up monitoring.",hr/conflict-resolution,billing/hr/conflict-resolution-workflow
 consent-management-workflow,consent-management,Consent Management Workflow,workflow,business-operations,compliance,,compliance,3,7,2,consent-management;gdpr;cookie-consent;privacy-preferences;opt-in-opt-out;compliance,"User consent management workflow with cookie banner, preference center, consent recording, downstream system sync, and audit trail.",business-operations/consent-management,compliance/business-operations/consent-management-workflow
 container-loading-workflow,container-loading,Container Loading Workflow,workflow,logistics,uncategorized,,,3,7,2,container-loading;load-planning;weight-distribution;cube-utilization;seal-verification;ocean-freight,"Container loading workflow with load plan optimization, weight distribution, cube utilization maximization, seal application, and bill of lading generation.",logistics/container-loading,uncategorized/logistics/container-loading-workflow
-content-enricher-workflow,content-enricher,Content Enricher Workflow,workflow,patterns,uncategorized,,,3,10,3,content;enricher;patterns;decision,This workflow models adding extra data from other sources.,patterns/content-enricher,uncategorized/patterns/content-enricher-workflow
+content-enricher-workflow,content-enricher,Content Enricher Workflow,workflow,patterns,patterns,,patterns,3,10,3,content;enricher;patterns;decision,This workflow models adding extra data from other sources.,patterns/content-enricher,patterns/patterns/content-enricher-workflow
 cost-center-workflow,cost-center,Cost Center Workflow,workflow,finance,uncategorized,,,2,7,2,cost;center;finance;decision,This workflow models managing cost center budgets.,finance/cost-center,uncategorized/finance/cost-center-workflow
-cqrs-workflow,cqrs,Cqrs Workflow,workflow,patterns,uncategorized,,,4,19,4,cqrs;command-query-separation;event-sourcing;read-model;write-model;domain-events;eventual-consistency,"CQRS (Command Query Responsibility Segregation) pattern with separate command and query paths, domain event publishing, read model synchronization, and DTO transformation.",patterns/cqrs,uncategorized/patterns/cqrs-workflow
+cqrs-workflow,cqrs,Cqrs Workflow,workflow,patterns,patterns,,patterns,4,19,4,cqrs;command-query-separation;event-sourcing;read-model;write-model;domain-events;eventual-consistency,"CQRS (Command Query Responsibility Segregation) pattern with separate command and query paths, domain event publishing, read model synchronization, and DTO transformation.",patterns/cqrs,patterns/patterns/cqrs-workflow
 credit-control-workflow,credit-control,Credit Control Workflow,workflow,finance,uncategorized,,,3,10,3,credit-control;credit-limit;customer-credit;credit-scoring;collections;accounts-receivable,"Customer credit control workflow with credit limit assessment, credit scoring, order hold management, collections escalation, and payment plan negotiation.",finance/credit-control,uncategorized/finance/credit-control-workflow
 cross-docking-workflow,cross-docking,Cross Docking Workflow,workflow,logistics,uncategorized,,,3,10,3,cross-docking;flow-through;dock-scheduling;sortation;consolidation;just-in-time,"Cross-docking workflow with inbound scheduling, sortation by destination, outbound consolidation, and direct transfer without storage for just-in-time delivery.",logistics/cross-docking,uncategorized/logistics/cross-docking-workflow
-crud-user-browser-server-workflow,crud-user-browser-server,Crud User Browser Server Workflow,workflow,patterns,uncategorized,,,2,7,2,crud;user;browser;server;patterns,"This workflow models user creates, reads, updates, and deletes data through a browser and server.",patterns/crud-user-browser-server,uncategorized/patterns/crud-user-browser-server-workflow
+cross-lane-circular-workflow,cross-lane-circular,Cross Lane Circular Workflow,workflow,edge-cases,edge-cases,,edge-cases,4,13,4,cross;lane;circular,This workflow models arrows that loop across lanes.,edge-cases/cross-lane-circular,edge-cases/edge-cases/cross-lane-circular-workflow
+crud-user-browser-server-workflow,crud-user-browser-server,Crud User Browser Server Workflow,workflow,patterns,patterns,,patterns,2,7,2,crud;user;browser;server;patterns,"This workflow models user creates, reads, updates, and deletes data through a browser and server.",patterns/crud-user-browser-server,patterns/patterns/crud-user-browser-server-workflow
 customs-clearance-workflow,customs-clearance,Customs Clearance Workflow,workflow,logistics,uncategorized,,,4,19,3,customs-clearance;international-trade;customs-broker;hs-codes;import-export;duties-taxes;inspection,"International customs clearance workflow with importer documentation, customs broker HS code classification, duty calculation, customs authority inspection, and clearance certificate issuance.",logistics/customs-clearance,uncategorized/logistics/customs-clearance-workflow
 cycle-counting-workflow,cycle-counting,Cycle Counting Workflow,workflow,logistics,compliance,,compliance,3,10,3,cycle-counting;inventory-accuracy;abc-analysis;variance-investigation;perpetual-inventory;audit,"Inventory cycle counting workflow with ABC classification, count scheduling, variance investigation, adjustment approval, and inventory accuracy tracking.",logistics/cycle-counting,compliance/logistics/cycle-counting-workflow
 damaged-goods-workflow,damaged-goods,Damaged Goods Workflow,workflow,logistics,uncategorized,,,3,7,2,damaged-goods;damage-claim;inventory-write-off;carrier-claim;disposition;loss-prevention,"Damaged goods processing workflow with damage documentation, carrier claim filing, disposition decision (salvage/dispose), inventory adjustment, and loss tracking.",logistics/damaged-goods,uncategorized/logistics/damaged-goods-workflow
 data-export-workflow,data-export,Data Export Workflow,workflow,business-operations,compliance,,compliance,3,10,3,data-export;data-portability;gdpr;bulk-export;async-job;download-link,"User data export workflow with export request, async job processing, data aggregation, secure file generation, and download link delivery.",business-operations/data-export,compliance/business-operations/data-export-workflow
 database-migration-workflow,database-migration,Database Migration Workflow,workflow,devops,approval,delivery,approval;delivery,4,20,4,database-migration;schema-changes;flyway;liquibase;rollback;dba-approval;maintenance-window,"Database schema migration workflow with CI testing, DBA review and approval, maintenance window scheduling, backup snapshots, migration execution, data integrity verification, and automatic rollback.",devops/database-migration,approval/devops/database-migration-workflow
-dead-letter-queue-workflow,dead-letter-queue,Dead Letter Queue Workflow,workflow,patterns,uncategorized,,,3,7,2,dead-letter-queue;dlq;message-retry;poison-message;error-handling;message-queue,"Dead letter queue pattern for handling failed messages with retry exhaustion detection, DLQ routing, manual inspection, and reprocessing capability.",patterns/dead-letter-queue,uncategorized/patterns/dead-letter-queue-workflow
-decision-diamond-workflow,decision-diamond,Decision Diamond Workflow,workflow,patterns,uncategorized,,,3,10,3,decision;diamond;patterns,This workflow models an if or then style branch for approval or rejection.,patterns/decision-diamond,uncategorized/patterns/decision-diamond-workflow
+dead-letter-queue-workflow,dead-letter-queue,Dead Letter Queue Workflow,workflow,patterns,patterns,,patterns,3,7,2,dead-letter-queue;dlq;message-retry;poison-message;error-handling;message-queue,"Dead letter queue pattern for handling failed messages with retry exhaustion detection, DLQ routing, manual inspection, and reprocessing capability.",patterns/dead-letter-queue,patterns/patterns/dead-letter-queue-workflow
+decision-diamond-workflow,decision-diamond,Decision Diamond Workflow,workflow,patterns,patterns,,patterns,3,10,3,decision;diamond;patterns,This workflow models an if or then style branch for approval or rejection.,patterns/decision-diamond,patterns/patterns/decision-diamond-workflow
+deep-nesting-workflow,deep-nesting,Deep Nesting Workflow,workflow,edge-cases,edge-cases,,edge-cases,4,13,4,deep;nesting;parallel,This workflow models lanes that are conceptually nested within each other.,edge-cases/deep-nesting,edge-cases/edge-cases/deep-nesting-workflow
 delivery-confirmation-workflow,delivery-confirmation,Delivery Confirmation Workflow,workflow,logistics,uncategorized,,,2,7,2,delivery-confirmation;pod;signature-capture;order-completion;customer-notification;tracking-update,"Delivery confirmation workflow with proof of delivery capture, signature collection, photo documentation, order status update, and customer notification.",logistics/delivery-confirmation,uncategorized/logistics/delivery-confirmation-workflow
 deployment-rollback-workflow,deployment-rollback,Deployment Rollback Workflow,workflow,devops,incident,delivery,incident;delivery,3,10,3,deployment-rollback;version-revert;incident-response;kubernetes;helm-rollback;service-recovery,"Deployment rollback workflow with issue detection, rollback decision, previous version restoration, health verification, and post-mortem documentation.",devops/deployment-rollback,incident/devops/deployment-rollback-workflow
+disconnected-lanes-workflow,disconnected-lanes,Disconnected Lanes Workflow,workflow,edge-cases,edge-cases,,edge-cases,2,7,2,disconnected;lanes;decision;loop,This workflow models lanes that never connect to each other.,edge-cases/disconnected-lanes,edge-cases/edge-cases/disconnected-lanes-workflow
 diversity-initiative-workflow,diversity-initiative,Diversity Initiative Workflow,workflow,hr,uncategorized,,,3,10,3,diversity;initiative;hr,This workflow models promoting workplace diversity.,hr/diversity-initiative,uncategorized/hr/diversity-initiative-workflow
 dunning-flow-workflow,dunning-flow,Dunning Flow Workflow,workflow,business-operations,billing,,billing,3,10,3,dunning-flow;collections;overdue-payment;payment-reminder;account-suspension;revenue-recovery,"Dunning collection workflow with escalating reminder emails, grace period management, account suspension, and payment recovery tracking.",business-operations/dunning-flow,billing/business-operations/dunning-flow-workflow
+duplicate-node-ids-workflow,duplicate-node-ids,Duplicate Node Ids Workflow,workflow,edge-cases,edge-cases,,edge-cases,3,10,3,duplicate;node;ids,This workflow models the same node IDs reused in different lanes.,edge-cases/duplicate-node-ids,edge-cases/edge-cases/duplicate-node-ids-workflow
 email-campaign-workflow,email-campaign,Email Campaign Workflow,workflow,business-operations,uncategorized,,,4,13,4,email-campaign;marketing-automation;mailchimp;segmentation;a-b-testing;deliverability,"Email marketing campaign workflow with audience segmentation, A/B testing, send scheduling, deliverability monitoring, and engagement analytics.",business-operations/email-campaign,uncategorized/business-operations/email-campaign-workflow
 employee-engagement-workflow,employee-engagement,Employee Engagement Workflow,workflow,hr,uncategorized,,,2,7,2,employee;engagement;hr;parallel,This workflow models measuring and improving engagement.,hr/employee-engagement,uncategorized/hr/employee-engagement-workflow
-enricher-workflow,enricher,Enricher Workflow,workflow,patterns,uncategorized,,,3,10,3,enricher;patterns,This workflow models adding metadata to messages before passing them on.,patterns/enricher,uncategorized/patterns/enricher-workflow
-error-retry-loop-workflow,error-retry-loop,Error Retry Loop Workflow,workflow,patterns,uncategorized,,,2,7,2,error;retry;loop;patterns,This workflow models a failed operation that retries with backoff.,patterns/error-retry-loop,uncategorized/patterns/error-retry-loop-workflow
-escalation-pattern-workflow,escalation-pattern,Escalation Pattern Workflow,workflow,patterns,handoff,,handoff,3,10,3,escalation;pattern;patterns,This workflow models escalating issues to higher authority when needed.,patterns/escalation-pattern,handoff/patterns/escalation-pattern-workflow
-event-driven-workflow,event-driven,Event Driven Workflow,workflow,patterns,uncategorized,,,3,10,3,event;driven;patterns,This workflow models reacting to incoming business events.,patterns/event-driven,uncategorized/patterns/event-driven-workflow
-event-sourcing-workflow,event-sourcing,Event Sourcing Workflow,workflow,patterns,compliance,,compliance,4,10,3,event-sourcing;event-store;aggregate;replay;audit-log;temporal-query,"Event sourcing pattern with event capture, event store persistence, aggregate reconstruction, snapshot optimization, and temporal state queries.",patterns/event-sourcing,compliance/patterns/event-sourcing-workflow
+empty-lane-workflow,empty-lane,Empty Lane Workflow,workflow,edge-cases,edge-cases,,edge-cases,3,10,3,empty;lane,This workflow models a lane with no nodes.,edge-cases/empty-lane,edge-cases/edge-cases/empty-lane-workflow
+enricher-workflow,enricher,Enricher Workflow,workflow,patterns,patterns,,patterns,3,10,3,enricher;patterns,This workflow models adding metadata to messages before passing them on.,patterns/enricher,patterns/patterns/enricher-workflow
+error-retry-loop-workflow,error-retry-loop,Error Retry Loop Workflow,workflow,patterns,patterns,,patterns,2,7,2,error;retry;loop;patterns,This workflow models a failed operation that retries with backoff.,patterns/error-retry-loop,patterns/patterns/error-retry-loop-workflow
+escalation-pattern-workflow,escalation-pattern,Escalation Pattern Workflow,workflow,patterns,handoff,patterns,handoff;patterns,3,10,3,escalation;pattern;patterns,This workflow models escalating issues to higher authority when needed.,patterns/escalation-pattern,handoff/patterns/escalation-pattern-workflow
+event-driven-workflow,event-driven,Event Driven Workflow,workflow,patterns,architecture,patterns,architecture;patterns,3,10,3,event;driven;patterns,This workflow models reacting to incoming business events.,patterns/event-driven,architecture/patterns/event-driven-workflow
+event-sourcing-workflow,event-sourcing,Event Sourcing Workflow,workflow,patterns,compliance,patterns,compliance;patterns,4,10,3,event-sourcing;event-store;aggregate;replay;audit-log;temporal-query,"Event sourcing pattern with event capture, event store persistence, aggregate reconstruction, snapshot optimization, and temporal state queries.",patterns/event-sourcing,compliance/patterns/event-sourcing-workflow
 expense-allocation-workflow,expense-allocation,Expense Allocation Workflow,workflow,finance,uncategorized,,,3,10,3,expense;allocation;finance,This workflow models allocating costs to departments.,finance/expense-allocation,uncategorized/finance/expense-allocation-workflow
 expense-approval-workflow,expense-approval,Expense Approval Workflow,workflow,hr,approval,compliance,approval;compliance,3,10,3,expense-approval;travel-expenses;receipt-validation;policy-compliance;tiered-approval;reimbursement,"Employee expense approval workflow with receipt validation, policy compliance check, tiered approval based on amount, and reimbursement processing.",hr/expense-approval,approval/hr/expense-approval-workflow
 expense-claim-workflow,expense-claim,Expense Claim Workflow,workflow,finance,approval,,approval,3,10,3,expense-reimbursement;employee-expenses;receipt-upload;manager-approval;finance-review;direct-deposit,"Employee expense reimbursement workflow with receipt submission, manager approval, finance review, policy compliance check, and direct deposit payment.",finance/expense-claim,approval/finance/expense-claim-workflow
-fan-out-fan-in-workflow,fan-out-fan-in,Fan Out Fan In Workflow,workflow,patterns,ai-orchestration,,ai-orchestration,4,13,4,fan-out-fan-in;scatter-gather;parallel-processing;aggregation;map-reduce;concurrency,"Fan-out/fan-in pattern with work distribution to parallel workers, concurrent execution, result aggregation, and error handling for partial failures.",patterns/fan-out-fan-in,ai-orchestration/patterns/fan-out-fan-in-workflow
-feature-toggle-workflow,feature-toggle,Feature Toggle Workflow,workflow,patterns,uncategorized,,,3,10,3,feature-toggle;feature-flags;dark-launch;a-b-testing;gradual-rollout;kill-switch,"Feature toggle pattern with flag configuration, user targeting rules, percentage rollouts, and instant kill-switch capability for production features.",patterns/feature-toggle,uncategorized/patterns/feature-toggle-workflow
-filter-workflow,filter,Filter Workflow,workflow,patterns,uncategorized,,,4,13,4,filter;patterns;decision;loop,This workflow models removing items that do not meet criteria.,patterns/filter,uncategorized/patterns/filter-workflow
+extra-whitespace-workflow,extra-whitespace,Extra Whitespace Workflow,workflow,edge-cases,edge-cases,,edge-cases,5,16,4,extra;whitespace,This workflow models labels that include leading and trailing spaces.,edge-cases/extra-whitespace,edge-cases/edge-cases/extra-whitespace-workflow
+fan-out-fan-in-workflow,fan-out-fan-in,Fan Out Fan In Workflow,workflow,patterns,ai-orchestration,patterns,ai-orchestration;patterns,4,13,4,fan-out-fan-in;scatter-gather;parallel-processing;aggregation;map-reduce;concurrency,"Fan-out/fan-in pattern with work distribution to parallel workers, concurrent execution, result aggregation, and error handling for partial failures.",patterns/fan-out-fan-in,ai-orchestration/patterns/fan-out-fan-in-workflow
+feature-toggle-workflow,feature-toggle,Feature Toggle Workflow,workflow,patterns,patterns,,patterns,3,10,3,feature-toggle;feature-flags;dark-launch;a-b-testing;gradual-rollout;kill-switch,"Feature toggle pattern with flag configuration, user targeting rules, percentage rollouts, and instant kill-switch capability for production features.",patterns/feature-toggle,patterns/patterns/feature-toggle-workflow
+filter-workflow,filter,Filter Workflow,workflow,patterns,patterns,,patterns,4,13,4,filter;patterns;decision;loop,This workflow models removing items that do not meet criteria.,patterns/filter,patterns/patterns/filter-workflow
 financial-reporting-workflow,financial-reporting,Financial Reporting Workflow,workflow,finance,compliance,,compliance,4,10,3,financial-reporting;gaap-compliance;income-statement;balance-sheet;cash-flow-statement;sec-filing,"Financial reporting workflow with GAAP-compliant statement preparation, management review, audit committee approval, and SEC filing for public companies.",finance/financial-reporting,compliance/finance/financial-reporting-workflow
 fixed-assets-workflow,fixed-assets,Fixed Assets Workflow,workflow,finance,uncategorized,,,3,7,2,fixed-assets;asset-tracking;depreciation;capitalization;asset-disposal;physical-inventory,"Fixed asset management workflow with asset capitalization, depreciation scheduling, physical inventory verification, and asset disposal/retirement processing.",finance/fixed-assets,uncategorized/finance/fixed-assets-workflow
 fleet-maintenance-workflow,fleet-maintenance,Fleet Maintenance Workflow,workflow,logistics,compliance,,compliance,3,7,2,fleet-maintenance;preventive-maintenance;vehicle-inspection;work-order;dot-compliance;telematics,"Fleet maintenance workflow with preventive maintenance scheduling, vehicle inspection, work order creation, parts ordering, and DOT compliance tracking.",logistics/fleet-maintenance,compliance/logistics/fleet-maintenance-workflow
-gdpr-deletion-workflow,gdpr-deletion,Gdpr Deletion Workflow,workflow,business-operations,compliance,,compliance,4,13,4,gdpr-deletion;right-to-be-forgotten;data-privacy;pii-removal;compliance;dsar,"GDPR data deletion workflow with identity verification, data inventory scan, PII removal across systems, backup purging, and deletion confirmation.",business-operations/gdpr-deletion,compliance/business-operations/gdpr-deletion-workflow
+gdpr-deletion-workflow,gdpr-deletion,Gdpr Deletion Workflow,workflow,business-operations,compliance,process-mapping,compliance;process-mapping,4,13,4,gdpr-deletion;right-to-be-forgotten;data-privacy;pii-removal;compliance;dsar,"GDPR data deletion workflow with identity verification, data inventory scan, PII removal across systems, backup purging, and deletion confirmation.",business-operations/gdpr-deletion,compliance/business-operations/gdpr-deletion-workflow
 hazmat-handling-workflow,hazmat-handling,Hazmat Handling Workflow,workflow,logistics,incident,compliance,incident;compliance,4,10,3,hazmat-handling;dangerous-goods;un-classification;sds-documentation;dot-compliance;emergency-response,"Hazardous materials handling workflow with UN classification, SDS documentation, proper labeling, certified handler assignment, and emergency response procedures.",logistics/hazmat-handling,incident/logistics/hazmat-handling-workflow
-idempotent-consumer-workflow,idempotent-consumer,Idempotent Consumer Workflow,workflow,patterns,uncategorized,,,3,10,3,idempotent;consumer;patterns,This workflow models processing each message safely only once.,patterns/idempotent-consumer,uncategorized/patterns/idempotent-consumer-workflow
+idempotent-consumer-workflow,idempotent-consumer,Idempotent Consumer Workflow,workflow,patterns,patterns,,patterns,3,10,3,idempotent;consumer;patterns,This workflow models processing each message safely only once.,patterns/idempotent-consumer,patterns/patterns/idempotent-consumer-workflow
 in-app-message-workflow,in-app-message,In App Message Workflow,workflow,business-operations,uncategorized,,,2,7,2,in-app-message;product-tours;tooltips;announcements;user-engagement;intercom,"In-app messaging workflow with trigger conditions, audience targeting, message display, user interaction tracking, and conversion measurement.",business-operations/in-app-message,uncategorized/business-operations/in-app-message-workflow
 incident-response-workflow,incident-response,Incident Response Workflow,workflow,devops,incident,,incident,5,23,4,incident-management;on-call;pagerduty;war-room;severity-levels;postmortem;sre,"Production incident response workflow with severity-based routing, war room coordination, incident commander assignment, customer communication, root cause analysis, and postmortem scheduling.",devops/incident-response,incident/devops/incident-response-workflow
 infrastructure-provisioning-workflow,infrastructure-provisioning,Infrastructure Provisioning Workflow,workflow,devops,delivery,,delivery,4,10,3,infrastructure-provisioning;terraform;iac;cloud-resources;gitops;state-management,"Infrastructure as Code provisioning workflow with Terraform plan, approval gates, state management, resource creation, and drift detection.",devops/infrastructure-provisioning,delivery/devops/infrastructure-provisioning-workflow
@@ -80,24 +108,32 @@ interview-process-workflow,interview-process,Interview Process Workflow,workflow
 inventory-receipt-workflow,inventory-receipt,Inventory Receipt Workflow,workflow,logistics,uncategorized,,,3,7,2,inventory-receipt;goods-receiving;po-matching;asn-verification;dock-scheduling;wms,"Inventory receiving workflow with ASN verification, PO matching, quantity count, damage inspection, and WMS inventory update.",logistics/inventory-receipt,uncategorized/logistics/inventory-receipt-workflow
 invoice-processing-workflow,invoice-processing,Invoice Processing Workflow,workflow,finance,approval,billing,approval;billing,4,19,4,accounts-payable;invoice-automation;ocr;po-matching;approval-workflow;payment-processing;three-way-match,"Accounts payable invoice automation with OCR data extraction, three-way PO matching, tiered approval workflow, and automated payment processing with GL updates.",finance/invoice-processing,approval/finance/invoice-processing-workflow
 job-posting-workflow,job-posting,Job Posting Workflow,workflow,hr,uncategorized,,,4,19,3,job-posting;job-requisition;ats;linkedin;indeed;ai-screening;talent-acquisition,"Job posting workflow with requisition approval, job description drafting, multi-channel posting (LinkedIn, Indeed, career sites), AI resume screening, and ATS candidate tracking.",hr/job-posting,uncategorized/hr/job-posting-workflow
+json-in-label-workflow,json-in-label,Json In Label Workflow,workflow,edge-cases,edge-cases,,edge-cases,4,13,4,json;in;label,This workflow models a label that contains JSON text.,edge-cases/json-in-label,edge-cases/edge-cases/json-in-label-workflow
 kitting-process-workflow,kitting-process,Kitting Process Workflow,workflow,logistics,uncategorized,,,2,7,2,kitting-process;kit-assembly;bom;component-picking;value-added-services;bundling,"Kit assembly workflow with BOM explosion, component picking, assembly verification, kit labeling, and inventory conversion from components to finished kit.",logistics/kitting-process,uncategorized/logistics/kitting-process-workflow
 knowledge-base-workflow,knowledge-base,Knowledge Base Workflow,workflow,business-operations,support,,support,3,13,4,knowledge-base;help-center;documentation;self-service;article-management;zendesk,"Knowledge base management workflow with article creation, review approval, SEO optimization, version control, and search analytics tracking.",business-operations/knowledge-base,support/business-operations/knowledge-base-workflow
+label-escaping-workflow,label-escaping,Label Escaping Workflow,workflow,edge-cases,edge-cases,,edge-cases,5,16,4,label;escaping,This workflow models labels containing quotes and special characters.,edge-cases/label-escaping,edge-cases/edge-cases/label-escaping-workflow
 last-mile-delivery-workflow,last-mile-delivery,Last Mile Delivery Workflow,workflow,logistics,uncategorized,,,3,7,2,last-mile-delivery;route-optimization;proof-of-delivery;delivery-exception;customer-notification;gps-tracking,"Last mile delivery workflow with route optimization, real-time GPS tracking, delivery attempt handling, proof of delivery capture, and customer notification.",logistics/last-mile-delivery,uncategorized/logistics/last-mile-delivery-workflow
 load-testing-workflow,load-testing,Load Testing Workflow,workflow,devops,delivery,,delivery,4,13,4,load-testing;performance-testing;stress-testing;k6;jmeter;capacity-planning,"Load testing workflow with test scenario design, gradual ramp-up, performance metrics collection, bottleneck identification, and capacity recommendations.",devops/load-testing,delivery/devops/load-testing-workflow
-materialized-view-workflow,materialized-view,Materialized View Workflow,workflow,patterns,uncategorized,,,4,13,4,materialized;view;patterns;decision;loop,This workflow models serving queries from a precomputed view.,patterns/materialized-view,uncategorized/patterns/materialized-view-workflow
-message-queue-workflow,message-queue,Message Queue Workflow,workflow,patterns,uncategorized,,,3,10,3,message;queue;patterns;decision,This workflow models asynchronous processing of work via a queue.,patterns/message-queue,uncategorized/patterns/message-queue-workflow
+markdown-in-label-workflow,markdown-in-label,Markdown In Label Workflow,workflow,edge-cases,edge-cases,,edge-cases,1,5,1,markdown;in;label,This workflow models a label that contains markdown formatting.,edge-cases/markdown-in-label,edge-cases/edge-cases/markdown-in-label-workflow
+materialized-view-workflow,materialized-view,Materialized View Workflow,workflow,patterns,patterns,,patterns,4,13,4,materialized;view;patterns;decision;loop,This workflow models serving queries from a precomputed view.,patterns/materialized-view,patterns/patterns/materialized-view-workflow
+max-lanes-workflow,max-lanes,Max Lanes Workflow,workflow,edge-cases,edge-cases,,edge-cases,3,10,10,max;lanes,This workflow models 10 lanes with simple cross-lane arrows.,edge-cases/max-lanes,edge-cases/edge-cases/max-lanes-workflow
+max-nodes-workflow,max-nodes,Max Nodes Workflow,workflow,edge-cases,edge-cases,,edge-cases,2,50,2,max;nodes,This workflow models 50 nodes in a single lane as a parser stress test.,edge-cases/max-nodes,edge-cases/edge-cases/max-nodes-workflow
+message-queue-workflow,message-queue,Message Queue Workflow,workflow,patterns,patterns,,patterns,3,10,3,message;queue;patterns;decision,This workflow models asynchronous processing of work via a queue.,patterns/message-queue,patterns/patterns/message-queue-workflow
+minimal-workflow,minimal,Minimal Workflow,workflow,edge-cases,edge-cases,,edge-cases,2,1,2,minimal;workflow,This workflow models a workflow with a single node only.,edge-cases/minimal-workflow,edge-cases/edge-cases/minimal-workflow
+missing-labels-workflow,missing-labels,Missing Labels Workflow,workflow,edge-cases,edge-cases,,edge-cases,4,13,4,missing;labels;decision,This workflow models nodes without label parameters.,edge-cases/missing-labels,edge-cases/edge-cases/missing-labels-workflow
 monitoring-alert-workflow,monitoring-alert,Monitoring Alert Workflow,workflow,devops,incident,,incident,3,10,3,monitoring-alerting;prometheus;pagerduty;threshold-alerts;anomaly-detection;on-call,"Monitoring and alerting workflow with metric collection, threshold evaluation, alert routing, escalation policies, and incident creation.",devops/monitoring-alert,incident/devops/monitoring-alert-workflow
 monthly-close-workflow,monthly-close,Monthly Close Workflow,workflow,finance,uncategorized,,,4,22,4,monthly-close;financial-reporting;accounting;reconciliation;trial-balance;period-close,"Corporate month-end financial close process including transaction posting, bank reconciliation, accruals, depreciation, trial balance validation, and financial statement generation.",finance/monthly-close,uncategorized/finance/monthly-close-workflow
-nested-decisions-workflow,nested-decisions,Nested Decisions Workflow,workflow,patterns,uncategorized,,,3,10,3,nested;decisions;patterns;decision;loop,This workflow models multiple layers of decisions before completion.,patterns/nested-decisions,uncategorized/patterns/nested-decisions-workflow
-normalizer-workflow,normalizer,Normalizer Workflow,workflow,patterns,uncategorized,,,4,13,4,normalizer;patterns,This workflow models converting varied inputs to a standard format.,patterns/normalizer,uncategorized/patterns/normalizer-workflow
-notification-pattern-workflow,notification-pattern,Notification Pattern Workflow,workflow,patterns,uncategorized,,,2,7,2,notification;pattern;patterns,This workflow models sending alerts via multiple channels.,patterns/notification-pattern,uncategorized/patterns/notification-pattern-workflow
+nested-decisions-workflow,nested-decisions,Nested Decisions Workflow,workflow,patterns,patterns,,patterns,3,10,3,nested;decisions;patterns;decision;loop,This workflow models multiple layers of decisions before completion.,patterns/nested-decisions,patterns/patterns/nested-decisions-workflow
+normalizer-workflow,normalizer,Normalizer Workflow,workflow,patterns,patterns,,patterns,4,13,4,normalizer;patterns,This workflow models converting varied inputs to a standard format.,patterns/normalizer,patterns/patterns/normalizer-workflow
+notification-pattern-workflow,notification-pattern,Notification Pattern Workflow,workflow,patterns,patterns,,patterns,2,7,2,notification;pattern;patterns,This workflow models sending alerts via multiple channels.,patterns/notification-pattern,patterns/patterns/notification-pattern-workflow
 oauth-flow-workflow,oauth-flow,Oauth Flow Workflow,workflow,business-operations,approval,security,approval;security,4,13,4,oauth-flow;oauth2;authorization-code;token-exchange;sso;third-party-auth,"OAuth 2.0 authorization code flow with redirect handling, code exchange, token storage, refresh token rotation, and scope management.",business-operations/oauth-flow,approval/business-operations/oauth-flow-workflow
 offboarding-workflow,offboarding,Offboarding Workflow,workflow,hr,handoff,offboarding,handoff;offboarding,4,10,3,employee-offboarding;exit-interview;access-revocation;asset-return;knowledge-transfer;final-paycheck,"Employee offboarding workflow with exit interview, knowledge transfer, asset collection, access revocation, final pay processing, and benefits continuation.",hr/offboarding,handoff/hr/offboarding-workflow
 on-call-rotation-workflow,on-call-rotation,On Call Rotation Workflow,workflow,devops,handoff,incident;security,handoff;incident;security,3,13,4,on-call-rotation;incident-management;pagerduty;escalation;schedule-management;handoff,"On-call rotation workflow with schedule creation, shift handoffs, override management, escalation policies, and fair rotation distribution.",devops/on-call-rotation,handoff/devops/on-call-rotation-workflow
 onboarding-workflow,onboarding,Onboarding Workflow,workflow,hr,onboarding,delivery,onboarding;delivery,4,20,3,employee-onboarding;new-hire;hr-workflow;background-check;it-provisioning;benefits-enrollment,"Complete employee onboarding workflow covering offer acceptance, HR record creation, benefits enrollment, background check verification, IT account provisioning, equipment setup, and first day orientation.",hr/onboarding,onboarding/hr/onboarding-workflow
+orphan-node-workflow,orphan-node,Orphan Node Workflow,workflow,edge-cases,edge-cases,,edge-cases,1,5,1,orphan;node,This workflow models a node with no connections.,edge-cases/orphan-node,edge-cases/edge-cases/orphan-node-workflow
 packing-process-workflow,packing-process,Packing Process Workflow,workflow,logistics,uncategorized,,,2,7,2,order-packing;box-selection;packing-slip;weight-verification;cartonization;fulfillment,"Order packing workflow with carton selection, item verification, packing slip insertion, weight check, and package sealing for shipment.",logistics/packing-process,uncategorized/logistics/packing-process-workflow
-parallel-execution-workflow,parallel-execution,Parallel Execution Workflow,workflow,patterns,uncategorized,,,4,13,4,parallel;execution;patterns;loop,This workflow models multiple tasks that run at the same time.,patterns/parallel-execution,uncategorized/patterns/parallel-execution-workflow
-payment-failure-workflow,payment-failure,Payment Failure Workflow,workflow,business-operations,billing,,billing,3,7,2,payment-failure;dunning;retry-logic;card-decline;revenue-recovery;stripe,"Failed payment recovery workflow with smart retry scheduling, dunning email sequence, payment method update prompts, and involuntary churn prevention.",business-operations/payment-failure,billing/business-operations/payment-failure-workflow
+parallel-execution-workflow,parallel-execution,Parallel Execution Workflow,workflow,patterns,patterns,,patterns,4,13,4,parallel;execution;patterns;loop,This workflow models multiple tasks that run at the same time.,patterns/parallel-execution,patterns/patterns/parallel-execution-workflow
+payment-failure-workflow,payment-failure,Payment Failure Workflow,workflow,business-operations,billing,commerce-automation;patterns,billing;commerce-automation;patterns,3,7,2,payment-failure;dunning;retry-logic;card-decline;revenue-recovery;stripe,"Failed payment recovery workflow with smart retry scheduling, dunning email sequence, payment method update prompts, and involuntary churn prevention.",business-operations/payment-failure,billing/business-operations/payment-failure-workflow
 payment-run-workflow,payment-run,Payment Run Workflow,workflow,finance,handoff,approval;billing,handoff;approval;billing,4,18,3,payment-run;accounts-payable;ach-payments;check-run;dual-approval;bank-transfer;vendor-payments,"Accounts payable payment run workflow with batch creation, tiered approval (single/dual based on amount), ACH file generation, check printing, and vendor record updates.",finance/payment-run,handoff/finance/payment-run-workflow
 payroll-processing-workflow,payroll-processing,Payroll Processing Workflow,workflow,finance,compliance,,compliance,5,24,4,payroll-processing;salary-calculation;tax-withholding;fica;ach-direct-deposit;benefits-deductions;compliance,"Complete payroll processing workflow with timesheet collection, gross pay calculation, overtime, tax withholding (federal, state, FICA), benefits deductions, compliance validation, and ACH direct deposit.",finance/payroll-processing,compliance/finance/payroll-processing-workflow
 performance-review-workflow,performance-review,Performance Review Workflow,workflow,hr,approval,,approval,4,10,3,performance-review;annual-evaluation;goal-setting;360-feedback;calibration;merit-increase,"Annual performance review workflow with self-assessment, manager evaluation, 360 feedback collection, calibration sessions, and merit increase recommendations.",hr/performance-review,approval/hr/performance-review-workflow
@@ -105,117 +141,122 @@ personalization-engine-workflow,personalization-engine,Personalization Engine Wo
 picking-process-workflow,picking-process,Picking Process Workflow,workflow,logistics,uncategorized,,,3,10,3,order-picking;warehouse-management;pick-list;batch-picking;wave-picking;wms,"Warehouse order picking workflow with pick list generation, zone routing, batch picking optimization, barcode scanning verification, and pick completion confirmation.",logistics/picking-process,uncategorized/logistics/picking-process-workflow
 plan-downgrade-workflow,plan-downgrade,Plan Downgrade Workflow,workflow,business-operations,billing,delivery,billing;delivery,3,13,4,plan-downgrade;retention;feature-restriction;data-migration;churn-prevention;billing,"Subscription plan downgrade workflow with retention offer, feature restriction warning, data migration handling, and end-of-period scheduling.",business-operations/plan-downgrade,billing/business-operations/plan-downgrade-workflow
 plan-upgrade-workflow,plan-upgrade,Plan Upgrade Workflow,workflow,business-operations,billing,,billing,3,10,3,plan-upgrade;upsell;proration;feature-unlock;expansion-revenue;billing,"Subscription plan upgrade workflow with feature comparison, proration calculation, immediate feature unlock, and billing adjustment.",business-operations/plan-upgrade,billing/business-operations/plan-upgrade-workflow
-polling-pattern-workflow,polling-pattern,Polling Pattern Workflow,workflow,patterns,uncategorized,,,4,13,4,polling;pattern;patterns;loop,This workflow models periodically checking status until work is done.,patterns/polling-pattern,uncategorized/patterns/polling-pattern-workflow
-process-manager-workflow,process-manager,Process Manager Workflow,workflow,patterns,uncategorized,,,3,10,3,process;manager;patterns,This workflow models orchestrating multiple services to complete a process.,patterns/process-manager,uncategorized/patterns/process-manager-workflow
+polling-pattern-workflow,polling-pattern,Polling Pattern Workflow,workflow,patterns,patterns,,patterns,4,13,4,polling;pattern;patterns;loop,This workflow models periodically checking status until work is done.,patterns/polling-pattern,patterns/patterns/polling-pattern-workflow
+process-manager-workflow,process-manager,Process Manager Workflow,workflow,patterns,patterns,,patterns,3,10,3,process;manager;patterns,This workflow models orchestrating multiple services to complete a process.,patterns/process-manager,patterns/patterns/process-manager-workflow
 procurement-card-workflow,procurement-card,Procurement Card Workflow,workflow,finance,uncategorized,,,3,10,3,procurement;card;finance,This workflow models managing company credit cards.,finance/procurement-card,uncategorized/finance/procurement-card-workflow
 promotion-process-workflow,promotion-process,Promotion Process Workflow,workflow,hr,uncategorized,,,3,7,2,promotion-process;career-advancement;job-leveling;title-change;compensation-adjustment;succession-planning,"Employee promotion workflow with performance validation, job level assessment, compensation adjustment, title change, and announcement coordination.",hr/promotion-process,uncategorized/hr/promotion-process-workflow
 pto-request-workflow,pto-request,Pto Request Workflow,workflow,hr,approval,,approval,2,7,2,pto-request;time-off;vacation;leave-management;manager-approval;accrual-balance,"PTO request workflow with balance verification, manager approval, calendar blocking, and team coverage check before approval.",hr/pto-request,approval/hr/pto-request-workflow
-pub-sub-workflow,pub-sub,Pub Sub Workflow,workflow,patterns,uncategorized,,,4,13,4,pub;sub;patterns,This workflow models one publisher notifying many subscribers of events.,patterns/pub-sub,uncategorized/patterns/pub-sub-workflow
+pub-sub-workflow,pub-sub,Pub Sub Workflow,workflow,patterns,patterns,,patterns,4,13,4,pub;sub;patterns,This workflow models one publisher notifying many subscribers of events.,patterns/pub-sub,patterns/patterns/pub-sub-workflow
 purchase-order-workflow,purchase-order,Purchase Order Workflow,workflow,finance,approval,ai-orchestration,approval;ai-orchestration,4,22,3,purchase-order;procurement;requisition;vendor-sourcing;competitive-bidding;tiered-approval;budget-validation,"Procurement purchase order workflow with requisition creation, budget validation, vendor sourcing, competitive bidding, and tiered approval routing based on amount thresholds.",finance/purchase-order,approval/finance/purchase-order-workflow
 push-notification-workflow,push-notification,Push Notification Workflow,workflow,business-operations,uncategorized,,,3,10,3,push-notification;mobile-engagement;firebase-fcm;apns;segmentation;deep-linking,"Mobile push notification workflow with audience targeting, platform routing (iOS/Android), delivery tracking, and engagement analytics.",business-operations/push-notification,uncategorized/business-operations/push-notification-workflow
 put-away-process-workflow,put-away-process,Put Away Process Workflow,workflow,logistics,uncategorized,,,2,7,2,put-away;warehouse-storage;location-assignment;slotting;wms;inventory-placement,"Warehouse put-away workflow with location assignment, slotting optimization, forklift routing, barcode confirmation, and WMS location update.",logistics/put-away-process,uncategorized/logistics/put-away-process-workflow
 quality-inspection-workflow,quality-inspection,Quality Inspection Workflow,workflow,logistics,uncategorized,,,3,10,3,quality-inspection;incoming-inspection;aql-sampling;defect-tracking;supplier-quality;hold-release,"Incoming quality inspection workflow with AQL sampling, defect classification, hold/release decision, supplier notification, and quality metrics tracking.",logistics/quality-inspection,uncategorized/logistics/quality-inspection-workflow
-rate-limiter-workflow,rate-limiter,Rate Limiter Workflow,workflow,patterns,uncategorized,,,4,13,4,rate;limiter;patterns,This workflow models preventing too many requests from being processed.,patterns/rate-limiter,uncategorized/patterns/rate-limiter-workflow
+rate-limiter-workflow,rate-limiter,Rate Limiter Workflow,workflow,patterns,patterns,,patterns,4,13,4,rate;limiter;patterns,This workflow models preventing too many requests from being processed.,patterns/rate-limiter,patterns/patterns/rate-limiter-workflow
 reference-check-workflow,reference-check,Reference Check Workflow,workflow,hr,uncategorized,,,3,10,3,reference-check;employment-verification;professional-references;hiring-decision;candidate-vetting;feedback-collection,"Professional reference check workflow with reference collection, outreach scheduling, structured interview questions, feedback documentation, and hiring recommendation.",hr/reference-check,uncategorized/hr/reference-check-workflow
 referral-program-workflow,referral-program,Referral Program Workflow,workflow,business-operations,uncategorized,,,3,13,4,referral-program;viral-growth;referral-tracking;reward-fulfillment;affiliate;word-of-mouth,"Customer referral program workflow with unique link generation, referral tracking, conversion validation, and dual-sided reward fulfillment.",business-operations/referral-program,uncategorized/business-operations/referral-program-workflow
 relocation-assistance-workflow,relocation-assistance,Relocation Assistance Workflow,workflow,hr,uncategorized,,,3,10,3,relocation;assistance;hr;decision,This workflow models helping employees relocate.,hr/relocation-assistance,uncategorized/hr/relocation-assistance-workflow
 reorder-process-workflow,reorder-process,Reorder Process Workflow,workflow,logistics,uncategorized,,,3,7,2,reorder-process;reorder-point;safety-stock;eoq;demand-planning;auto-replenishment,"Inventory reorder workflow with reorder point monitoring, economic order quantity calculation, safety stock consideration, and automatic purchase requisition generation.",logistics/reorder-process,uncategorized/logistics/reorder-process-workflow
-request-reply-workflow,request-reply,Request Reply Workflow,workflow,patterns,uncategorized,,,2,7,2,request;reply;patterns,This workflow models a synchronous request that waits for a reply.,patterns/request-reply,uncategorized/patterns/request-reply-workflow
-retry-with-backoff-workflow,retry-with-backoff,Retry With Backoff Workflow,workflow,patterns,uncategorized,,,4,20,3,retry-pattern;exponential-backoff;fault-tolerance;api-resilience;transient-errors;http-retry;jitter,"Exponential backoff retry pattern for API calls with configurable retry limits, delay calculation, retryable error detection, and graceful degradation on permanent failures.",patterns/retry-with-backoff,uncategorized/patterns/retry-with-backoff-workflow
+request-reply-workflow,request-reply,Request Reply Workflow,workflow,patterns,patterns,,patterns,2,7,2,request;reply;patterns,This workflow models a synchronous request that waits for a reply.,patterns/request-reply,patterns/patterns/request-reply-workflow
+retry-with-backoff-workflow,retry-with-backoff,Retry With Backoff Workflow,workflow,patterns,patterns,,patterns,4,20,3,retry-pattern;exponential-backoff;fault-tolerance;api-resilience;transient-errors;http-retry;jitter,"Exponential backoff retry pattern for API calls with configurable retry limits, delay calculation, retryable error detection, and graceful degradation on permanent failures.",patterns/retry-with-backoff,patterns/patterns/retry-with-backoff-workflow
 returns-processing-workflow,returns-processing,Returns Processing Workflow,workflow,logistics,billing,,billing,3,7,2,returns-processing;rma;refund;restocking;quality-inspection;reverse-logistics,"Customer returns processing workflow with RMA generation, return receipt, quality inspection, disposition decision, and refund or exchange processing.",logistics/returns-processing,billing/logistics/returns-processing-workflow
 reverse-logistics-workflow,reverse-logistics,Reverse Logistics Workflow,workflow,logistics,uncategorized,,,4,10,3,reverse-logistics;product-returns;refurbishment;recycling;disposition;sustainability,"Reverse logistics workflow with return authorization, product grading, refurbishment decision, recycling coordination, and secondary market disposition.",logistics/reverse-logistics,uncategorized/logistics/reverse-logistics-workflow
 review-collection-workflow,review-collection,Review Collection Workflow,workflow,business-operations,approval,,approval,2,7,2,review-collection;customer-feedback;nps;ratings;social-proof;testimonials,"Customer review collection workflow with post-purchase trigger, review request email, rating submission, moderation, and public display.",business-operations/review-collection,approval/business-operations/review-collection-workflow
-router-workflow,router,Router Workflow,workflow,patterns,uncategorized,,,3,10,3,router;patterns;decision,This workflow models routing messages based on their content.,patterns/router,uncategorized/patterns/router-workflow
-routing-slip-workflow,routing-slip,Routing Slip Workflow,workflow,patterns,handoff,,handoff,4,13,4,routing;slip;patterns,This workflow models having messages carry their own routing instructions.,patterns/routing-slip,handoff/patterns/routing-slip-workflow
-saga-pattern-workflow,saga-pattern,Saga Pattern Workflow,workflow,patterns,delivery,ai-orchestration,delivery;ai-orchestration,5,20,4,saga-pattern;distributed-transactions;microservices;compensation;orchestration;eventual-consistency;rollback,"Saga orchestration pattern for distributed transactions across Order, Payment, and Shipping services with automatic compensation rollback on failures.",patterns/saga-pattern,delivery/patterns/saga-pattern-workflow
+router-workflow,router,Router Workflow,workflow,patterns,patterns,,patterns,3,10,3,router;patterns;decision,This workflow models routing messages based on their content.,patterns/router,patterns/patterns/router-workflow
+routing-slip-workflow,routing-slip,Routing Slip Workflow,workflow,patterns,handoff,patterns,handoff;patterns,4,13,4,routing;slip;patterns,This workflow models having messages carry their own routing instructions.,patterns/routing-slip,handoff/patterns/routing-slip-workflow
+saga-pattern-workflow,saga-pattern,Saga Pattern Workflow,workflow,patterns,delivery,ai-orchestration;architecture;patterns,delivery;ai-orchestration;architecture;patterns,5,20,4,saga-pattern;distributed-transactions;microservices;compensation;orchestration;eventual-consistency;rollback,"Saga orchestration pattern for distributed transactions across Order, Payment, and Shipping services with automatic compensation rollback on failures.",patterns/saga-pattern,delivery/patterns/saga-pattern-workflow
 salary-increase-workflow,salary-increase,Salary Increase Workflow,workflow,hr,approval,,approval,3,10,3,salary-increase;compensation;merit-raise;market-adjustment;budget-approval;comp-ratio,"Salary increase workflow with market analysis, comp ratio review, budget validation, tiered approval based on increase percentage, and payroll system update.",hr/salary-increase,approval/hr/salary-increase-workflow
 search-optimization-workflow,search-optimization,Search Optimization Workflow,workflow,business-operations,uncategorized,,,4,13,4,search-optimization;elasticsearch;relevance-tuning;query-analysis;algolia;search-analytics,"Search optimization workflow with query analysis, relevance tuning, synonym management, click-through tracking, and A/B testing of ranking algorithms.",business-operations/search-optimization,uncategorized/business-operations/search-optimization-workflow
 secret-rotation-workflow,secret-rotation,Secret Rotation Workflow,workflow,devops,security,,security,4,18,3,secret-rotation;vault;kubernetes-secrets;api-keys;database-passwords;certificates;security,"Automated secret rotation workflow with HashiCorp Vault for API keys, database passwords, and certificates including Kubernetes secret updates and rolling service restarts.",devops/secret-rotation,security/devops/secret-rotation-workflow
 security-scan-workflow,security-scan,Security Scan Workflow,workflow,devops,security,,security,3,10,3,security-scanning;sast;dast;dependency-check;snyk;devsecops,"Security scanning workflow with SAST, DAST, dependency vulnerability scanning, finding triage, and remediation tracking in CI/CD pipeline.",devops/security-scan,security/devops/security-scan-workflow
 shipping-process-workflow,shipping-process,Shipping Process Workflow,workflow,logistics,security,,security,3,10,3,shipping-process;order-fulfillment;carrier-selection;label-generation;tracking-number;dispatch,"Order shipping workflow with carrier selection, rate shopping, label generation, tracking number assignment, and dispatch confirmation.",logistics/shipping-process,security/logistics/shipping-process-workflow
 sms-verification-workflow,sms-verification,Sms Verification Workflow,workflow,business-operations,security,,security,3,13,4,sms-verification;otp;twilio;phone-verification;2fa;fraud-prevention,"SMS phone verification workflow with OTP generation, rate limiting, code validation, retry handling, and verification status tracking.",business-operations/sms-verification,security/business-operations/sms-verification-workflow
-snapshot-pattern-workflow,snapshot-pattern,Snapshot Pattern Workflow,workflow,patterns,uncategorized,,,2,7,2,snapshot;pattern;patterns;decision;loop,This workflow models taking periodic snapshots of important state.,patterns/snapshot-pattern,uncategorized/patterns/snapshot-pattern-workflow
-state-machine-workflow,state-machine,State Machine Workflow,workflow,patterns,uncategorized,,,4,13,4,state;machine;patterns;parallel,This workflow models tracking object state changes over time.,patterns/state-machine,uncategorized/patterns/state-machine-workflow
+snapshot-pattern-workflow,snapshot-pattern,Snapshot Pattern Workflow,workflow,patterns,patterns,,patterns,2,7,2,snapshot;pattern;patterns;decision;loop,This workflow models taking periodic snapshots of important state.,patterns/snapshot-pattern,patterns/patterns/snapshot-pattern-workflow
+sql-injection-label-workflow,sql-injection-label,Sql Injection Label Workflow,workflow,edge-cases,edge-cases,,edge-cases,2,7,2,sql;injection;label,This workflow models a label that looks like an SQL injection attempt.,edge-cases/sql-injection-label,edge-cases/edge-cases/sql-injection-label-workflow
+state-machine-workflow,state-machine,State Machine Workflow,workflow,patterns,patterns,,patterns,4,13,4,state;machine;patterns;parallel,This workflow models tracking object state changes over time.,patterns/state-machine,patterns/patterns/state-machine-workflow
 stock-transfer-workflow,stock-transfer,Stock Transfer Workflow,workflow,logistics,handoff,,handoff,3,10,3,stock-transfer;inventory-movement;location-transfer;bin-to-bin;wms;inventory-rebalancing,"Internal stock transfer workflow with transfer request, source location pick, destination put-away, and inventory record updates across locations.",logistics/stock-transfer,handoff/logistics/stock-transfer-workflow
-strangler-fig-workflow,strangler-fig,Strangler Fig Workflow,workflow,patterns,uncategorized,,,2,7,2,strangler;fig;patterns;decision,This workflow models gradually replacing an old system with a new one.,patterns/strangler-fig,uncategorized/patterns/strangler-fig-workflow
-subscription-lifecycle-workflow,subscription-lifecycle,Subscription Lifecycle Workflow,workflow,business-operations,billing,,billing,4,10,3,subscription-lifecycle;saas;trial-conversion;renewal;churn-prevention;stripe,"SaaS subscription lifecycle workflow with trial signup, conversion nurturing, payment processing, renewal management, and churn prevention campaigns.",business-operations/subscription-lifecycle,billing/business-operations/subscription-lifecycle-workflow
+strangler-fig-workflow,strangler-fig,Strangler Fig Workflow,workflow,patterns,patterns,,patterns,2,7,2,strangler;fig;patterns;decision,This workflow models gradually replacing an old system with a new one.,patterns/strangler-fig,patterns/patterns/strangler-fig-workflow
+subscription-lifecycle-workflow,subscription-lifecycle,Subscription Lifecycle Workflow,workflow,business-operations,billing,commerce-automation,billing;commerce-automation,4,10,3,subscription-lifecycle;saas;trial-conversion;renewal;churn-prevention;stripe,"SaaS subscription lifecycle workflow with trial signup, conversion nurturing, payment processing, renewal management, and churn prevention campaigns.",business-operations/subscription-lifecycle,billing/business-operations/subscription-lifecycle-workflow
 support-ticket-workflow,support-ticket,Support Ticket Workflow,workflow,business-operations,handoff,support,handoff;support,3,10,3,support-ticket;helpdesk;zendesk;sla;ticket-routing;customer-service,"Customer support ticket workflow with auto-categorization, SLA tracking, agent assignment, escalation rules, and satisfaction survey.",business-operations/support-ticket,handoff/business-operations/support-ticket-workflow
 tax-filing-workflow,tax-filing,Tax Filing Workflow,workflow,finance,compliance,,compliance,4,19,3,tax-filing;corporate-tax;tax-calculation;irs-efile;tax-credits;deductions;compliance,"Corporate tax filing workflow with taxable income calculation, deductions, tax credits, variance review, and electronic or paper filing to IRS with receipt confirmation.",finance/tax-filing,compliance/finance/tax-filing-workflow
 termination-process-workflow,termination-process,Termination Process Workflow,workflow,hr,approval,offboarding,approval;offboarding,4,20,3,employee-termination;offboarding;separation-agreement;final-pay;cobra;severance;legal-review,"Employee termination workflow handling voluntary and involuntary separations with legal review, separation agreements, final pay calculation, COBRA notices, and severance processing.",hr/termination-process,approval/hr/termination-process-workflow
-timeout-pattern-workflow,timeout-pattern,Timeout Pattern Workflow,workflow,patterns,uncategorized,,,4,13,4,timeout;pattern;patterns,This workflow models an operation that times out after a delay.,patterns/timeout-pattern,uncategorized/patterns/timeout-pattern-workflow
+timeout-pattern-workflow,timeout-pattern,Timeout Pattern Workflow,workflow,patterns,patterns,,patterns,4,13,4,timeout;pattern;patterns,This workflow models an operation that times out after a delay.,patterns/timeout-pattern,patterns/patterns/timeout-pattern-workflow
 training-enrollment-workflow,training-enrollment,Training Enrollment Workflow,workflow,hr,compliance,,compliance,2,7,2,training-enrollment;learning-management;lms;professional-development;compliance-training;certification,"Training enrollment workflow with course catalog browsing, manager approval, LMS registration, completion tracking, and certification management.",hr/training-enrollment,compliance/hr/training-enrollment-workflow
-transactional-outbox-workflow,transactional-outbox,Transactional Outbox Workflow,workflow,patterns,uncategorized,,,4,13,4,transactional;outbox;patterns;parallel,This workflow models writing data and publishing messages in one transaction.,patterns/transactional-outbox,uncategorized/patterns/transactional-outbox-workflow
-transform-workflow,transform,Transform Workflow,workflow,patterns,uncategorized,,,2,7,2,transform;patterns,This workflow models converting messages into a new shape.,patterns/transform,uncategorized/patterns/transform-workflow
+transactional-outbox-workflow,transactional-outbox,Transactional Outbox Workflow,workflow,patterns,patterns,,patterns,4,13,4,transactional;outbox;patterns;parallel,This workflow models writing data and publishing messages in one transaction.,patterns/transactional-outbox,patterns/patterns/transactional-outbox-workflow
+transform-workflow,transform,Transform Workflow,workflow,patterns,patterns,,patterns,2,7,2,transform;patterns,This workflow models converting messages into a new shape.,patterns/transform,patterns/patterns/transform-workflow
 treasury-management-workflow,treasury-management,Treasury Management Workflow,workflow,finance,uncategorized,,,3,7,2,treasury-management;cash-pooling;fx-hedging;investment-portfolio;bank-relationships;liquidity,"Corporate treasury management workflow with cash pooling, FX exposure hedging, short-term investment decisions, and bank relationship management.",finance/treasury-management,uncategorized/finance/treasury-management-workflow
 two-factor-setup-workflow,two-factor-setup,Two Factor Setup Workflow,workflow,business-operations,onboarding,security,onboarding;security,2,7,2,two-factor-auth;mfa;totp;authenticator-app;security;account-protection,"Two-factor authentication setup workflow with method selection (TOTP/SMS), QR code generation, backup codes, and verification confirmation.",business-operations/two-factor-setup,onboarding/business-operations/two-factor-setup-workflow
+unicode-labels-workflow,unicode-labels,Unicode Labels Workflow,workflow,edge-cases,edge-cases,,edge-cases,1,5,1,unicode;labels,This workflow models emoji and international characters in labels.,edge-cases/unicode-labels,edge-cases/edge-cases/unicode-labels-workflow
 user-onboarding-workflow,user-onboarding,User Onboarding Workflow,workflow,business-operations,onboarding,,onboarding,2,7,2,user-onboarding;activation;product-tour;welcome-email;first-time-user;time-to-value,"New user onboarding workflow with welcome email, profile setup, product tour, first action prompt, and activation milestone tracking.",business-operations/user-onboarding,onboarding/business-operations/user-onboarding-workflow
 user-segmentation-workflow,user-segmentation,User Segmentation Workflow,workflow,business-operations,uncategorized,,,2,7,2,user-segmentation;audience-targeting;behavioral-cohorts;customer-segments;segment;marketing-automation,"User segmentation workflow with attribute collection, behavioral event tracking, segment rule definition, dynamic membership, and downstream sync.",business-operations/user-segmentation,uncategorized/business-operations/user-segmentation-workflow
-validator-workflow,validator,Validator Workflow,workflow,patterns,uncategorized,,,2,7,2,validator;patterns;parallel,This workflow models checking that incoming data is valid.,patterns/validator,uncategorized/patterns/validator-workflow
+validator-workflow,validator,Validator Workflow,workflow,patterns,patterns,,patterns,2,7,2,validator;patterns;parallel,This workflow models checking that incoming data is valid.,patterns/validator,patterns/patterns/validator-workflow
 vendor-onboarding-workflow,vendor-onboarding,Vendor Onboarding Workflow,workflow,finance,onboarding,billing;compliance,onboarding;billing;compliance,4,19,3,vendor-onboarding;supplier-management;w9-verification;insurance-compliance;background-check;payment-terms;procurement,"Vendor onboarding workflow with application review, W-9/W-8BEN verification, insurance certificate validation, background checks, and compliance approval before vendor activation.",finance/vendor-onboarding,onboarding/finance/vendor-onboarding-workflow
+very-long-label-workflow,very-long-label,Very Long Label Workflow,workflow,edge-cases,edge-cases,,edge-cases,1,5,1,very;long;label;decision;loop,This workflow models labels with very long text.,edge-cases/very-long-label,edge-cases/edge-cases/very-long-label-workflow
 vulnerability-patch-workflow,vulnerability-patch,Vulnerability Patch Workflow,workflow,devops,security,compliance;delivery,security;compliance;delivery,4,19,3,vulnerability-management;security-patching;cve-triage;cvss-scoring;patch-testing;rollback;compliance,"Security vulnerability patching workflow with CVE scanning, severity-based triage (critical/high/medium), patch testing, staging deployment, and production rollout with rollback capability.",devops/vulnerability-patch,security/devops/vulnerability-patch-workflow
 warehouse-transfer-workflow,warehouse-transfer,Warehouse Transfer Workflow,workflow,logistics,handoff,,handoff,3,10,3,warehouse-transfer;inter-facility;transfer-order;in-transit-inventory;network-optimization;distribution,"Inter-warehouse transfer workflow with transfer order creation, shipping from source DC, in-transit tracking, and receiving at destination warehouse.",logistics/warehouse-transfer,handoff/logistics/warehouse-transfer-workflow
-webhook-integration-workflow,webhook-integration,Webhook Integration Workflow,workflow,business-operations,uncategorized,,,2,7,2,webhook;event-driven;http-callback;integration;retry-logic;payload-signing,"Webhook integration workflow with endpoint registration, payload signing, delivery attempt, retry with backoff, and delivery status tracking.",business-operations/webhook-integration,uncategorized/business-operations/webhook-integration-workflow
-webhook-pattern-workflow,webhook-pattern,Webhook Pattern Workflow,workflow,patterns,uncategorized,,,2,7,2,webhook;pattern;patterns;decision;loop,This workflow models an HTTP callback when an event occurs.,patterns/webhook-pattern,uncategorized/patterns/webhook-pattern-workflow
+webhook-integration-workflow,webhook-integration,Webhook Integration Workflow,workflow,business-operations,architecture,patterns,architecture;patterns,2,7,2,webhook;event-driven;http-callback;integration;retry-logic;payload-signing,"Webhook integration workflow with endpoint registration, payload signing, delivery attempt, retry with backoff, and delivery status tracking.",business-operations/webhook-integration,architecture/business-operations/webhook-integration-workflow
+webhook-pattern-workflow,webhook-pattern,Webhook Pattern Workflow,workflow,patterns,patterns,,patterns,2,7,2,webhook;pattern;patterns;decision;loop,This workflow models an HTTP callback when an event occurs.,patterns/webhook-pattern,patterns/patterns/webhook-pattern-workflow
 webinar-registration-workflow,webinar-registration,Webinar Registration Workflow,workflow,business-operations,onboarding,,onboarding,3,10,3,webinar;event-registration;zoom;calendar-invite;reminder-sequence;lead-capture,"Webinar registration workflow with signup form, calendar invite, reminder email sequence, attendance tracking, and post-event follow-up.",business-operations/webinar-registration,onboarding/business-operations/webinar-registration-workflow
+xml-in-label-workflow,xml-in-label,Xml In Label Workflow,workflow,edge-cases,edge-cases,,edge-cases,5,16,4,xml;in;label,This workflow models a label that contains XML text.,edge-cases/xml-in-label,edge-cases/edge-cases/xml-in-label-workflow
+xss-label-workflow,xss-label,Xss Label Workflow,workflow,edge-cases,edge-cases,,edge-cases,3,10,3,xss;label,This workflow models a label that looks like an XSS script.,edge-cases/xss-label,edge-cases/edge-cases/xss-label-workflow
 yearly-audit-workflow,yearly-audit,Yearly Audit Workflow,workflow,finance,compliance,,compliance,4,10,3,annual-audit;external-auditors;sox-compliance;financial-statements;audit-findings;management-letter,"Annual financial audit workflow with external auditor engagement, document preparation, fieldwork coordination, findings remediation, and management letter response.",finance/yearly-audit,compliance/finance/yearly-audit-workflow
-shopify-universal-commerce-protocol,shopify-universal-commerce-protocol,Shopify Universal Commerce Protocol,workflow,business-operations,billing,agentic,billing;agentic,4,47,5,shopify;ucp;universal-commerce-protocol;agentic-commerce;ai-shopping;chatgpt;e-commerce;checkout;payment,"End-to-end agentic commerce workflow showing how an AI assistant (ChatGPT) orchestrates product search, checkout, and payment through Shopify's Universal Commerce Protocol (UCP) gateway, enabling conversational shopping experiences.",business-operations/shopify-universal-commerce-protocol,billing/business-operations/shopify-universal-commerce-protocol
-microservices-api-gateway-architecture,microservices-api-gateway-architecture,Microservices API Gateway Architecture,architecture,Architecture,security,mcp,security;mcp,4,17,3,microservices;api-gateway;jwt-authentication;rate-limiting;service-discovery;load-balancing;architecture-diagram;distributed-systems,"A microservices API gateway architecture diagram showing request routing, JWT authentication, rate limiting, service discovery, and response aggregation across distributed backend services. This template models the entry point for all client traffic in a microservices ecosystem, enforcing security policies before requests reach internal services. Ideal for platform engineers designing scalable API infrastructure with centralized cross-cutting concerns.",,security/architecture/microservices-api-gateway-architecture
-microservices-service-mesh-architecture,microservices-service-mesh-architecture,Microservices Service Mesh Architecture,architecture,Architecture,mcp,,mcp,4,18,3,service-mesh;istio;linkerd;mtls;sidecar-proxy;distributed-tracing;traffic-management;architecture-diagram,"A service mesh architecture diagram with Istio or Linkerd sidecar proxies handling mTLS encryption, traffic policies, circuit breaking, and distributed tracing across microservices. This template visualizes how a service mesh abstracts networking concerns away from application code, enabling zero-trust communication between services. Essential for teams adopting service mesh infrastructure to improve observability and security.",,mcp/architecture/microservices-service-mesh-architecture
-microservices-database-per-service-architecture,microservices-database-per-service-architecture,Microservices Database-Per-Service Architecture,architecture,Architecture,uncategorized,,,4,16,4,database-per-service;polyglot-persistence;microservices;kafka;event-driven;data-isolation;eventual-consistency;architecture-diagram,"A database-per-service architecture diagram where each microservice owns its dedicated data store, with event-driven synchronization via Kafka for cross-service data consistency. This template demonstrates the core microservices data isolation principle, showing how PostgreSQL and MongoDB coexist in a polyglot persistence strategy. Critical for architects enforcing service autonomy while maintaining eventual consistency.",,uncategorized/architecture/microservices-database-per-service-architecture
-microservices-decomposition-by-business-capability,microservices-decomposition-by-business-capability,Microservices Decomposition by Business Capability,architecture,Architecture,uncategorized,,,4,17,5,microservices-decomposition;business-capability;bff;domain-driven-design;service-boundaries;monolith-to-microservices;architecture-diagram,"A microservices decomposition architecture diagram organized by business capabilities: Identity, Product Catalog, Pricing, and Order Fulfillment, each with independent data stores and APIs. This template shows how to break a monolith into services aligned with business domains, using a Backend-for-Frontend (BFF) pattern for client-specific aggregation. Useful for architects planning domain-driven microservice boundaries.",,uncategorized/architecture/microservices-decomposition-by-business-capability
-microservices-strangler-fig-migration,microservices-strangler-fig-migration,Microservices Strangler Fig Migration Architecture,architecture,Architecture,delivery,,delivery,4,16,4,strangler-fig;legacy-migration;monolith-decomposition;anti-corruption-layer;incremental-migration;modernization;architecture-diagram,"A strangler fig migration architecture diagram showing the incremental replacement of a legacy monolith with new microservices, using a routing layer to split traffic between old and new systems. This template models the proven migration strategy where new features are built as microservices while legacy endpoints are gradually retired. Essential for teams modernizing legacy systems without risky big-bang rewrites.",,delivery/architecture/microservices-strangler-fig-migration
-microservices-service-discovery-architecture,microservices-service-discovery-architecture,Microservices Service Discovery Architecture,architecture,Architecture,handoff,,handoff,3,16,3,service-discovery;consul;eureka;health-check;client-side-load-balancing;service-registry;dynamic-routing;architecture-diagram,"A service discovery architecture diagram with Consul or Eureka registry, client-side load balancing, health check heartbeats, and automatic instance registration and deregistration. This template visualizes how microservices dynamically locate each other without hardcoded endpoints, enabling elastic scaling and self-healing infrastructure. Key for platform teams building resilient service-to-service communication.",,handoff/architecture/microservices-service-discovery-architecture
-microservices-sidecar-pattern-architecture,microservices-sidecar-pattern-architecture,Microservices Sidecar Pattern Architecture,architecture,Architecture,mcp,,mcp,4,13,3,sidecar-pattern;envoy-proxy;kubernetes;container-pattern;observability;control-plane;cloud-native;architecture-diagram,"A sidecar pattern architecture diagram showing Envoy proxy, log collector, and config watcher sidecars running alongside application containers in a Kubernetes pod, with a control plane managing configuration. This template demonstrates how auxiliary concerns like logging, monitoring, and configuration are deployed as co-located containers. Foundational for teams adopting cloud-native container orchestration patterns.",,mcp/architecture/microservices-sidecar-pattern-architecture
-microservices-backend-for-frontend-architecture,microservices-backend-for-frontend-architecture,Microservices Backend-for-Frontend (BFF) Architecture,architecture,Architecture,uncategorized,,,3,12,3,backend-for-frontend;bff-pattern;mobile-api;web-api;api-aggregation;payload-optimization;microservices;architecture-diagram,"A Backend-for-Frontend architecture diagram with separate BFF layers for web and mobile clients, each optimizing API responses for their specific platform while sharing common backend microservices. This template shows how to avoid one-size-fits-all APIs by tailoring data aggregation and payload optimization per client type. Recommended for teams serving multiple frontend platforms from a shared microservices backend.",,uncategorized/architecture/microservices-backend-for-frontend-architecture
-event-driven-publish-subscribe-architecture,event-driven-publish-subscribe-architecture,Event-Driven Publish-Subscribe Architecture,architecture,Architecture,uncategorized,,,4,17,3,publish-subscribe;event-driven;kafka;rabbitmq;message-broker;fan-out;dead-letter-queue;architecture-diagram,"An event-driven publish-subscribe architecture diagram with Kafka or RabbitMQ message broker, event serialization, topic partitioning, fan-out delivery to multiple consumers, and dead letter queue error handling. This template models the foundational async messaging pattern where producers and consumers are fully decoupled through a message broker. Essential for architects building loosely coupled, scalable event-driven systems.",,uncategorized/architecture/event-driven-publish-subscribe-architecture
-event-driven-event-sourcing-architecture,event-driven-event-sourcing-architecture,Event-Driven Event Sourcing Architecture,architecture,Architecture,uncategorized,,,4,18,4,event-sourcing;immutable-events;event-store;projections;snapshot;aggregate;temporal-query;architecture-diagram,"An event sourcing architecture diagram where all state changes are stored as an immutable sequence of domain events, with read projections built from the event stream and snapshot optimization for fast aggregate loading. This template shows how event sourcing eliminates data loss by preserving the complete history of every state transition. Critical for systems requiring full audit trails, temporal queries, and event replay capabilities.",,uncategorized/architecture/event-driven-event-sourcing-architecture
-event-driven-cqrs-with-event-store-architecture,event-driven-cqrs-with-event-store-architecture,Event-Driven CQRS with Event Store Architecture,architecture,Architecture,uncategorized,,,4,18,4,cqrs;event-store;command-query-separation;read-model;write-model;projector;eventual-consistency;architecture-diagram,"A CQRS architecture diagram combining separate command and query APIs with an event bus for asynchronous read model synchronization, including projectors that build denormalized views from domain events. This template demonstrates the full CQRS+ES stack where writes go through domain validation and reads are served from optimized materialized views. Ideal for high-throughput systems where read and write workloads have fundamentally different scaling requirements.",,uncategorized/architecture/event-driven-cqrs-with-event-store-architecture
-event-driven-choreography-architecture,event-driven-choreography-architecture,Event-Driven Choreography Architecture,architecture,Architecture,uncategorized,,,4,19,5,choreography;event-driven;decentralized-coordination;domain-events;microservices;autonomous-services;pub-sub;architecture-diagram,"An event-driven choreography architecture diagram where microservices coordinate through events without a central orchestrator, with Order, Payment, Inventory, and Shipping services reacting to each other's domain events. This template models the decentralized coordination pattern where each service knows only its own responsibilities and publishes events for others to consume. Best for teams favoring autonomous services over centralized workflow control.",,uncategorized/architecture/event-driven-choreography-architecture
-event-driven-event-streaming-pipeline-architecture,event-driven-event-streaming-pipeline-architecture,Event-Driven Streaming Pipeline Architecture,architecture,Architecture,delivery,,delivery,4,18,4,event-streaming;kafka;apache-flink;stream-processing;real-time-analytics;iot;data-pipeline;architecture-diagram,"A real-time event streaming pipeline architecture diagram with IoT sensors, application logs, and clickstream data flowing through Kafka into Apache Flink for window aggregation, anomaly detection, and multi-sink output to data lakes and dashboards. This template visualizes end-to-end stream processing from ingestion through transformation to storage and alerting. Essential for data engineers building real-time analytics and monitoring platforms.",,delivery/architecture/event-driven-event-streaming-pipeline-architecture
-event-driven-domain-events-architecture,event-driven-domain-events-architecture,Event-Driven Domain Events Architecture,architecture,Architecture,security,,security,4,17,4,domain-events;ddd;aggregate-root;bounded-context;event-dispatcher;integration-events;domain-driven-design;architecture-diagram,"A domain events architecture diagram showing how aggregate roots raise domain events that are dispatched both in-process to local handlers and cross-boundary to integration event consumers in other bounded contexts. This template models the DDD event pattern where domain logic triggers side effects through a clean event dispatcher, maintaining separation between domain and infrastructure concerns. Key for teams implementing Domain-Driven Design with event-based integration.",,security/architecture/event-driven-domain-events-architecture
-event-driven-cdc-change-data-capture-architecture,event-driven-cdc-change-data-capture-architecture,Event-Driven CDC (Change Data Capture) Architecture,architecture,Architecture,uncategorized,,,4,17,4,change-data-capture;cdc;debezium;transaction-log;kafka-connect;data-synchronization;dual-write;architecture-diagram,"A Change Data Capture architecture diagram using Debezium to tail database transaction logs and publish change events to Kafka, feeding downstream consumers that update search indexes, invalidate caches, load data warehouses, and write audit logs. This template shows how CDC eliminates dual-write problems by capturing changes at the database level without modifying application code. Critical for data synchronization across heterogeneous systems.",,uncategorized/architecture/event-driven-cdc-change-data-capture-architecture
-event-driven-dead-letter-queue-architecture,event-driven-dead-letter-queue-architecture,Event-Driven Dead Letter Queue Architecture,architecture,Architecture,incident,compliance,incident;compliance,3,16,3,dead-letter-queue;dlq;retry-policy;message-processing;error-handling;operations-alerting;message-reliability;architecture-diagram,"A dead letter queue architecture diagram with retry policies, exponential backoff, max retry thresholds, DLQ routing for failed messages, operations alerting, and manual reprocessing workflows. This template models the critical error handling pattern for asynchronous messaging systems, ensuring no message is silently lost when processing fails. Essential for building reliable event-driven systems with proper failure recovery mechanisms.",,incident/architecture/event-driven-dead-letter-queue-architecture
-cqrs-read-write-separation-architecture,cqrs-read-write-separation-architecture,CQRS Read-Write Separation Architecture,architecture,Architecture,uncategorized,,,4,18,4,cqrs;read-write-separation;command-query;postgresql;redis;elasticsearch;read-model-sync;architecture-diagram,"A CQRS read-write separation architecture diagram with dedicated command and query paths, PostgreSQL for writes, Redis or Elasticsearch for optimized reads, and an event-driven synchronization layer with lag monitoring. This template demonstrates the core CQRS principle of separating read and write models to independently scale and optimize each path. Ideal for applications with asymmetric read/write ratios where query performance is critical.",,uncategorized/architecture/cqrs-read-write-separation-architecture
-cqrs-materialized-view-architecture,cqrs-materialized-view-architecture,CQRS Materialized View Architecture,architecture,Architecture,uncategorized,,,4,18,4,materialized-view;cqrs;projectors;read-model;denormalization;query-optimization;event-stream;architecture-diagram,"A CQRS materialized view architecture diagram with multiple projectors building purpose-specific read models: order summaries, customer dashboards, analytics cubes, and search indexes, all fed from a single event stream. This template shows how to create multiple optimized query views from the same write events, each tailored to a specific use case with sub-millisecond read latency. Perfect for systems requiring diverse query patterns from a single data source.",,uncategorized/architecture/cqrs-materialized-view-architecture
-cqrs-task-based-ui-architecture,cqrs-task-based-ui-architecture,CQRS Task-Based UI Architecture,architecture,Architecture,uncategorized,,,4,19,4,task-based-ui;cqrs;optimistic-update;websocket;command-pattern;idempotency;reactive-ui;architecture-diagram,"A CQRS task-based UI architecture diagram where the frontend captures user intent as explicit commands, submits them asynchronously with optimistic updates, and receives real-time confirmations via WebSocket when the read model is synchronized. This template models the modern UI pattern that replaces CRUD forms with intent-driven commands, enabling responsive user experiences with eventual consistency. Recommended for teams building reactive frontends on CQRS backends.",,uncategorized/architecture/cqrs-task-based-ui-architecture
-serverless-api-backend-architecture,serverless-api-backend-architecture,Serverless API Backend Architecture,architecture,Architecture,mcp,,mcp,3,15,3,serverless;aws-lambda;api-gateway;dynamodb;cloud-architecture;auto-scaling;pay-per-use;architecture-diagram,"A serverless API backend architecture diagram with API Gateway, Lambda authorizer functions, business logic functions, and managed cloud services including DynamoDB, S3, SQS, and SNS for a fully managed, auto-scaling backend. This template models the serverless-first approach where infrastructure management is eliminated entirely, with pay-per-invocation pricing and automatic scaling to zero. Essential for startups and teams building cost-efficient, event-driven API backends.",,mcp/architecture/serverless-api-backend-architecture
-serverless-event-processing-architecture,serverless-event-processing-architecture,Serverless Event Processing Architecture,architecture,Architecture,uncategorized,,,4,17,4,serverless;event-processing;step-functions;lambda-triggers;sqs;s3-events;dynamodb-streams;architecture-diagram,"A serverless event processing architecture diagram with S3, DynamoDB Streams, API Gateway, and CloudWatch triggers invoking Lambda functions, orchestrated by Step Functions with fan-out via SQS and dead letter queue error handling. This template shows how to build complex event processing pipelines entirely from managed serverless components, with no servers to provision or manage. Ideal for data processing workflows that need elastic scaling and built-in fault tolerance.",,uncategorized/architecture/serverless-event-processing-architecture
-serverless-step-functions-orchestration-architecture,serverless-step-functions-orchestration-architecture,Serverless Step Functions Orchestration Architecture,architecture,Architecture,incident,ai-orchestration,incident;ai-orchestration,4,17,3,step-functions;serverless-orchestration;state-machine;workflow-automation;callback-pattern;compensation;aws;architecture-diagram,"An AWS Step Functions orchestration architecture diagram with state machine workflows including choice states, parallel processing, wait-for-callback patterns, and compensation rollback for failed steps. This template models serverless workflow orchestration where complex multi-step processes are defined as state machines with built-in error handling and retry logic. Critical for teams building reliable serverless workflows that require human approval or long-running processes.",,incident/architecture/serverless-step-functions-orchestration-architecture
-serverless-edge-computing-architecture,serverless-edge-computing-architecture,Serverless Edge Computing Architecture,architecture,Architecture,handoff,,handoff,3,15,3,edge-computing;lambda-at-edge;cloudfront;cloudflare;cdn;geo-routing;cache-strategy;architecture-diagram,"A serverless edge computing architecture diagram with CloudFront or Cloudflare edge locations, Lambda@Edge functions for A/B testing and geo-personalization, origin shield request collapsing, and cache-first response strategies. This template visualizes how computation moves to the network edge for ultra-low latency responses, with edge functions modifying requests and responses before they reach the origin. Essential for performance-critical applications serving global audiences.",,handoff/architecture/serverless-edge-computing-architecture
-serverless-data-pipeline-architecture,serverless-data-pipeline-architecture,Serverless Data Pipeline Architecture,architecture,Architecture,delivery,,delivery,4,17,4,serverless-data-pipeline;kinesis;glue;athena;s3-data-lake;etl;sagemaker;architecture-diagram,"A serverless data pipeline architecture diagram with Kinesis ingestion, Lambda transformation functions, S3 data lake storage zones (raw and curated), Glue catalog registration, and Athena query engine feeding QuickSight dashboards and SageMaker ML models. This template models a complete serverless ETL pipeline from data ingestion through transformation, cataloging, and analytics without managing any infrastructure. Ideal for data teams building cost-effective analytics platforms.",,delivery/architecture/serverless-data-pipeline-architecture
-serverless-multi-cloud-architecture,serverless-multi-cloud-architecture,Serverless Multi-Cloud Architecture,architecture,Architecture,handoff,,handoff,4,18,4,multi-cloud;aws;azure;cloud-failover;dns-routing;data-replication;vendor-independence;architecture-diagram,"A multi-cloud serverless architecture diagram with DNS-based traffic routing between AWS and Azure regions, automatic failover on health check failures, and bi-directional data replication with conflict resolution across cloud providers. This template models the multi-cloud strategy for maximum availability and vendor independence, using serverless services from both AWS (Lambda, DynamoDB) and Azure (Functions, Cosmos DB). Critical for enterprises requiring cloud provider redundancy.",,handoff/architecture/serverless-multi-cloud-architecture
-saga-orchestration-pattern-architecture,saga-orchestration-pattern-architecture,Saga Orchestration Pattern Architecture,architecture,Architecture,delivery,ai-orchestration,delivery;ai-orchestration,4,19,5,saga-pattern;orchestration;distributed-transaction;compensation;microservices;rollback;consistency;architecture-diagram,"A saga orchestration architecture diagram with a central orchestrator coordinating multi-step distributed transactions across Order, Inventory, and Payment services, with a dedicated compensation chain for rollback on failure. This template models the orchestration-based saga pattern where a single coordinator manages the transaction lifecycle and triggers compensating actions when any step fails. Essential for architects implementing reliable distributed transactions without two-phase commit.",,delivery/architecture/saga-orchestration-pattern-architecture
-saga-choreography-pattern-architecture,saga-choreography-pattern-architecture,Saga Choreography Pattern Architecture,architecture,Architecture,uncategorized,,,4,18,5,saga-choreography;event-driven-saga;decentralized;domain-events;compensation;autonomous-services;distributed-transaction;architecture-diagram,"A saga choreography architecture diagram where Order, Payment, and Inventory services coordinate through domain events without a central orchestrator, with each service publishing and subscribing to events that drive the transaction forward or trigger compensation. This template models the decentralized saga approach where services autonomously react to events, reducing single points of failure at the cost of increased complexity in tracking saga state. Best for teams preferring service autonomy over centralized control.",,uncategorized/architecture/saga-choreography-pattern-architecture
-saga-distributed-transaction-architecture,saga-distributed-transaction-architecture,Saga Distributed Transaction Architecture,architecture,Architecture,ai-orchestration,,ai-orchestration,4,17,4,distributed-transaction;two-phase-commit;2pc;transaction-coordinator;consensus;strong-consistency;prepare-commit;architecture-diagram,"A distributed transaction architecture diagram implementing the two-phase commit protocol with a transaction coordinator sending prepare and commit messages to participating services, with global abort on any vote failure. This template visualizes the classic 2PC protocol used when strong consistency is required across multiple services, showing the prepare, vote, and commit/abort phases. Important for understanding distributed consensus trade-offs in microservices architectures.",,ai-orchestration/architecture/saga-distributed-transaction-architecture
-saga-travel-booking-architecture,saga-travel-booking-architecture,Saga Travel Booking Architecture,architecture,Architecture,ai-orchestration,,ai-orchestration,4,17,5,saga-pattern;travel-booking;flight-reservation;hotel-booking;compensation;distributed-transaction;orchestration;architecture-diagram,"A travel booking saga architecture diagram orchestrating flight, hotel, and car rental reservations as a single distributed transaction, with automatic compensation to cancel all bookings if any reservation step fails. This template models the classic saga use case where multiple independent services must either all succeed or all roll back, ensuring travelers never end up with partial bookings. Perfect for demonstrating saga patterns with a real-world business scenario.",,ai-orchestration/architecture/saga-travel-booking-architecture
-saga-order-fulfillment-architecture,saga-order-fulfillment-architecture,Saga Order Fulfillment Architecture,architecture,Architecture,approval,billing;security,approval;billing;security,4,18,3,order-fulfillment;saga-pattern;e-commerce;payment-authorization;inventory-reservation;compensation-chain;distributed-transaction;architecture-diagram,"An order fulfillment saga architecture diagram with four sequential steps: customer verification, inventory reservation, payment authorization, and shipment creation, with a compensation chain that reverses completed steps on failure. This template models the end-to-end order lifecycle as a saga, showing how each service participates in the transaction and how compensating actions maintain data consistency. Ideal for e-commerce architects designing reliable order processing pipelines.",,approval/architecture/saga-order-fulfillment-architecture
-circuit-breaker-resilience-architecture,circuit-breaker-resilience-architecture,Circuit Breaker Resilience Architecture,architecture,Architecture,mcp,,mcp,4,18,3,circuit-breaker;resilience;fault-tolerance;cascading-failure;half-open-state;fallback;state-machine;architecture-diagram,"A circuit breaker resilience architecture diagram showing the complete state machine with closed, open, and half-open states, failure threshold tracking, recovery timer, and fallback response strategies for protecting services from cascading failures. This template visualizes the circuit breaker pattern in detail, including how the breaker transitions between states based on success and failure counts. Essential for building fault-tolerant microservices that degrade gracefully under load.",,mcp/architecture/circuit-breaker-resilience-architecture
-bulkhead-isolation-architecture,bulkhead-isolation-architecture,Bulkhead Isolation Architecture,architecture,Architecture,handoff,,handoff,4,18,4,bulkhead-pattern;resource-isolation;thread-pool;backpressure;fault-isolation;resilience;priority-routing;architecture-diagram,"A bulkhead isolation architecture diagram with separate thread pools for critical, standard, and batch workloads, each with independent connection pools, exhaustion detection, and backpressure strategies to prevent one workload from starving others. This template models the bulkhead pattern inspired by ship hull compartments, where resource isolation ensures that a failure or overload in one component cannot cascade to others. Critical for systems requiring guaranteed availability for high-priority operations.",,handoff/architecture/bulkhead-isolation-architecture
-retry-with-exponential-backoff-architecture,retry-with-exponential-backoff-architecture,Retry with Exponential Backoff Architecture,architecture,Architecture,uncategorized,,,3,17,3,retry-pattern;exponential-backoff;jitter;transient-failure;resilience;error-handling;thundering-herd;architecture-diagram,"A retry with exponential backoff architecture diagram showing the complete retry policy engine with retryable vs non-retryable error classification, exponential delay calculation with jitter, max retry thresholds, and graceful exhaustion handling. This template models the essential resilience pattern for handling transient failures in distributed systems, preventing thundering herd problems through randomized backoff delays. Foundational for any service-to-service communication in cloud architectures.",,uncategorized/architecture/retry-with-exponential-backoff-architecture
-rate-limiter-architecture,rate-limiter-architecture,Rate Limiter Architecture,architecture,Architecture,uncategorized,,,3,17,4,rate-limiter;token-bucket;sliding-window;redis;api-protection;throttling;distributed-rate-limiting;architecture-diagram,"A rate limiter architecture diagram implementing the token bucket algorithm with Redis-backed distributed counters, sliding window logs, API key identification, rate limit headers, and multi-node synchronization for consistent enforcement. This template shows how to protect APIs from abuse and ensure fair usage across clients, with proper HTTP 429 responses and Retry-After headers. Essential for API platform teams building production-grade rate limiting infrastructure.",,uncategorized/architecture/rate-limiter-architecture
-health-check-pattern-architecture,health-check-pattern-architecture,Health Check Pattern Architecture,architecture,Architecture,incident,security,incident;security,3,19,4,health-check;load-balancer;self-healing;monitoring;pagerduty;instance-rotation;deep-health-check;architecture-diagram,"A health check pattern architecture diagram with load balancer probes, deep health checks verifying database, cache, disk, and dependency status, automatic instance rotation, and alerting integration with PagerDuty for consecutive failures. This template models the health monitoring infrastructure that enables self-healing systems, where unhealthy instances are automatically removed from rotation and operations teams are alerted. Key for building production-ready services with proper observability.",,incident/architecture/health-check-pattern-architecture
-hexagonal-ports-adapters-architecture,hexagonal-ports-adapters-architecture,Hexagonal (Ports and Adapters) Architecture,architecture,Architecture,uncategorized,,,4,16,4,hexagonal-architecture;ports-and-adapters;clean-architecture;dependency-inversion;domain-core;testability;technology-agnostic;architecture-diagram,"A hexagonal architecture diagram showing the clean separation between domain core, inbound adapters (REST, GraphQL, CLI, message consumers), outbound adapters (PostgreSQL, Stripe, email, Redis), and the port interfaces that connect them. This template visualizes the ports and adapters pattern where the domain core has zero dependencies on infrastructure, making it fully testable and technology-agnostic. Foundational for teams adopting clean architecture principles in their codebase.",,uncategorized/architecture/hexagonal-ports-adapters-architecture
-clean-architecture-layers,clean-architecture-layers,Clean Architecture Layers,architecture,Architecture,uncategorized,,,3,16,4,clean-architecture;uncle-bob;dependency-rule;layered-architecture;use-cases;entities;interface-adapters;architecture-diagram,"A clean architecture layers diagram showing the four concentric layers: Entities (domain), Use Cases (application), Interface Adapters (controllers, presenters, repositories), and Frameworks & Drivers (web server, database, cloud SDK). This template models Uncle Bob's Clean Architecture with the dependency rule where inner layers never depend on outer layers, ensuring the domain model remains pure and framework-independent. Essential reference for software architects enforcing architectural boundaries.",,uncategorized/architecture/clean-architecture-layers
-domain-driven-design-bounded-contexts-architecture,domain-driven-design-bounded-contexts-architecture,Domain-Driven Design Bounded Contexts Architecture,architecture,Architecture,uncategorized,,,4,18,5,domain-driven-design;bounded-context;anti-corruption-layer;context-map;shared-kernel;strategic-ddd;aggregate;architecture-diagram,"A DDD bounded contexts architecture diagram with Order, Customer, Shipping, and Billing contexts connected through an anti-corruption layer, shared kernel, and context map defining integration relationships. This template visualizes the strategic DDD patterns for decomposing complex domains into autonomous bounded contexts that communicate through well-defined integration events. Critical for architects applying Domain-Driven Design to large-scale enterprise systems.",,uncategorized/architecture/domain-driven-design-bounded-contexts-architecture
-api-composition-pattern-architecture,api-composition-pattern-architecture,API Composition Pattern Architecture,architecture,Architecture,incident,,incident,3,16,3,api-composition;response-aggregation;fan-out;parallel-requests;timeout-handling;partial-response;microservices;architecture-diagram,"An API composition architecture diagram with a composer service that fans out parallel requests to multiple microservices, collects responses with timeout handling, and merges results into a single unified response with partial fallback support. This template models the API composition pattern used when a single client query requires data from multiple services, avoiding the need for direct service-to-service calls. Useful for teams building aggregation layers in microservices architectures.",,incident/architecture/api-composition-pattern-architecture
-outbox-pattern-reliable-messaging-architecture,outbox-pattern-reliable-messaging-architecture,Outbox Pattern for Reliable Messaging Architecture,architecture,Architecture,uncategorized,,,4,18,4,outbox-pattern;transactional-outbox;reliable-messaging;dual-write;exactly-once;debezium;event-publishing;architecture-diagram,"A transactional outbox architecture diagram where domain writes and event publishing happen in the same database transaction, with a relay process polling the outbox table and publishing events to a message broker with guaranteed delivery. This template solves the dual-write problem where updating a database and publishing an event are not atomic, ensuring exactly-once event delivery without distributed transactions. Critical for event-driven architectures requiring reliable message publishing.",,uncategorized/architecture/outbox-pattern-reliable-messaging-architecture
-ambassador-pattern-architecture,ambassador-pattern-architecture,Ambassador Pattern Architecture,architecture,Architecture,mcp,,mcp,3,15,3,ambassador-pattern;sidecar-proxy;external-api;retry-logic;circuit-breaker;metrics-collection;cross-cutting-concerns;architecture-diagram,"An ambassador pattern architecture diagram with a local proxy sidecar handling authentication header injection, circuit breaking, retry logic, and metrics collection for outbound requests to external third-party APIs. This template models the ambassador pattern where a helper service running alongside the application offloads cross-cutting concerns for external communication. Useful for teams integrating with unreliable third-party services that need resilience wrappers.",,mcp/architecture/ambassador-pattern-architecture
+shopify-universal-commerce-protocol,shopify-universal-commerce-protocol,Shopify Universal Commerce Protocol,workflow,business-operations,billing,agentic;commerce-automation,billing;agentic;commerce-automation,4,47,5,shopify;ucp;universal-commerce-protocol;agentic-commerce;ai-shopping;chatgpt;e-commerce;checkout;payment,"End-to-end agentic commerce workflow showing how an AI assistant (ChatGPT) orchestrates product search, checkout, and payment through Shopify's Universal Commerce Protocol (UCP) gateway, enabling conversational shopping experiences.",business-operations/shopify-universal-commerce-protocol,billing/business-operations/shopify-universal-commerce-protocol
+microservices-api-gateway-architecture,microservices-api-gateway-architecture,Microservices API Gateway Architecture,architecture,Architecture,security,mcp;architecture,security;mcp;architecture,4,17,3,microservices;api-gateway;jwt-authentication;rate-limiting;service-discovery;load-balancing;architecture-diagram;distributed-systems,"A microservices API gateway architecture diagram showing request routing, JWT authentication, rate limiting, service discovery, and response aggregation across distributed backend services. This template models the entry point for all client traffic in a microservices ecosystem, enforcing security policies before requests reach internal services. Ideal for platform engineers designing scalable API infrastructure with centralized cross-cutting concerns.",,security/architecture/microservices-api-gateway-architecture
+microservices-service-mesh-architecture,microservices-service-mesh-architecture,Microservices Service Mesh Architecture,architecture,Architecture,mcp,architecture,mcp;architecture,4,18,3,service-mesh;istio;linkerd;mtls;sidecar-proxy;distributed-tracing;traffic-management;architecture-diagram,"A service mesh architecture diagram with Istio or Linkerd sidecar proxies handling mTLS encryption, traffic policies, circuit breaking, and distributed tracing across microservices. This template visualizes how a service mesh abstracts networking concerns away from application code, enabling zero-trust communication between services. Essential for teams adopting service mesh infrastructure to improve observability and security.",,mcp/architecture/microservices-service-mesh-architecture
+microservices-database-per-service-architecture,microservices-database-per-service-architecture,Microservices Database-Per-Service Architecture,architecture,Architecture,architecture,,architecture,4,16,4,database-per-service;polyglot-persistence;microservices;kafka;event-driven;data-isolation;eventual-consistency;architecture-diagram,"A database-per-service architecture diagram where each microservice owns its dedicated data store, with event-driven synchronization via Kafka for cross-service data consistency. This template demonstrates the core microservices data isolation principle, showing how PostgreSQL and MongoDB coexist in a polyglot persistence strategy. Critical for architects enforcing service autonomy while maintaining eventual consistency.",,architecture/architecture/microservices-database-per-service-architecture
+microservices-decomposition-by-business-capability,microservices-decomposition-by-business-capability,Microservices Decomposition by Business Capability,architecture,Architecture,architecture,,architecture,4,17,5,microservices-decomposition;business-capability;bff;domain-driven-design;service-boundaries;monolith-to-microservices;architecture-diagram,"A microservices decomposition architecture diagram organized by business capabilities: Identity, Product Catalog, Pricing, and Order Fulfillment, each with independent data stores and APIs. This template shows how to break a monolith into services aligned with business domains, using a Backend-for-Frontend (BFF) pattern for client-specific aggregation. Useful for architects planning domain-driven microservice boundaries.",,architecture/architecture/microservices-decomposition-by-business-capability
+microservices-strangler-fig-migration,microservices-strangler-fig-migration,Microservices Strangler Fig Migration Architecture,architecture,Architecture,delivery,architecture,delivery;architecture,4,16,4,strangler-fig;legacy-migration;monolith-decomposition;anti-corruption-layer;incremental-migration;modernization;architecture-diagram,"A strangler fig migration architecture diagram showing the incremental replacement of a legacy monolith with new microservices, using a routing layer to split traffic between old and new systems. This template models the proven migration strategy where new features are built as microservices while legacy endpoints are gradually retired. Essential for teams modernizing legacy systems without risky big-bang rewrites.",,delivery/architecture/microservices-strangler-fig-migration
+microservices-service-discovery-architecture,microservices-service-discovery-architecture,Microservices Service Discovery Architecture,architecture,Architecture,handoff,architecture,handoff;architecture,3,16,3,service-discovery;consul;eureka;health-check;client-side-load-balancing;service-registry;dynamic-routing;architecture-diagram,"A service discovery architecture diagram with Consul or Eureka registry, client-side load balancing, health check heartbeats, and automatic instance registration and deregistration. This template visualizes how microservices dynamically locate each other without hardcoded endpoints, enabling elastic scaling and self-healing infrastructure. Key for platform teams building resilient service-to-service communication.",,handoff/architecture/microservices-service-discovery-architecture
+microservices-sidecar-pattern-architecture,microservices-sidecar-pattern-architecture,Microservices Sidecar Pattern Architecture,architecture,Architecture,mcp,architecture;patterns,mcp;architecture;patterns,4,13,3,sidecar-pattern;envoy-proxy;kubernetes;container-pattern;observability;control-plane;cloud-native;architecture-diagram,"A sidecar pattern architecture diagram showing Envoy proxy, log collector, and config watcher sidecars running alongside application containers in a Kubernetes pod, with a control plane managing configuration. This template demonstrates how auxiliary concerns like logging, monitoring, and configuration are deployed as co-located containers. Foundational for teams adopting cloud-native container orchestration patterns.",,mcp/architecture/microservices-sidecar-pattern-architecture
+microservices-backend-for-frontend-architecture,microservices-backend-for-frontend-architecture,Microservices Backend-for-Frontend (BFF) Architecture,architecture,Architecture,architecture,patterns,architecture;patterns,3,12,3,backend-for-frontend;bff-pattern;mobile-api;web-api;api-aggregation;payload-optimization;microservices;architecture-diagram,"A Backend-for-Frontend architecture diagram with separate BFF layers for web and mobile clients, each optimizing API responses for their specific platform while sharing common backend microservices. This template shows how to avoid one-size-fits-all APIs by tailoring data aggregation and payload optimization per client type. Recommended for teams serving multiple frontend platforms from a shared microservices backend.",,architecture/architecture/microservices-backend-for-frontend-architecture
+event-driven-publish-subscribe-architecture,event-driven-publish-subscribe-architecture,Event-Driven Publish-Subscribe Architecture,architecture,Architecture,architecture,,architecture,4,17,3,publish-subscribe;event-driven;kafka;rabbitmq;message-broker;fan-out;dead-letter-queue;architecture-diagram,"An event-driven publish-subscribe architecture diagram with Kafka or RabbitMQ message broker, event serialization, topic partitioning, fan-out delivery to multiple consumers, and dead letter queue error handling. This template models the foundational async messaging pattern where producers and consumers are fully decoupled through a message broker. Essential for architects building loosely coupled, scalable event-driven systems.",,architecture/architecture/event-driven-publish-subscribe-architecture
+event-driven-event-sourcing-architecture,event-driven-event-sourcing-architecture,Event-Driven Event Sourcing Architecture,architecture,Architecture,architecture,,architecture,4,18,4,event-sourcing;immutable-events;event-store;projections;snapshot;aggregate;temporal-query;architecture-diagram,"An event sourcing architecture diagram where all state changes are stored as an immutable sequence of domain events, with read projections built from the event stream and snapshot optimization for fast aggregate loading. This template shows how event sourcing eliminates data loss by preserving the complete history of every state transition. Critical for systems requiring full audit trails, temporal queries, and event replay capabilities.",,architecture/architecture/event-driven-event-sourcing-architecture
+event-driven-cqrs-with-event-store-architecture,event-driven-cqrs-with-event-store-architecture,Event-Driven CQRS with Event Store Architecture,architecture,Architecture,architecture,,architecture,4,18,4,cqrs;event-store;command-query-separation;read-model;write-model;projector;eventual-consistency;architecture-diagram,"A CQRS architecture diagram combining separate command and query APIs with an event bus for asynchronous read model synchronization, including projectors that build denormalized views from domain events. This template demonstrates the full CQRS+ES stack where writes go through domain validation and reads are served from optimized materialized views. Ideal for high-throughput systems where read and write workloads have fundamentally different scaling requirements.",,architecture/architecture/event-driven-cqrs-with-event-store-architecture
+event-driven-choreography-architecture,event-driven-choreography-architecture,Event-Driven Choreography Architecture,architecture,Architecture,architecture,patterns,architecture;patterns,4,19,5,choreography;event-driven;decentralized-coordination;domain-events;microservices;autonomous-services;pub-sub;architecture-diagram,"An event-driven choreography architecture diagram where microservices coordinate through events without a central orchestrator, with Order, Payment, Inventory, and Shipping services reacting to each other's domain events. This template models the decentralized coordination pattern where each service knows only its own responsibilities and publishes events for others to consume. Best for teams favoring autonomous services over centralized workflow control.",,architecture/architecture/event-driven-choreography-architecture
+event-driven-event-streaming-pipeline-architecture,event-driven-event-streaming-pipeline-architecture,Event-Driven Streaming Pipeline Architecture,architecture,Architecture,delivery,architecture,delivery;architecture,4,18,4,event-streaming;kafka;apache-flink;stream-processing;real-time-analytics;iot;data-pipeline;architecture-diagram,"A real-time event streaming pipeline architecture diagram with IoT sensors, application logs, and clickstream data flowing through Kafka into Apache Flink for window aggregation, anomaly detection, and multi-sink output to data lakes and dashboards. This template visualizes end-to-end stream processing from ingestion through transformation to storage and alerting. Essential for data engineers building real-time analytics and monitoring platforms.",,delivery/architecture/event-driven-event-streaming-pipeline-architecture
+event-driven-domain-events-architecture,event-driven-domain-events-architecture,Event-Driven Domain Events Architecture,architecture,Architecture,security,architecture,security;architecture,4,17,4,domain-events;ddd;aggregate-root;bounded-context;event-dispatcher;integration-events;domain-driven-design;architecture-diagram,"A domain events architecture diagram showing how aggregate roots raise domain events that are dispatched both in-process to local handlers and cross-boundary to integration event consumers in other bounded contexts. This template models the DDD event pattern where domain logic triggers side effects through a clean event dispatcher, maintaining separation between domain and infrastructure concerns. Key for teams implementing Domain-Driven Design with event-based integration.",,security/architecture/event-driven-domain-events-architecture
+event-driven-cdc-change-data-capture-architecture,event-driven-cdc-change-data-capture-architecture,Event-Driven CDC (Change Data Capture) Architecture,architecture,Architecture,architecture,,architecture,4,17,4,change-data-capture;cdc;debezium;transaction-log;kafka-connect;data-synchronization;dual-write;architecture-diagram,"A Change Data Capture architecture diagram using Debezium to tail database transaction logs and publish change events to Kafka, feeding downstream consumers that update search indexes, invalidate caches, load data warehouses, and write audit logs. This template shows how CDC eliminates dual-write problems by capturing changes at the database level without modifying application code. Critical for data synchronization across heterogeneous systems.",,architecture/architecture/event-driven-cdc-change-data-capture-architecture
+event-driven-dead-letter-queue-architecture,event-driven-dead-letter-queue-architecture,Event-Driven Dead Letter Queue Architecture,architecture,Architecture,incident,compliance;architecture;patterns,incident;compliance;architecture;patterns,3,16,3,dead-letter-queue;dlq;retry-policy;message-processing;error-handling;operations-alerting;message-reliability;architecture-diagram,"A dead letter queue architecture diagram with retry policies, exponential backoff, max retry thresholds, DLQ routing for failed messages, operations alerting, and manual reprocessing workflows. This template models the critical error handling pattern for asynchronous messaging systems, ensuring no message is silently lost when processing fails. Essential for building reliable event-driven systems with proper failure recovery mechanisms.",,incident/architecture/event-driven-dead-letter-queue-architecture
+cqrs-read-write-separation-architecture,cqrs-read-write-separation-architecture,CQRS Read-Write Separation Architecture,architecture,Architecture,architecture,,architecture,4,18,4,cqrs;read-write-separation;command-query;postgresql;redis;elasticsearch;read-model-sync;architecture-diagram,"A CQRS read-write separation architecture diagram with dedicated command and query paths, PostgreSQL for writes, Redis or Elasticsearch for optimized reads, and an event-driven synchronization layer with lag monitoring. This template demonstrates the core CQRS principle of separating read and write models to independently scale and optimize each path. Ideal for applications with asymmetric read/write ratios where query performance is critical.",,architecture/architecture/cqrs-read-write-separation-architecture
+cqrs-materialized-view-architecture,cqrs-materialized-view-architecture,CQRS Materialized View Architecture,architecture,Architecture,architecture,,architecture,4,18,4,materialized-view;cqrs;projectors;read-model;denormalization;query-optimization;event-stream;architecture-diagram,"A CQRS materialized view architecture diagram with multiple projectors building purpose-specific read models: order summaries, customer dashboards, analytics cubes, and search indexes, all fed from a single event stream. This template shows how to create multiple optimized query views from the same write events, each tailored to a specific use case with sub-millisecond read latency. Perfect for systems requiring diverse query patterns from a single data source.",,architecture/architecture/cqrs-materialized-view-architecture
+cqrs-task-based-ui-architecture,cqrs-task-based-ui-architecture,CQRS Task-Based UI Architecture,architecture,Architecture,patterns,,patterns,4,19,4,task-based-ui;cqrs;optimistic-update;websocket;command-pattern;idempotency;reactive-ui;architecture-diagram,"A CQRS task-based UI architecture diagram where the frontend captures user intent as explicit commands, submits them asynchronously with optimistic updates, and receives real-time confirmations via WebSocket when the read model is synchronized. This template models the modern UI pattern that replaces CRUD forms with intent-driven commands, enabling responsive user experiences with eventual consistency. Recommended for teams building reactive frontends on CQRS backends.",,patterns/architecture/cqrs-task-based-ui-architecture
+serverless-api-backend-architecture,serverless-api-backend-architecture,Serverless API Backend Architecture,architecture,Architecture,mcp,architecture,mcp;architecture,3,15,3,serverless;aws-lambda;api-gateway;dynamodb;cloud-architecture;auto-scaling;pay-per-use;architecture-diagram,"A serverless API backend architecture diagram with API Gateway, Lambda authorizer functions, business logic functions, and managed cloud services including DynamoDB, S3, SQS, and SNS for a fully managed, auto-scaling backend. This template models the serverless-first approach where infrastructure management is eliminated entirely, with pay-per-invocation pricing and automatic scaling to zero. Essential for startups and teams building cost-efficient, event-driven API backends.",,mcp/architecture/serverless-api-backend-architecture
+serverless-event-processing-architecture,serverless-event-processing-architecture,Serverless Event Processing Architecture,architecture,Architecture,architecture,,architecture,4,17,4,serverless;event-processing;step-functions;lambda-triggers;sqs;s3-events;dynamodb-streams;architecture-diagram,"A serverless event processing architecture diagram with S3, DynamoDB Streams, API Gateway, and CloudWatch triggers invoking Lambda functions, orchestrated by Step Functions with fan-out via SQS and dead letter queue error handling. This template shows how to build complex event processing pipelines entirely from managed serverless components, with no servers to provision or manage. Ideal for data processing workflows that need elastic scaling and built-in fault tolerance.",,architecture/architecture/serverless-event-processing-architecture
+serverless-step-functions-orchestration-architecture,serverless-step-functions-orchestration-architecture,Serverless Step Functions Orchestration Architecture,architecture,Architecture,incident,ai-orchestration;architecture;patterns,incident;ai-orchestration;architecture;patterns,4,17,3,step-functions;serverless-orchestration;state-machine;workflow-automation;callback-pattern;compensation;aws;architecture-diagram,"An AWS Step Functions orchestration architecture diagram with state machine workflows including choice states, parallel processing, wait-for-callback patterns, and compensation rollback for failed steps. This template models serverless workflow orchestration where complex multi-step processes are defined as state machines with built-in error handling and retry logic. Critical for teams building reliable serverless workflows that require human approval or long-running processes.",,incident/architecture/serverless-step-functions-orchestration-architecture
+serverless-edge-computing-architecture,serverless-edge-computing-architecture,Serverless Edge Computing Architecture,architecture,Architecture,handoff,architecture,handoff;architecture,3,15,3,edge-computing;lambda-at-edge;cloudfront;cloudflare;cdn;geo-routing;cache-strategy;architecture-diagram,"A serverless edge computing architecture diagram with CloudFront or Cloudflare edge locations, Lambda@Edge functions for A/B testing and geo-personalization, origin shield request collapsing, and cache-first response strategies. This template visualizes how computation moves to the network edge for ultra-low latency responses, with edge functions modifying requests and responses before they reach the origin. Essential for performance-critical applications serving global audiences.",,handoff/architecture/serverless-edge-computing-architecture
+serverless-data-pipeline-architecture,serverless-data-pipeline-architecture,Serverless Data Pipeline Architecture,architecture,Architecture,delivery,architecture,delivery;architecture,4,17,4,serverless-data-pipeline;kinesis;glue;athena;s3-data-lake;etl;sagemaker;architecture-diagram,"A serverless data pipeline architecture diagram with Kinesis ingestion, Lambda transformation functions, S3 data lake storage zones (raw and curated), Glue catalog registration, and Athena query engine feeding QuickSight dashboards and SageMaker ML models. This template models a complete serverless ETL pipeline from data ingestion through transformation, cataloging, and analytics without managing any infrastructure. Ideal for data teams building cost-effective analytics platforms.",,delivery/architecture/serverless-data-pipeline-architecture
+serverless-multi-cloud-architecture,serverless-multi-cloud-architecture,Serverless Multi-Cloud Architecture,architecture,Architecture,handoff,platform-reliability;architecture,handoff;platform-reliability;architecture,4,18,4,multi-cloud;aws;azure;cloud-failover;dns-routing;data-replication;vendor-independence;architecture-diagram,"A multi-cloud serverless architecture diagram with DNS-based traffic routing between AWS and Azure regions, automatic failover on health check failures, and bi-directional data replication with conflict resolution across cloud providers. This template models the multi-cloud strategy for maximum availability and vendor independence, using serverless services from both AWS (Lambda, DynamoDB) and Azure (Functions, Cosmos DB). Critical for enterprises requiring cloud provider redundancy.",,handoff/architecture/serverless-multi-cloud-architecture
+saga-orchestration-pattern-architecture,saga-orchestration-pattern-architecture,Saga Orchestration Pattern Architecture,architecture,Architecture,delivery,ai-orchestration;architecture;patterns,delivery;ai-orchestration;architecture;patterns,4,19,5,saga-pattern;orchestration;distributed-transaction;compensation;microservices;rollback;consistency;architecture-diagram,"A saga orchestration architecture diagram with a central orchestrator coordinating multi-step distributed transactions across Order, Inventory, and Payment services, with a dedicated compensation chain for rollback on failure. This template models the orchestration-based saga pattern where a single coordinator manages the transaction lifecycle and triggers compensating actions when any step fails. Essential for architects implementing reliable distributed transactions without two-phase commit.",,delivery/architecture/saga-orchestration-pattern-architecture
+saga-choreography-pattern-architecture,saga-choreography-pattern-architecture,Saga Choreography Pattern Architecture,architecture,Architecture,architecture,patterns,architecture;patterns,4,18,5,saga-choreography;event-driven-saga;decentralized;domain-events;compensation;autonomous-services;distributed-transaction;architecture-diagram,"A saga choreography architecture diagram where Order, Payment, and Inventory services coordinate through domain events without a central orchestrator, with each service publishing and subscribing to events that drive the transaction forward or trigger compensation. This template models the decentralized saga approach where services autonomously react to events, reducing single points of failure at the cost of increased complexity in tracking saga state. Best for teams preferring service autonomy over centralized control.",,architecture/architecture/saga-choreography-pattern-architecture
+saga-distributed-transaction-architecture,saga-distributed-transaction-architecture,Saga Distributed Transaction Architecture,architecture,Architecture,ai-orchestration,architecture,ai-orchestration;architecture,4,17,4,distributed-transaction;two-phase-commit;2pc;transaction-coordinator;consensus;strong-consistency;prepare-commit;architecture-diagram,"A distributed transaction architecture diagram implementing the two-phase commit protocol with a transaction coordinator sending prepare and commit messages to participating services, with global abort on any vote failure. This template visualizes the classic 2PC protocol used when strong consistency is required across multiple services, showing the prepare, vote, and commit/abort phases. Important for understanding distributed consensus trade-offs in microservices architectures.",,ai-orchestration/architecture/saga-distributed-transaction-architecture
+saga-travel-booking-architecture,saga-travel-booking-architecture,Saga Travel Booking Architecture,architecture,Architecture,ai-orchestration,architecture;patterns,ai-orchestration;architecture;patterns,4,17,5,saga-pattern;travel-booking;flight-reservation;hotel-booking;compensation;distributed-transaction;orchestration;architecture-diagram,"A travel booking saga architecture diagram orchestrating flight, hotel, and car rental reservations as a single distributed transaction, with automatic compensation to cancel all bookings if any reservation step fails. This template models the classic saga use case where multiple independent services must either all succeed or all roll back, ensuring travelers never end up with partial bookings. Perfect for demonstrating saga patterns with a real-world business scenario.",,ai-orchestration/architecture/saga-travel-booking-architecture
+saga-order-fulfillment-architecture,saga-order-fulfillment-architecture,Saga Order Fulfillment Architecture,architecture,Architecture,approval,billing;security;commerce-automation;architecture;patterns,approval;billing;security;commerce-automation;architecture;patterns,4,18,3,order-fulfillment;saga-pattern;e-commerce;payment-authorization;inventory-reservation;compensation-chain;distributed-transaction;architecture-diagram,"An order fulfillment saga architecture diagram with four sequential steps: customer verification, inventory reservation, payment authorization, and shipment creation, with a compensation chain that reverses completed steps on failure. This template models the end-to-end order lifecycle as a saga, showing how each service participates in the transaction and how compensating actions maintain data consistency. Ideal for e-commerce architects designing reliable order processing pipelines.",,approval/architecture/saga-order-fulfillment-architecture
+circuit-breaker-resilience-architecture,circuit-breaker-resilience-architecture,Circuit Breaker Resilience Architecture,architecture,Architecture,mcp,patterns,mcp;patterns,4,18,3,circuit-breaker;resilience;fault-tolerance;cascading-failure;half-open-state;fallback;state-machine;architecture-diagram,"A circuit breaker resilience architecture diagram showing the complete state machine with closed, open, and half-open states, failure threshold tracking, recovery timer, and fallback response strategies for protecting services from cascading failures. This template visualizes the circuit breaker pattern in detail, including how the breaker transitions between states based on success and failure counts. Essential for building fault-tolerant microservices that degrade gracefully under load.",,mcp/architecture/circuit-breaker-resilience-architecture
+bulkhead-isolation-architecture,bulkhead-isolation-architecture,Bulkhead Isolation Architecture,architecture,Architecture,handoff,patterns,handoff;patterns,4,18,4,bulkhead-pattern;resource-isolation;thread-pool;backpressure;fault-isolation;resilience;priority-routing;architecture-diagram,"A bulkhead isolation architecture diagram with separate thread pools for critical, standard, and batch workloads, each with independent connection pools, exhaustion detection, and backpressure strategies to prevent one workload from starving others. This template models the bulkhead pattern inspired by ship hull compartments, where resource isolation ensures that a failure or overload in one component cannot cascade to others. Critical for systems requiring guaranteed availability for high-priority operations.",,handoff/architecture/bulkhead-isolation-architecture
+retry-with-exponential-backoff-architecture,retry-with-exponential-backoff-architecture,Retry with Exponential Backoff Architecture,architecture,Architecture,patterns,,patterns,3,17,3,retry-pattern;exponential-backoff;jitter;transient-failure;resilience;error-handling;thundering-herd;architecture-diagram,"A retry with exponential backoff architecture diagram showing the complete retry policy engine with retryable vs non-retryable error classification, exponential delay calculation with jitter, max retry thresholds, and graceful exhaustion handling. This template models the essential resilience pattern for handling transient failures in distributed systems, preventing thundering herd problems through randomized backoff delays. Foundational for any service-to-service communication in cloud architectures.",,patterns/architecture/retry-with-exponential-backoff-architecture
+rate-limiter-architecture,rate-limiter-architecture,Rate Limiter Architecture,architecture,Architecture,architecture,,architecture,3,17,4,rate-limiter;token-bucket;sliding-window;redis;api-protection;throttling;distributed-rate-limiting;architecture-diagram,"A rate limiter architecture diagram implementing the token bucket algorithm with Redis-backed distributed counters, sliding window logs, API key identification, rate limit headers, and multi-node synchronization for consistent enforcement. This template shows how to protect APIs from abuse and ensure fair usage across clients, with proper HTTP 429 responses and Retry-After headers. Essential for API platform teams building production-grade rate limiting infrastructure.",,architecture/architecture/rate-limiter-architecture
+health-check-pattern-architecture,health-check-pattern-architecture,Health Check Pattern Architecture,architecture,Architecture,incident,security;patterns,incident;security;patterns,3,19,4,health-check;load-balancer;self-healing;monitoring;pagerduty;instance-rotation;deep-health-check;architecture-diagram,"A health check pattern architecture diagram with load balancer probes, deep health checks verifying database, cache, disk, and dependency status, automatic instance rotation, and alerting integration with PagerDuty for consecutive failures. This template models the health monitoring infrastructure that enables self-healing systems, where unhealthy instances are automatically removed from rotation and operations teams are alerted. Key for building production-ready services with proper observability.",,incident/architecture/health-check-pattern-architecture
+hexagonal-ports-adapters-architecture,hexagonal-ports-adapters-architecture,Hexagonal (Ports and Adapters) Architecture,architecture,Architecture,architecture,,architecture,4,16,4,hexagonal-architecture;ports-and-adapters;clean-architecture;dependency-inversion;domain-core;testability;technology-agnostic;architecture-diagram,"A hexagonal architecture diagram showing the clean separation between domain core, inbound adapters (REST, GraphQL, CLI, message consumers), outbound adapters (PostgreSQL, Stripe, email, Redis), and the port interfaces that connect them. This template visualizes the ports and adapters pattern where the domain core has zero dependencies on infrastructure, making it fully testable and technology-agnostic. Foundational for teams adopting clean architecture principles in their codebase.",,architecture/architecture/hexagonal-ports-adapters-architecture
+clean-architecture-layers,clean-architecture-layers,Clean Architecture Layers,architecture,Architecture,architecture,,architecture,3,16,4,clean-architecture;uncle-bob;dependency-rule;layered-architecture;use-cases;entities;interface-adapters;architecture-diagram,"A clean architecture layers diagram showing the four concentric layers: Entities (domain), Use Cases (application), Interface Adapters (controllers, presenters, repositories), and Frameworks & Drivers (web server, database, cloud SDK). This template models Uncle Bob's Clean Architecture with the dependency rule where inner layers never depend on outer layers, ensuring the domain model remains pure and framework-independent. Essential reference for software architects enforcing architectural boundaries.",,architecture/architecture/clean-architecture-layers
+domain-driven-design-bounded-contexts-architecture,domain-driven-design-bounded-contexts-architecture,Domain-Driven Design Bounded Contexts Architecture,architecture,Architecture,architecture,,architecture,4,18,5,domain-driven-design;bounded-context;anti-corruption-layer;context-map;shared-kernel;strategic-ddd;aggregate;architecture-diagram,"A DDD bounded contexts architecture diagram with Order, Customer, Shipping, and Billing contexts connected through an anti-corruption layer, shared kernel, and context map defining integration relationships. This template visualizes the strategic DDD patterns for decomposing complex domains into autonomous bounded contexts that communicate through well-defined integration events. Critical for architects applying Domain-Driven Design to large-scale enterprise systems.",,architecture/architecture/domain-driven-design-bounded-contexts-architecture
+api-composition-pattern-architecture,api-composition-pattern-architecture,API Composition Pattern Architecture,architecture,Architecture,incident,architecture;patterns,incident;architecture;patterns,3,16,3,api-composition;response-aggregation;fan-out;parallel-requests;timeout-handling;partial-response;microservices;architecture-diagram,"An API composition architecture diagram with a composer service that fans out parallel requests to multiple microservices, collects responses with timeout handling, and merges results into a single unified response with partial fallback support. This template models the API composition pattern used when a single client query requires data from multiple services, avoiding the need for direct service-to-service calls. Useful for teams building aggregation layers in microservices architectures.",,incident/architecture/api-composition-pattern-architecture
+outbox-pattern-reliable-messaging-architecture,outbox-pattern-reliable-messaging-architecture,Outbox Pattern for Reliable Messaging Architecture,architecture,Architecture,patterns,,patterns,4,18,4,outbox-pattern;transactional-outbox;reliable-messaging;dual-write;exactly-once;debezium;event-publishing;architecture-diagram,"A transactional outbox architecture diagram where domain writes and event publishing happen in the same database transaction, with a relay process polling the outbox table and publishing events to a message broker with guaranteed delivery. This template solves the dual-write problem where updating a database and publishing an event are not atomic, ensuring exactly-once event delivery without distributed transactions. Critical for event-driven architectures requiring reliable message publishing.",,patterns/architecture/outbox-pattern-reliable-messaging-architecture
+ambassador-pattern-architecture,ambassador-pattern-architecture,Ambassador Pattern Architecture,architecture,Architecture,mcp,patterns,mcp;patterns,3,15,3,ambassador-pattern;sidecar-proxy;external-api;retry-logic;circuit-breaker;metrics-collection;cross-cutting-concerns;architecture-diagram,"An ambassador pattern architecture diagram with a local proxy sidecar handling authentication header injection, circuit breaking, retry logic, and metrics collection for outbound requests to external third-party APIs. This template models the ambassador pattern where a helper service running alongside the application offloads cross-cutting concerns for external communication. Useful for teams integrating with unreliable third-party services that need resilience wrappers.",,mcp/architecture/ambassador-pattern-architecture
 graphql-federation-architecture,graphql-federation-architecture,GraphQL Federation Architecture,architecture,Architecture,mcp,,mcp,3,15,3,graphql-federation;apollo-gateway;subgraph;schema-stitching;query-plan;federated-api;graphql;architecture-diagram,"A GraphQL federation architecture diagram with an Apollo Gateway building query plans and fanning out to User, Product, and Review subgraphs, each owning its schema and database, with response stitching into a unified GraphQL result. This template models the federated GraphQL approach where multiple teams independently develop and deploy their subgraphs while clients see a single unified API. Ideal for organizations scaling GraphQL across multiple teams and services.",,mcp/architecture/graphql-federation-architecture
 zero-trust-security-architecture,zero-trust-security-architecture,Zero Trust Security Architecture,architecture,Architecture,security,,security,4,19,4,zero-trust;security-architecture;mfa;micro-segmentation;mtls;least-privilege;continuous-verification;architecture-diagram,"A zero trust security architecture diagram with device posture checks, MFA identity verification, risk-based policy decisions, short-lived JWT tokens, micro-segmentation, mTLS encryption, least-privilege access enforcement, and continuous monitoring. This template models the 'never trust, always verify' security paradigm where every request is authenticated and authorized regardless of network location. Essential for security architects implementing modern zero-trust frameworks in cloud-native environments.",,security/architecture/zero-trust-security-architecture
 multi-tenant-saas-architecture,multi-tenant-saas-architecture,Multi-Tenant SaaS Architecture,architecture,Architecture,security,delivery,security;delivery,4,17,4,multi-tenant;saas-architecture;tenant-isolation;row-level-security;shared-infrastructure;enterprise-tier;data-isolation;architecture-diagram,"A multi-tenant SaaS architecture diagram with tenant identification, tier-based routing (shared vs dedicated pools), row-level security, per-tenant encryption keys, and isolated backup strategies for standard and enterprise isolation models. This template models the architecture decisions for building SaaS platforms that serve multiple customers from shared infrastructure while maintaining strict data isolation. Critical for SaaS architects balancing cost efficiency with enterprise security requirements.",,security/architecture/multi-tenant-saas-architecture
 kubernetes-container-orchestration-architecture,kubernetes-container-orchestration-architecture,Kubernetes Container Orchestration Architecture,architecture,Architecture,ai-orchestration,,ai-orchestration,4,18,4,kubernetes;container-orchestration;k8s;control-plane;worker-node;ingress;persistent-storage;architecture-diagram,"A Kubernetes container orchestration architecture diagram showing the control plane (API Server, etcd, Scheduler, Controller Manager), worker nodes (Kubelet, container runtime, kube-proxy, pods), networking layer (Ingress, Network Policy, Service Mesh), and persistent storage with CSI drivers. This template provides a comprehensive view of the Kubernetes architecture stack from control plane to storage layer. Foundational reference for DevOps engineers and platform teams managing Kubernetes clusters.",,ai-orchestration/architecture/kubernetes-container-orchestration-architecture
-data-mesh-architecture,data-mesh-architecture,Data Mesh Architecture,architecture,Architecture,uncategorized,,,4,17,4,data-mesh;domain-ownership;data-product;self-serve-data;federated-governance;data-platform;data-architecture;architecture-diagram,"A data mesh architecture diagram with domain-oriented data ownership across Sales, Marketing, and Finance domains, each exposing self-serve data products through APIs with quality SLAs, governed by a federated data platform with a shared catalog and cross-domain query engine. This template models the paradigm shift from centralized data teams to domain-owned data products, applying microservices principles to data architecture. Essential for organizations scaling data operations beyond centralized data warehouse bottlenecks.",,uncategorized/architecture/data-mesh-architecture
+data-mesh-architecture,data-mesh-architecture,Data Mesh Architecture,architecture,Architecture,architecture,,architecture,4,17,4,data-mesh;domain-ownership;data-product;self-serve-data;federated-governance;data-platform;data-architecture;architecture-diagram,"A data mesh architecture diagram with domain-oriented data ownership across Sales, Marketing, and Finance domains, each exposing self-serve data products through APIs with quality SLAs, governed by a federated data platform with a shared catalog and cross-domain query engine. This template models the paradigm shift from centralized data teams to domain-owned data products, applying microservices principles to data architecture. Essential for organizations scaling data operations beyond centralized data warehouse bottlenecks.",,architecture/architecture/data-mesh-architecture
 cell-based-architecture,cell-based-architecture,Cell-Based Architecture,architecture,Architecture,handoff,,handoff,4,20,4,cell-based-architecture;blast-radius;geographic-routing;fault-isolation;independent-cells;cross-cell-replication;hyperscale;architecture-diagram,"A cell-based architecture diagram with geographic routing to independent, self-contained cells (US-East, EU-West), each with its own gateway, compute, database, cache, and message queue, plus shared services for cross-cell replication and global configuration. This template models the cell architecture pattern used by hyperscale systems to achieve blast radius isolation, where failures in one cell cannot affect users in another. Key for architects designing systems that require extreme availability and fault isolation.",,handoff/architecture/cell-based-architecture
-observability-three-pillars-architecture,observability-three-pillars-architecture,Observability Three Pillars Architecture,architecture,Architecture,uncategorized,,,4,17,4,observability;three-pillars;opentelemetry;prometheus;jaeger;loki;grafana;slo-sli;architecture-diagram,"An observability architecture diagram implementing the three pillars (metrics, traces, logs) with OpenTelemetry SDK instrumentation, OTLP collector pipeline, Prometheus, Jaeger, and Loki backends, Grafana dashboards, SLO/SLI tracking, and PagerDuty alerting integration. This template provides a complete observability stack reference showing how telemetry data flows from application instrumentation through collection, storage, visualization, and incident response. Essential for SRE teams building production monitoring infrastructure.",,uncategorized/architecture/observability-three-pillars-architecture
+observability-three-pillars-architecture,observability-three-pillars-architecture,Observability Three Pillars Architecture,architecture,Architecture,architecture,,architecture,4,17,4,observability;three-pillars;opentelemetry;prometheus;jaeger;loki;grafana;slo-sli;architecture-diagram,"An observability architecture diagram implementing the three pillars (metrics, traces, logs) with OpenTelemetry SDK instrumentation, OTLP collector pipeline, Prometheus, Jaeger, and Loki backends, Grafana dashboards, SLO/SLI tracking, and PagerDuty alerting integration. This template provides a complete observability stack reference showing how telemetry data flows from application instrumentation through collection, storage, visualization, and incident response. Essential for SRE teams building production monitoring infrastructure.",,architecture/architecture/observability-three-pillars-architecture
 gitops-deployment-architecture,gitops-deployment-architecture,GitOps Deployment Architecture,architecture,Architecture,delivery,,delivery,4,19,4,gitops;argocd;flux;kubernetes-deployment;declarative-infrastructure;drift-detection;rolling-update;architecture-diagram,"A GitOps deployment architecture diagram with developer Git workflow, CI/CD pipeline building and pushing container images, ArgoCD or Flux detecting Git manifest changes, drift detection, automatic cluster synchronization, and rolling update deployment to Kubernetes. This template models the GitOps paradigm where Git is the single source of truth for both application code and infrastructure state, enabling declarative, auditable, and reproducible deployments. Critical for teams adopting GitOps practices for Kubernetes deployments.",,delivery/architecture/gitops-deployment-architecture
 ai-native-single-agent-architecture,ai-native-single-agent-architecture,AI-Native Single Agent Architecture,architecture,Architecture,agentic,ai-orchestration;mcp,agentic;ai-orchestration;mcp,2,11,3,ai-native;single-agent;agentic-ai;mcp;architecture-diagram,"A single-agent AI architecture where one agent handles everything: parsing requests, reasoning, calling tools via MCP, and generating responses. This is the default architecture for prototypes and simple automations—easy to debug but hits context-window limits quickly and is hard to parallelize. Ideal for MVPs and solo builders shipping fast.",,agentic/architecture/ai-native-single-agent-architecture
-ai-native-sequential-pipeline-architecture,ai-native-sequential-pipeline-architecture,AI-Native Sequential Pipeline Architecture,architecture,Architecture,delivery,agentic;ai-orchestration,delivery;agentic;ai-orchestration,2,7,2,ai-native;sequential-pipeline;agentic-ai;llm-microservices;architecture-diagram,"A sequential pipeline architecture chaining multiple agents in a fixed order (parse → enrich → analyze → format), which is a common 'LLM microservices' setup when each step can be isolated. This structure is often used in document processing and ETL-like workflows because each step is testable and predictable.",,delivery/architecture/ai-native-sequential-pipeline-architecture
+ai-native-sequential-pipeline-architecture,ai-native-sequential-pipeline-architecture,AI-Native Sequential Pipeline Architecture,architecture,Architecture,delivery,agentic;ai-orchestration;architecture,delivery;agentic;ai-orchestration;architecture,2,7,2,ai-native;sequential-pipeline;agentic-ai;llm-microservices;architecture-diagram,"A sequential pipeline architecture chaining multiple agents in a fixed order (parse → enrich → analyze → format), which is a common 'LLM microservices' setup when each step can be isolated. This structure is often used in document processing and ETL-like workflows because each step is testable and predictable.",,delivery/architecture/ai-native-sequential-pipeline-architecture
 ai-native-orchestrator-worker-architecture,ai-native-orchestrator-worker-architecture,AI-Native Orchestrator-Worker Architecture,architecture,Architecture,agentic,ai-orchestration,agentic;ai-orchestration,3,14,4,ai-native;orchestrator-worker;agentic-ai;langgraph;multi-agent;architecture-diagram,"An orchestrator-worker architecture where an orchestrator agent breaks a goal into subtasks, dispatches to specialized workers, then synthesizes a final response. This is the most common 'agent orchestration' architecture—powerful but the orchestrator can become a bottleneck as the number of workers grows. Frameworks like LangGraph focus on explicit routing/state to manage this.",,agentic/architecture/ai-native-orchestrator-worker-architecture
 ai-native-hierarchical-architecture,ai-native-hierarchical-architecture,AI-Native Hierarchical Architecture,architecture,Architecture,agentic,ai-orchestration,agentic;ai-orchestration,4,16,4,ai-native;hierarchical;agentic-ai;enterprise;multi-agent;architecture-diagram,"A hierarchical multi-agent architecture that scales orchestration by stacking supervisors and team leads (a tree structure), which mirrors enterprise org structures and helps partition context. This is the 'enterprise-grade agentic AI architecture' when a single orchestrator cannot manage all workers directly. Ideal for large enterprises and multi-domain workflows.",,agentic/architecture/ai-native-hierarchical-architecture
 ai-native-parallel-fan-out-architecture,ai-native-parallel-fan-out-architecture,AI-Native Parallel Fan-Out Architecture,architecture,Architecture,delivery,agentic;ai-orchestration,delivery;agentic;ai-orchestration,3,11,2,ai-native;parallel-fan-out;agentic-ai;map-reduce;ci-cd;architecture-diagram,"A parallel fan-out architecture that runs multiple agents simultaneously on independent checks (style, security, performance) and then merges results. This is a standard multi-agent design approach for throughput, mapping cleanly to CI/CD, incident response, and research. Fan-in reconciliation becomes the subtle part.",,delivery/architecture/ai-native-parallel-fan-out-architecture
-ai-native-event-driven-kafka-architecture,ai-native-event-driven-kafka-architecture,AI-Native Event-Driven Kafka Architecture,architecture,Architecture,agentic,ai-orchestration;mcp,agentic;ai-orchestration;mcp,3,12,5,ai-native;event-driven;agentic-ai;kafka;pub-sub;agent-mesh;architecture-diagram,"An event-driven agentic AI architecture that replaces the central orchestrator with Kafka/PubSub topics: agents subscribe, react, and publish new events. This aligns multi-agent systems with proven microservices choreography and is ideal for real-time, high-throughput systems and 'agent mesh' setups.",,agentic/architecture/ai-native-event-driven-kafka-architecture
+ai-native-event-driven-kafka-architecture,ai-native-event-driven-kafka-architecture,AI-Native Event-Driven Kafka Architecture,architecture,Architecture,agentic,ai-orchestration;mcp;architecture;patterns,agentic;ai-orchestration;mcp;architecture;patterns,3,12,5,ai-native;event-driven;agentic-ai;kafka;pub-sub;agent-mesh;architecture-diagram,"An event-driven agentic AI architecture that replaces the central orchestrator with Kafka/PubSub topics: agents subscribe, react, and publish new events. This aligns multi-agent systems with proven microservices choreography and is ideal for real-time, high-throughput systems and 'agent mesh' setups.",,agentic/architecture/ai-native-event-driven-kafka-architecture
 ai-native-generator-critic-architecture,ai-native-generator-critic-architecture,AI-Native Generator-Critic Architecture,architecture,Architecture,agentic,ai-orchestration,agentic;ai-orchestration,3,9,3,ai-native;generator-critic;agentic-ai;tournament-mode;multi-agent;architecture-diagram,"A competitive / generator-critic architecture where multiple generators produce independent answers, then an evaluator agent scores and selects the best output. This approach improves quality and reduces single-model brittleness. It's costlier (multiple LLM calls) but pays off when correctness or creativity matters more than latency.",,agentic/architecture/ai-native-generator-critic-architecture
-event-driven-notification-hub-architecture,event-driven-notification-hub-architecture,Event-Driven Notification Hub Architecture,architecture,Architecture,uncategorized,,,4,20,3,notification-hub;multi-channel;event-driven;sendgrid;firebase-cloud-messaging;twilio;delivery-tracking;architecture-diagram,"An event-driven notification hub architecture diagram with multi-source event ingestion, template-based message rendering, user preference routing across email (SendGrid/SES), push (FCM), SMS (Twilio), and Slack channels, with delivery tracking and retry mechanisms. This template models a centralized notification system that decouples business services from delivery infrastructure, supporting multi-channel communication with user-controlled preferences. Ideal for platform teams building scalable notification infrastructure.",,uncategorized/architecture/event-driven-notification-hub-architecture
+event-driven-notification-hub-architecture,event-driven-notification-hub-architecture,Event-Driven Notification Hub Architecture,architecture,Architecture,architecture,,architecture,4,20,3,notification-hub;multi-channel;event-driven;sendgrid;firebase-cloud-messaging;twilio;delivery-tracking;architecture-diagram,"An event-driven notification hub architecture diagram with multi-source event ingestion, template-based message rendering, user preference routing across email (SendGrid/SES), push (FCM), SMS (Twilio), and Slack channels, with delivery tracking and retry mechanisms. This template models a centralized notification system that decouples business services from delivery infrastructure, supporting multi-channel communication with user-controlled preferences. Ideal for platform teams building scalable notification infrastructure.",,architecture/architecture/event-driven-notification-hub-architecture
 agentic-supervisor-worker,agentic-supervisor-worker,Agentic Supervisor-Worker Architecture,architecture,Architecture,agentic,,agentic,3,10,4,agentic;supervisor-worker;multi-agent;orchestrator;architecture-diagram;ai-team,"A supervisor-worker multi-agent architecture where an orchestrator agent receives a high-level goal, breaks it into subtasks, delegates each to specialist worker agents (researcher, writer, QA), monitors execution, handles failures, and synthesizes results. The orchestrator manages but does not execute tasks itself.",,agentic/architecture/agentic-supervisor-worker
 agentic-sequential-pipeline,agentic-sequential-pipeline,Agentic Sequential Pipeline Architecture,architecture,Architecture,delivery,agentic;ai-orchestration,delivery;agentic;ai-orchestration,2,5,5,agentic;sequential-pipeline;multi-agent;assembly-line;architecture-diagram;ai-team,"A sequential pipeline multi-agent architecture where agents are arranged in a strict sequence. Each agent transforms or enriches the output of the previous one, then passes it forward. No central orchestrator — the flow is deterministic like an assembly line.",,delivery/architecture/agentic-sequential-pipeline
 agentic-swarm,agentic-swarm,Agentic Swarm Architecture,architecture,Architecture,agentic,,agentic,3,6,5,agentic;swarm;multi-agent;parallel;aggregator;architecture-diagram;ai-team,"A swarm multi-agent architecture where multiple agents work on the same or related tasks simultaneously, with no central coordinator. Their outputs are then aggregated, voted on, or merged by a dedicated aggregator node. Agents may compete — the best output wins.",,agentic/architecture/agentic-swarm
@@ -226,13 +267,13 @@ ai-orchestration-sequential-pipeline,ai-orchestration-sequential-pipeline,AI Orc
 ai-orchestration-orchestrator-worker,ai-orchestration-orchestrator-worker,AI Orchestration - Orchestrator-Worker,architecture,Architecture,agentic,ai-orchestration,agentic;ai-orchestration,3,15,5,ai-native;orchestrator-worker;conductor;multi-agent;architecture-diagram;orchestration,"A conductor-style architecture where one orchestrator agent receives a complex task, breaks it into subtasks, dispatches each to specialist worker agents (research, code, review), collects results, and synthesizes the final answer. Best for complex multi-step tasks with dynamic decomposition.",,agentic/architecture/ai-orchestration-orchestrator-worker
 ai-orchestration-hierarchical,ai-orchestration-hierarchical,AI Orchestration - Hierarchical (Org Chart),architecture,Architecture,agentic,ai-orchestration,agentic;ai-orchestration,4,17,5,ai-native;hierarchical;org-chart;enterprise;multi-agent;architecture-diagram;orchestration,"An org-chart architecture with multi-level structure. A top-level supervisor manages team leads, who each manage their own pool of specialist workers. Teams within teams. Best for enterprise-scale automation with 10+ specialized agents spanning multiple domains.",,agentic/architecture/ai-orchestration-hierarchical
 ai-orchestration-parallel-fan-out,ai-orchestration-parallel-fan-out,AI Orchestration - Parallel Fan-Out (Map-Reduce),architecture,Architecture,agentic,ai-orchestration,agentic;ai-orchestration,3,9,3,ai-native;parallel-fan-out;map-reduce;coordinator;multi-agent;architecture-diagram;orchestration,"A map-reduce style architecture where a coordinator fans out tasks to multiple parallel worker agents (style check, security audit, performance analysis), gathers all results, and makes an aggregate decision. Best for PR reviews, code reviews, and multi-dimensional analysis.",,agentic/architecture/ai-orchestration-parallel-fan-out
-ai-orchestration-event-driven-mesh,ai-orchestration-event-driven-mesh,AI Orchestration - Event-Driven Mesh (Kafka-First),architecture,Architecture,ai-orchestration,mcp,ai-orchestration;mcp,3,13,5,ai-native;event-driven;kafka;agent-mesh;pub-sub;architecture-diagram;orchestration,"An event-driven agent mesh architecture using a Kafka-style event broker. Multiple agents subscribe to topics (orders, alerts, analytics), process events independently, and publish results back to the bus. Best for real-time event processing and decoupled service architectures.",,ai-orchestration/architecture/ai-orchestration-event-driven-mesh
+ai-orchestration-event-driven-mesh,ai-orchestration-event-driven-mesh,AI Orchestration - Event-Driven Mesh (Kafka-First),architecture,Architecture,ai-orchestration,mcp;architecture;patterns,ai-orchestration;mcp;architecture;patterns,3,13,5,ai-native;event-driven;kafka;agent-mesh;pub-sub;architecture-diagram;orchestration,"An event-driven agent mesh architecture using a Kafka-style event broker. Multiple agents subscribe to topics (orders, alerts, analytics), process events independently, and publish results back to the bus. Best for real-time event processing and decoupled service architectures.",,ai-orchestration/architecture/ai-orchestration-event-driven-mesh
 ai-orchestration-competitive-generator-critic,ai-orchestration-competitive-generator-critic,AI Orchestration - Competitive Generator-Critic,architecture,Architecture,agentic,ai-orchestration,agentic;ai-orchestration,3,10,3,ai-native;competitive;generator-critic;tournament;multi-agent;architecture-diagram;orchestration,"A tournament-mode architecture where multiple generator agents produce independent outputs in parallel, then an evaluator agent scores and selects the best. Quality threshold checking with refinement loops. Best when correctness or creativity matters more than latency.",,agentic/architecture/ai-orchestration-competitive-generator-critic
 mcp-direct-connect,mcp-direct-connect,MCP Direct Connect Architecture,architecture,DevOps,mcp,,mcp,1,6,2,mcp;direct-connect;stdio;http;architecture-diagram;production-grade,"The simplest MCP pattern — direct connection between host application and MCP server over stdio or HTTP. No extra hops, lowest latency, easiest debugging. Perfect for MVPs, hackathons, and single-team setups where security governance is not yet a concern.",,mcp/devops/mcp-direct-connect
 mcp-gateway-proxy,mcp-gateway-proxy,MCP Gateway Proxy Architecture,architecture,DevOps,security,compliance;mcp,security;compliance;mcp,3,7,3,mcp;gateway;proxy;oauth;rate-limiting;audit;architecture-diagram;production-grade,"An API gateway pattern that sits between agents and MCP servers to handle authentication, rate limits, and auditing. The gateway enforces OAuth 2.0, SAML, SSO, tool-level rate limiting, and team-based quotas. Essential for multi-team or multi-tenant MCP deployments.",,security/devops/mcp-gateway-proxy
 mcp-tool-router,mcp-tool-router,MCP Tool Router Architecture,architecture,DevOps,handoff,mcp,handoff;mcp,3,8,4,mcp;tool-router;semantic-routing;embeddings;token-optimization;architecture-diagram;production-grade,A routing pattern that puts a semantic router in front of MCP tools so the LLM only sees the subset it needs. Uses vector embeddings and cosine similarity to match user intent to tools dynamically. Achieves up to 96% reduction in input tokens when dealing with large tool catalogs.,,handoff/devops/mcp-tool-router
 mcp-agent-mesh,mcp-agent-mesh,MCP Agent Mesh Architecture,architecture,DevOps,agentic,mcp,agentic;mcp,4,10,4,mcp;agent-mesh;shared-context;multi-agent;broker;architecture-diagram;production-grade,"A multi-agent mesh pattern where agents communicate through a shared context broker backed by MCP. Enables coordinated tool access and state synchronization across multiple specialized agents (planner, coder, reviewer, operator). Supports both orchestrated and choreographed interaction patterns.",,agentic/devops/mcp-agent-mesh
-mcp-circuit-breaker,mcp-circuit-breaker,MCP Circuit Breaker Architecture,architecture,DevOps,mcp,,mcp,3,9,3,mcp;circuit-breaker;resilience;fault-tolerance;health-check;architecture-diagram;production-grade,"A resilience pattern that wraps MCP calls with health-aware gates using three states: Closed (normal), Open (failures detected, fast-fail), and Half-Open (testing recovery). Prevents cascading failures when tools become unresponsive. Essential for production-grade reliability.",,mcp/devops/mcp-circuit-breaker
+mcp-circuit-breaker,mcp-circuit-breaker,MCP Circuit Breaker Architecture,architecture,DevOps,mcp,patterns,mcp;patterns,3,9,3,mcp;circuit-breaker;resilience;fault-tolerance;health-check;architecture-diagram;production-grade,"A resilience pattern that wraps MCP calls with health-aware gates using three states: Closed (normal), Open (failures detected, fast-fail), and Half-Open (testing recovery). Prevents cascading failures when tools become unresponsive. Essential for production-grade reliability.",,mcp/devops/mcp-circuit-breaker
 mcp-context-proxy,mcp-context-proxy,MCP Context Proxy Architecture,architecture,DevOps,mcp,,mcp,3,7,3,mcp;context-proxy;caching;compression;token-optimization;architecture-diagram;production-grade,"A caching and compression layer that sits between agents and MCP servers, intercepting redundant context requests before they hit the wire. Uses TTL-based cache invalidation, Brotli compression, and semantic caching. Can achieve up to 95%+ token reduction and significantly lower LLM bills.",,mcp/devops/mcp-context-proxy
 context-session-memory,context-session-memory,Context Management - Session Memory,architecture,Architecture,context-management,,context-management,2,9,3,context-management;session-memory;short-term;memory;architecture-diagram,"Short-term context pattern where the channel sends new messages plus recent history. The agent runtime merges that with local session state, assembles the prompt, and persists the response back into history. Simple but cost and latency grow with history length.",,context-management/architecture/context-session-memory
 context-rolling-summary-memory,context-rolling-summary-memory,Context Management - Rolling Summary Memory,architecture,Architecture,context-management,,context-management,3,8,4,context-management;rolling-summary;compression;memory;architecture-diagram,"Compressed history pattern that keeps full history for a while, then when a threshold is hit, summarizes the last chunk and replaces detailed turns with a shorter summary message. Dramatically reduces prompt size on long-running chats while maintaining gist continuity.",,context-management/architecture/context-rolling-summary-memory
@@ -241,3 +282,76 @@ context-semantic-memory,context-semantic-memory,Context Management - Semantic Me
 context-episodic-memory,context-episodic-memory,Context Management - Episodic Memory,architecture,Architecture,context-management,,context-management,3,11,4,context-management;episodic-memory;learning;experience;architecture-diagram,"Learning-from-experience pattern where every task run becomes an episode with input, actions, and outcome. Before tackling a new task, the agent fetches similar episodes and uses them as hints. Over time, the agent feels like it's learning instead of repeating the same failed plans.",,context-management/architecture/context-episodic-memory
 context-hybrid-retrieval-memory,context-hybrid-retrieval-memory,Context Management - Hybrid Retrieval Memory,architecture,Architecture,context-management,,context-management,4,11,5,context-management;hybrid-retrieval;semantic;keyword;recency;architecture-diagram,"Multi-modal retrieval pattern combining semantic search, exact/keyword search, and recency search in parallel. Results are merged and reranked into a single context set. Much higher recall because the agent can find both fuzzy references and exact entities. Essential for comprehensive knowledge retrieval.",,context-management/architecture/context-hybrid-retrieval-memory
 context-shared-memory,context-shared-memory,Context Management - Shared Memory,architecture,Architecture,agentic,context-management,agentic;context-management,3,9,4,context-management;shared-memory;multi-agent;orchestrator;architecture-diagram,"Multi-agent coordination pattern where an orchestrator breaks work into subtasks, specialist agents pull from and push to a shared state store, and the orchestrator composes the final answer from that shared state. Multi-agent setups feel coherent instead of each assistant having its own inconsistent memory.",,agentic/architecture/context-shared-memory
+claw-code-harness-architecture,claw-code-harness-architecture,Claw Code Harness Architecture,architecture,Architecture,ai-orchestration,mcp,ai-orchestration;mcp,4,17,4,Claw Code;Claude Code;Harness Engineering;AI Agent Architecture;MCP;Python Orchestration;Rust Runtime;LLM;Agent Runtime,"Claw Code harness architecture diagram showing the user loop, Python orchestration layer, Rust runtime, and external systems such as the LLM provider, file system, and MCP server.",,ai-orchestration/architecture/claw-code-harness-architecture
+zero-trust-agent-identity-pipeline,zero-trust-agent-identity-pipeline,Zero Trust Agent Identity Pipeline,architecture,Architecture,security,delivery;mcp,security;delivery;mcp,3,12,3,AI Agent Security;Zero Trust;Agent Identity;Non-Human Identity;NHI;OAuth 2.0 Token Exchange;OBO Token;SPIFFE;MCP;JWT,"Zero-trust AI agent identity architecture with JWT validation, scoped OBO token exchange, SPIFFE/SVID workload identity, and MCP tool authorization.",,security/architecture/zero-trust-agent-identity-pipeline
+mcp-zero-trust-boundary,mcp-zero-trust-boundary,MCP Zero-Trust Boundary,architecture,Architecture,security,mcp;agentic-security,security;mcp;agentic-security,3,12,3,MCP;Model Context Protocol;AI Agent Security;Zero Trust;MCP Security;Tool Sandbox;Sandbox;Prompt Injection;Secure Tool Calling,"MCP security gateway architecture that authenticates tool calls, routes execution into isolated sandboxes, sanitizes responses, and returns clean results to the AI agent.",,security/architecture/mcp-zero-trust-boundary
+runtime-permission-gating,runtime-permission-gating,Runtime Permission Gating,architecture,Architecture,security,compliance,security;compliance,3,11,3,AI Agent Security;Least Privilege;Permission Gating;AI Agent Permissions;JIT Access;Policy Engine;RBAC;ABAC;OPA;Cerbos,"Least-privilege AI agent architecture with policy-engine evaluation, just-in-time access, short-lived credentials, and action-scoped grants before tool execution.",,security/architecture/runtime-permission-gating
+risk-tiered-hitl,risk-tiered-hitl,Risk-Tiered Human-in-the-Loop,architecture,Architecture,approval,security;compliance,approval;security;compliance,4,14,4,Human in the Loop;HITL;AI Agent Security;AI Governance;Risk Policy;Approval Workflow;Audit Log;Human Approval,"Human-in-the-loop approval architecture that scores agent actions by risk, routes high-risk requests for review, and writes immutable audit records.",,approval/architecture/risk-tiered-hitl
+secure-multi-agent-communication,secure-multi-agent-communication,Secure Multi-Agent Communication,architecture,Architecture,security,agentic;mcp,security;agentic;mcp,4,20,4,Multi-Agent;AI Agent Security;Secure Multi-Agent;mTLS;API Gateway;Scoped Tokens;Agent-to-Agent Communication;A2A;Orchestrator;Worker Agent,"Multi-agent security architecture with scoped tokens, API gateway enforcement, mTLS-protected worker calls, and orchestrator-driven result aggregation.",,security/architecture/secure-multi-agent-communication
+openclaw-native-install-architecture,openclaw-native-install-architecture,OpenClaw Native Install Architecture,architecture,Architecture,delivery,,delivery,2,9,3,OpenClaw;AI Agent Deployment;Native Install;Local Install;Self-Hosted AI Agent;Web UI;Claude;GPT;Gemini,"OpenClaw deployment on your everyday machine with the gateway, workspace, and commercial LLM API connected locally through the web UI.",,delivery/architecture/openclaw-native-install-architecture
+openclaw-docker-isolated-architecture,openclaw-docker-isolated-architecture,OpenClaw Docker Isolated Architecture,architecture,Architecture,delivery,,delivery,2,7,3,OpenClaw;Docker;Docker Container;OpenClaw Docker;AI Agent Deployment;Self-Hosted AI Agent;Volume Mount;Local AI Agent,"OpenClaw Docker deployment with an isolated gateway runtime, mounted workspace and config volumes, and a commercial LLM API.",,delivery/architecture/openclaw-docker-isolated-architecture
+openclaw-dedicated-local-machine-architecture,openclaw-dedicated-local-machine-architecture,OpenClaw Dedicated Local Machine Architecture,architecture,Architecture,architecture,,architecture,2,7,3,OpenClaw;Mac Mini;Homelab;Dedicated Machine;Self-Hosted AI Agent;24/7 AI Agent;Telegram;Local Server,"OpenClaw architecture for a dedicated Mac Mini or homelab server with persistent workspace, agent state, and remote messaging access.",,architecture/architecture/openclaw-dedicated-local-machine-architecture
+openclaw-vps-self-managed-architecture,openclaw-vps-self-managed-architecture,OpenClaw VPS Self-Managed Architecture,architecture,Architecture,delivery,,delivery,2,7,3,OpenClaw;VPS;Self-Managed VPS;Cloud Deployment;Hetzner;DigitalOcean;Remote Access;SSH Tunnel,"Self-managed OpenClaw VPS deployment with gateway, workspace, firewall/auth layer, and commercial LLM provider access from any device.",,delivery/architecture/openclaw-vps-self-managed-architecture
+openclaw-managed-cloud-architecture,openclaw-managed-cloud-architecture,OpenClaw Managed Cloud Architecture,architecture,Architecture,delivery,,delivery,3,9,3,OpenClaw;Managed Cloud;Railway;Northflank;Cloud Deployment;AI Agent Hosting;One-Click Deploy;Hosted AI Agent,"Managed cloud OpenClaw deployment using platforms like Railway or Northflank with a hosted gateway, integrations, monitoring, and commercial LLM APIs.",,delivery/architecture/openclaw-managed-cloud-architecture
+openclaw-hybrid-cloud-local-nodes-architecture,openclaw-hybrid-cloud-local-nodes-architecture,OpenClaw Hybrid Cloud + Local Nodes Architecture,architecture,Architecture,delivery,mcp,delivery;mcp,4,10,4,OpenClaw;Hybrid Architecture;Cloud Gateway;Local Nodes;AI Agent Deployment;Remote AI Agent;WhatsApp;24/7 AI Agent,"Hybrid OpenClaw architecture with a cloud gateway, local nodes for device actions, persistent agent state, and commercial LLM provider calls.",,delivery/architecture/openclaw-hybrid-cloud-local-nodes-architecture
+incident-root-cause-prevention-workflow,incident-root-cause-prevention,Incident Root Cause & Prevention Workflow,workflow,Process Mapping,incident,compliance;process-mapping,incident;compliance;process-mapping,2,10,2,process-mapping;incident;root-cause;prevention;controls,"Incident response workflow that documents the current state, traces the root cause, validates controls and creates a prevention protocol before the case is closed.",,incident/process-mapping/incident-root-cause-prevention-workflow
+ownership-assignment-escalation-workflow,ownership-assignment-escalation,Ownership Assignment & Escalation Workflow,workflow,Process Mapping,handoff,process-mapping,handoff;process-mapping,2,12,2,process-mapping;ownership;escalation;assignment;blockers,"Work assignment workflow that names an accountable owner, checks for blockers, escalates to the manager and confirms the assignment with everyone involved.",,handoff/process-mapping/ownership-assignment-escalation-workflow
+handoff-readiness-checklist-workflow,handoff-readiness-checklist,Handoff Readiness Checklist Workflow,workflow,Process Mapping,handoff,approval;process-mapping,handoff;approval;process-mapping,2,10,2,process-mapping;handoff;checklist;approval;transition,Handoff workflow with a completeness gate: the handoff checklist must be fully met before the receiving team approves and work moves forward.,,handoff/process-mapping/handoff-readiness-checklist-workflow
+customer-service-escalation-workflow,customer-service-escalation,Customer Service Escalation Workflow,workflow,Process Mapping,handoff,support;process-mapping,handoff;support;process-mapping,2,11,2,process-mapping;support;escalation;service;tier-2,"Customer support workflow that applies the standard greeting and service protocol, then escalates to tier 2 when the standard path cannot resolve the request.",,handoff/process-mapping/customer-service-escalation-workflow
+process-documentation-knowledge-capture-workflow,process-documentation-knowledge-capture,Process Documentation & Knowledge Capture Workflow,workflow,Process Mapping,onboarding,process-mapping,onboarding;process-mapping,3,13,2,process-mapping;documentation;knowledge;onboarding;sop,"Knowledge capture workflow: document the current process steps, write the step-by-step guide, get it approved and track onboarding to completion.",,onboarding/process-mapping/process-documentation-knowledge-capture-workflow
+process-analysis-future-state-workflow,process-analysis-future-state,Process Analysis & Future State Workflow,workflow,Process Mapping,process-mapping,,process-mapping,2,12,2,process-mapping;process-analysis;future-state;bottlenecks;redesign,"Process redesign workflow that identifies bottlenecks, designs the future state, adjusts the design and deploys the technology solution on the new baseline.",,process-mapping/process-mapping/process-analysis-future-state-workflow
+work-tracking-dashboard-workflow,work-tracking-dashboard,Work Tracking Dashboard Workflow,workflow,Process Mapping,process-mapping,,process-mapping,2,12,2,process-mapping;tracking;dashboard;status;visibility,"Work visibility workflow: create the centralized tracking record, define status categories, keep the information current and publish it on a central dashboard.",,process-mapping/process-mapping/work-tracking-dashboard-workflow
+cross-department-customer-onboarding-workflow,cross-department-customer-onboarding,Cross-Department Customer Onboarding Workflow,workflow,Process Mapping,onboarding,process-mapping,onboarding;process-mapping,3,32,5,process-mapping;customer-onboarding;cross-functional;sales;legal;finance,"Five-lane customer onboarding workflow spanning sales, legal, finance, onboarding and the customer, with acceptance gates and a 30-day check-in before activation.",,onboarding/process-mapping/cross-department-customer-onboarding-workflow
+customer-onboarding-sales-handoff-workflow,customer-onboarding-sales-handoff,Customer Onboarding & Sales Handoff Workflow,workflow,Process Mapping,handoff,onboarding;process-mapping,handoff;onboarding;process-mapping,3,19,3,process-mapping;customer-onboarding;handoff;sales;kickoff,"Three-lane onboarding workflow where the sales team hands the closed deal to the onboarding specialist, who runs the kickoff and setup tasks with the customer.",,handoff/process-mapping/customer-onboarding-sales-handoff-workflow
+task-box-invoice-approval-workflow,task-box-invoice-approval,Task Box Invoice Approval Workflow,workflow,Process Mapping,approval,billing;process-mapping,approval;billing;process-mapping,2,10,1,process-mapping;task-boxes;invoice;approval;owner;system,"Task box diagram for invoice approval: owner, description and system on every step, from sale recording to payment, with a rejection loop back to the invoice draft.",,approval/process-mapping/task-box-invoice-approval-workflow
+fz-file-sequence-diagram-example,fz-file-sequence-diagram-example,FZ File Sequence Diagram Example,workflow,Diagram Authoring,diagram-authoring,security,diagram-authoring;security,1,4,2,flowzap-code;fz-file;diagrams-as-code;sequence-diagram,"The reference example from the .fz file announcement: a text-first sequence diagram with two lanes, four nodes and one labeled message, stored as a portable .fz file.",,diagram-authoring/diagram-authoring/fz-file-sequence-diagram-example
+n8n-json-workflow-as-flowzap-code,n8n-json-workflow-as-flowzap-code,n8n JSON Workflow as FlowZap Code,workflow,Diagram Authoring,diagram-authoring,security,diagram-authoring;security,2,11,1,n8n;flowzap-code;automation;json;conversion,"An n8n automation rendered as FlowZap Code: manual trigger, spreadsheet read, batch iteration, AI field mapping, PDF generation, email send, with success and error logging branches.",,diagram-authoring/diagram-authoring/n8n-json-workflow-as-flowzap-code
+mcp-server-order-fulfillment-example,mcp-server-order-fulfillment-example,MCP Server Order Fulfillment Example,workflow,Diagram Authoring,diagram-authoring,security;mcp,diagram-authoring;security;mcp,2,6,2,mcp;flowzap-code;shorthand-syntax;order-fulfillment,"Compact order fulfillment diagram generated through the FlowZap MCP server, written with the shorthand syntax: sales validation with a validity gate, then fulfillment processing and shipping.",,diagram-authoring/diagram-authoring/mcp-server-order-fulfillment-example
+ai-assisted-ecommerce-onboarding-workflow,ai-assisted-ecommerce-onboarding,AI-Assisted E-Commerce Onboarding Workflow,workflow,Diagram Authoring,diagram-authoring,onboarding;security;commerce-automation,diagram-authoring;onboarding;security;commerce-automation,2,10,2,flowzap-code;vibe-coding;ecommerce;ai-assistant;cart,"Vibe-coding example: a cart lane and an AI lane, where the assistant analyses the shopper profile, asks for missing details and adds the suggested products to the cart.",,diagram-authoring/diagram-authoring/ai-assisted-ecommerce-onboarding-workflow
+agent-sandbox-containment-workflow,agent-sandbox-containment,Agent Sandbox Containment Workflow,workflow,Agentic Security,agentic-security,security;agentic,agentic-security;security;agentic,2,8,2,agent-containment;sandbox;blast-radius;security;tool-call,"Layer 1 of the agent containment stack: every tool call executes in an ephemeral container, and any path outside the workspace is denied and logged as a security event.",,agentic-security/agentic-security/agent-sandbox-containment-workflow
+permission-gate-containment-workflow,permission-gate-containment,Permission Gate Containment Workflow,workflow,Agentic Security,agentic-security,security;agentic,agentic-security;security;agentic,2,8,2,agent-containment;permissions;whitelist;security;blast-radius,"Layer 2 of the agent containment stack: a permission gate checks the whitelist and path scope before execution, and aborts the call with a logged denial when the scope does not match.",,agentic-security/agentic-security/permission-gate-containment-workflow
+hitl-approval-containment-workflow,hitl-approval-containment,HITL Approval Containment Workflow,workflow,Agentic Security,agentic-security,approval;security;agentic,agentic-security;approval;security;agentic,2,8,2,agent-containment;hitl;human-approval;security;dangerous-operations,"Layer 3 of the agent containment stack: dangerous tool calls are suspended and sent to a human reviewer, who approves or aborts the operation before anything executes.",,agentic-security/agentic-security/hitl-approval-containment-workflow
+audit-logging-siem-containment-workflow,audit-logging-siem-containment,Audit Logging & SIEM Containment Workflow,workflow,Agentic Security,agentic-security,security;compliance;agentic,agentic-security;security;compliance;agentic,2,6,2,agent-containment;audit;siem;logging;secrets,"Layer 4 of the agent containment stack: arguments are sanitized, secrets stripped and the action trace written to the SIEM before execution continues.",,agentic-security/agentic-security/audit-logging-siem-containment-workflow
+four-layer-agent-containment-stack,four-layer-agent-containment-stack,Four-Layer Agent Containment Stack,workflow,Agentic Security,agentic-security,security;compliance;agentic,agentic-security;security;compliance;agentic,2,10,2,agent-containment;sandbox;permissions;hitl;audit;blast-radius,"The full containment stack in one diagram: sandbox, permission gate, HITL approval and SIEM audit applied in sequence around a single dangerous tool call.",,agentic-security/agentic-security/four-layer-agent-containment-stack
+patch-closure-proof-workflow,patch-closure-proof,Patch Closure Proof Workflow,workflow,Agentic Security,agentic-security,incident;security;agentic,agentic-security;incident;security;agentic,2,12,4,patch-management;closing-proof;remediation;assurance;incident,"Closing-proof workflow across detection, remediation and assurance: measure the fix rather than the reaction, rate the outage risk and refuse closure without evidence.",,agentic-security/agentic-security/patch-closure-proof-workflow
+artifact-provenance-verification-workflow,artifact-provenance-verification,Artifact Provenance Verification Workflow,workflow,Agentic Security,agentic-security,security;agentic,agentic-security;security;agentic,2,8,3,provenance;supply-chain;attestation;build;registry,"Build, provenance and registry lanes: an artifact is only accepted when its attestation matches the build that produced it, and a hijacked repo sends it back to build.",,agentic-security/agentic-security/artifact-provenance-verification-workflow
+independent-action-verification-workflow,independent-action-verification,Independent Action Verification Workflow,workflow,Agentic Security,agentic-security,security;compliance;agentic,agentic-security;security;compliance;agentic,2,8,3,closing-proof;verification;audit;agentic-security;hitl,"Rule 3 in practice: the agent that acts emits the action trace, a separate verification lane confirms the effect, and only a human closes the case.",,agentic-security/agentic-security/independent-action-verification-workflow
+agent-mandate-scope-enforcement-workflow,agent-mandate-scope-enforcement,Agent Mandate Scope Enforcement Workflow,workflow,Agentic Security,agentic-security,security;compliance;agentic,agentic-security;security;compliance;agentic,2,8,3,agent-identity;mandate;access-control;audit;consent,"Consent is not a mandate: a third-party agent's requested scope is compared to the customer mandate before read-only access is granted, and every access event is audited.",,agentic-security/agentic-security/agent-mandate-scope-enforcement-workflow
+problem-mind-map-credit-decision,problem-mind-map-credit-decision,Problem Mind Map — Credit Decision,workflow,Mindmap,mindmap,agentic;agentic-architecture,mindmap;agentic;agentic-architecture,3,32,1,mind-map;problem-mind-map;credit-decision;problem-first;agentic-architecture,"A problem mind map for an AI credit decision, mapping decisions, data, policies, actors, risks, constraints and open questions before any component is designed.",,mindmap/mindmap/problem-mind-map-credit-decision
+agent-generated-mind-map-incident-root-cause,agent-generated-mind-map-incident-root-cause,Agent-Generated Mind Map — Incident Root Cause,workflow,Mindmap,mindmap,incident;agentic;agentic-architecture,mindmap;incident;agentic;agentic-architecture,3,13,1,mind-map;agmm;explainability;incident;sre;agentic-architecture,"An AGMM example: an SRE agent outputs its API latency root-cause reasoning chain as an interactive mind map, reversing the Human-to-Machine explainability flow.",,mindmap/mindmap/agent-generated-mind-map-incident-root-cause
+agentic-taste-evaluation-loop,agentic-taste-evaluation-loop,Agentic Taste Evaluation Loop,workflow,Agentic Architecture,agentic-architecture,agentic,agentic-architecture;agentic,2,9,3,agentic-taste;llm-as-judge;agent-evaluation;interoperability;trajectory,"Legacy executor, LLM-as-judge evaluator and next-gen consumer: an evaluator scores the full trajectory, rejects structural sloppiness and forwards only validated payloads.",,agentic-architecture/agentic-architecture/agentic-taste-evaluation-loop
+reflection-loop-agent-self-improvement,reflection-loop-agent-self-improvement,Reflection Loop — Agent Self-Improvement,workflow,Agentic Architecture,agentic-architecture,agentic,agentic-architecture;agentic,3,22,4,reflexion;self-improvement;critic;orchestrator-worker;agent-frameworks,"The reflection loop: a worker drafts, a critic reviews the draft against the brief and the orchestrator only approves once the revision closes every gap.",,agentic-architecture/agentic-architecture/reflection-loop-agent-self-improvement
+memory-loop-agent-self-improvement,memory-loop-agent-self-improvement,Memory Loop — Agent Self-Improvement,workflow,Agentic Architecture,agentic-architecture,agentic;context-management,agentic-architecture;agentic;context-management,3,29,5,memory-management;self-improvement;planner;lessons-learned;agent-frameworks,"The memory loop: before planning, the planner queries the memory store for similar past lessons, then writes the new lesson back once the task is closed.",,agentic-architecture/agentic-architecture/memory-loop-agent-self-improvement
+evolution-loop-agent-self-improvement,evolution-loop-agent-self-improvement,Evolution Loop — Agent Self-Improvement,workflow,Agentic Architecture,agentic-architecture,agentic,agentic-architecture;agentic,3,24,5,evolution;benchmark;self-improvement;optimizer;agent-frameworks,"The evolution loop: an optimizer benchmarks candidate agents against the production baseline, keeps the best score and confirms persistence before promotion.",,agentic-architecture/agentic-architecture/evolution-loop-agent-self-improvement
+hermes-multi-tenant-isolation-architecture,hermes-multi-tenant-isolation-architecture,Hermes Multi-Tenant Isolation Architecture,workflow,Agentic Architecture,agentic-architecture,agentic;agentic-security,agentic-architecture;agentic;agentic-security,2,12,3,hermes;multi-tenant;isolation;profiles;sandboxing,"Shared host, per-client profiles and tool boundaries: how external clients reach their own Hermes workspaces without seeing another tenant's tools or data.",,agentic-architecture/agentic-architecture/hermes-multi-tenant-isolation-architecture
+hermes-single-client-single-department-architecture,hermes-single-client-single-department-architecture,"Hermes Single Client, Single Department Architecture",workflow,Agentic Architecture,agentic-architecture,agentic;mcp;agentic-security,agentic-architecture;agentic;mcp;agentic-security,1,5,3,hermes;multi-tenant;single-tenant;gateway;sandboxing,"Option 1 of the Hermes multi-tenant setup: one external actor, one gateway, one isolated workspace inside an execution sandbox, and a single client profile.",,agentic-architecture/agentic-architecture/hermes-single-client-single-department-architecture
+hermes-single-client-multi-department-routing-architecture,hermes-single-client-multi-department-routing-architecture,"Hermes Single Client, Multi-Department Routing Architecture",workflow,Agentic Architecture,agentic-architecture,handoff;agentic;mcp,agentic-architecture;handoff;agentic;mcp,2,7,4,hermes;multi-tenant;routing;departments;gateway,"Option 2: one client with several entry points, a prefix router that maps /eng or /support to a mode, and a single unified Hermes profile behind the gateway.",,agentic-architecture/agentic-architecture/hermes-single-client-multi-department-routing-architecture
+hermes-multi-client-isolated-profiles-architecture,hermes-multi-client-isolated-profiles-architecture,Hermes Multi-Client Isolated Profiles Architecture,workflow,Agentic Architecture,agentic-architecture,agentic,agentic-architecture;agentic,2,8,4,hermes;multi-tenant;profiles;isolation;docker,"Option 3, the core multi-tenant setup: per-token entry points, one gateway per client, and isolated Hermes profiles running in separate containers.",,agentic-architecture/agentic-architecture/hermes-multi-client-isolated-profiles-architecture
+hermes-full-multi-tenant-department-routing-architecture,hermes-full-multi-tenant-department-routing-architecture,Hermes Full Multi-Tenant with Department Routing,workflow,Agentic Architecture,agentic-architecture,handoff;agentic;agentic-security,agentic-architecture;handoff;agentic;agentic-security,2,10,4,hermes;multi-tenant;routing;sandboxing;departments,"Option 4: external participants, per-client gateways and routers, department prefixes inside each tenant, and a sandbox per client.",,agentic-architecture/agentic-architecture/hermes-full-multi-tenant-department-routing-architecture
+hermes-kanban-agent-coordination-workflow,hermes-kanban-agent-coordination,Hermes Kanban Agent Coordination Workflow,workflow,Agentic Architecture,agentic-architecture,agentic,agentic-architecture;agentic,2,6,4,hermes;kanban;multi-agent;orchestrator-worker;coordination,"A planner decomposes the request on a shared board, specialized workers claim tasks, and the orchestrator delivers once every card is closed.",,agentic-architecture/agentic-architecture/hermes-kanban-agent-coordination-workflow
+agent-to-agent-usdc-payment-workflow,agent-to-agent-usdc-payment,Agent-to-Agent USDC Payment Workflow,workflow,Commerce Automation,billing,commerce-automation,billing;commerce-automation,2,9,3,coinbase;agentkit;usdc;x402;agent-payments;stablecoin,"Coinbase AgentKit flow: a human allocates a USDC budget, the agent authenticates its Base wallet, pays an x402 invoice and processes the supplier data, with no fiat in the path.",,billing/commerce-automation/agent-to-agent-usdc-payment-workflow
+agent-mediated-fiat-payment-workflow,agent-mediated-fiat-payment,Agent-Mediated Fiat Payment Workflow,workflow,Commerce Automation,billing,commerce-automation,billing;commerce-automation,2,11,4,stripe;agent-toolkit;shared-payment-token;fiat;agent-payments,"Stripe Agent Toolkit flow: the consumer approves an agent spend, the agent requests a scoped token, passes it to the merchant and the order completes in fiat.",,billing/commerce-automation/agent-mediated-fiat-payment-workflow
+coinbase-trust-flow-onchain-settlement,coinbase-trust-flow-onchain-settlement,Coinbase Trust Flow — On-Chain Settlement,workflow,Commerce Automation,commerce-automation,,commerce-automation,1,5,2,coinbase;trust-flow;onchain;settlement;base,"The trust layer behind agent-to-agent payments on Coinbase: the agent initiates the spend, the transaction is broadcast, the block confirms and the payment finalizes on-chain.",,commerce-automation/commerce-automation/coinbase-trust-flow-onchain-settlement
+stripe-trust-flow-fiat-authorization,stripe-trust-flow-fiat-authorization,Stripe Trust Flow — Fiat Authorization,workflow,Commerce Automation,approval,security;compliance;commerce-automation,approval;security;compliance;commerce-automation,1,5,2,stripe;trust-flow;risk-engine;authorization;fiat,"The trust layer behind agent-mediated payments at Stripe: the agent submits a shared payment token, the risk engine approves it and fiat clears through the banking rails.",,approval/commerce-automation/stripe-trust-flow-fiat-authorization
+agentic-commerce-checkout-architecture,agentic-commerce-checkout-architecture,Agentic Commerce Checkout Architecture,workflow,Commerce Automation,billing,agentic;commerce-automation,billing;agentic;commerce-automation,3,21,5,agentic-commerce;chatgpt-commerce;checkout;merchant;payments,"Five-lane architecture for agent-driven checkout: merchant edge, commerce services, payment stack, fulfillment and the approval gate before an order is authorized.",,billing/commerce-automation/agentic-commerce-checkout-architecture
+multi-platform-ecommerce-integration-hub,multi-platform-ecommerce-integration-hub,Multi-Platform eCommerce Integration Hub,workflow,Commerce Automation,commerce-automation,,commerce-automation,2,11,1,n8n;ecommerce;integration;multi-channel;shopify;woocommerce,"n8n as the central integration layer: one workflow decides whether an event is a product sync or an order, routes it to the right channel and closes the loop.",,commerce-automation/commerce-automation/multi-platform-ecommerce-integration-hub
+ai-product-sync-pipeline-workflow,ai-product-sync-pipeline,AI Product Sync Pipeline Workflow,workflow,Commerce Automation,delivery,commerce-automation,delivery;commerce-automation,2,12,3,n8n;product-sync;ai-agents;schema-normalization;ecommerce,"Product sync between platforms with an AI agent in the middle: field extraction, category mapping and schema normalization before the write-back returns 200 OK.",,delivery/commerce-automation/ai-product-sync-pipeline-workflow
+ai-order-routing-workflow,ai-order-routing,AI Order Routing Workflow,workflow,Commerce Automation,handoff,commerce-automation,handoff;commerce-automation,3,14,3,n8n;order-routing;ai-decision;backorder;fulfillment,"Order routing where an AI decision engine classifies each order, auto-processes the clean ones and sends the rest to a backorder queue before operations completes it.",,handoff/commerce-automation/ai-order-routing-workflow
+shopify-river-four-layer-agent-architecture,shopify-river-four-layer-agent-architecture,Shopify River 4-Layer Agent Architecture,workflow,Commerce Automation,commerce-automation,,commerce-automation,3,13,4,shopify;river;internal-agents;architecture;slack;session,"Slack as interface, River as agent surface, Aquifer as foundation and a separate harness: the four layers behind an internal agent that treats a session as a durable entity.",,commerce-automation/commerce-automation/shopify-river-four-layer-agent-architecture
+shopify-river-brain-hands-decoupling-architecture,shopify-river-brain-hands-decoupling-architecture,Shopify River Brain-Hands Decoupling Architecture,workflow,Commerce Automation,commerce-automation,agentic-security,commerce-automation;agentic-security,2,12,3,shopify;river;harness;sandbox;agent-architecture,"Decoupling the brain from the hands: the harness calls the LLM and emits tool intents, while the sandbox executes them, so a new agent is a profile and not a platform.",,commerce-automation/commerce-automation/shopify-river-brain-hands-decoupling-architecture
+shopify-river-session-modes-workflow,shopify-river-session-modes,Shopify River Session Modes Workflow,workflow,Commerce Automation,approval,commerce-automation,approval;commerce-automation,2,9,4,shopify;river;session-modes;ci;code-review;automation,"Three session modes in one agent: interactive in Slack, automated review in the pull request, and ephemeral batch runs triggered by CI — cattle, not pets.",,approval/commerce-automation/shopify-river-session-modes-workflow
+llm-model-router-cost-aware-routing,llm-model-router-cost-aware-routing,LLM Model Router — Cost-Aware Routing,workflow,LLM Operations,handoff,mcp;llm-operations,handoff;mcp;llm-operations,2,10,3,token-optimization;model-routing;llm-gateway;cost;llmops,"An LLM gateway that reads the token budget, extracts intent and length, then routes the call to the cheap model or the premium one before delivering the response.",,handoff/llm-operations/llm-model-router-cost-aware-routing
+context-compaction-gateway-workflow,context-compaction-gateway,Context Compaction Gateway Workflow,workflow,LLM Operations,mcp,context-management;llm-operations,mcp;context-management;llm-operations,2,12,4,token-optimization;context-management;compaction;rag;llmops,"A context gateway that assembles raw context from the vector store and logs, compacts 100k tokens down to 15k and only then builds the final prompt.",,mcp/llm-operations/context-compaction-gateway-workflow
+prompt-caching-static-prefix-workflow,prompt-caching-static-prefix,Prompt Caching with Static Prefix Workflow,workflow,LLM Operations,context-management,llm-operations,context-management;llm-operations,3,14,2,token-optimization;prompt-caching;kv-cache;context-management;llmops,"Static system prompt assembled once and cached by the provider, then only the volatile user input is appended — a cache hit reads 50k tokens from the KV cache.",,context-management/llm-operations/prompt-caching-static-prefix-workflow
+dynamic-tool-schema-selection-workflow,dynamic-tool-schema-selection,Dynamic Tool Schema Selection Workflow,workflow,LLM Operations,handoff,mcp;llm-operations,handoff;mcp;llm-operations,2,8,3,token-optimization;mcp;tool-schemas;tool-routing;llmops,"Instead of loading all 50 tool schemas into every request, the agent analyses the step, queries the MCP tool registry and injects only the two schemas it needs.",,handoff/llm-operations/dynamic-tool-schema-selection-workflow
+structured-output-validation-workflow,structured-output-validation,Structured Output Validation Workflow,workflow,LLM Operations,llm-operations,,llm-operations,2,8,2,token-optimization;structured-output;validation;json-schema;llmops,"Output on a leash: the model generates against an output schema, the orchestrator validates that it parses as JSON or a diff, and regenerates or formats when it does not.",,llm-operations/llm-operations/structured-output-validation-workflow
+agent-world-model-simulation-loop,agent-world-model-simulation-loop,Agent-World Model Simulation Loop,workflow,Agent Simulation,agent-simulation,,agent-simulation,2,12,3,qwen;agentworld;world-model;simulation;agent-testing,"The agent analyses the request, the world model simulates the action, the simulated outcome returns a confirmation and the agent executes — with an adjustment loop on divergence.",,agent-simulation/agent-simulation/agent-world-model-simulation-loop
+validation-simulator-inside-agent-workflow,validation-simulator-inside-agent,Validation Simulator Inside the Agent Workflow,workflow,Agent Simulation,agent-simulation,,agent-simulation,3,14,4,qwen;agentworld;validation;insurance;simulation,"The validation simulator sits inside the workflow, not after it: the agent analyses the claim attachments, detects the anomaly and simulates the reimbursement before executing it.",,agent-simulation/agent-simulation/validation-simulator-inside-agent-workflow
+agentworld-testing-pipeline-workflow,agentworld-testing-pipeline,AgentWorld Testing Pipeline Workflow,workflow,Agent Simulation,delivery,agent-simulation,delivery;agent-simulation,3,14,3,qwen;agentworld;qa;test-pipeline;robustness,"A QA pipeline with a simulator in the loop: configure perturbations, add scenarios, run the agent under test and analyse the robustness report before release.",,delivery/agent-simulation/agentworld-testing-pipeline-workflow
+mirofish-synthetic-focus-group-architecture,mirofish-synthetic-focus-group-architecture,MiroFish Synthetic Focus Group Architecture,workflow,Agent Simulation,agentic,agent-simulation,agentic;agent-simulation,2,11,3,mirofish;synthetic-research;focus-group;multi-agent;llm,"Browser to MiroFish stack to LLM API: the seed document is distributed to each agent, agents produce outputs and the logs are aggregated into a report.",,agentic/agent-simulation/mirofish-synthetic-focus-group-architecture
+synthetic-focus-group-copy-validation,synthetic-focus-group-copy-validation,Synthetic Focus Group — Copy Validation,workflow,Agent Simulation,agentic,agent-simulation,agentic;agent-simulation,3,13,3,mirofish;synthetic-research;copy-validation;agent-swarm;personas,"Pre-launch copy validation: a builder spawns 50 LLM agents with a persona config, collects and ranks top objections, then builds the report.",,agentic/agent-simulation/synthetic-focus-group-copy-validation
+synthetic-focus-group-crisis-injection,synthetic-focus-group-crisis-injection,Synthetic Focus Group — Crisis Injection,workflow,Agent Simulation,agentic,agent-simulation,agentic;agent-simulation,3,16,3,mirofish;synthetic-research;crisis-injection;market-event;agent-swarm,"Mid-simulation crisis injection: the baseline is captured, a market event is injected, agents absorb the crisis context and the post-crisis logs are aggregated for comparison.",,agentic/agent-simulation/synthetic-focus-group-crisis-injection
+synthetic-focus-group-ab-offer-testing,synthetic-focus-group-ab-offer-testing,Synthetic Focus Group — A/B Offer Testing,workflow,Agent Simulation,agentic,agent-simulation,agentic;agent-simulation,2,12,2,mirofish;synthetic-research;ab-testing;offer-testing;agent-swarm,"A/B offer testing with synthetic agents: variant A and variant B are evaluated for perceived value, aggregated separately and compared to pick the winner.",,agentic/agent-simulation/synthetic-focus-group-ab-offer-testing
+gcp-account-suspension-outage-cascade,gcp-account-suspension-outage-cascade,GCP Account Suspension Outage Cascade,workflow,Platform Reliability,incident,platform-reliability,incident;platform-reliability,2,8,1,multi-cloud;outage;cascade;resilience;gcp,"How a single account suspension cascades into an 8-hour platform outage: control plane offline, API down, caches expiring, workloads returning 404 and OAuth throttled.",,incident/platform-reliability/gcp-account-suspension-outage-cascade
+multi-cloud-mesh-resilience-architecture,multi-cloud-mesh-resilience-architecture,Multi-Cloud Mesh Resilience Architecture,workflow,Platform Reliability,platform-reliability,,platform-reliability,2,9,1,multi-cloud;resilience;mesh;quorum;architecture,"Traffic through any edge proxy to a mesh control plane spread over AWS, GCP and metal, with quorum databases and no single-cloud dependency in the routing path.",,platform-reliability/platform-reliability/multi-cloud-mesh-resilience-architecture
+cross-cloud-failover-deployment-pipeline,cross-cloud-failover-deployment-pipeline,Cross-Cloud Failover Deployment Pipeline,workflow,Platform Reliability,delivery,platform-reliability,delivery;platform-reliability,2,11,5,multi-cloud;deployment;failover;ci-cd;health-check,"CI builds the container, pushes it to a cross-cloud registry, deploys to AWS, GCP and metal, health-checks every endpoint and updates mesh routing only when all are healthy.",,delivery/platform-reliability/cross-cloud-failover-deployment-pipeline
diff --git a/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/README.md b/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..ebeb6d0224b3107bb1dc0ba5f1dd73d8c009b2ef
--- /dev/null
+++ b/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/README.md
@@ -0,0 +1,19 @@
+# Agent-Generated Mind Map — Incident Root Cause
+
+An AGMM example: an SRE agent outputs its API latency root-cause reasoning chain as an interactive mind map, reversing the Human-to-Machine explainability flow.
+
+**Template ID:** `agent-generated-mind-map-incident-root-cause`  
+**Kind:** workflow  
+**Source domain:** Mindmap  
+**Primary use case:** mindmap  
+**Secondary use cases:** incident, agentic, agentic-architecture  
+**Complexity:** 3/5  
+**Nodes:** 13  
+**Lanes:** 1  
+**Tags:** [mind-map, agmm, explainability, incident, sre, agentic-architecture]  
+**Source path:** ``  
+**Repo path:** `mindmap/mindmap/agent-generated-mind-map-incident-root-cause`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/metadata.json b/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..b93a0216ceec42e5a9cd5331ca13806cf03295fa
--- /dev/null
+++ b/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/metadata.json
@@ -0,0 +1,33 @@
+{
+  "template_id": "agent-generated-mind-map-incident-root-cause",
+  "workflow_id": "agent-generated-mind-map-incident-root-cause",
+  "title": "Agent-Generated Mind Map — Incident Root Cause",
+  "kind": "workflow",
+  "source_domain": "Mindmap",
+  "primary_use_case": "mindmap",
+  "secondary_use_cases": [
+    "incident",
+    "agentic",
+    "agentic-architecture"
+  ],
+  "use_cases": [
+    "mindmap",
+    "incident",
+    "agentic",
+    "agentic-architecture"
+  ],
+  "complexity": 3,
+  "num_nodes": 13,
+  "num_lanes": 1,
+  "tags": [
+    "mind-map",
+    "agmm",
+    "explainability",
+    "incident",
+    "sre",
+    "agentic-architecture"
+  ],
+  "description": "An AGMM example: an SRE agent outputs its API latency root-cause reasoning chain as an interactive mind map, reversing the Human-to-Machine explainability flow.",
+  "source_path": "",
+  "repo_path": "mindmap/mindmap/agent-generated-mind-map-incident-root-cause"
+}
diff --git a/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/workflow.fz b/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..21487e916877fa51264377a13fd269f84a272c99
--- /dev/null
+++ b/mindmap/mindmap/agent-generated-mind-map-incident-root-cause/workflow.fz
@@ -0,0 +1,33 @@
+mindmap { # Mindmap
+  n1: circle label:"SRE Agent: API Latency Surge"
+  n2: rectangle label:"Detection"
+  n3: rectangle label:"Diagnosis"
+  n4: rectangle label:"Mitigation"
+  n5: rectangle label:"Scaling"
+  n6: rectangle label:"Observability"
+  n7: rectangle label:"Communication"
+  n8: rectangle label:"Alert Rules"
+  n9: rectangle label:"Anomaly Detection"
+  n10: rectangle label:"Service Dependency"
+  n11: rectangle label:"Log Analysis"
+  n12: rectangle label:"Circuit Breaker"
+  n13: rectangle label:"Throttling"
+  n1.handle(top) -> n2.handle(bottom)
+  n1.handle(right) -> n3.handle(left)
+  n1.handle(bottom) -> n4.handle(top)
+  n1.handle(left) -> n5.handle(right)
+  n2.handle(right) -> n8.handle(left)
+  n3.handle(top) -> n10.handle(bottom)
+  n3.handle(top) -> n11.handle(bottom)
+  n4.handle(right) -> n12.handle(bottom)
+  n1.handle(top) -> n8.handle(bottom)
+  n2.handle(top) -> n10.handle(top)
+  n3.handle(left) -> n1.handle(right)
+  n3.handle(bottom) -> n12.handle(top)
+  n3.handle(right) -> n13.handle(left)
+  n13.handle(bottom) -> n4.handle(right)
+  n6.handle(right) -> n1.handle(left)
+  n7.handle(top) -> n1.handle(bottom)
+  n11.handle(left) -> n2.handle(bottom)
+  n9.handle(top) -> n2.handle(left)
+}
diff --git a/mindmap/mindmap/problem-mind-map-credit-decision/README.md b/mindmap/mindmap/problem-mind-map-credit-decision/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..a83864b97c6b813e610cc75a96d74d32bf252439
--- /dev/null
+++ b/mindmap/mindmap/problem-mind-map-credit-decision/README.md
@@ -0,0 +1,19 @@
+# Problem Mind Map — Credit Decision
+
+A problem mind map for an AI credit decision, mapping decisions, data, policies, actors, risks, constraints and open questions before any component is designed.
+
+**Template ID:** `problem-mind-map-credit-decision`  
+**Kind:** workflow  
+**Source domain:** Mindmap  
+**Primary use case:** mindmap  
+**Secondary use cases:** agentic, agentic-architecture  
+**Complexity:** 3/5  
+**Nodes:** 32  
+**Lanes:** 1  
+**Tags:** [mind-map, problem-mind-map, credit-decision, problem-first, agentic-architecture]  
+**Source path:** ``  
+**Repo path:** `mindmap/mindmap/problem-mind-map-credit-decision`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/mindmap/mindmap/problem-mind-map-credit-decision/metadata.json b/mindmap/mindmap/problem-mind-map-credit-decision/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..47a8bae059e26e990d428b14ed43d7adbe35c2c1
--- /dev/null
+++ b/mindmap/mindmap/problem-mind-map-credit-decision/metadata.json
@@ -0,0 +1,30 @@
+{
+  "template_id": "problem-mind-map-credit-decision",
+  "workflow_id": "problem-mind-map-credit-decision",
+  "title": "Problem Mind Map — Credit Decision",
+  "kind": "workflow",
+  "source_domain": "Mindmap",
+  "primary_use_case": "mindmap",
+  "secondary_use_cases": [
+    "agentic",
+    "agentic-architecture"
+  ],
+  "use_cases": [
+    "mindmap",
+    "agentic",
+    "agentic-architecture"
+  ],
+  "complexity": 3,
+  "num_nodes": 32,
+  "num_lanes": 1,
+  "tags": [
+    "mind-map",
+    "problem-mind-map",
+    "credit-decision",
+    "problem-first",
+    "agentic-architecture"
+  ],
+  "description": "A problem mind map for an AI credit decision, mapping decisions, data, policies, actors, risks, constraints and open questions before any component is designed.",
+  "source_path": "",
+  "repo_path": "mindmap/mindmap/problem-mind-map-credit-decision"
+}
diff --git a/mindmap/mindmap/problem-mind-map-credit-decision/workflow.fz b/mindmap/mindmap/problem-mind-map-credit-decision/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..d046d347e692885ca79e053c06a841c2280e755e
--- /dev/null
+++ b/mindmap/mindmap/problem-mind-map-credit-decision/workflow.fz
@@ -0,0 +1,66 @@
+credit_decision { # Credit decision
+  n1: circle label:"Decide whether to grant credit"
+  n2: rectangle label:"Decisions"
+  n3: rectangle label:"Data"
+  n4: rectangle label:"Policies"
+  n5: rectangle label:"Actors"
+  n6: rectangle label:"Risks"
+  n7: rectangle label:"Constraints"
+  n8: rectangle label:"Open questions"
+  n9: rectangle label:"Approve / decline"
+  n10: rectangle label:"Amount & rate"
+  n11: rectangle label:"Human review"
+  n12: rectangle label:"Client history"
+  n13: rectangle label:"Income & contracts"
+  n14: rectangle label:"External score"
+  n15: rectangle label:"Thresholds"
+  n16: rectangle label:"Exceptions"
+  n17: rectangle label:"Regulations"
+  n18: rectangle label:"Who has authority?"
+  n19: rectangle label:"Customer"
+  n20: rectangle label:"Credit officer"
+  n21: rectangle label:"Supervisor"
+  n22: rectangle label:"Compliance"
+  n23: rectangle label:"Hallucination"
+  n24: rectangle label:"Bias"
+  n25: rectangle label:"Privacy"
+  n26: rectangle label:"Liability"
+  n27: rectangle label:"Audit trail"
+  n28: rectangle label:"Explainability"
+  n29: rectangle label:"GDPR"
+  n30: rectangle label:"Where do thresholds live?"
+  n31: rectangle label:"Dispute: who answers?"
+  n32: rectangle label:"Review margin?"
+
+  n1.handle(right) -> n2.handle(left)
+  n1.handle(bottom) -> n3.handle(top)
+  n1.handle(top) -> n4.handle(bottom)
+  n1.handle(left) -> n5.handle(right)
+  n1.handle(right) -> n6.handle(top)
+  n1.handle(bottom) -> n7.handle(left)
+  n1.handle(top) -> n8.handle(right)
+  n2.handle(right) -> n9.handle(left)
+  n2.handle(bottom) -> n10.handle(top)
+  n2.handle(top) -> n11.handle(bottom)
+  n3.handle(right) -> n12.handle(left)
+  n3.handle(bottom) -> n13.handle(top)
+  n3.handle(top) -> n14.handle(bottom)
+  n4.handle(right) -> n15.handle(left)
+  n4.handle(bottom) -> n16.handle(top)
+  n4.handle(top) -> n17.handle(bottom)
+  n4.handle(left) -> n18.handle(right)
+  n5.handle(right) -> n19.handle(left)
+  n5.handle(bottom) -> n20.handle(top)
+  n5.handle(top) -> n21.handle(bottom)
+  n5.handle(left) -> n22.handle(right)
+  n6.handle(right) -> n23.handle(left)
+  n6.handle(bottom) -> n24.handle(top)
+  n6.handle(top) -> n25.handle(bottom)
+  n6.handle(left) -> n26.handle(right)
+  n7.handle(right) -> n27.handle(left)
+  n7.handle(bottom) -> n28.handle(top)
+  n7.handle(top) -> n29.handle(bottom)
+  n8.handle(right) -> n30.handle(left)
+  n8.handle(bottom) -> n31.handle(top)
+  n8.handle(top) -> n32.handle(bottom)
+}
diff --git a/offboarding/business-operations/account-deletion-workflow/workflow.fz b/offboarding/business-operations/account-deletion-workflow/workflow.fz
index 68b67b608bd4d2e9e2a5e39ea549efe563ab276c..aa4e071ec4df28e5103230108b61b3f05f130e8a 100644
--- a/offboarding/business-operations/account-deletion-workflow/workflow.fz
+++ b/offboarding/business-operations/account-deletion-workflow/workflow.fz
@@ -1,40 +1,40 @@
-User { # User
-n1: circle label:"Start"
-n2: rectangle label:"Request account deletion"
-n3: rectangle label:"Confirm via email link"
-n4: rectangle label:"Download data export"
-n5: rectangle label:"Receive deletion confirmation"
-n6: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> App.n7.handle(top) [label="Submit request"]
-n3.handle(bottom) -> App.n10.handle(top) [label="Confirmed"]
-n4.handle(right) -> n5.handle(left)
-n5.handle(right) -> n6.handle(left)
-}
-App { # Application
-n7: rectangle label:"Validate user identity"
-n8: diamond label:"Active subscriptions?"
-n9: rectangle label:"Send confirmation email"
-n10: rectangle label:"Queue deletion job"
-n11: rectangle label:"Generate data export"
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left) [label="No"]
-n8.handle(bottom) -> Billing.n15.handle(top) [label="Yes - Cancel first"]
-n9.handle(top) -> User.n3.handle(bottom) [label="Email sent"]
-n10.handle(bottom) -> Backend.n12.handle(top) [label="Process"]
-n11.handle(top) -> User.n4.handle(bottom) [label="Ready"]
-}
-Backend { # Backend
-n12: rectangle label:"Anonymize user records"
-n13: rectangle label:"Delete personal data"
-n14: rectangle label:"Purge from backups"
-n12.handle(right) -> n13.handle(left)
-n13.handle(right) -> n14.handle(left)
-n14.handle(top) -> App.n11.handle(bottom) [label="Complete"]
-}
-Billing { # Billing
-n15: rectangle label:"Cancel active subscriptions"
-n16: rectangle label:"Process final invoice"
-n15.handle(right) -> n16.handle(left)
-n16.handle(top) -> App.n9.handle(bottom) [label="Cleared"]
+User { # User
+n1: circle label:"Start"
+n2: rectangle label:"Request account deletion"
+n3: rectangle label:"Confirm via email link"
+n4: rectangle label:"Download data export"
+n5: rectangle label:"Receive deletion confirmation"
+n6: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> App.n7.handle(top) [label="Submit request"]
+n3.handle(bottom) -> App.n10.handle(top) [label="Confirmed"]
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left)
+}
+App { # Application
+n7: rectangle label:"Validate user identity"
+n8: diamond label:"Active subscriptions?"
+n9: rectangle label:"Send confirmation email"
+n10: rectangle label:"Queue deletion job"
+n11: rectangle label:"Generate data export"
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left) [label="No"]
+n8.handle(bottom) -> Billing.n15.handle(top) [label="Yes - Cancel first"]
+n9.handle(top) -> User.n3.handle(bottom) [label="Email sent"]
+n10.handle(bottom) -> Backend.n12.handle(top) [label="Process"]
+n11.handle(top) -> User.n4.handle(bottom) [label="Ready"]
+}
+Backend { # Backend
+n12: rectangle label:"Anonymize user records"
+n13: rectangle label:"Delete personal data"
+n14: rectangle label:"Purge from backups"
+n12.handle(right) -> n13.handle(left)
+n13.handle(right) -> n14.handle(left)
+n14.handle(top) -> App.n11.handle(bottom) [label="Complete"]
+}
+Billing { # Billing
+n15: rectangle label:"Cancel active subscriptions"
+n16: rectangle label:"Process final invoice"
+n15.handle(right) -> n16.handle(left)
+n16.handle(top) -> App.n9.handle(bottom) [label="Cleared"]
 }
\ No newline at end of file
diff --git a/onboarding/business-operations/ab-test-setup-workflow/workflow.fz b/onboarding/business-operations/ab-test-setup-workflow/workflow.fz
index 30c82ece4fddecdbd549fc0aa173f060a3d4b8b9..9b515dc4a25314338004ae546433738a5c277ea5 100644
--- a/onboarding/business-operations/ab-test-setup-workflow/workflow.fz
+++ b/onboarding/business-operations/ab-test-setup-workflow/workflow.fz
@@ -1,40 +1,40 @@
-ProductManager { # Product Manager
-n1: circle label:"Start"
-n2: rectangle label:"Define test hypothesis"
-n3: rectangle label:"Select target audience segment"
-n4: rectangle label:"Review test results"
-n5: diamond label:"Statistically significant?"
-n6: rectangle label:"Document findings"
-n7: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(right) -> n3.handle(left)
-n3.handle(bottom) -> Engineering.n8.handle(top) [label="Request setup"]
-n4.handle(right) -> n5.handle(left)
-n5.handle(right) -> n6.handle(left) [label="Yes"]
-n5.handle(bottom) -> Analytics.n14.handle(top) [label="No - Extend test"]
-n6.handle(right) -> n7.handle(left)
-}
-Engineering { # Engineering
-n8: rectangle label:"Create feature flags"
-n9: rectangle label:"Implement variant A"
-n10: rectangle label:"Implement variant B"
-n11: diamond label:"QA passed?"
-n12: rectangle label:"Deploy to production"
-n8.handle(right) -> n9.handle(left)
-n9.handle(right) -> n10.handle(left)
-n10.handle(right) -> n11.handle(left)
-n11.handle(right) -> n12.handle(left) [label="Yes"]
-n11.handle(bottom) -> n9.handle(bottom) [label="No - Fix bugs"]
-n12.handle(bottom) -> Analytics.n13.handle(top) [label="Start tracking"]
-}
-Analytics { # Analytics
-n13: rectangle label:"Configure tracking events"
-n14: rectangle label:"Monitor conversion metrics"
-n15: diamond label:"Enough sample size?"
-n16: rectangle label:"Generate statistical report"
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left) [label="Yes"]
-n15.handle(bottom) -> n14.handle(bottom) [label="No - Continue"]
-n16.handle(top) -> ProductManager.n4.handle(bottom) [label="Results ready"]
+ProductManager { # Product Manager
+n1: circle label:"Start"
+n2: rectangle label:"Define test hypothesis"
+n3: rectangle label:"Select target audience segment"
+n4: rectangle label:"Review test results"
+n5: diamond label:"Statistically significant?"
+n6: rectangle label:"Document findings"
+n7: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(bottom) -> Engineering.n8.handle(top) [label="Request setup"]
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left) [label="Yes"]
+n5.handle(bottom) -> Analytics.n14.handle(top) [label="No - Extend test"]
+n6.handle(right) -> n7.handle(left)
+}
+Engineering { # Engineering
+n8: rectangle label:"Create feature flags"
+n9: rectangle label:"Implement variant A"
+n10: rectangle label:"Implement variant B"
+n11: diamond label:"QA passed?"
+n12: rectangle label:"Deploy to production"
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left)
+n10.handle(right) -> n11.handle(left)
+n11.handle(right) -> n12.handle(left) [label="Yes"]
+n11.handle(bottom) -> n9.handle(bottom) [label="No - Fix bugs"]
+n12.handle(bottom) -> Analytics.n13.handle(top) [label="Start tracking"]
+}
+Analytics { # Analytics
+n13: rectangle label:"Configure tracking events"
+n14: rectangle label:"Monitor conversion metrics"
+n15: diamond label:"Enough sample size?"
+n16: rectangle label:"Generate statistical report"
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left) [label="Yes"]
+n15.handle(bottom) -> n14.handle(bottom) [label="No - Continue"]
+n16.handle(top) -> ProductManager.n4.handle(bottom) [label="Results ready"]
 }
\ No newline at end of file
diff --git a/onboarding/business-operations/two-factor-setup-workflow/workflow.fz b/onboarding/business-operations/two-factor-setup-workflow/workflow.fz
index 9b516f242a9f065d2072fab2adeab38a6ed1a5b0..c4435723e032397713f9b6ac440f103c2b79ca2c 100644
--- a/onboarding/business-operations/two-factor-setup-workflow/workflow.fz
+++ b/onboarding/business-operations/two-factor-setup-workflow/workflow.fz
@@ -1,43 +1,43 @@
-User { # User
-n1: circle label:"Start"
-n2: rectangle label:"Navigate to security settings"
-n3: rectangle label:"Select 2FA method"
-n4: rectangle label:"Scan QR code with app"
-n5: rectangle label:"Enter verification code"
-n6: rectangle label:"Save backup codes"
-n7: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> AuthService.n8.handle(top) [label="Enable 2FA"]
-n3.handle(bottom) -> AuthService.n10.handle(top) [label="TOTP selected"]
-n4.handle(bottom) -> AuthService.n13.handle(top) [label="Submit code"]
-n5.handle(right) -> n6.handle(left)
-n6.handle(right) -> n7.handle(left)
-}
-AuthService { # Auth Service
-n8: rectangle label:"Check current 2FA status"
-n9: rectangle label:"Present method options"
-n10: rectangle label:"Generate TOTP secret"
-n11: rectangle label:"Create QR code"
-n12: rectangle label:"Store pending secret"
-n13: diamond label:"Code valid?"
-n14: rectangle label:"Activate 2FA"
-n15: rectangle label:"Show error message"
-n8.handle(right) -> n9.handle(left)
-n9.handle(top) -> User.n3.handle(bottom) [label="Choose method"]
-n10.handle(right) -> n11.handle(left)
-n11.handle(right) -> n12.handle(left)
-n12.handle(top) -> User.n4.handle(bottom) [label="Display QR"]
-n13.handle(right) -> n14.handle(left) [label="Yes"]
-n13.handle(bottom) -> n15.handle(top) [label="No"]
-n14.handle(bottom) -> BackupCodes.n16.handle(top) [label="Generate backups"]
-n15.handle(top) -> User.n4.handle(bottom) [label="Try again"]
-loop [retry until valid] n13 n15
-}
-BackupCodes { # Backup Codes
-n16: rectangle label:"Generate 10 backup codes"
-n17: rectangle label:"Hash and store codes"
-n18: rectangle label:"Display codes to user"
-n16.handle(right) -> n17.handle(left)
-n17.handle(right) -> n18.handle(left)
-n18.handle(top) -> User.n5.handle(bottom) [label="Save these"]
+User { # User
+n1: circle label:"Start"
+n2: rectangle label:"Navigate to security settings"
+n3: rectangle label:"Select 2FA method"
+n4: rectangle label:"Scan QR code with app"
+n5: rectangle label:"Enter verification code"
+n6: rectangle label:"Save backup codes"
+n7: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> AuthService.n8.handle(top) [label="Enable 2FA"]
+n3.handle(bottom) -> AuthService.n10.handle(top) [label="TOTP selected"]
+n4.handle(bottom) -> AuthService.n13.handle(top) [label="Submit code"]
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left)
+}
+AuthService { # Auth Service
+n8: rectangle label:"Check current 2FA status"
+n9: rectangle label:"Present method options"
+n10: rectangle label:"Generate TOTP secret"
+n11: rectangle label:"Create QR code"
+n12: rectangle label:"Store pending secret"
+n13: diamond label:"Code valid?"
+n14: rectangle label:"Activate 2FA"
+n15: rectangle label:"Show error message"
+n8.handle(right) -> n9.handle(left)
+n9.handle(top) -> User.n3.handle(bottom) [label="Choose method"]
+n10.handle(right) -> n11.handle(left)
+n11.handle(right) -> n12.handle(left)
+n12.handle(top) -> User.n4.handle(bottom) [label="Display QR"]
+n13.handle(right) -> n14.handle(left) [label="Yes"]
+n13.handle(bottom) -> n15.handle(top) [label="No"]
+n14.handle(bottom) -> BackupCodes.n16.handle(top) [label="Generate backups"]
+n15.handle(top) -> User.n4.handle(bottom) [label="Try again"]
+loop [retry until valid] n13 n15
+}
+BackupCodes { # Backup Codes
+n16: rectangle label:"Generate 10 backup codes"
+n17: rectangle label:"Hash and store codes"
+n18: rectangle label:"Display codes to user"
+n16.handle(right) -> n17.handle(left)
+n17.handle(right) -> n18.handle(left)
+n18.handle(top) -> User.n5.handle(bottom) [label="Save these"]
 }
\ No newline at end of file
diff --git a/onboarding/business-operations/user-onboarding-workflow/workflow.fz b/onboarding/business-operations/user-onboarding-workflow/workflow.fz
index fed505da4c7f896bf32831c61dc4431b2984becf..606a7f8c96ce4d956c4c2f8f6388f36e0e3a9e6d 100644
--- a/onboarding/business-operations/user-onboarding-workflow/workflow.fz
+++ b/onboarding/business-operations/user-onboarding-workflow/workflow.fz
@@ -1,20 +1,20 @@
-customer { # Customer
-  n1: circle label:"Start User Onboarding"
-  n3: rectangle label:"Review User Onboarding details"
-  n5: rectangle label:"Update records for User Onboarding"
-  n7: circle label:"End User Onboarding"
-
-  n1.handle(bottom) -> agent.n2.handle(top)
-  n3.handle(bottom) -> agent.n4.handle(top) [label="Processed"]
-  n5.handle(bottom) -> agent.n6.handle(top)
-}
-agent { # Agent
-  n2: rectangle label:"Receive User Onboarding request"
-  n4: rectangle label:"Make User Onboarding decision"
-  n6: diamond label:"Continue User Onboarding process"
-
-  n2.handle(bottom) -> customer.n3.handle(top)
-  n4.handle(bottom) -> customer.n5.handle(top)
-  n6.handle(bottom) -> customer.n7.handle(top) [label="Success"]
-  n6.handle(right) -> customer.n5.handle(right) [label="Retry/Rejected"]
+customer { # Customer
+  n1: circle label:"Start User Onboarding"
+  n3: rectangle label:"Review User Onboarding details"
+  n5: rectangle label:"Update records for User Onboarding"
+  n7: circle label:"End User Onboarding"
+
+  n1.handle(bottom) -> agent.n2.handle(top)
+  n3.handle(bottom) -> agent.n4.handle(top) [label="Processed"]
+  n5.handle(bottom) -> agent.n6.handle(top)
+}
+agent { # Agent
+  n2: rectangle label:"Receive User Onboarding request"
+  n4: rectangle label:"Make User Onboarding decision"
+  n6: diamond label:"Continue User Onboarding process"
+
+  n2.handle(bottom) -> customer.n3.handle(top)
+  n4.handle(bottom) -> customer.n5.handle(top)
+  n6.handle(bottom) -> customer.n7.handle(top) [label="Success"]
+  n6.handle(right) -> customer.n5.handle(right) [label="Retry/Rejected"]
 }
\ No newline at end of file
diff --git a/onboarding/business-operations/webinar-registration-workflow/workflow.fz b/onboarding/business-operations/webinar-registration-workflow/workflow.fz
index 8e3634dff746bcd067dbd582db6234f3373ab714..686afc5480afb70138f6c991558f0813ba79051f 100644
--- a/onboarding/business-operations/webinar-registration-workflow/workflow.fz
+++ b/onboarding/business-operations/webinar-registration-workflow/workflow.fz
@@ -1,29 +1,29 @@
-customer { # Customer
-  n1: circle label:"Start Webinar Registration"
-  n4: rectangle label:"Make Webinar Registration decision"
-  n7: rectangle label:"Continue Webinar Registration process"
-  n10: circle label:"End Webinar Registration"
-
-  n1.handle(bottom) -> agent.n2.handle(top)
-  n4.handle(bottom) -> agent.n5.handle(top)
-  n7.handle(bottom) -> agent.n8.handle(top)
-}
-agent { # Agent
-  n2: rectangle label:"Receive Webinar Registration request"
-  n5: diamond label:"Update records for Webinar Registration"
-  n8: rectangle label:"Continue Webinar Registration process"
-
-  n2.handle(bottom) -> billing.n3.handle(top) [label="Next"]
-  n5.handle(bottom) -> billing.n6.handle(top) [label="Done"]
-  n5.handle(right) -> customer.n4.handle(right) [label="Retry/Rejected"]
-  n8.handle(bottom) -> billing.n9.handle(top) [label="Processed"]
-}
-billing { # Billing
-  n3: rectangle label:"Review Webinar Registration details"
-  n6: rectangle label:"Continue Webinar Registration process"
-  n9: rectangle label:"Continue Webinar Registration process"
-
-  n3.handle(bottom) -> customer.n4.handle(top)
-  n6.handle(bottom) -> customer.n7.handle(top)
-  n9.handle(bottom) -> customer.n10.handle(top)
+customer { # Customer
+  n1: circle label:"Start Webinar Registration"
+  n4: rectangle label:"Make Webinar Registration decision"
+  n7: rectangle label:"Continue Webinar Registration process"
+  n10: circle label:"End Webinar Registration"
+
+  n1.handle(bottom) -> agent.n2.handle(top)
+  n4.handle(bottom) -> agent.n5.handle(top)
+  n7.handle(bottom) -> agent.n8.handle(top)
+}
+agent { # Agent
+  n2: rectangle label:"Receive Webinar Registration request"
+  n5: diamond label:"Update records for Webinar Registration"
+  n8: rectangle label:"Continue Webinar Registration process"
+
+  n2.handle(bottom) -> billing.n3.handle(top) [label="Next"]
+  n5.handle(bottom) -> billing.n6.handle(top) [label="Done"]
+  n5.handle(right) -> customer.n4.handle(right) [label="Retry/Rejected"]
+  n8.handle(bottom) -> billing.n9.handle(top) [label="Processed"]
+}
+billing { # Billing
+  n3: rectangle label:"Review Webinar Registration details"
+  n6: rectangle label:"Continue Webinar Registration process"
+  n9: rectangle label:"Continue Webinar Registration process"
+
+  n3.handle(bottom) -> customer.n4.handle(top)
+  n6.handle(bottom) -> customer.n7.handle(top)
+  n9.handle(bottom) -> customer.n10.handle(top)
 }
\ No newline at end of file
diff --git a/onboarding/finance/vendor-onboarding-workflow/workflow.fz b/onboarding/finance/vendor-onboarding-workflow/workflow.fz
index b01727e313b6c75fc77407aa2f8a28ba885aa28d..4b6c60fef22609237053f98803858093f7300e9a 100644
--- a/onboarding/finance/vendor-onboarding-workflow/workflow.fz
+++ b/onboarding/finance/vendor-onboarding-workflow/workflow.fz
@@ -1,47 +1,47 @@
-Vendor { # Vendor
-n1: circle label:"Start"
-n2: rectangle label:"Submit registration form"
-n3: rectangle label:"Upload required documents"
-n4: rectangle label:"Receive approval notification"
-n5: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> Procurement.n6.handle(top) [label="Apply"]
-n3.handle(bottom) -> Compliance.n12.handle(top) [label="Documents"]
-n4.handle(right) -> n5.handle(left)
-}
-Procurement { # Procurement
-n6: rectangle label:"Review vendor application"
-n7: diamond label:"Business need valid?"
-n8: rectangle label:"Request additional info"
-n9: rectangle label:"Assign vendor category"
-n10: rectangle label:"Set payment terms"
-n11: rectangle label:"Reject application"
-n6.handle(right) -> n7.handle(left)
-n7.handle(right) -> n9.handle(left) [label="Yes"]
-n7.handle(bottom) -> n8.handle(top) [label="Need info"]
-n7.handle(left) -> n11.handle(top) [label="No"]
-n8.handle(top) -> Vendor.n3.handle(bottom) [label="Request docs"]
-n9.handle(right) -> n10.handle(left)
-n10.handle(bottom) -> Compliance.n12.handle(top) [label="Verify"]
-n11.handle(top) -> Vendor.n4.handle(bottom) [label="Rejected"]
-}
-Compliance { # Compliance
-n12: rectangle label:"Verify W-9 or W-8BEN"
-n13: rectangle label:"Check insurance certificates"
-n14: diamond label:"Compliance passed?"
-n15: rectangle label:"Run background check"
-n16: rectangle label:"Flag compliance issues"
-n17: diamond label:"Background clear?"
-n18: rectangle label:"Approve vendor"
-n19: rectangle label:"Reject vendor"
-n12.handle(right) -> n13.handle(left)
-n13.handle(right) -> n14.handle(left)
-n14.handle(right) -> n15.handle(left) [label="Yes"]
-n14.handle(bottom) -> n16.handle(top) [label="No"]
-n15.handle(right) -> n17.handle(left)
-n16.handle(top) -> Vendor.n3.handle(bottom) [label="Fix issues"]
-n17.handle(right) -> n18.handle(left) [label="Yes"]
-n17.handle(bottom) -> n19.handle(top) [label="No"]
-n18.handle(top) -> Vendor.n4.handle(bottom) [label="Approved"]
-n19.handle(top) -> Vendor.n4.handle(bottom) [label="Rejected"]
-}
+Vendor { # Vendor
+n1: circle label:"Start"
+n2: rectangle label:"Submit registration form"
+n3: rectangle label:"Upload required documents"
+n4: rectangle label:"Receive approval notification"
+n5: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> Procurement.n6.handle(top) [label="Apply"]
+n3.handle(bottom) -> Compliance.n12.handle(top) [label="Documents"]
+n4.handle(right) -> n5.handle(left)
+}
+Procurement { # Procurement
+n6: rectangle label:"Review vendor application"
+n7: diamond label:"Business need valid?"
+n8: rectangle label:"Request additional info"
+n9: rectangle label:"Assign vendor category"
+n10: rectangle label:"Set payment terms"
+n11: rectangle label:"Reject application"
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n9.handle(left) [label="Yes"]
+n7.handle(bottom) -> n8.handle(top) [label="Need info"]
+n7.handle(left) -> n11.handle(top) [label="No"]
+n8.handle(top) -> Vendor.n3.handle(bottom) [label="Request docs"]
+n9.handle(right) -> n10.handle(left)
+n10.handle(bottom) -> Compliance.n12.handle(top) [label="Verify"]
+n11.handle(top) -> Vendor.n4.handle(bottom) [label="Rejected"]
+}
+Compliance { # Compliance
+n12: rectangle label:"Verify W-9 or W-8BEN"
+n13: rectangle label:"Check insurance certificates"
+n14: diamond label:"Compliance passed?"
+n15: rectangle label:"Run background check"
+n16: rectangle label:"Flag compliance issues"
+n17: diamond label:"Background clear?"
+n18: rectangle label:"Approve vendor"
+n19: rectangle label:"Reject vendor"
+n12.handle(right) -> n13.handle(left)
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left) [label="Yes"]
+n14.handle(bottom) -> n16.handle(top) [label="No"]
+n15.handle(right) -> n17.handle(left)
+n16.handle(top) -> Vendor.n3.handle(bottom) [label="Fix issues"]
+n17.handle(right) -> n18.handle(left) [label="Yes"]
+n17.handle(bottom) -> n19.handle(top) [label="No"]
+n18.handle(top) -> Vendor.n4.handle(bottom) [label="Approved"]
+n19.handle(top) -> Vendor.n4.handle(bottom) [label="Rejected"]
+}
diff --git a/onboarding/hr/onboarding-workflow/workflow.fz b/onboarding/hr/onboarding-workflow/workflow.fz
index 636ef583ce931015cda290652069fca8b94b864f..cd9db2149e03e87804e39e229008019f431b957e 100644
--- a/onboarding/hr/onboarding-workflow/workflow.fz
+++ b/onboarding/hr/onboarding-workflow/workflow.fz
@@ -1,47 +1,47 @@
-NewHire { # New Hire
-n1: circle label:"Start"
-n2: rectangle label:"Accept offer letter"
-n3: rectangle label:"Complete I-9 and W-4 forms"
-n4: rectangle label:"Set up direct deposit"
-n5: rectangle label:"Complete first day orientation"
-n6: circle label:"End"
-n1.handle(right) -> n2.handle(left)
-n2.handle(bottom) -> HR.n7.handle(top) [label="Signed"]
-n3.handle(bottom) -> IT.n14.handle(top) [label="Docs complete"]
-n4.handle(right) -> n5.handle(left)
-n5.handle(right) -> n6.handle(left)
-}
-HR { # Human Resources
-n7: rectangle label:"Create employee record"
-n8: rectangle label:"Enroll in benefits"
-n9: rectangle label:"Assign to department"
-n10: rectangle label:"Schedule orientation"
-n11: diamond label:"Background check clear?"
-n12: rectangle label:"Proceed with onboarding"
-n13: rectangle label:"Rescind offer"
-n7.handle(right) -> n8.handle(left)
-n8.handle(right) -> n9.handle(left)
-n9.handle(right) -> n10.handle(left)
-n10.handle(right) -> n11.handle(left)
-n11.handle(right) -> n12.handle(left) [label="Yes"]
-n11.handle(bottom) -> n13.handle(top) [label="No"]
-n12.handle(top) -> NewHire.n3.handle(bottom) [label="Continue"]
-n13.handle(top) -> NewHire.n6.handle(bottom) [label="Terminated"]
-}
-IT { # IT Department
-n14: rectangle label:"Create user accounts"
-n15: rectangle label:"Provision laptop"
-n16: rectangle label:"Set up email and Slack"
-n17: rectangle label:"Grant system access"
-n18: diamond label:"Equipment ready?"
-n19: rectangle label:"Ship to employee"
-n20: rectangle label:"Order equipment"
-n14.handle(right) -> n15.handle(left)
-n15.handle(right) -> n16.handle(left)
-n16.handle(right) -> n17.handle(left)
-n17.handle(right) -> n18.handle(left)
-n18.handle(right) -> n19.handle(left) [label="Yes"]
-n18.handle(bottom) -> n20.handle(top) [label="No"]
-n19.handle(top) -> NewHire.n4.handle(bottom) [label="Ready"]
-n20.handle(right) -> n19.handle(top)
-}
+NewHire { # New Hire
+n1: circle label:"Start"
+n2: rectangle label:"Accept offer letter"
+n3: rectangle label:"Complete I-9 and W-4 forms"
+n4: rectangle label:"Set up direct deposit"
+n5: rectangle label:"Complete first day orientation"
+n6: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> HR.n7.handle(top) [label="Signed"]
+n3.handle(bottom) -> IT.n14.handle(top) [label="Docs complete"]
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left)
+}
+HR { # Human Resources
+n7: rectangle label:"Create employee record"
+n8: rectangle label:"Enroll in benefits"
+n9: rectangle label:"Assign to department"
+n10: rectangle label:"Schedule orientation"
+n11: diamond label:"Background check clear?"
+n12: rectangle label:"Proceed with onboarding"
+n13: rectangle label:"Rescind offer"
+n7.handle(right) -> n8.handle(left)
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left)
+n10.handle(right) -> n11.handle(left)
+n11.handle(right) -> n12.handle(left) [label="Yes"]
+n11.handle(bottom) -> n13.handle(top) [label="No"]
+n12.handle(top) -> NewHire.n3.handle(bottom) [label="Continue"]
+n13.handle(top) -> NewHire.n6.handle(bottom) [label="Terminated"]
+}
+IT { # IT Department
+n14: rectangle label:"Create user accounts"
+n15: rectangle label:"Provision laptop"
+n16: rectangle label:"Set up email and Slack"
+n17: rectangle label:"Grant system access"
+n18: diamond label:"Equipment ready?"
+n19: rectangle label:"Ship to employee"
+n20: rectangle label:"Order equipment"
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left)
+n17.handle(right) -> n18.handle(left)
+n18.handle(right) -> n19.handle(left) [label="Yes"]
+n18.handle(bottom) -> n20.handle(top) [label="No"]
+n19.handle(top) -> NewHire.n4.handle(bottom) [label="Ready"]
+n20.handle(right) -> n19.handle(top)
+}
diff --git a/onboarding/process-mapping/cross-department-customer-onboarding-workflow/README.md b/onboarding/process-mapping/cross-department-customer-onboarding-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..410a18abe6ab7dc6744ac886f65837c5cf3f340b
--- /dev/null
+++ b/onboarding/process-mapping/cross-department-customer-onboarding-workflow/README.md
@@ -0,0 +1,19 @@
+# Cross-Department Customer Onboarding Workflow
+
+Five-lane customer onboarding workflow spanning sales, legal, finance, onboarding and the customer, with acceptance gates and a 30-day check-in before activation.
+
+**Template ID:** `cross-department-customer-onboarding-workflow`  
+**Kind:** workflow  
+**Source domain:** Process Mapping  
+**Primary use case:** onboarding  
+**Secondary use cases:** process-mapping  
+**Complexity:** 3/5  
+**Nodes:** 32  
+**Lanes:** 5  
+**Tags:** [process-mapping, customer-onboarding, cross-functional, sales, legal, finance]  
+**Source path:** ``  
+**Repo path:** `onboarding/process-mapping/cross-department-customer-onboarding-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/onboarding/process-mapping/cross-department-customer-onboarding-workflow/metadata.json b/onboarding/process-mapping/cross-department-customer-onboarding-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..0a1535aea59559fbdd0a76380ee24de544992477
--- /dev/null
+++ b/onboarding/process-mapping/cross-department-customer-onboarding-workflow/metadata.json
@@ -0,0 +1,29 @@
+{
+  "template_id": "cross-department-customer-onboarding-workflow",
+  "workflow_id": "cross-department-customer-onboarding",
+  "title": "Cross-Department Customer Onboarding Workflow",
+  "kind": "workflow",
+  "source_domain": "Process Mapping",
+  "primary_use_case": "onboarding",
+  "secondary_use_cases": [
+    "process-mapping"
+  ],
+  "use_cases": [
+    "onboarding",
+    "process-mapping"
+  ],
+  "complexity": 3,
+  "num_nodes": 32,
+  "num_lanes": 5,
+  "tags": [
+    "process-mapping",
+    "customer-onboarding",
+    "cross-functional",
+    "sales",
+    "legal",
+    "finance"
+  ],
+  "description": "Five-lane customer onboarding workflow spanning sales, legal, finance, onboarding and the customer, with acceptance gates and a 30-day check-in before activation.",
+  "source_path": "",
+  "repo_path": "onboarding/process-mapping/cross-department-customer-onboarding-workflow"
+}
diff --git a/onboarding/process-mapping/cross-department-customer-onboarding-workflow/workflow.fz b/onboarding/process-mapping/cross-department-customer-onboarding-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..7059cb89d7ad132135b48471e06b08d6876497b1
--- /dev/null
+++ b/onboarding/process-mapping/cross-department-customer-onboarding-workflow/workflow.fz
@@ -0,0 +1,81 @@
+sales { # sales
+n1: circle label:"Lead Qualified"
+n2: rectangle label:"Initial Contact"
+n3: rectangle label:"Discovery Call"
+n4: diamond label:"Good Fit?"
+n5: rectangle label:"Prepare Proposal"
+n6: rectangle label:"Present Proposal"
+n7: diamond label:"Accepted?"
+n8: rectangle label:"Send Contract"
+n9: circle label:"Deal Lost"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(right) -> n4.handle(left)
+n4.handle(right) -> n5.handle(left) [label="Yes"]
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left) [label="Yes"]
+n8.handle(bottom) -> legal.n10.handle(top) [label="Review"]
+n7.handle(top) -> n9.handle(top) [label="No"]
+n4.handle(top) -> n9.handle(top) [label="No"]
+}
+
+legal { # legal
+n10: rectangle label:"Contract Review"
+n11: diamond label:"Terms OK?"
+n12: rectangle label:"Request Changes"
+n13: rectangle label:"Finalize Contract"
+n14: rectangle label:"Contract Signed"
+n10.handle(right) -> n11.handle(left)
+n12.handle(top) -> sales.n6.handle(bottom) [label="Negotiate"]
+n13.handle(right) -> n14.handle(left)
+n14.handle(bottom) -> finance.n15.handle(top) [label="Process"]
+n11.handle(bottom) -> n13.handle(bottom) [label="Yes"]
+n11.handle(right) -> n12.handle(left) [label="No"]
+}
+
+finance { # finance
+n15: rectangle label:"Setup Billing"
+n16: rectangle label:"Process Payment"
+n17: diamond label:"Payment OK?"
+n18: rectangle label:"Payment Issue"
+n19: rectangle label:"Account Active"
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left)
+n19.handle(bottom) -> operations.n20.handle(top) [label="Activate"]
+n17.handle(top) -> n19.handle(top) [label="Yes"]
+n18.handle(bottom) -> n16.handle(bottom) [label="Retry"]
+n17.handle(right) -> n18.handle(left) [label="No"]
+}
+
+operations { # operations
+n20: rectangle label:"Create Account"
+n21: rectangle label:"Setup Environment"
+n22: rectangle label:"Configure Settings"
+n23: rectangle label:"Assign Team"
+n24: rectangle label:"Schedule Training"
+n20.handle(right) -> n21.handle(left)
+n21.handle(right) -> n22.handle(left)
+n22.handle(right) -> n23.handle(left)
+n23.handle(right) -> n24.handle(left)
+n24.handle(bottom) -> customersuccess.n25.handle(top) [label="Handoff"]
+}
+
+customersuccess { # customersuccess
+n25: rectangle label:"Welcome Call"
+n26: rectangle label:"Product Training"
+n27: rectangle label:"Implementation Support"
+n28: diamond label:"Ready to Launch?"
+n29: rectangle label:"Additional Training"
+n30: rectangle label:"Go Live"
+n31: rectangle label:"30-Day Check-in"
+n32: circle label:"Onboarding Complete"
+n25.handle(right) -> n26.handle(left)
+n26.handle(right) -> n27.handle(left)
+n27.handle(right) -> n28.handle(left)
+n28.handle(right) -> n30.handle(left) [label="Yes"]
+n30.handle(right) -> n31.handle(left)
+n31.handle(right) -> n32.handle(left)
+n28.handle(top) -> n29.handle(top) [label="No"]
+n29.handle(bottom) -> n27.handle(bottom) [label="Continue"]
+}
diff --git a/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/README.md b/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..d2e67fffd04d4acd2cd12f5caa78896d68b35c0f
--- /dev/null
+++ b/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/README.md
@@ -0,0 +1,19 @@
+# Process Documentation & Knowledge Capture Workflow
+
+Knowledge capture workflow: document the current process steps, write the step-by-step guide, get it approved and track onboarding to completion.
+
+**Template ID:** `process-documentation-knowledge-capture-workflow`  
+**Kind:** workflow  
+**Source domain:** Process Mapping  
+**Primary use case:** onboarding  
+**Secondary use cases:** process-mapping  
+**Complexity:** 3/5  
+**Nodes:** 13  
+**Lanes:** 2  
+**Tags:** [process-mapping, documentation, knowledge, onboarding, sop]  
+**Source path:** ``  
+**Repo path:** `onboarding/process-mapping/process-documentation-knowledge-capture-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/metadata.json b/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..6473c4fe692109dfe128ea108dc0a1a28a49abbd
--- /dev/null
+++ b/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/metadata.json
@@ -0,0 +1,28 @@
+{
+  "template_id": "process-documentation-knowledge-capture-workflow",
+  "workflow_id": "process-documentation-knowledge-capture",
+  "title": "Process Documentation & Knowledge Capture Workflow",
+  "kind": "workflow",
+  "source_domain": "Process Mapping",
+  "primary_use_case": "onboarding",
+  "secondary_use_cases": [
+    "process-mapping"
+  ],
+  "use_cases": [
+    "onboarding",
+    "process-mapping"
+  ],
+  "complexity": 3,
+  "num_nodes": 13,
+  "num_lanes": 2,
+  "tags": [
+    "process-mapping",
+    "documentation",
+    "knowledge",
+    "onboarding",
+    "sop"
+  ],
+  "description": "Knowledge capture workflow: document the current process steps, write the step-by-step guide, get it approved and track onboarding to completion.",
+  "source_path": "",
+  "repo_path": "onboarding/process-mapping/process-documentation-knowledge-capture-workflow"
+}
diff --git a/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/workflow.fz b/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..f4d3b8d873d407e6717ec94d2f5eec6ee184cd18
--- /dev/null
+++ b/onboarding/process-mapping/process-documentation-knowledge-capture-workflow/workflow.fz
@@ -0,0 +1,32 @@
+ProcessDocumentation { # ProcessDocumentation
+  n1: circle label:"Knowledge Gap Identified"
+  n2: rectangle label:"Document Current Process Steps"
+  n3: rectangle label:"Create Step-by-Step Guide"
+  n4: rectangle label:"Review and Validate with Team"
+  n5: diamond label:"Documentation Approved?"
+  n6: rectangle label:"Revise Documentation"
+  n4.handle(bottom) -> n5.handle(top)
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left)
+  n5.handle(left) -> OnboardingImplementation.n8.handle(top) [label="Yes"]
+  n5.handle(right) -> n6.handle(bottom) [label="No"]
+  n3.handle(right) -> n4.handle(left)
+  n6.handle(top) -> n4.handle(top)
+}
+
+OnboardingImplementation { # OnboardingImplementation
+  n7: circle label:"New Employee Starts"
+  n8: rectangle label:"Provide Process Documentation"
+  n9: rectangle label:"Self-Guided Learning"
+  n10: rectangle label:"Supervised Practice"
+  n11: diamond label:"Proficiency Achieved?"
+  n12: rectangle label:"Provide Additional Training"
+  n13: circle label:"Fully Onboarded"
+  n11.handle(right) -> n13.handle(left) [label="Yes"]
+  n11.handle(bottom) -> n12.handle(top) [label="No"]
+  n7.handle(right) -> n8.handle(left)
+  n8.handle(right) -> n9.handle(left)
+  n10.handle(right) -> n11.handle(left)
+  n12.handle(left) -> n10.handle(bottom)
+  n9.handle(right) -> n10.handle(left)
+}
diff --git a/patterns/architecture/cqrs-task-based-ui-architecture/README.md b/patterns/architecture/cqrs-task-based-ui-architecture/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..8513cfc4addd75dd1b3a6764be8c8873e4964cdc
--- /dev/null
+++ b/patterns/architecture/cqrs-task-based-ui-architecture/README.md
@@ -0,0 +1,19 @@
+# CQRS Task-Based UI Architecture
+
+A CQRS task-based UI architecture diagram where the frontend captures user intent as explicit commands, submits them asynchronously with optimistic updates, and receives real-time confirmations via WebSocket when the read model is synchronized. This template models the modern UI pattern that replaces CRUD forms with intent-driven commands, enabling responsive user experiences with eventual consistency. Recommended for teams building reactive frontends on CQRS backends.
+
+**Template ID:** `cqrs-task-based-ui-architecture`  
+**Kind:** architecture  
+**Source domain:** Architecture  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 4/5  
+**Nodes:** 19  
+**Lanes:** 4  
+**Tags:** [task-based-ui, cqrs, optimistic-update, websocket, command-pattern, idempotency, reactive-ui, architecture-diagram]  
+**Source path:** ``  
+**Repo path:** `patterns/architecture/cqrs-task-based-ui-architecture`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/architecture/cqrs-task-based-ui-architecture/metadata.json b/patterns/architecture/cqrs-task-based-ui-architecture/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..a59b0a058bdd0a2816aee3164ffd7a9d01c8aa9d
--- /dev/null
+++ b/patterns/architecture/cqrs-task-based-ui-architecture/metadata.json
@@ -0,0 +1,28 @@
+{
+  "template_id": "cqrs-task-based-ui-architecture",
+  "workflow_id": "cqrs-task-based-ui-architecture",
+  "title": "CQRS Task-Based UI Architecture",
+  "kind": "architecture",
+  "source_domain": "Architecture",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 4,
+  "num_nodes": 19,
+  "num_lanes": 4,
+  "tags": [
+    "task-based-ui",
+    "cqrs",
+    "optimistic-update",
+    "websocket",
+    "command-pattern",
+    "idempotency",
+    "reactive-ui",
+    "architecture-diagram"
+  ],
+  "description": "A CQRS task-based UI architecture diagram where the frontend captures user intent as explicit commands, submits them asynchronously with optimistic updates, and receives real-time confirmations via WebSocket when the read model is synchronized. This template models the modern UI pattern that replaces CRUD forms with intent-driven commands, enabling responsive user experiences with eventual consistency. Recommended for teams building reactive frontends on CQRS backends.",
+  "source_path": "",
+  "repo_path": "patterns/architecture/cqrs-task-based-ui-architecture"
+}
diff --git a/patterns/architecture/cqrs-task-based-ui-architecture/workflow.fz b/patterns/architecture/cqrs-task-based-ui-architecture/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..e18798c1d603965e3d61d517c130a698e08a0371
--- /dev/null
+++ b/patterns/architecture/cqrs-task-based-ui-architecture/workflow.fz
@@ -0,0 +1,48 @@
+UI { # Task-Based UI
+n1: circle label:"User Intent"
+n2: rectangle label:"Render Task Form"
+n3: rectangle label:"Capture User Intent as Command"
+n4: rectangle label:"Submit Command"
+n23: rectangle label:"Show Optimistic Update"
+n24: circle label:"UI Confirmed"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left) [label="PlaceOrder"]
+n3.handle(right) -> n4.handle(left) [label="Command DTO"]
+n4.handle(bottom) -> CommandAPI.n5.handle(top) [label="POST /commands"]
+n23.handle(right) -> n24.handle(left)
+}
+CommandAPI { # Command API
+n5: rectangle label:"Deserialize Command"
+n6: rectangle label:"Authorize User"
+n7: diamond label:"Idempotency Check"
+n8: rectangle label:"Dispatch to Handler"
+n9: rectangle label:"Return 202 Accepted"
+n10: rectangle label:"Return 409 Duplicate"
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left) [label="New"]
+n7.handle(bottom) -> n10.handle(top) [label="Duplicate"]
+n8.handle(right) -> n9.handle(left) [label="Queued"]
+n8.handle(bottom) -> Domain.n11.handle(top) [label="Process"]
+n9.handle(top) -> UI.n23.handle(bottom) [label="202 Accepted"]
+}
+Domain { # Domain Model
+n11: rectangle label:"Load Aggregate"
+n12: rectangle label:"Execute Business Logic"
+n13: rectangle label:"Persist State Change"
+n14: rectangle label:"Emit Events"
+n11.handle(right) -> n12.handle(left) [label="Current State"]
+n12.handle(right) -> n13.handle(left) [label="New State"]
+n13.handle(right) -> n14.handle(left) [label="Committed"]
+n14.handle(bottom) -> QuerySync.n15.handle(top) [label="Async"]
+}
+QuerySync { # Query Synchronization
+n15: rectangle label:"Update Read Model"
+n16: rectangle label:"Invalidate Cache"
+n17: rectangle label:"Push via WebSocket"
+n18: rectangle label:"Send Confirmed Update"
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left) [label="Real-Time"]
+n17.handle(right) -> n18.handle(left)
+n18.handle(top) -> UI.n23.handle(bottom) [label="Confirmed"]
+}
diff --git a/patterns/architecture/outbox-pattern-reliable-messaging-architecture/README.md b/patterns/architecture/outbox-pattern-reliable-messaging-architecture/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..48746425afd0bcd557a238846e4c435bc6bbe638
--- /dev/null
+++ b/patterns/architecture/outbox-pattern-reliable-messaging-architecture/README.md
@@ -0,0 +1,19 @@
+# Outbox Pattern for Reliable Messaging Architecture
+
+A transactional outbox architecture diagram where domain writes and event publishing happen in the same database transaction, with a relay process polling the outbox table and publishing events to a message broker with guaranteed delivery. This template solves the dual-write problem where updating a database and publishing an event are not atomic, ensuring exactly-once event delivery without distributed transactions. Critical for event-driven architectures requiring reliable message publishing.
+
+**Template ID:** `outbox-pattern-reliable-messaging-architecture`  
+**Kind:** architecture  
+**Source domain:** Architecture  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 4/5  
+**Nodes:** 18  
+**Lanes:** 4  
+**Tags:** [outbox-pattern, transactional-outbox, reliable-messaging, dual-write, exactly-once, debezium, event-publishing, architecture-diagram]  
+**Source path:** ``  
+**Repo path:** `patterns/architecture/outbox-pattern-reliable-messaging-architecture`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/architecture/outbox-pattern-reliable-messaging-architecture/metadata.json b/patterns/architecture/outbox-pattern-reliable-messaging-architecture/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..2d30926ec97bfa0d50bb0a83fb45116ff923f9b2
--- /dev/null
+++ b/patterns/architecture/outbox-pattern-reliable-messaging-architecture/metadata.json
@@ -0,0 +1,28 @@
+{
+  "template_id": "outbox-pattern-reliable-messaging-architecture",
+  "workflow_id": "outbox-pattern-reliable-messaging-architecture",
+  "title": "Outbox Pattern for Reliable Messaging Architecture",
+  "kind": "architecture",
+  "source_domain": "Architecture",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 4,
+  "num_nodes": 18,
+  "num_lanes": 4,
+  "tags": [
+    "outbox-pattern",
+    "transactional-outbox",
+    "reliable-messaging",
+    "dual-write",
+    "exactly-once",
+    "debezium",
+    "event-publishing",
+    "architecture-diagram"
+  ],
+  "description": "A transactional outbox architecture diagram where domain writes and event publishing happen in the same database transaction, with a relay process polling the outbox table and publishing events to a message broker with guaranteed delivery. This template solves the dual-write problem where updating a database and publishing an event are not atomic, ensuring exactly-once event delivery without distributed transactions. Critical for event-driven architectures requiring reliable message publishing.",
+  "source_path": "",
+  "repo_path": "patterns/architecture/outbox-pattern-reliable-messaging-architecture"
+}
diff --git a/patterns/architecture/outbox-pattern-reliable-messaging-architecture/workflow.fz b/patterns/architecture/outbox-pattern-reliable-messaging-architecture/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..205ae4d31c96d776c007b57d7c87b4efbd482117
--- /dev/null
+++ b/patterns/architecture/outbox-pattern-reliable-messaging-architecture/workflow.fz
@@ -0,0 +1,54 @@
+Application { # Application Service
+n1: circle label:"Business Operation"
+n2: rectangle label:"Begin Transaction"
+n3: rectangle label:"Update Domain Table"
+n4: rectangle label:"Insert into Outbox Table"
+n9: rectangle label:"Write Confirmed"
+n10: rectangle label:"Commit Transaction"
+n11: circle label:"Return Success"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left) [label="Atomic"]
+n3.handle(right) -> n4.handle(left) [label="Same TX"]
+n4.handle(bottom) -> Database.n5.handle(top) [label="Write"]
+n9.handle(right) -> n10.handle(left) [label="Committed"]
+n10.handle(right) -> n11.handle(left)
+}
+Database { # Database
+n5: rectangle label:"Domain Table (Orders)"
+n6: rectangle label:"Outbox Table (Events)"
+n7: rectangle label:"Persist Records"
+n8: rectangle label:"Confirm Write"
+n12: rectangle label:"Outbox Row: Pending"
+n24: rectangle label:"Row Marked Processed"
+n5.handle(right) -> n6.handle(left) [label="Same Database"]
+n6.handle(right) -> n7.handle(left)
+n7.handle(right) -> n8.handle(left)
+n8.handle(top) -> Application.n9.handle(bottom) [label="Confirmed"]
+n12.handle(bottom) -> Relay.n13.handle(top) [label="Poll"]
+}
+Relay { # Outbox Relay (Debezium/Poller)
+n13: rectangle label:"Poll Outbox Table"
+n14: rectangle label:"Read Pending Events"
+n15: rectangle label:"Publish to Message Broker"
+n16: diamond label:"Published Successfully?"
+n17: rectangle label:"Deliver to Consumers"
+n18: rectangle label:"Schedule Retry"
+n23: rectangle label:"Receive Consumer Ack"
+n13.handle(right) -> n14.handle(left) [label="SELECT WHERE status=PENDING"]
+n14.handle(right) -> n15.handle(left) [label="Serialize"]
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left) [label="Yes"]
+n16.handle(bottom) -> n18.handle(top) [label="No"]
+n17.handle(bottom) -> Consumers.n19.handle(top) [label="Deliver"]
+n23.handle(top) -> Database.n24.handle(bottom) [label="Mark Processed"]
+}
+Consumers { # Downstream Consumers
+n19: rectangle label:"Notification Service"
+n20: rectangle label:"Analytics Service"
+n21: rectangle label:"Search Index Service"
+n22: rectangle label:"Acknowledge Receipt"
+n19.handle(right) -> n20.handle(left) [label="OrderCreated"]
+n20.handle(right) -> n21.handle(left) [label="OrderCreated"]
+n21.handle(right) -> n22.handle(left)
+n22.handle(top) -> Relay.n23.handle(bottom) [label="Ack"]
+}
diff --git a/patterns/architecture/retry-with-exponential-backoff-architecture/README.md b/patterns/architecture/retry-with-exponential-backoff-architecture/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..44859a16ca0ad6b5de37766f6d5bb4c5921dc1ac
--- /dev/null
+++ b/patterns/architecture/retry-with-exponential-backoff-architecture/README.md
@@ -0,0 +1,19 @@
+# Retry with Exponential Backoff Architecture
+
+A retry with exponential backoff architecture diagram showing the complete retry policy engine with retryable vs non-retryable error classification, exponential delay calculation with jitter, max retry thresholds, and graceful exhaustion handling. This template models the essential resilience pattern for handling transient failures in distributed systems, preventing thundering herd problems through randomized backoff delays. Foundational for any service-to-service communication in cloud architectures.
+
+**Template ID:** `retry-with-exponential-backoff-architecture`  
+**Kind:** architecture  
+**Source domain:** Architecture  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 17  
+**Lanes:** 3  
+**Tags:** [retry-pattern, exponential-backoff, jitter, transient-failure, resilience, error-handling, thundering-herd, architecture-diagram]  
+**Source path:** ``  
+**Repo path:** `patterns/architecture/retry-with-exponential-backoff-architecture`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/architecture/retry-with-exponential-backoff-architecture/metadata.json b/patterns/architecture/retry-with-exponential-backoff-architecture/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..856a960fbc41fbec1719eba3178d217404367d50
--- /dev/null
+++ b/patterns/architecture/retry-with-exponential-backoff-architecture/metadata.json
@@ -0,0 +1,28 @@
+{
+  "template_id": "retry-with-exponential-backoff-architecture",
+  "workflow_id": "retry-with-exponential-backoff-architecture",
+  "title": "Retry with Exponential Backoff Architecture",
+  "kind": "architecture",
+  "source_domain": "Architecture",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 17,
+  "num_lanes": 3,
+  "tags": [
+    "retry-pattern",
+    "exponential-backoff",
+    "jitter",
+    "transient-failure",
+    "resilience",
+    "error-handling",
+    "thundering-herd",
+    "architecture-diagram"
+  ],
+  "description": "A retry with exponential backoff architecture diagram showing the complete retry policy engine with retryable vs non-retryable error classification, exponential delay calculation with jitter, max retry thresholds, and graceful exhaustion handling. This template models the essential resilience pattern for handling transient failures in distributed systems, preventing thundering herd problems through randomized backoff delays. Foundational for any service-to-service communication in cloud architectures.",
+  "source_path": "",
+  "repo_path": "patterns/architecture/retry-with-exponential-backoff-architecture"
+}
diff --git a/patterns/architecture/retry-with-exponential-backoff-architecture/workflow.fz b/patterns/architecture/retry-with-exponential-backoff-architecture/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..786916bf9eb012fa4b29defbb88c324fb4d98e37
--- /dev/null
+++ b/patterns/architecture/retry-with-exponential-backoff-architecture/workflow.fz
@@ -0,0 +1,48 @@
+Caller { # Calling Service
+n1: circle label:"Initiate Request"
+n2: rectangle label:"Send HTTP Request"
+n19: rectangle label:"Receive Response"
+n20: circle label:"Request Complete"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> RetryPolicy.n3.handle(top) [label="Execute"]
+n19.handle(right) -> n20.handle(left)
+}
+RetryPolicy { # Retry Policy Engine
+n3: rectangle label:"Attempt Request"
+n8: diamond label:"Response Status?"
+n9: rectangle label:"Return Success"
+n10: diamond label:"Retryable Error?"
+n11: rectangle label:"Return Permanent Failure"
+n12: rectangle label:"Calculate Backoff Delay"
+n13: diamond label:"Max Retries Exceeded?"
+n14: rectangle label:"Wait with Jitter"
+n15: rectangle label:"Return Exhausted Error"
+n16: rectangle label:"Forward Success"
+n17: rectangle label:"Forward Failure"
+n18: rectangle label:"Forward Exhausted"
+n3.handle(bottom) -> Target.n4.handle(top) [label="HTTP"]
+n8.handle(right) -> n9.handle(left) [label="2xx"]
+n8.handle(bottom) -> n10.handle(top) [label="Error"]
+n9.handle(right) -> n16.handle(left)
+n10.handle(right) -> n12.handle(left) [label="429/503/Timeout"]
+n10.handle(bottom) -> n11.handle(top) [label="400/401/404"]
+n11.handle(right) -> n17.handle(left)
+n12.handle(right) -> n13.handle(left) [label="2^n * base"]
+n13.handle(bottom) -> n15.handle(top) [label="Yes"]
+n13.handle(right) -> n14.handle(left) [label="No"]
+n15.handle(right) -> n18.handle(left)
+n16.handle(top) -> Caller.n19.handle(bottom) [label="Success"]
+n17.handle(top) -> Caller.n19.handle(bottom) [label="Non-Retryable"]
+n18.handle(top) -> Caller.n19.handle(bottom) [label="Max Retries"]
+}
+Target { # Target Service
+n4: rectangle label:"Process Request"
+n5: diamond label:"Service Healthy?"
+n6: rectangle label:"Return 200 OK"
+n7: rectangle label:"Return 503 Unavailable"
+n4.handle(right) -> n5.handle(left)
+n5.handle(right) -> n6.handle(left) [label="Yes"]
+n5.handle(bottom) -> n7.handle(top) [label="No"]
+n6.handle(top) -> RetryPolicy.n8.handle(bottom) [label="Success"]
+n7.handle(top) -> RetryPolicy.n8.handle(bottom) [label="Error"]
+}
diff --git a/patterns/patterns/a-b-testing-workflow/README.md b/patterns/patterns/a-b-testing-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..331cd2e3fae716365dc0dfa9292ff5434afb228b
--- /dev/null
+++ b/patterns/patterns/a-b-testing-workflow/README.md
@@ -0,0 +1,19 @@
+# A B Testing Workflow
+
+This workflow models comparing two versions to see which performs better.
+
+**Template ID:** `a-b-testing-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [a, b, testing, patterns]  
+**Source path:** `patterns/a-b-testing`  
+**Repo path:** `patterns/patterns/a-b-testing-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/a-b-testing-workflow/metadata.json b/patterns/patterns/a-b-testing-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..61c2128f34b210db617769d0c9a50768d09ccd25
--- /dev/null
+++ b/patterns/patterns/a-b-testing-workflow/metadata.json
@@ -0,0 +1,24 @@
+{
+  "template_id": "a-b-testing-workflow",
+  "workflow_id": "a-b-testing",
+  "title": "A B Testing Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "a",
+    "b",
+    "testing",
+    "patterns"
+  ],
+  "description": "This workflow models comparing two versions to see which performs better.",
+  "source_path": "patterns/a-b-testing",
+  "repo_path": "patterns/patterns/a-b-testing-workflow"
+}
diff --git a/patterns/patterns/a-b-testing-workflow/workflow.fz b/patterns/patterns/a-b-testing-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..a1298eed5feb8ae7bb3ee4de2de196c3a291f56e
--- /dev/null
+++ b/patterns/patterns/a-b-testing-workflow/workflow.fz
@@ -0,0 +1,28 @@
+user { # User
+  n1: circle label:"Start A B Testing"
+  n4: rectangle label:"Execute A B Testing action"
+  n7: rectangle label:"Monitor A B Testing status"
+  n10: circle label:"End A B Testing"
+  n1.handle(bottom) -> app.n2.handle(top)
+  n4.handle(bottom) -> app.n5.handle(top)
+  n7.handle(bottom) -> app.n8.handle(top)
+}
+
+app { # App
+  n2: rectangle label:"Receive A B Testing event"
+  n5: rectangle label:"Record A B Testing outcome"
+  n8: rectangle label:"Monitor A B Testing status"
+  n2.handle(bottom) -> service.n3.handle(top) [label="Next"]
+  n5.handle(bottom) -> service.n6.handle(top) [label="Done"]
+  n8.handle(bottom) -> service.n9.handle(top) [label="Processed"]
+}
+
+service { # Service
+  n3: rectangle label:"Validate A B Testing conditions"
+  n6: rectangle label:"Monitor A B Testing status"
+  n9: diamond label:"Monitor A B Testing status"
+  n3.handle(right) -> user.n4.handle(left)
+  n6.handle(right) -> user.n7.handle(left)
+  n9.handle(right) -> user.n10.handle(left)
+  n9.handle(left) -> app.n8.handle(left) [label="Retry/Rejected"]
+}
diff --git a/patterns/patterns/batch-processing-workflow/README.md b/patterns/patterns/batch-processing-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..866522dd9784f0fe7a9497c0da35acf67f94522b
--- /dev/null
+++ b/patterns/patterns/batch-processing-workflow/README.md
@@ -0,0 +1,19 @@
+# Batch Processing Workflow
+
+Batch processing pattern with job scheduling, chunk-based processing, checkpoint/restart capability, error handling, and completion reporting.
+
+**Template ID:** `batch-processing-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 7  
+**Lanes:** 2  
+**Tags:** [batch-processing, scheduled-jobs, bulk-operations, etl, chunk-processing, job-scheduler]  
+**Source path:** `patterns/batch-processing`  
+**Repo path:** `patterns/patterns/batch-processing-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/batch-processing-workflow/metadata.json b/patterns/patterns/batch-processing-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..d49bc909e6faf1ec58fa8af745304c9d55c830f7
--- /dev/null
+++ b/patterns/patterns/batch-processing-workflow/metadata.json
@@ -0,0 +1,26 @@
+{
+  "template_id": "batch-processing-workflow",
+  "workflow_id": "batch-processing",
+  "title": "Batch Processing Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 7,
+  "num_lanes": 2,
+  "tags": [
+    "batch-processing",
+    "scheduled-jobs",
+    "bulk-operations",
+    "etl",
+    "chunk-processing",
+    "job-scheduler"
+  ],
+  "description": "Batch processing pattern with job scheduling, chunk-based processing, checkpoint/restart capability, error handling, and completion reporting.",
+  "source_path": "patterns/batch-processing",
+  "repo_path": "patterns/patterns/batch-processing-workflow"
+}
diff --git a/patterns/patterns/batch-processing-workflow/workflow.fz b/patterns/patterns/batch-processing-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..39e8ce3cc96047f6f7e279a0054a6b04d7a48150
--- /dev/null
+++ b/patterns/patterns/batch-processing-workflow/workflow.fz
@@ -0,0 +1,19 @@
+user { # User
+  n1: circle label:"Start Batch Processing"
+  n3: rectangle label:"Validate Batch Processing conditions"
+  n5: rectangle label:"Record Batch Processing outcome"
+  n7: circle label:"End Batch Processing"
+  n1.handle(bottom) -> app.n2.handle(top)
+  n3.handle(bottom) -> app.n4.handle(top) [label="Processed"]
+  n5.handle(bottom) -> app.n6.handle(top)
+}
+
+app { # App
+  n2: rectangle label:"Receive Batch Processing event"
+  n4: diamond label:"Execute Batch Processing action"
+  n6: rectangle label:"Monitor Batch Processing status"
+  n6.handle(right) -> user.n7.handle(left) [label="Success"]
+  n2.handle(right) -> user.n3.handle(left)
+  n4.handle(left) -> user.n3.handle(left) [label="Retry/Rejected"]
+  n4.handle(right) -> user.n5.handle(left)
+}
diff --git a/patterns/patterns/cache-aside-workflow/README.md b/patterns/patterns/cache-aside-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..f2313c5235b3724064a466e09bdedba818797078
--- /dev/null
+++ b/patterns/patterns/cache-aside-workflow/README.md
@@ -0,0 +1,19 @@
+# Cache Aside Workflow
+
+Cache-aside pattern with cache lookup, database fallback on miss, cache population, TTL-based expiration, and write-through invalidation.
+
+**Template ID:** `cache-aside-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [cache-aside, lazy-loading, cache-miss, cache-invalidation, redis, performance]  
+**Source path:** `patterns/cache-aside`  
+**Repo path:** `patterns/patterns/cache-aside-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/cache-aside-workflow/metadata.json b/patterns/patterns/cache-aside-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..cec589c1256fc31f9f3f87e18dba3eb075fc7aec
--- /dev/null
+++ b/patterns/patterns/cache-aside-workflow/metadata.json
@@ -0,0 +1,26 @@
+{
+  "template_id": "cache-aside-workflow",
+  "workflow_id": "cache-aside",
+  "title": "Cache Aside Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "cache-aside",
+    "lazy-loading",
+    "cache-miss",
+    "cache-invalidation",
+    "redis",
+    "performance"
+  ],
+  "description": "Cache-aside pattern with cache lookup, database fallback on miss, cache population, TTL-based expiration, and write-through invalidation.",
+  "source_path": "patterns/cache-aside",
+  "repo_path": "patterns/patterns/cache-aside-workflow"
+}
diff --git a/patterns/patterns/cache-aside-workflow/workflow.fz b/patterns/patterns/cache-aside-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..e215eed70a7e57cdd6e0aa7b2ddf08967ba270bf
--- /dev/null
+++ b/patterns/patterns/cache-aside-workflow/workflow.fz
@@ -0,0 +1,46 @@
+Application { # Application
+n1: circle label:"Start"
+n2: rectangle label:"Request data by key"
+n3: rectangle label:"Return data to caller"
+n4: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(bottom) -> CacheLayer.n5.handle(top) [label="Lookup"]
+n3.handle(right) -> n4.handle(left)
+}
+CacheLayer { # Cache Layer
+n5: rectangle label:"Check cache for key"
+n6: diamond label:"Cache hit?"
+n7: rectangle label:"Return cached value"
+n8: rectangle label:"Query database"
+n9: rectangle label:"Store in cache with TTL"
+n5.handle(right) -> n6.handle(left)
+n6.handle(right) -> n7.handle(left) [label="Yes"]
+n6.handle(bottom) -> n8.handle(top) [label="No"]
+n7.handle(top) -> Application.n3.handle(bottom) [label="From cache"]
+n8.handle(bottom) -> Database.n10.handle(top) [label="Fetch"]
+n9.handle(top) -> Application.n3.handle(bottom) [label="From DB"]
+}
+Database { # Database
+n10: rectangle label:"Execute query"
+n11: diamond label:"Data found?"
+n12: rectangle label:"Return result set"
+n13: rectangle label:"Return empty result"
+n10.handle(right) -> n11.handle(left)
+n11.handle(right) -> n12.handle(left) [label="Yes"]
+n11.handle(bottom) -> n13.handle(top) [label="No"]
+n12.handle(top) -> CacheLayer.n9.handle(bottom) [label="Populate cache"]
+n13.handle(top) -> Application.n3.handle(bottom) [label="Not found"]
+}
+WriteOperation { # Write Operation
+n14: rectangle label:"Update database"
+n15: rectangle label:"Invalidate cache key"
+n16: diamond label:"Write-through?"
+n17: rectangle label:"Update cache directly"
+n18: rectangle label:"Let cache expire"
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left) [label="Yes"]
+n16.handle(bottom) -> n18.handle(top) [label="No"]
+n17.handle(top) -> Application.n3.handle(bottom) [label="Updated"]
+n18.handle(top) -> Application.n3.handle(bottom) [label="Invalidated"]
+}
diff --git a/patterns/patterns/callback-pattern-workflow/README.md b/patterns/patterns/callback-pattern-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e91a3a971d5510a212df2deb4c97e96f46767ab
--- /dev/null
+++ b/patterns/patterns/callback-pattern-workflow/README.md
@@ -0,0 +1,19 @@
+# Callback Pattern Workflow
+
+This workflow models an async operation that notifies a callback when done.
+
+**Template ID:** `callback-pattern-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [callback, pattern, patterns, decision, loop]  
+**Source path:** `patterns/callback-pattern`  
+**Repo path:** `patterns/patterns/callback-pattern-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/callback-pattern-workflow/metadata.json b/patterns/patterns/callback-pattern-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..97edb0028101f239bca58a2cd27e2feff4edea4e
--- /dev/null
+++ b/patterns/patterns/callback-pattern-workflow/metadata.json
@@ -0,0 +1,25 @@
+{
+  "template_id": "callback-pattern-workflow",
+  "workflow_id": "callback-pattern",
+  "title": "Callback Pattern Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "callback",
+    "pattern",
+    "patterns",
+    "decision",
+    "loop"
+  ],
+  "description": "This workflow models an async operation that notifies a callback when done.",
+  "source_path": "patterns/callback-pattern",
+  "repo_path": "patterns/patterns/callback-pattern-workflow"
+}
diff --git a/patterns/patterns/callback-pattern-workflow/workflow.fz b/patterns/patterns/callback-pattern-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..65b1be0a85c2d836efe02b74f65b9368a4987f38
--- /dev/null
+++ b/patterns/patterns/callback-pattern-workflow/workflow.fz
@@ -0,0 +1,28 @@
+user { # User
+  n1: circle label:"Start Callback Pattern"
+  n2: diamond label:"Receive Callback Pattern event"
+  n4: rectangle label:"Execute Callback Pattern action"
+  n7: rectangle label:"Monitor Callback Pattern status"
+  n10: circle label:"End Callback Pattern"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(bottom) -> service.n3.handle(top) [label="Yes/Approved"]
+  n4.handle(bottom) -> app.n5.handle(top)
+  n7.handle(right) -> app.n8.handle(top)
+  n2.handle(top) -> n4.handle(top) [label="No/Rejected"]
+}
+
+app { # App
+  n5: rectangle label:"Record Callback Pattern outcome"
+  n8: rectangle label:"Monitor Callback Pattern status"
+  n5.handle(bottom) -> service.n6.handle(top)
+  n8.handle(bottom) -> service.n9.handle(top)
+}
+
+service { # Service
+  n3: rectangle label:"Validate Callback Pattern conditions"
+  n6: rectangle label:"Monitor Callback Pattern status"
+  n9: rectangle label:"Monitor Callback Pattern status"
+  n9.handle(right) -> user.n10.handle(bottom)
+  n6.handle(right) -> user.n7.handle(bottom)
+  n3.handle(left) -> app.n5.handle(left)
+}
diff --git a/patterns/patterns/claim-check-workflow/README.md b/patterns/patterns/claim-check-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..d8346fac092fafd2521bb7c847d294c8ed031f64
--- /dev/null
+++ b/patterns/patterns/claim-check-workflow/README.md
@@ -0,0 +1,19 @@
+# Claim Check Workflow
+
+This workflow models keeping large payloads external and only passing references.
+
+**Template ID:** `claim-check-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 2/5  
+**Nodes:** 7  
+**Lanes:** 2  
+**Tags:** [claim, check, patterns]  
+**Source path:** `patterns/claim-check`  
+**Repo path:** `patterns/patterns/claim-check-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/claim-check-workflow/metadata.json b/patterns/patterns/claim-check-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..f6ef118612dc340f04fb3848228c81a7fdd049b6
--- /dev/null
+++ b/patterns/patterns/claim-check-workflow/metadata.json
@@ -0,0 +1,23 @@
+{
+  "template_id": "claim-check-workflow",
+  "workflow_id": "claim-check",
+  "title": "Claim Check Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 2,
+  "num_nodes": 7,
+  "num_lanes": 2,
+  "tags": [
+    "claim",
+    "check",
+    "patterns"
+  ],
+  "description": "This workflow models keeping large payloads external and only passing references.",
+  "source_path": "patterns/claim-check",
+  "repo_path": "patterns/patterns/claim-check-workflow"
+}
diff --git a/patterns/patterns/claim-check-workflow/workflow.fz b/patterns/patterns/claim-check-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..28bcc2cb035411e10a7a8e1583e3e2f376c6d48f
--- /dev/null
+++ b/patterns/patterns/claim-check-workflow/workflow.fz
@@ -0,0 +1,18 @@
+user { # User
+  n1: circle label:"Start Claim Check"
+  n3: rectangle label:"Validate Claim Check conditions"
+  n5: rectangle label:"Record Claim Check outcome"
+  n7: circle label:"End Claim Check"
+  n1.handle(bottom) -> app.n2.handle(top)
+  n3.handle(bottom) -> app.n4.handle(top) [label="Processed"]
+  n5.handle(bottom) -> app.n6.handle(top)
+}
+
+app { # App
+  n2: rectangle label:"Receive Claim Check event"
+  n4: rectangle label:"Execute Claim Check action"
+  n6: rectangle label:"Monitor Claim Check status"
+  n2.handle(right) -> user.n3.handle(left)
+  n4.handle(right) -> user.n5.handle(left)
+  n6.handle(right) -> user.n7.handle(left) [label="Success"]
+}
diff --git a/patterns/patterns/compensation-transaction-workflow/README.md b/patterns/patterns/compensation-transaction-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..e2147f38247e62dbb2f3dd6c71808e9291a02c12
--- /dev/null
+++ b/patterns/patterns/compensation-transaction-workflow/README.md
@@ -0,0 +1,19 @@
+# Compensation Transaction Workflow
+
+This workflow models rolling back work when a later step fails.
+
+**Template ID:** `compensation-transaction-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 2/5  
+**Nodes:** 7  
+**Lanes:** 2  
+**Tags:** [compensation, transaction, patterns, decision, loop]  
+**Source path:** `patterns/compensation-transaction`  
+**Repo path:** `patterns/patterns/compensation-transaction-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/compensation-transaction-workflow/metadata.json b/patterns/patterns/compensation-transaction-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..cb3a37c8b898eddc2a7fcca3b6e8cf9be6dbeded
--- /dev/null
+++ b/patterns/patterns/compensation-transaction-workflow/metadata.json
@@ -0,0 +1,25 @@
+{
+  "template_id": "compensation-transaction-workflow",
+  "workflow_id": "compensation-transaction",
+  "title": "Compensation Transaction Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 2,
+  "num_nodes": 7,
+  "num_lanes": 2,
+  "tags": [
+    "compensation",
+    "transaction",
+    "patterns",
+    "decision",
+    "loop"
+  ],
+  "description": "This workflow models rolling back work when a later step fails.",
+  "source_path": "patterns/compensation-transaction",
+  "repo_path": "patterns/patterns/compensation-transaction-workflow"
+}
diff --git a/patterns/patterns/compensation-transaction-workflow/workflow.fz b/patterns/patterns/compensation-transaction-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..fce5cc1b2640309c9289f40ced61a27d3dcf861f
--- /dev/null
+++ b/patterns/patterns/compensation-transaction-workflow/workflow.fz
@@ -0,0 +1,19 @@
+user { # User
+  n1: circle label:"Start Compensation Transaction"
+  n2: diamond label:"Receive Compensation Transaction event"
+  n3: rectangle label:"Validate Compensation Transaction conditions"
+  n5: rectangle label:"Record Compensation Transaction outcome"
+  n7: circle label:"End Compensation Transaction"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left) [label="Yes/Approved"]
+  n2.handle(bottom) -> app.n4.handle(top) [label="No/Rejected"]
+  n3.handle(right) -> n5.handle(left)
+  n5.handle(right) -> app.n6.handle(top)
+}
+
+app { # App
+  n4: rectangle label:"Execute Compensation Transaction action"
+  n6: rectangle label:"Monitor Compensation Transaction status"
+  n6.handle(right) -> user.n7.handle(bottom)
+  n4.handle(right) -> user.n5.handle(bottom)
+}
diff --git a/patterns/patterns/content-enricher-workflow/README.md b/patterns/patterns/content-enricher-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..218c2ca8a35961eb54b2e987b9758a1467c1e963
--- /dev/null
+++ b/patterns/patterns/content-enricher-workflow/README.md
@@ -0,0 +1,19 @@
+# Content Enricher Workflow
+
+This workflow models adding extra data from other sources.
+
+**Template ID:** `content-enricher-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [content, enricher, patterns, decision]  
+**Source path:** `patterns/content-enricher`  
+**Repo path:** `patterns/patterns/content-enricher-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/content-enricher-workflow/metadata.json b/patterns/patterns/content-enricher-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..2797f124ea21ed76738350844bf0da1b993cb7f2
--- /dev/null
+++ b/patterns/patterns/content-enricher-workflow/metadata.json
@@ -0,0 +1,24 @@
+{
+  "template_id": "content-enricher-workflow",
+  "workflow_id": "content-enricher",
+  "title": "Content Enricher Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "content",
+    "enricher",
+    "patterns",
+    "decision"
+  ],
+  "description": "This workflow models adding extra data from other sources.",
+  "source_path": "patterns/content-enricher",
+  "repo_path": "patterns/patterns/content-enricher-workflow"
+}
diff --git a/patterns/patterns/content-enricher-workflow/workflow.fz b/patterns/patterns/content-enricher-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..2068cfb7636a8532230ef020499f77778ec90997
--- /dev/null
+++ b/patterns/patterns/content-enricher-workflow/workflow.fz
@@ -0,0 +1,28 @@
+user { # User
+  n1: circle label:"Start Content Enricher"
+  n2: diamond label:"Receive Content Enricher event"
+  n4: rectangle label:"Execute Content Enricher action"
+  n7: rectangle label:"Monitor Content Enricher status"
+  n10: circle label:"End Content Enricher"
+  n1.handle(right) -> n2.handle(left)
+  n4.handle(bottom) -> app.n5.handle(top)
+  n7.handle(bottom) -> app.n8.handle(top)
+  n2.handle(top) -> n4.handle(top) [label="No/Rejected"]
+  n2.handle(bottom) -> service.n3.handle(top) [label="Yes/Approved"]
+}
+
+app { # App
+  n5: rectangle label:"Record Content Enricher outcome"
+  n8: rectangle label:"Monitor Content Enricher status"
+  n5.handle(bottom) -> service.n6.handle(top)
+  n8.handle(bottom) -> service.n9.handle(top)
+}
+
+service { # Service
+  n3: rectangle label:"Validate Content Enricher conditions"
+  n6: rectangle label:"Monitor Content Enricher status"
+  n9: rectangle label:"Monitor Content Enricher status"
+  n9.handle(right) -> user.n10.handle(bottom)
+  n6.handle(right) -> user.n7.handle(left)
+  n3.handle(left) -> app.n5.handle(left)
+}
diff --git a/patterns/patterns/cqrs-workflow/README.md b/patterns/patterns/cqrs-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..9c57f992f540f2667efdac1164243afe526f734e
--- /dev/null
+++ b/patterns/patterns/cqrs-workflow/README.md
@@ -0,0 +1,19 @@
+# Cqrs Workflow
+
+CQRS (Command Query Responsibility Segregation) pattern with separate command and query paths, domain event publishing, read model synchronization, and DTO transformation.
+
+**Template ID:** `cqrs-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 4/5  
+**Nodes:** 19  
+**Lanes:** 4  
+**Tags:** [cqrs, command-query-separation, event-sourcing, read-model, write-model, domain-events, eventual-consistency]  
+**Source path:** `patterns/cqrs`  
+**Repo path:** `patterns/patterns/cqrs-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/cqrs-workflow/metadata.json b/patterns/patterns/cqrs-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..a314df9c5b8ac7a1bb3474f1dea7f3b4d7ac6a73
--- /dev/null
+++ b/patterns/patterns/cqrs-workflow/metadata.json
@@ -0,0 +1,27 @@
+{
+  "template_id": "cqrs-workflow",
+  "workflow_id": "cqrs",
+  "title": "Cqrs Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 4,
+  "num_nodes": 19,
+  "num_lanes": 4,
+  "tags": [
+    "cqrs",
+    "command-query-separation",
+    "event-sourcing",
+    "read-model",
+    "write-model",
+    "domain-events",
+    "eventual-consistency"
+  ],
+  "description": "CQRS (Command Query Responsibility Segregation) pattern with separate command and query paths, domain event publishing, read model synchronization, and DTO transformation.",
+  "source_path": "patterns/cqrs",
+  "repo_path": "patterns/patterns/cqrs-workflow"
+}
diff --git a/patterns/patterns/cqrs-workflow/workflow.fz b/patterns/patterns/cqrs-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..edae1e4a799d52138fdab07bfc4702e0385db945
--- /dev/null
+++ b/patterns/patterns/cqrs-workflow/workflow.fz
@@ -0,0 +1,48 @@
+Client { # Client Application
+n1: circle label:"Start"
+n2: rectangle label:"User initiates action"
+n3: diamond label:"Read or write?"
+n4: rectangle label:"Send command"
+n5: rectangle label:"Send query"
+n6: rectangle label:"Receive response"
+n7: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(right) -> n4.handle(left) [label="Write"]
+n3.handle(bottom) -> n5.handle(top) [label="Read"]
+n4.handle(bottom) -> CommandSide.n8.handle(top) [label="Command"]
+n5.handle(bottom) -> QuerySide.n16.handle(top) [label="Query"]
+n6.handle(right) -> n7.handle(left)
+}
+CommandSide { # Command Side
+n8: rectangle label:"Validate command"
+n9: diamond label:"Command valid?"
+n10: rectangle label:"Execute domain logic"
+n11: rectangle label:"Persist to write store"
+n12: rectangle label:"Publish domain event"
+n13: rectangle label:"Return validation error"
+n8.handle(right) -> n9.handle(left)
+n9.handle(right) -> n10.handle(left) [label="Yes"]
+n9.handle(bottom) -> n13.handle(top) [label="No"]
+n10.handle(right) -> n11.handle(left)
+n11.handle(right) -> n12.handle(left)
+n12.handle(bottom) -> EventHandler.n14.handle(top) [label="Event"]
+n12.handle(top) -> Client.n6.handle(bottom) [label="Success"]
+n13.handle(top) -> Client.n6.handle(bottom) [label="Error"]
+}
+EventHandler { # Event Handler
+n14: rectangle label:"Receive domain event"
+n15: rectangle label:"Update read model"
+n14.handle(right) -> n15.handle(left)
+n15.handle(top) -> QuerySide.n16.handle(bottom) [label="Sync"]
+}
+QuerySide { # Query Side
+n16: rectangle label:"Parse query parameters"
+n17: rectangle label:"Query read store"
+n18: rectangle label:"Transform to DTO"
+n19: rectangle label:"Return results"
+n16.handle(right) -> n17.handle(left)
+n17.handle(right) -> n18.handle(left)
+n18.handle(right) -> n19.handle(left)
+n19.handle(top) -> Client.n6.handle(bottom) [label="Data"]
+}
diff --git a/patterns/patterns/crud-user-browser-server-workflow/README.md b/patterns/patterns/crud-user-browser-server-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..446d9c201ee7df4750127178e05f5e2f4fb18ca1
--- /dev/null
+++ b/patterns/patterns/crud-user-browser-server-workflow/README.md
@@ -0,0 +1,19 @@
+# Crud User Browser Server Workflow
+
+This workflow models user creates, reads, updates, and deletes data through a browser and server.
+
+**Template ID:** `crud-user-browser-server-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 2/5  
+**Nodes:** 7  
+**Lanes:** 2  
+**Tags:** [crud, user, browser, server, patterns]  
+**Source path:** `patterns/crud-user-browser-server`  
+**Repo path:** `patterns/patterns/crud-user-browser-server-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/crud-user-browser-server-workflow/metadata.json b/patterns/patterns/crud-user-browser-server-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..3eed361bf5fde273d3a2ddf3a7654626c9964fa1
--- /dev/null
+++ b/patterns/patterns/crud-user-browser-server-workflow/metadata.json
@@ -0,0 +1,25 @@
+{
+  "template_id": "crud-user-browser-server-workflow",
+  "workflow_id": "crud-user-browser-server",
+  "title": "Crud User Browser Server Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 2,
+  "num_nodes": 7,
+  "num_lanes": 2,
+  "tags": [
+    "crud",
+    "user",
+    "browser",
+    "server",
+    "patterns"
+  ],
+  "description": "This workflow models user creates, reads, updates, and deletes data through a browser and server.",
+  "source_path": "patterns/crud-user-browser-server",
+  "repo_path": "patterns/patterns/crud-user-browser-server-workflow"
+}
diff --git a/patterns/patterns/crud-user-browser-server-workflow/workflow.fz b/patterns/patterns/crud-user-browser-server-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..2377b39531486ebd91db1cd667bc385b247c42b9
--- /dev/null
+++ b/patterns/patterns/crud-user-browser-server-workflow/workflow.fz
@@ -0,0 +1,19 @@
+user { # User
+  n1: circle label:"Start Crud User Browser Server"
+  n2: diamond label:"Receive Crud User Browser Server event"
+  n3: rectangle label:"Validate Crud User Browser Server conditions"
+  n5: rectangle label:"Record Crud User Browser Server outcome"
+  n7: circle label:"End Crud User Browser Server"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(right) -> n3.handle(left) [label="Yes/Approved"]
+  n2.handle(bottom) -> app.n4.handle(top) [label="No/Rejected"]
+  n3.handle(right) -> n5.handle(left)
+  n5.handle(bottom) -> app.n6.handle(top)
+}
+
+app { # App
+  n4: rectangle label:"Execute Crud User Browser Server action"
+  n6: rectangle label:"Monitor Crud User Browser Server status"
+  n6.handle(right) -> user.n7.handle(left)
+  n4.handle(right) -> user.n5.handle(top)
+}
diff --git a/patterns/patterns/dead-letter-queue-workflow/README.md b/patterns/patterns/dead-letter-queue-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..95f3a44165a48bfaeab884a345d69916ef5fa38d
--- /dev/null
+++ b/patterns/patterns/dead-letter-queue-workflow/README.md
@@ -0,0 +1,19 @@
+# Dead Letter Queue Workflow
+
+Dead letter queue pattern for handling failed messages with retry exhaustion detection, DLQ routing, manual inspection, and reprocessing capability.
+
+**Template ID:** `dead-letter-queue-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 7  
+**Lanes:** 2  
+**Tags:** [dead-letter-queue, dlq, message-retry, poison-message, error-handling, message-queue]  
+**Source path:** `patterns/dead-letter-queue`  
+**Repo path:** `patterns/patterns/dead-letter-queue-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/dead-letter-queue-workflow/metadata.json b/patterns/patterns/dead-letter-queue-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..1c7510df8dae610549ebd17d92400e84b19fa78c
--- /dev/null
+++ b/patterns/patterns/dead-letter-queue-workflow/metadata.json
@@ -0,0 +1,26 @@
+{
+  "template_id": "dead-letter-queue-workflow",
+  "workflow_id": "dead-letter-queue",
+  "title": "Dead Letter Queue Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 7,
+  "num_lanes": 2,
+  "tags": [
+    "dead-letter-queue",
+    "dlq",
+    "message-retry",
+    "poison-message",
+    "error-handling",
+    "message-queue"
+  ],
+  "description": "Dead letter queue pattern for handling failed messages with retry exhaustion detection, DLQ routing, manual inspection, and reprocessing capability.",
+  "source_path": "patterns/dead-letter-queue",
+  "repo_path": "patterns/patterns/dead-letter-queue-workflow"
+}
diff --git a/patterns/patterns/dead-letter-queue-workflow/workflow.fz b/patterns/patterns/dead-letter-queue-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..4a712cd811d2838a3814752a892b2205ed48ef74
--- /dev/null
+++ b/patterns/patterns/dead-letter-queue-workflow/workflow.fz
@@ -0,0 +1,44 @@
+MainQueue { # Main Queue
+n1: circle label:"Start"
+n2: rectangle label:"Receive message"
+n3: rectangle label:"Attempt processing"
+n4: diamond label:"Processing successful?"
+n5: rectangle label:"Acknowledge message"
+n6: rectangle label:"Increment retry count"
+n7: circle label:"End"
+n1.handle(right) -> n2.handle(left)
+n2.handle(right) -> n3.handle(left)
+n3.handle(right) -> n4.handle(left)
+n4.handle(right) -> n5.handle(left) [label="Yes"]
+n4.handle(bottom) -> n6.handle(top) [label="No"]
+n5.handle(right) -> n7.handle(left)
+n6.handle(bottom) -> RetryLogic.n8.handle(top) [label="Check retries"]
+}
+RetryLogic { # Retry Logic
+n8: diamond label:"Max retries exceeded?"
+n9: rectangle label:"Wait with backoff"
+n10: rectangle label:"Requeue message"
+n11: rectangle label:"Move to DLQ"
+n8.handle(right) -> n9.handle(left) [label="No"]
+n8.handle(bottom) -> n11.handle(top) [label="Yes"]
+n9.handle(right) -> n10.handle(left)
+n10.handle(top) -> MainQueue.n3.handle(bottom) [label="Retry"]
+n11.handle(bottom) -> DeadLetterQueue.n12.handle(top) [label="Failed"]
+}
+DeadLetterQueue { # Dead Letter Queue
+n12: rectangle label:"Store failed message"
+n13: rectangle label:"Log failure details"
+n14: rectangle label:"Send alert notification"
+n15: rectangle label:"Await manual review"
+n16: diamond label:"Reprocess or discard?"
+n17: rectangle label:"Move back to main queue"
+n18: rectangle label:"Archive and delete"
+n12.handle(right) -> n13.handle(left)
+n13.handle(right) -> n14.handle(left)
+n14.handle(right) -> n15.handle(left)
+n15.handle(right) -> n16.handle(left)
+n16.handle(right) -> n17.handle(left) [label="Reprocess"]
+n16.handle(bottom) -> n18.handle(top) [label="Discard"]
+n17.handle(top) -> MainQueue.n2.handle(bottom) [label="Retry"]
+n18.handle(top) -> MainQueue.n7.handle(bottom) [label="Discarded"]
+}
diff --git a/patterns/patterns/decision-diamond-workflow/README.md b/patterns/patterns/decision-diamond-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..444c766d0e6c03844e4af9c038c875645ed34173
--- /dev/null
+++ b/patterns/patterns/decision-diamond-workflow/README.md
@@ -0,0 +1,19 @@
+# Decision Diamond Workflow
+
+This workflow models an if or then style branch for approval or rejection.
+
+**Template ID:** `decision-diamond-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [decision, diamond, patterns]  
+**Source path:** `patterns/decision-diamond`  
+**Repo path:** `patterns/patterns/decision-diamond-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/decision-diamond-workflow/metadata.json b/patterns/patterns/decision-diamond-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..d9c3ad9861d27bfa92520f147934a285190cfddb
--- /dev/null
+++ b/patterns/patterns/decision-diamond-workflow/metadata.json
@@ -0,0 +1,23 @@
+{
+  "template_id": "decision-diamond-workflow",
+  "workflow_id": "decision-diamond",
+  "title": "Decision Diamond Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "decision",
+    "diamond",
+    "patterns"
+  ],
+  "description": "This workflow models an if or then style branch for approval or rejection.",
+  "source_path": "patterns/decision-diamond",
+  "repo_path": "patterns/patterns/decision-diamond-workflow"
+}
diff --git a/patterns/patterns/decision-diamond-workflow/workflow.fz b/patterns/patterns/decision-diamond-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..ed0f3f8a3b1552e8383446173a2247f6ef3cf8bd
--- /dev/null
+++ b/patterns/patterns/decision-diamond-workflow/workflow.fz
@@ -0,0 +1,28 @@
+user { # User
+  n1: circle label:"Start Decision Diamond"
+  n2: diamond label:"Receive Decision Diamond event"
+  n4: rectangle label:"Execute Decision Diamond action"
+  n7: rectangle label:"Monitor Decision Diamond status"
+  n10: circle label:"End Decision Diamond"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(bottom) -> service.n3.handle(top) [label="Yes/Approved"]
+  n4.handle(bottom) -> app.n5.handle(top)
+  n7.handle(bottom) -> app.n8.handle(top)
+  n2.handle(top) -> n4.handle(top) [label="No/Rejected"]
+}
+
+app { # App
+  n5: rectangle label:"Record Decision Diamond outcome"
+  n8: rectangle label:"Monitor Decision Diamond status"
+  n5.handle(bottom) -> service.n6.handle(top)
+  n8.handle(bottom) -> service.n9.handle(top)
+}
+
+service { # Service
+  n3: diamond label:"Validate Decision Diamond conditions"
+  n6: rectangle label:"Monitor Decision Diamond status"
+  n9: rectangle label:"Monitor Decision Diamond status"
+  n9.handle(right) -> user.n10.handle(bottom)
+  n6.handle(right) -> user.n7.handle(left)
+  n3.handle(left) -> app.n5.handle(left)
+}
diff --git a/patterns/patterns/enricher-workflow/README.md b/patterns/patterns/enricher-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..2cb46fc51aa3014449315de0252ea83bf5352d24
--- /dev/null
+++ b/patterns/patterns/enricher-workflow/README.md
@@ -0,0 +1,19 @@
+# Enricher Workflow
+
+This workflow models adding metadata to messages before passing them on.
+
+**Template ID:** `enricher-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [enricher, patterns]  
+**Source path:** `patterns/enricher`  
+**Repo path:** `patterns/patterns/enricher-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/enricher-workflow/metadata.json b/patterns/patterns/enricher-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..ad6fc43a490a1d51ad27da4d3853fc78c11026b8
--- /dev/null
+++ b/patterns/patterns/enricher-workflow/metadata.json
@@ -0,0 +1,22 @@
+{
+  "template_id": "enricher-workflow",
+  "workflow_id": "enricher",
+  "title": "Enricher Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "enricher",
+    "patterns"
+  ],
+  "description": "This workflow models adding metadata to messages before passing them on.",
+  "source_path": "patterns/enricher",
+  "repo_path": "patterns/patterns/enricher-workflow"
+}
diff --git a/patterns/patterns/enricher-workflow/workflow.fz b/patterns/patterns/enricher-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..dce75037ac895d0a200ea2b983ab387f4faef3ab
--- /dev/null
+++ b/patterns/patterns/enricher-workflow/workflow.fz
@@ -0,0 +1,28 @@
+user { # User
+  n1: circle label:"Start Enricher"
+  n4: diamond label:"Execute Enricher action"
+  n7: rectangle label:"Monitor Enricher status"
+  n10: circle label:"End Enricher"
+  n1.handle(bottom) -> app.n2.handle(top)
+  n4.handle(bottom) -> app.n5.handle(top)
+  n4.handle(right) -> service.n3.handle(right) [label="Retry/Rejected"]
+  n7.handle(bottom) -> app.n8.handle(top)
+}
+
+app { # App
+  n2: rectangle label:"Receive Enricher event"
+  n5: rectangle label:"Record Enricher outcome"
+  n8: rectangle label:"Monitor Enricher status"
+  n2.handle(bottom) -> service.n3.handle(top)
+  n5.handle(bottom) -> service.n6.handle(top)
+  n8.handle(bottom) -> service.n9.handle(top)
+}
+
+service { # Service
+  n3: rectangle label:"Validate Enricher conditions"
+  n6: rectangle label:"Monitor Enricher status"
+  n9: rectangle label:"Monitor Enricher status"
+  n9.handle(right) -> user.n10.handle(bottom) [label="Valid"]
+  n6.handle(right) -> user.n7.handle(left) [label="Success"]
+  n3.handle(bottom) -> user.n4.handle(left) [label="Processed"]
+}
diff --git a/patterns/patterns/error-retry-loop-workflow/README.md b/patterns/patterns/error-retry-loop-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..3930f83ebfde9ad13d0839f6e9a6bd582504a6ab
--- /dev/null
+++ b/patterns/patterns/error-retry-loop-workflow/README.md
@@ -0,0 +1,19 @@
+# Error Retry Loop Workflow
+
+This workflow models a failed operation that retries with backoff.
+
+**Template ID:** `error-retry-loop-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 2/5  
+**Nodes:** 7  
+**Lanes:** 2  
+**Tags:** [error, retry, loop, patterns]  
+**Source path:** `patterns/error-retry-loop`  
+**Repo path:** `patterns/patterns/error-retry-loop-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/error-retry-loop-workflow/metadata.json b/patterns/patterns/error-retry-loop-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..55c9b422e1e5c680a5dc948803b9a1d841307732
--- /dev/null
+++ b/patterns/patterns/error-retry-loop-workflow/metadata.json
@@ -0,0 +1,24 @@
+{
+  "template_id": "error-retry-loop-workflow",
+  "workflow_id": "error-retry-loop",
+  "title": "Error Retry Loop Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 2,
+  "num_nodes": 7,
+  "num_lanes": 2,
+  "tags": [
+    "error",
+    "retry",
+    "loop",
+    "patterns"
+  ],
+  "description": "This workflow models a failed operation that retries with backoff.",
+  "source_path": "patterns/error-retry-loop",
+  "repo_path": "patterns/patterns/error-retry-loop-workflow"
+}
diff --git a/patterns/patterns/error-retry-loop-workflow/workflow.fz b/patterns/patterns/error-retry-loop-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..1cdb442f134383c782655d0f1282973c3271bf03
--- /dev/null
+++ b/patterns/patterns/error-retry-loop-workflow/workflow.fz
@@ -0,0 +1,17 @@
+Client { # Client
+  n1: circle label:"Start Transaction"
+  n2: rectangle label:"Attempt Payment"
+  n5: circle label:"Payment Success"
+  n1.handle(right) -> n2.handle(left)
+  n2.handle(bottom) -> Server.n3.handle(top) [label="Submit"]
+  n2.handle(right) -> n5.handle(left) [label="Authorized"]
+}
+
+Server { # Server
+  n3: rectangle label:"Process Payment"
+  n4: diamond label:"Authorized?"
+  n3.handle(right) -> n4.handle(left)
+  n4.handle(right) -> Client.n5.handle(bottom) [label="Approved"]
+  n4.handle(top) -> Client.n2.handle(bottom) [label="Decline/Retry"]
+  loop [Retry until approved] n2 n3 n4
+}
diff --git a/patterns/patterns/feature-toggle-workflow/README.md b/patterns/patterns/feature-toggle-workflow/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..aa15fef851b21604475bd0c08d1a3afc3221100c
--- /dev/null
+++ b/patterns/patterns/feature-toggle-workflow/README.md
@@ -0,0 +1,19 @@
+# Feature Toggle Workflow
+
+Feature toggle pattern with flag configuration, user targeting rules, percentage rollouts, and instant kill-switch capability for production features.
+
+**Template ID:** `feature-toggle-workflow`  
+**Kind:** workflow  
+**Source domain:** patterns  
+**Primary use case:** patterns  
+**Secondary use cases:** None  
+**Complexity:** 3/5  
+**Nodes:** 10  
+**Lanes:** 3  
+**Tags:** [feature-toggle, feature-flags, dark-launch, a-b-testing, gradual-rollout, kill-switch]  
+**Source path:** `patterns/feature-toggle`  
+**Repo path:** `patterns/patterns/feature-toggle-workflow`
+
+## Files
+- `workflow.fz` — FlowZap Code source
+- `metadata.json` — Structured metadata
diff --git a/patterns/patterns/feature-toggle-workflow/metadata.json b/patterns/patterns/feature-toggle-workflow/metadata.json
new file mode 100644
index 0000000000000000000000000000000000000000..685563cfe84e0468a5b810b15d870dad62335480
--- /dev/null
+++ b/patterns/patterns/feature-toggle-workflow/metadata.json
@@ -0,0 +1,26 @@
+{
+  "template_id": "feature-toggle-workflow",
+  "workflow_id": "feature-toggle",
+  "title": "Feature Toggle Workflow",
+  "kind": "workflow",
+  "source_domain": "patterns",
+  "primary_use_case": "patterns",
+  "secondary_use_cases": [],
+  "use_cases": [
+    "patterns"
+  ],
+  "complexity": 3,
+  "num_nodes": 10,
+  "num_lanes": 3,
+  "tags": [
+    "feature-toggle",
+    "feature-flags",
+    "dark-launch",
+    "a-b-testing",
+    "gradual-rollout",
+    "kill-switch"
+  ],
+  "description": "Feature toggle pattern with flag configuration, user targeting rules, percentage rollouts, and instant kill-switch capability for production features.",
+  "source_path": "patterns/feature-toggle",
+  "repo_path": "patterns/patterns/feature-toggle-workflow"
+}
diff --git a/patterns/patterns/feature-toggle-workflow/workflow.fz b/patterns/patterns/feature-toggle-workflow/workflow.fz
new file mode 100644
index 0000000000000000000000000000000000000000..98d1a5ab9cfc18b998fb8aee8ea5e375f2371909
--- /dev/null
+++ b/patterns/patterns/feature-toggle-workflow/workflow.fz
@@ -0,0 +1,28 @@
+user { # User
+  n1: circle label:"Start Feature Toggle"
+  n4: rectangle label:"Execute Feature Toggle action"
+  n7: rectangle label:"Monitor Feature Toggle status"
+  n10: circle label:"End Feature Toggle"
+  n1.handle(bottom) -> app.n2.handle(top)
+  n4.handle(bottom) -> app.n5.handle(top)
+  n7.handle(bottom) -> app.n8.handle(top)
+}
+
+app { # App
+  n2: rectangle label:"Receive Feature Toggle event"
+  n5: rectangle label:"Record Feature Toggle outcome"
+  n8: rectangle label:"Monitor Feature Toggle status"
+  n2.handle(bottom) -> service.n3.handle(top)
+  n5.handle(bottom) -> service.n6.handle(top)
+  n8.handle(bottom) -> service.n9.handle(top)
+}
+
+service { # Service
+  n3: rectangle label:"Validate Feature Toggle conditions"
+  n6: diamond label:"Monitor Feature Toggle status"
+  n9: rectangle label:"Monitor Feature Toggle status"
+  n9.handle(right) -> user.n10.handle(bottom) [label="Valid"]
+  n6.handle(left) -> app.n5.handle(left) [label="Retry/Rejected"]
+  n6.handle(right) -> user.n7.handle(left) [label="Success"]
+  n3.handle(right) -> user.n4.handle(left) [label="Processed"]
+}