29 builds, 26 live. Each one replaces a manual loop and stops for a human wherever a decision has consequences. The three flagships are on the home page.
Integrations across real business systems are the four n8n workflows further down, none of which can send without a person. Everything below is the full inventory, ordered by what it is rather than by what it proves.
An MCP server an agent cannot talk past, measured against a control arm rather than asserted. Same model, same prompt, same tools, nineteen scenarios: ungoverned the agent took an unauthorized action in 19 of 19, twenty-seven calls including a refund, a 40,000 row delete and a production deploy. Governed, 0 of 19, and the legitimate work still finished in all nineteen. Two scenarios were built to make it over-block instead, and one did: it escalated a legitimate password reset for an account named billing-ana, because billing matched the financial rule. Precision fell to 96.7 percent, which is the first false escalation the suite ever produced, and the point. Class 2 refusals are MCP error -32042 carrying the approval URL, and every decision is sealed into a hash chain that names the row where it parts if anyone edits it.
governance · evals · Python ↗ landing-page-engineMutation testing of a quality gate: break a page that already passed, one defect at a time, and check the right check fires. 14 of 14. It found a check that could not fail, because the page set overflow-x hidden and clamped the measurement the responsive check depended on. The model had written CSS that switched off the check meant to catch its own layout.
MCP server · mutation evals ↗ meridian-evalsA golden set of real and adversarial incidents, scored against both production brains for gate correctness, cost, and latency, rerun and recommitted nightly by CI. On the 2026-09-01 run: gpt-4.1-mini 11/11 at $0.0022, claude-sonnet-5 9/11 at $0.0426, failing on a truncated response and a VIP severity floor. Its unit tests caught a live security-floor bug that had survived three deployments.
evaluation · Python ↗ runbook-ragGrounded retrieval with Azure OpenAI embeddings, per-claim citations, an explicit refusal when the corpus cannot answer, and deterministic faithfulness evals. Committed run: 10/10. The corpus is 11 chunks from 6 runbooks and the index is an exact cosine scan over all of them, which is the correct answer at that size: an approximate index over 11 rows would be cosplay. The hybrid pgvector and BM25 version over 1,199 chunks is labor-ph, further up this page.
RAG · Python ↗ meridian-brain-azureThe triage stage re-platformed to Azure Functions and Azure OpenAI through an AI Foundry deployment, with the same deterministic gates ported. Same brain, same rules, different cloud, reachable from n8n.
Azure · migration ↗A TypeScript agent on the Anthropic Messages API, no agent framework: the tool-use loop, the memory that spans a whole guest stay, and the guardrail that force-escalates money, safety, and legal before the model gets a turn are all mine. LangGraph is in the Back-office Agent, where a graph earns its keep.
Alagà · Guest AI Agent →Wired to my n8n instance through its official MCP server. A workflow gets described in a sentence, written as SDK code, validated, created, and published without opening the editor.
n8n Workflow Builder Agent →The page engine registers three tools over stdio, so any MCP client can call the same draft-and-grade pipeline I use.
Landing Page Engine →Seven Claude Code skills hold the rules, an eight-step orchestrator runs the contract, and twelve sub-agents do the judgment-heavy authoring. The pipeline is public as a sanitized rebuild, with none of the client material.
phishing-sim-line ↗A golden set of real and adversarial incidents scored against both production brains for gate correctness, cost, and latency, with the scorecard committed to the repo and rerun nightly by CI. Its unit tests caught a live security-floor bug that had survived three deployments in two codebases.
meridian-evals →The pattern under six of these builds: the model proposes, code decides. Severity floors, flag counts, confidence thresholds, and escalation rules live outside the prompt, where they cannot be talked out of.
MSP Ticket Triage →Each workflow carries its own locked template, and the prompt tool re-syncs Anthropic's live docs so its guidance cannot quietly go stale.
Prompt Maker →Sonnet's thinking block breaks a naive content[0].text parse, max_tokens is tuned per job, and the sim pipeline has one named seam where a better model swaps in while the deterministic half stays byte for byte.
Cywareness Simulation Archive →