n8n-vigil-workflow

Configure the 3-branch n8n workflow by setting up branches A–C in the 24-node pipeline, defining weighted scoring rules in unified_config.json, and connecting each branch to the arbiter fusion node. The arbiter combines branch outputs and applies PII detection logic to produce block/sanitize decisions.

Arbiter fusion is the central decision node that aggregates outputs from all three branches, applies weighted scoring across branch results, and determines final PII redaction and block/sanitize actions. It unifies detection signals into a single audit-logged decision.

Configure dual-language PII detection by defining language-specific patterns in pii.conf, deploying parallel detection nodes in branches A–C, and routing detected PII through the arbiter for unified redaction. Dual-language support ensures consistent PII masking across multiple languages in the same pipeline.

unified_config.json centrally manages branch configuration, weighted scoring parameters, PII detection rules, redaction policies, and ClickHouse logging settings. It eliminates per-node config drift and ensures consistency across the 24-node pipeline.

Troubleshoot by verifying node quality metrics, checking version consistency across all 24 nodes, validating unified_config.json syntax, and reviewing ClickHouse audit logs for error patterns. Start with branch-level checks before investigating arbiter fusion logic.

Yes, ClickHouse is the required logging backend for Vigil Guard v2.0.0. All workflow decisions, PII detections, redactions, and block/sanitize actions are logged to ClickHouse to maintain an immutable audit trail across the 24-node pipeline.