Strategy

2 Articles

The Company's Memory Must Be an Enterprise Record

Inference Is Rented. Institutional Knowledge Must Survive the Supplier.

Companion to Agent Control Points

Model routers and customer-controlled agent state are now concrete product architectures, but they do not make every model interchangeable or every memory store strategic. The important boundary is narrower. Task checkpoints are operational state, transcripts are evidence, embeddings are derived indexes, and model-generated memories are untrusted proposals. Canonical institutional knowledge becomes an enterprise record only when the company can govern its meaning, provenance, lifecycle, access, retention, and portability. That record feeds a context compiler, which builds a purpose-bounded view for an approved task, and a router, which selects an execution supplier. Reads are exposure decisions, and writes are changes to future behavior. The approved-task record should bound both without being confused with the memory itself. A vendor may operate the store, but the record must remain intelligible, governable, and recoverable when the vendor changes.

Agentic Identity Strategy Interoperability Authorization

The Enterprise Agent Control Stack

Three Contested Control Points, One Final Decision, and the Records That Must Survive

Companion to Agent Control Points

The enterprise agent control stack is not one product or one call chain. It is a set of independently governed answers: which instance is running, whose Agent it is, which deployment was approved, why its current work remains authorized, what an issuer may project, how credentials are acquired and presented, whether a resource permits one concrete action, and which evidence proves the joins afterward. Three upstream positions are contested control points: the provider seam, identity binding, and the approved-task record. The resource decision remains the non-delegable final word, while runtime evidence, issuance, and audit support the chain without substituting for its records. The context and memory plane crosses this path but does not merge with it: approved work bounds exposure and memory-write rights, while canonical institutional memory keeps its own lifecycle. Six rules, one forward-and-reverse trace, and five component-replacement tests turn the series into an architecture and procurement tool.

Agentic Identity Authorization Standards Strategy Interoperability