AIGP / Engineering Journal

Engineering systems worthy of trust.

Field notes on AI governance, distributed systems, protocols, and the decisions behind reliable systems.

11 essaysArchitecture · Governance · Engineering · Protocols

Explore the journal

Latest first ↓

Featured essay / Governance

Permission vs Authority

An agent can be authenticated and permitted by an API—and still take an action it was never authorized to decide.

Oct 11, 2026 · 7 min readRead essay ↗
Engineering

The incident report is not evidence

Why operational logs cannot replace decision evidence.

5 min read ↗

Protocols

Stateless MCP did not require a control-plane rewrite

Transport compatibility without changing governance ownership.

7 min read ↗

Engineering

AI agent skills are not system knowledge

Reusable skills teach workflows; repository instructions carry the context that makes a system safe to change.

6 min read ↗

Architecture

Lineage is not analytics

A graph should make governed relationships inspectable, not pretend to be an operational dashboard.

7 min read ↗

Architecture

Why dataset metadata belongs in the control plane—and dataset bytes do not

A governed registry record and an artifact store have distinct jobs.

7 min read ↗

Architecture

Observed is not managed: the ownership model AI registries miss

Runtime evidence is valuable without turning the platform into an upstream authoring system.

7 min read ↗

Architecture

A governed asset plane for AI systems: catalog first, MLOps later

A versioned asset plane establishes ownership, immutable artifacts, and inspectable lineage.

8 min read ↗

Governance

Replay is not retry: one word that changes the integrity of the evidence

A replay must reproduce and defend a historical decision; a retry only asks whether work finished.

9 min read ↗

Architecture

The hard scaling problem in AI is deciding what to remember

Reliable systems need a boundary between search projections and authoritative evidence.

7 min read ↗

Protocols

MCPO vs Streamable HTTP: choosing the right interface for AIGP

MCP transports and REST adapters serve different integration needs.

8 min read ↗

Engineering principles

How we build

Principles behind the control plane, kept distinct from the editorial archive.

Engineering principle 001

Build with clear boundaries.

Governance state and runtime execution require explicit ownership.

Engineering principle 002

Protocols are interfaces.

The right transport depends on who—or what—needs to consume the capability.