ChatOps Control Plane
Approve, diff, and triage from your phone without opening a laptop.
Slack surface
/compliance why J-142
“NY A8887-B fired: synthetic-performer likeness without conspicuous disclosure. Rule cited · remediation attached.”
Approval DM · one-tap
Marcus approves from a conference · Priya rejects from a hallway.
Web app surface
Policy finding · inline
Same rule citation · remediation inline in the journey canvas.
Approval button · in-product
Same action · same role-scoped authorisation.
One signed ledger · audit boundary doesn't move with the channel
Every chat-initiated action writes the same ledger event as every in-product action.
MCP-compatible tool definitions · Slack at MVP · Teams before chasm-cross · WhatsApp + Telegram via MCP in Year 2.
What it is
Enterprise professionals switch context ~1,200 times a day. The CMO doesn't need a sixth web portal. The Deputy GC doesn't need a seventh dashboard. ChatOps is how the team approves, asks, and acts where they already work Slack at MVP, Teams before chasm-cross, WhatsApp and Telegram via MCP after.
A Slack app (built on Slack Bolt SDK) that surfaces approval requests, anomaly alerts, and command-driven queries. Every chat-initiated action is signed into the same hash-chained ledger as in-product actions. Tool definitions are MCP-compatible from day one so the Teams and WhatsApp surfaces drop in without re-architecture.
Capabilities
What this surface does
Approval DMs with diff + one-tap
Marcus approves a paused campaign from a conference. Priya rejects a misconfigured journey from a hallway. The signed approval enters the ledger before the Slack message disappears.
/compliance why <artefact-id>
Priya asks 'why did this campaign trigger NY A8887-B?' from her phone at 9 p.m. and gets a structured answer citing the policy rule and the artefact's offending element.
Anomaly alerts to channel
Spend spikes, brand-safety flags, export failures, policy-fire storms pushed to the designated channel with a one-tap acknowledge action.
Audit-logged at the chat boundary
Every chat-initiated action writes a ledger event. The Slack thread is searchable; the audit trail is immutable.
MCP-compatible by construction
Slack at MVP. Teams before first chasm-crossing pragmatist contract. WhatsApp + Telegram via MCP servers in Year 2 same tool definitions, different transports.
Shared dashboard surface
The throughput dashboard (cycle time, rework rate, compliance-pass rate) renders to Slack canvas for the weekly trio review.
Proof points
What this means in numbers
Slack at MVP
Teams next
MCP architecture means the second surface is configuration, not engineering.
1,200/day
Context-switches removed
Action where you already work.
Ledger-signed
Every chat action
Audit boundary doesn't move with the channel.
Specifications
Spec map feature requirements + non-functional bar
Mapped to PRD §7 functional requirements and §8 non-functional requirements.
Related surfaces
What this composes with
PS4 the purchase-criterion feature
Evidence Pack
The artefact you hand a regulator. Assembled in seconds, signed by default.
Read
PS2 compliance-as-code
Policy Engine
Compliance-as-code for every live jurisdiction enforced at draft time.
Read
PS1 the moat primitive
Artefact Graph
Versioned, signed, cross-vendor the system of record for every campaign object.
Read
EU AI Act Article 50
Twenty minutes. One conversation. If the outside-counsel-displacement math works, we keep talking. If it doesn't, it's honest and short.