ACM — Agentic Content Manager
A structured content production system for building a thought leadership presence — campaigns, drafts, workflows, and publish pipelines for the ideas coming out of AGF and the Agentic Work System.
What It Is
ACM is the content system behind jessepike.dev. It’s where campaigns are planned, drafts are written, and posts move from idea to published. It’s built with ADF stage discipline — campaigns go through Discover, Design, Develop, Deliver — but it’s a workflow system, not a software product.
The honest description: structured, not yet agentic. It has the scaffolding for agentic workflows — defined stages, capture pipelines, campaign intent documents — but the autonomous pieces are still being built.
What It Produces
The writing on this site is ACM output. The AGF campaign is ACM’s current focus: building a content library that establishes the governance framework for agentic systems, piece by piece, over 3–6 months. Each post stands alone and assembles into the larger narrative.
ACM also produced the AGF diagrams — working through the architecture in writing surfaced the ideas that became the visuals.
Why It’s Separate
ACM doesn’t connect back into the Agentic Work System the way KB, Memory, and Krypton do. It’s a product of the system — built using ADF patterns, drawing on KB for research, using Memory for continuity — but its output flows out to the public rather than feeding back into the infrastructure.
This makes it a different kind of project: not ecosystem infrastructure, but a downstream application of the methodology. The distinction matters for how it’s developed and governed.
What’s Coming
The agentic part of “Agentic Content Manager” is the roadmap, not the current state. The target architecture: agents that draft from a campaign brief, validate against intent, check KB for supporting research, and surface content for human review — with humans in the loop for judgment calls, not for mechanical production tasks.