THE WORKFLOW LIBRARY · SNAPSHOT AUGUST 2026
Write access is
earned, not assumed.
Every repeatable piece of the content operation is packaged as a governed workflow: versioned, owned, and tagged with exactly how much it is allowed to touch. This is the full library, grouped by what each does in the pipeline.
PERMISSION MODEL
Four tiers, one rule.
A workflow is allowed to touch only what it has earned. New workflows start advisory or drafts-only; live-write permission is added per workflow with an explicit approval gate. Exactly one runs autonomously — and only after its supervised twin proved the procedure post by post.
Reads, audits, scores, recommends. Writes nothing anywhere.
Produces content and CMS drafts. Never publishes, never touches a live page.
Changes live systems — but every write is shown and approved first.
Runs on a schedule under standing, pre-authorized conditions. Earned via its supervised twin.
THE LIBRARY
Thirty-two workflows, by what they do.
Strategy & research 4 workflows
Content creation 3 workflows
Quality gates 3 workflows
The audit layer. These never rewrite — they grade, block and report, which keeps the reviewer separate from the writer.
Publishing & CMS 6 workflows
Editor migration 4 workflows
The clearest example of the governance ladder: the supervised version ran first with per-post approval, and only after it proved itself did the autonomous version earn standing rules.
Localization & markets 3 workflows
Audience intelligence 4 workflows
A weekly three-step pipeline — scout, score, gap-check — on a shared research context. Research only; nothing ever posts or replies.
Site & personal operations 5 workflows
GOVERNANCE NOTES
What holds it together.
- 01 / Every workflow declares itself
Owner, version, status, last-updated and review-due date live in the workflow header — so a library this size stays auditable rather than becoming folklore.
- 02 / One definition of quality
All creation, refresh and audit workflows load the same shared editorial standard rather than carrying their own. Change the standard once, and every workflow inherits it.
- 03 / Autonomy is a promotion
No workflow starts with live-write access. It is granted per workflow, gated on approval, and only lifted to standing autonomy after a supervised run proved the procedure.
- 04 / The reviewer never writes
Audit workflows grade, block and report. They do not fix what they judge, which is what keeps a verdict worth having.
Scope and limits
What this describes: the library I designed and operate, as of August 2026, at the level of category, permission tier and purpose. Workflow identifiers, version numbers, internal documentation and the prompt content itself are not published.
Limits: “built” counts the library; five workflows run in active production today and the remainder are in draft or staged use. Counts move as the library grows — this page is a dated snapshot, not a live dashboard.