
The AI Dev Tools I Built in 2026: 58 Builds, Five Shifts
Trace 58 AI dev tools I built across 70 workspaces in 2026 — from early agent loops to DXP ontologies, fleet worktrees, FinOps gateways, and signed proof.
Models propose. Systems preserve state, bind evidence to exact candidates, enforce policy, and keep consequential decisions with named humans.
Dakota Smith AI Systems Architect & Full-Stack Engineer daksmith.dev
Current analysis

Trace 58 AI dev tools I built across 70 workspaces in 2026 — from early agent loops to DXP ontologies, fleet worktrees, FinOps gateways, and signed proof.
One argument, carried through the publication: define the boundary, teach the machinery, inspect the implementation, and keep the unproven claims visible.
About the practicePosition
A falsifiable seven-invariant profile for accountable acceptance outside model sessions.
Read the conformance profileField guide
The machinery that separates runtime execution from evidence, policy, and authorization.
Study the control layerPublic system
Durable work state, exact-candidate gates, content-addressed evidence, and bounded authority.
Inspect the implementationEvidence boundary
An author self-audit: process conformance is documented; live delivery and external acceptance remain unproven.
Review the stated limitsA four-part field guide from work structure and portable capabilities through runtime control, delivery authority, and security.