Category positions
Essays
Arguments that shape the Workspace Intelligence category. These pages begin with the engineering idea; product implementation remains supporting evidence, not the subject.
AI Does Not Need More Code. It Needs a Workspace Contract.
Why file-by-file context is too weak for reliable engineering decisions, and how a workspace contract turns scattered project state into inspectable evidence.
The Workspace Intelligence Loop Is a Decision Contract
Why model, impact, health, readiness, verification, context, and explanation must run in a stable, evidence-backed order.
The Workspace Model Comes First. The Graph Comes Next.
A practical architecture for turning code, contracts, infrastructure, and evidence into a canonical model and several useful representations.
A Repository Is Not a Software System
Repository-centric AI can read implementation text while still missing ownership, policy, consequence, and operational meaning.
AI-native Engineering Needs a Shared Operating Layer
Faster code generation increases the need for a governed layer that explains system state, evidence, impact, and safe action.