How We Produce Our Content: Hybrid Division of Labour in Live Operations

This article is its own evidence. It came about exactly as it describes: as a chain of handoffs between a human and a machine, triggered by fixed routines, signed off by a named person. The piece discloses the hybrid division of labour behind this hub in full — tools, numbers and one article as a worked example.

Contents

• Why we disclose the process
• Hybrid division of labour: five handoffs
• Worked example: how one article was made
• The routines: which cadence triggers what
• The gate: judgement, not error hunting
• The feedback loop: why the next run knows more
• When the consultant becomes a developer
• What transfers
• Conclusion
• Frequently asked questions
• Sources

Why we disclose the process

Two reasons, one obligatory and one strategic.

The obligatory one: the AI Act transparency obligations have applied since 2 August 2026. For AI-generated text on matters of public interest, an exemption applies where the text underwent human review and a named person holds editorial responsibility. This page is the record of that process. What disclosure requires in detail is covered in a dedicated article.

The strategic one: we sell companies the build-out of AI Operations. A process we cannot show is not an argument. This hub is our own use case — we run on ourselves what we build for clients.

Hybrid division of labour: five handoffs

The difference between an AI tool and AI operations is not who does what. It is where the baton changes hands — and how you can tell. Every handoff has a trigger, an artefact and a recipient. Without the artefact it is not a handoff but a hope.

For presentations:SVGPNG

The eight steps behind those five changes, in order:

#	Who	Step	Artefact
1	Human	Set positioning and topic plan, write a brief with structure, keywords, sources and angle	Asana ticket
2	AI	Check weekly which articles fall inside the 14-day window and are missing from the repo	run log
3	AI	Verify product facts and statistics against original sources — not against the brief	source list
4	AI	Write DE and EN, build SVG diagrams, run astro check as a mandatory gate, commit	commit
5	AI	Document the result in the ticket, close it, create a review task	comment + review task
6	Human	Check tone, structure and stance, edit, push	git push
7	AI	Daily deploy to Coolify, publication on the stored date	live article
8	Human	Feed what surfaced in review back into standards and project memory	updated standard

Tools, named: Claude for steps 2 to 5, Asana for brief and documentation, Astro as the framework, GitHub Actions for the deploy, Coolify as the target. We name them deliberately — not because they are fixed, but because swappability is only verifiable when you know what is inside.

Where your company stands on AI Operations can be mapped in minutes with the free Self-Check.

Worked example: how one article was made

Every process sounds good in the abstract. So here is a real run: the article “81% cannot measure their AI ROI”, written on 3 August 2026, published on 17 August 2026.

1. The brief — human, around 20 minutes. Created on 7 July 2026 as an Asana ticket. It contained the core message, the H2 structure, three mandatory metrics, primary and secondary keyword, source pointers, internal links and the intended angle — “measurability as a budget survival question, do not repeat the gap narrative”.

2. The run — AI. On 3 August 2026 the routine checked the 14-day window and found two articles due. With nothing due, nothing would have happened.

3. Verification — AI. Where it got interesting. The brief cited “~5,000 companies” as the sample of the DIHK digitalisation survey. Checking the original source gave 4,686 participants, surveyed between 10 and 28 November 2025, report titled “Artificial Intelligence, Sovereignty and Resilience”. The two headline figures — 81 percent cannot quantify AI value, more than 75 percent see no measurable return — held up. The sample size did not.

4. Production — AI. German and English versions, one SVG diagram with language-specific labels, astro check clean, one commit. No push.

5. The handoff back — AI. Result comment in the ticket with the verified facts, the commit hash and the planned date. Ticket closed, review task created.

6. The review — human, around one hour. Factually there was nothing to correct. What changed were sharpening and sequence — and the one figure in the text that had to read 4,686 instead of 5,000.

The third step deserves its own note. The sample size being wrong is not a detail — it is the reason that step exists at all. Briefs age. Checking facts against the brief instead of the source perpetuates old numbers.

Previously the same article would have cost five to six hours: research, writing, diagram, English version. The factor is five. It does not come from writing faster but from removing the work between decisions.

The routines: which cadence triggers what

A process without cadence is a statement of intent. Four routines hold this one together.

For presentations:SVGPNG

One detail matters more than it looks: the deploy runs daily, but publication follows the date in the frontmatter. Push and appearance are decoupled. That is exactly what allows lead time — and takes the time pressure out of the review.

The gate: judgement, not error hunting

