precon · case-study
A Download Is Not Publication
Files arrive before meaning does.
Systems In Practice
Decisions under operational pressure.
Follow concrete operating tensions through decisions, controls, failure paths, and repair.
Stories and architecture
platform · case-study
Failures Are Work Items, Not Just Log Lines
Some failures mean the software is wrong. Others mean the software has reached the edge of what it can decide safely.
data · case-study
One Database, Several Kinds Of Truth
One Postgres database can make several kinds of truth look interchangeable. They are not.
platform · case-study
Humans And Agents Share Controls
Capability is getting cheaper. Authority is not.
geo · case-study
Geography Becomes An Operating Decision
A map can reveal a pattern and still fail to preserve a decision.
platform · architecture
Platform Layers
Layering is how we keep a convenient change from becoming a permanent coordination problem. Runtime surfaces, stateful capabilities, deterministic policy, provider translation, data movement, executable jobs, infrastructure, and durable…
platform · architecture
Monorepo As Operational Platform
The monorepo is a coordination choice. It lets us change the data contract, the automation that acts on it, the review surface that handles ambiguity, and the documentation that preserves the decision as one reviewable unit. Physical…
data · architecture
One Database, Many Responsibilities
One Postgres database currently holds several different kinds of truth. That is an economical deployment choice, not permission to treat every table as one shared model. Analytical history, interactive workflow state, and execution…
data · architecture
Designing For Future Separation
Future separation is mostly determined before anything is split. If today's code knows which capability owns a decision, which data can cross a boundary, and how a failed effect is repaired, then moving a database or service is a change…