What an Autonomous Publishing Pipeline Actually Looks Like
An autonomous publishing pipeline should automate evidence collection, drafting, validation, and observation without confusing a generated candidate with an approved publication.
Autonomic Web
build-log
Engineering case studies and operating principles for adaptive web systems: bounded agency, observable state, human override, and reversible publication.
Running a Multi-Domain Publishing System on One Content Model
A shared content model can remove repeated engineering work, but it also spreads generic assumptions. The difficult part is sharing capability without cloning editorial identity.
n8n: Orchestration for an Autonomic Pipeline
Why a visual workflow tool, not a bigger model, is the missing piece that turns one-off generation into a standing autonomic pipeline.
Five Distances, One Run
The same autonomic run, seen at five distances -- from the whole system lit up at once down to the single point where one decision actually happens.
What Broke While Building an Autonomic Publishing System
A build log about the assumptions that failed, the problems hidden by technically correct pages, and what a multi-domain experiment taught me about autonomy.
Generation Is Not Publication
Why an autonomous content pipeline still needs human override, observable decisions, and a hard boundary between producing a draft and making it public.