docs.dev vs The Deterministic Core

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

The Deterministic Core: A Fixed Foundation for AI Collaboration, by Brandon Bell.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About The Deterministic Core

The Deterministic Core: A Fixed Foundation for AI Collaboration, by Brandon Bell. The engineer patches a defect, runs an audit, receives a score. They are measuring distance, from each model's internal, implicit, and mutually inconsistent standard of completeness. The surface area of "not quite done" expands faster than it can be closed. The model cannot recognize completion, not because the build is incomplete, but because completion is not a state the model's architecture can represent.