Home · Writing · AI operating models · essay
The hard part of AI content operations is control
Generating more material is easy. A useful content operation needs source authority, bounded execution, approval and evidence that the work changed something.
Content generation is one of the easiest AI demonstrations to build. Give a model a topic, a voice guide and a target format, and it can produce an article, a social post and an image brief in minutes.
That capability does not create a content operation. It creates output.
The FundRobin Content Factory has pushed me to think about the system around generation: where an idea comes from, which sources are authoritative, what an agent may publish, how work is recovered and what evidence tells us whether the content was useful.
The harder design problem is control.
Start with the decision the content should support
An automated pipeline can fill a calendar very efficiently. Volume is a poor objective when the underlying topics have weak relevance or cannot be supported by evidence.
I want each piece of content to connect to a decision or a customer question. It might help an organisation understand a funding problem, explain how a product workflow works or test whether a proposition resonates with a particular audience.
This gives the system a reason to create the piece and a way to judge it later. “Publish three posts” describes activity. “Help first-time applicants understand why eligibility should be checked before drafting” describes useful work.
Source authority has to survive generation
Models are good at turning fragments into fluent prose. Fluency can hide where a claim came from.
The content operation therefore needs a source hierarchy. Product behaviour should come from the current product source of truth. Customer outcomes need verified evidence. Market or policy claims need dated external sources. Voice guidance can shape expression, but it cannot create facts.
This is especially important in a system that spans several repositories and tools. A company brain can make information discoverable. It should not flatten an old planning note and a current implementation record into equivalent evidence.
Generation should carry provenance forward. When the source is weak or contradictory, the workflow should stop or mark the claim for review.
Agents need an execution contract
“Create and publish useful content” gives an agent too much room to invent policy.
The bounded organic-growth model behind FundRobin uses explicit execution contracts, narrow approval authority, deterministic handlers for known steps and a constrained path for work that genuinely needs model judgement. It also keeps append-only events and controls how interrupted work is retried.
Those mechanisms have a simple editorial meaning:
- the researcher can collect evidence without changing the product record;
- the writer can draft without deciding that the draft is approved;
- the publisher can act only on content that crossed the required gate;
- a retry cannot quietly duplicate an external action;
- a reviewer can reconstruct what happened.
The roles can be implemented by agents, scripts or people. The useful part is the contract between them.
Deterministic steps reduce editorial ambiguity
Many content operations ask a model to make decisions that a rule can handle more safely.
A script can validate required metadata, reject a missing source, check whether a URL already exists and prevent a draft from appearing in a public feed. A model is better used for work that benefits from interpretation: grouping research, challenging an argument or adapting a verified idea to a different format.
This division improves quality and makes failures easier to diagnose. If a required field is missing, the system should report that condition. It should not ask a model to infer whether publication is probably acceptable.
Approval should match consequence
Different outputs carry different risks. An internal topic suggestion is easy to reverse. A public article containing a product claim is harder. A direct message sent to a named person has another level of consequence.
The approval model should reflect that difference. FundRobin’s operating approach keeps consequential customer-facing and external actions under human authority while allowing lower-risk preparation to run with more autonomy.
This does not mean a person must touch every step. It means the workflow identifies the point where judgement and accountability matter.
For content, that point usually includes factual review, voice, confidentiality and the decision to publish.
Measurement needs a longer memory than the feed
Content systems are vulnerable to immediate signals. A post gets an early burst of impressions, so the pipeline produces more of the same. A useful article starts slowly, so the system treats it as a failure.
The FundRobin growth control plane uses both shorter and longer outcome windows. The principle matters more than the exact interval. Different content has different jobs and different time horizons.
A social post may create discussion today. A detailed guide may earn search traffic or become sales evidence over months. A product explanation may reduce repeated questions even if it attracts little public attention.
The measurement layer should preserve those distinctions. Otherwise automation accelerates the bias of the easiest metric.
Human review should improve the system
A review gate can become ceremonial: approve, publish, move on. The better use of review is to feed a durable correction back into the operation.
If a draft repeatedly confuses designed capability with live capability, the source rules need improvement. If topics drift away from the audience, the strategy needs adjustment. If a format creates plenty of output and little useful response, the queue should change.
The content operation becomes stronger when corrections update the brief, source hierarchy or execution contract. Editing one article fixes one article.
The output is evidence of the operating model
The most useful lesson from building an AI content system is that generation is a small part of the work. The system still needs strategy, authoritative inputs, roles, state, permissions, quality gates and measurement.
Without those controls, AI increases the speed of publishing uncertainty. With them, it can reduce the repetitive work around research and adaptation while leaving factual judgement and public accountability where they belong.
That is the standard I would use for any AI content operation: fewer unexplained actions, clearer evidence and a direct connection between what gets published and the decision it was meant to support.
Related ideas
- Organisational memory and source authority — How source ownership prevents context and evidence from drifting.
- AI agent boundaries — How bounded authority controls what automation may publish.
Sources and further reading
- Creating helpful, reliable, people-first content — Google Search Central
- Spam policies for Google web search, scaled content abuse — Google Search Central
- C2PA Technical Specification — Coalition for Content Provenance and Authenticity