mbachaud

Use after PR-sized work completes (or on /mek-drift) to compare auto scores against .mek/drift-baseline.json and surface divergences > 0.15.

Use when the agent is about to perform a risky operation (destructive shell, deploy, schema migration, money write, force-push). Reminds to record HITL approval and points at compliance/ templates.

STUB. Future v0.2.0 feature — a mini-SQLite ledger so the agent can record/query journal entries for any context (token spend, invoicing, etc.). Not active in v0.1.0.

Use when the agent encounters money-shaped identifiers (amount, price, balance, total, cost), performs arithmetic across monetary fields, or writes/reads money to a database. Enforces Decimal-only math.

Use when starting any conversation in a project where MEK is installed - announces the three guardrails (compliance, drift, ledger) and how to invoke them.

Use Cymatix MCP tools for architectural, historical, semantic, or cross-file repo questions before broad raw-file exploration. Prefer local file reads for exact current code or line-accurate edits, and use Cymatix health, ingest, and session tools with the full Cymatix identity contract so context stays attributable and retrievable.

Use Helix MCP tools for architectural, historical, semantic, or cross-file repo questions before broad raw-file exploration. Prefer local file reads for exact current code or line-accurate edits, and use Helix health, ingest, and session tools with the full Helix identity contract so context stays attributable and retrievable.

Orchestrate a 3-layer agent hierarchy (Department Head → Pod Leads → Sub-Agents) for complex, multi-domain tasks. Use when the user invokes /team or when auto-detect suggests team mode.