Constitutional Guard (C-361)

IP claim: C-361 · Tier A candidate · Linked VP: VP-093 · Author trail: ARIA_ORACLE_AND_MICROSITE_v1.md §4

Thesis — Brand-Voice as a Specialist Agent

Brand voice is not a style-guide PDF that lives in a shared drive and gets ignored. It is a specialist agent with read-veto power over every outbound message — sales email, marketing copy, support reply, Aria response, executive memo. Non-compliant copy is refused at emission time with a hash-chained rejection log.

If a sales rep generates a cold-outreach email that violates your CISO-approved style guide, the Constitutional Guard refuses to let the mail server send it — and writes a glass_events row explaining why. The CMO sees auditable evidence that the style guide is enforced; the CRO sees the rejection (and either revises or escalates).

How It Works

  1. Brand-voice rules are codified as constitutional artifacts (docs/brand/VOICE_v*.md) — not PDFs.
  2. Constitutional Guard agent loads the rules at startup and registers as a hook on every outbound emission channel (mail-server, CRM API, marketing-automation webhook, Aria response).
  3. On every emit, the agent classifies the copy against the rule set and returns allow / refuse / revise-suggested.
  4. refuse events are appended to the C-362 hash-chain so the rejection itself is auditable.

Head-to-Head

CapabilityOrchestrAi (C-361)"Brand voice PDF"
Enforcement at emission timeYes (hook on every channel)No (reviewed post-hoc)
Auditable refusalsYes (hash-chained)No
CMO × CISO co-approvedYes (single artifact)Rarely
Multi-channel scopeMail + CRM + marketing + AriaWhichever channel a human reviews
Survives staff turnoverYes (constitutional)No (institutional memory)

Why the D-7 Buyer Cares

Honest-tense (Law #19): Constitutional Guard agent SPEC ratified; runtime code lands Phase C per Constitutional Pod (ADR-0019 v2 §6). C-361 is a CANDIDATE IP claim — CTO ratification PENDING.
Ask Aria → Phase D.2