Here sits the most uncomfortable finding, and it contradicts the common narrative.

The usual story goes: the AI writes, the human fixes mistakes. In our operation that is not true. Factually, almost nothing is wrong. What gets adjusted in nearly every article is tone, structure and sharpening — mostly small things. Very rarely a misunderstanding, missing context or a different point of view.

What the human contributes is therefore not correctness but judgement. Not “is this right” but “is this our view”. Stance, emphasis, and the context from twenty client conversations that no brief captures in full.

The AI writes correctly. The human decides whether it is right.

Legally that is clean. The exemption in Article 50 requires a deliberate substantive review with a real option to reject — not that mistakes are regularly found.

The feedback loop: why the next run knows more

Step 8 is the least spectacular and the most important. What surfaces in review flows back into two places: the permanent standards ticket that governs all articles, and the project memory that the next run reads.

Three examples from recent weeks: the rule that every article needs its own diagram and that the metrics row does not replace it. The rule that product facts are always checked against the original source, because briefs age. And the finding that emphasis is set as an inline marker, not as a colour block.

None of these rules existed at the start. Each came out of a correction. Without that loop the pipeline would be automation — with it, it is an operation that improves. Exactly the difference we build for clients: not introducing a tool, but building a machine that learns.

When the consultant becomes a developer

The most interesting effect appears in no flow chart.

To run this process, I now work in the repository myself. I read commits, check frontmatter, decide on components and push to Coolify. Two years ago that would have been a developer task, cleanly separated from strategy and editorial. That separation is gone.

This is not an anecdote but the core of it. Anyone running AI has to be able to help build the systems — at least far enough to understand where decisions are made. Otherwise judgement gets delegated to tools nobody controls.

For leaders that carries something uncomfortable: the role changes, not just the team. Getting AI into production means building technical proximity. Not coding — but systems understanding, sign-off competence and the ability to read a pipeline.

That is the most concrete thing to talk through in a diagnosis call.

What transfers

The pipeline itself is a special case. The pattern behind it is not.

Hybrid division of labour means tasks are allocated by fit rather than by person — and handoff points are designed deliberately instead of left to chance. That changes processes, and it changes org charts.

For presentations:SVGPNG

Four questions turn any workflow into a hybrid division of labour:

1. Where are the handoff points? Every change of hands needs an artefact you can show.
2. Which cadence triggers what? Without cadence, nothing happens or everything happens at once.
3. Who decides, and how can you tell? A push, a sign-off, a comment — not a feeling.
4. Where does the learning go? Without a feedback loop it stays automation.

Answer those four for a single workflow and you have the entry point. Why the workflow comes before the tool is covered in workflow-first.

Conclusion

The factor of five in turnaround time is the result, not the reason. The reason is a division of labour designed as hybrid from the start: named handoffs, a fixed cadence, a human gate for judgement, and a loop that returns what was learned.

That is also the answer to the transparency question. A company that can build its process so it may be shown does not have a compliance problem — it has an argument. This page is both: the record and the evidence.

Frequently asked questions

Does the AI write this hub on its own?

No. Topic selection, source selection, fact-checking and approval rest with the human; research, drafting, diagrams and publishing sit with the AI. Without a human push no article appears. The notice block under every piece shows the split for that specific article.

How much time does it actually save?

An article in two languages with a diagram used to cost five to six hours. Today around sixty minutes remain for brief and review. The saving does not come from writing faster but from removing the work between decisions.

What happens when the AI gets something wrong?

Factually it rarely does — but the case is planned for. Nothing appears without a push, and checking against original sources is a separate step. One example: the brief cited a sample of roughly 5,000 companies; the verified figure was 4,686. The correction happened before publication.

Why is there no automatic push?

Because the push is the decision. It marks the point where a human takes responsibility — technically and in the sense of Article 50 of the AI Act. Automatic pushing would remove precisely the step that makes the process defensible.

Does this transfer to other areas?

Yes, if you answer four questions: where are the handoff points, which cadence triggers what, who decides and how you can tell, and where the learning goes. We work that through for one concrete workflow in a free diagnosis call.

Sources

• European Commission: Quick Facts — Transparency rules for AI systems, 2026
• DIHK: Digitalisation Survey 2026 — Artificial Intelligence, Sovereignty and Resilience, 2026
• Astro: Content Collections documentation, 2026
• Coolify: documentation, 2026

All time figures and process details in this article come from the internal operations of the AI Operations Hub, as of August 2026.