Gates → guardrails
A gate is a person who has to say yes before you move. A guardrail is a rule the system enforces while you move. Gates mostly protect against blame. Guardrails protect against actual harm, so pick those.
Keep exactly one human gate: the owner's final glance before publish. Everything upstream of it is automated. That single gate is cheap because the guardrails have already done the heavy lifting.
Brand-as-prompt
Stop treating your style guide as a 40-page PDF nobody reads. Make it a system prompt the model loads on every generation. Encode voice, editorial rules, banned phrases, and a glossary once. Version it in git. Every agent inherits it automatically.
A prompt drifts the moment your brand does. Treat brand.spec.md like code: PR to change it, one owner approves, changelog kept. Don't let three people quietly fork their own voice.
Automated evals before publish
Before any draft ships, an eval suite runs against it, the same way tests run against code. It checks that the draft is on-brand, grounded in your sources, free of hallucinations, and at the right reading level. A runner like promptfoo (illustrative, not an endorsement) can wire these into CI so a failing check blocks merge. Below is the owner's live pre-publish checklist. Toggle each item.
Pre-publish checklist
Disclosure & provenance, kept light
You don't need a compliance department. You need honesty where it matters and a record you can reconstruct. Label AI-assisted content where a reader would care, and keep a one-line source trail per asset. That's it.
Disclose where it matters
- Do label AI-assisted thought-leadership, customer-facing claims, and anything attributed to a named person.
- Skip the badge on routine product copy or internal drafts. Over-disclosure just adds noise.
- Use a single, plain tag: "Drafted with AI, reviewed by [name]."
Keep a simple source record
A spec hash, a source list, and a reviewer name let you answer "where did this claim come from?" in seconds. That's the only governance question that actually matters when something gets challenged.
The five risks that matter
Ignore the long enterprise risk register. For a lean content engine, these are the failure modes that actually bite, each paired with the one guardrail that contains it. Amber = manage, red = block on it.
Five risks, five guardrails. If a control doesn't map to one of these, you're adding weight that slows a lean team down. Add controls only when a risk graduates from amber to red.
Before you move on
Guardrails are the thing that lets a one-person engine ship fast without shipping something off-brand or untrue. Make sure these are in place before you scale volume, everything downstream assumes a draft can't reach the public unless it has already cleared them.
What you should have now
- ✓ Brand rules as machine-readable context, voice, banned phrases and glossary in a versioned
brand.spec.mdthat every agent loads. - ✓ An automated eval suite that gates publish on accuracy and on-brand voice, grounding, hallucination, readability and disclosure checks that block merge when they fail.
- ✓ Risk tiers you act on, the few amber/red failure modes named, each mapped to the one guardrail that contains it, with nothing extra slowing you down.
- ✓ One human sign-off where it matters, the owner's final glance plus a light provenance record, so you can always reconstruct where a claim came from.
Why this sets up the next stage
Guardrails are what make it safe to scale: once checks run on every draft automatically, you can turn up volume without turning up risk, because nothing reaches the public until it has passed.
With safety handled, the open question becomes output. Next, Done & Measure defines what “done” actually looks like and picks the few metrics that prove the whole system is working.