Good content needs operational consistency and actual judgment. Manual workflows fail on consistency; unbounded automation turns into a feed of plausible words nobody should have published.
The obvious automation was not the whole problem.
The system needed to capture ideas from anywhere, preserve human edits, recover cleanly from failed scheduled jobs, and make it structurally impossible for a changed draft to pass on the strength of an old approval.
The reliable architecture splits work by its nature: deterministic code for state, language models for judgment, and a human for accountability—enforced by the system, not a reminder.
Build the operating loop, not only the intelligent step.
- 01
Made Obsidian the human source of truth and used a deterministic controller for state, reconciliation, logs, and retries.
- 02
Used scheduled agent turns for research, drafting, and critique rather than for irreversible actions.
- 03
Bound approval to the exact content version so material edits reset review automatically.
- 04
Recorded unavailable analytics as unavailable, never zero, so the learning loop does not optimize on fiction.
A daily operating system that captures, researches, drafts, critiques, and measures content—while asking for attention only where judgment and accountability are genuinely required.
What stayed after shipping.
The goal is not maximum automation. It is precise allocation: determinism for state, models for judgment, and human approval where the consequences should remain owned by a person.