Engineering principle 001
Build with clear boundaries.
Governance state and runtime execution require explicit ownership.
AIGP / Engineering Journal
Field notes on AI governance, distributed systems, protocols, and the decisions behind reliable systems.
Explore the journal
An agent can be authenticated and permitted by an API—and still take an action it was never authorized to decide.
Why operational logs cannot replace decision evidence.
5 min read ↗
Transport compatibility without changing governance ownership.
7 min read ↗
Reusable skills teach workflows; repository instructions carry the context that makes a system safe to change.
6 min read ↗
A graph should make governed relationships inspectable, not pretend to be an operational dashboard.
7 min read ↗
A governed registry record and an artifact store have distinct jobs.
7 min read ↗
Runtime evidence is valuable without turning the platform into an upstream authoring system.
7 min read ↗
A versioned asset plane establishes ownership, immutable artifacts, and inspectable lineage.
8 min read ↗
A replay must reproduce and defend a historical decision; a retry only asks whether work finished.
9 min read ↗
Reliable systems need a boundary between search projections and authoritative evidence.
7 min read ↗
MCP transports and REST adapters serve different integration needs.
8 min read ↗
Engineering principles
Principles behind the control plane, kept distinct from the editorial archive.
Engineering principle 001
Governance state and runtime execution require explicit ownership.
Engineering principle 002
The right transport depends on who—or what—needs to consume the capability.