Roadmap — Building OMAP in the Open

Build the layer in the open. Then give the contract away.

OMAP — the Open Memory & Action Protocol — is the open artifact of OrgLM.ai: a contract for governed retrieval and action across interchangeable models. A protocol earns the right to be canonical only if it is genuinely open. This is how we get it there.

Protocol OMAP v0.1 · public draft Posture Above the model. Above the ecosystem's protocols. Not against them. Home Neutral governance, by design

The model is rented. The contract above it is yours.

Everything on the roadmap serves one boundary: keep judgment, policy, and memory on the organization's side, and keep the model a swappable choice on the other. The protocol that draws that boundary should belong to everyone — so we are building it in the open and contributing it to a neutral home.

What stays owned

Typed memory, explicit policy, and a learning loop that compounds. Reached through a structured contract, never a text channel. This is the part no roadmap step ever rents out.

What stays rented

The reasoning engine — open-weights by default, frontier when the work demands it, swapped as the field moves. Brilliant and borrowed, and never the keeper of the boundary.

Three acts: plant the thesis, prove it, then hand the standard to a neutral home.

Act One

Now — live

Shipped & ongoing

Plant the thesis in the open

State the argument publicly and precisely: the memory, policy, and learning layer belongs to the organization, sitting above interchangeable models — and above, not against, the protocols the ecosystem already trusts.

01OMAP v0.1 published — typed facts, governed actions, interchangeable model access
02The thesis, the reference stack, and the State of the Union paper released
03"Above MCP, not against it" — framed as complementary to the open standard, not a rival
04Public series drawing the context-graph distinction and the before/after of owning the boundary

Act Two

In progress

Active

Prove it, then give the contract a neutral home

A thesis earns its place by working. We prove OMAP against real work, show conformance anyone can run, and contribute the contract to vendor-neutral governance — so no single party, including us, owns the standard.

01Reference implementation on the open stack — addressing open-weights and frontier endpoints as equals
02Open conformance examples and evaluation data the community can run against the envelopes
03Submit OMAP as a project proposal to the Agentic AI Foundation, under the Linux Foundation
04Join the relevant working groups as the typed-memory and policy layer that sits above MCP

Act Three

On the horizon

Prove the contract is general, then formalize standing

Show OMAP holding up across more than one real domain — the proof that the contract is portable and the model underneath is genuinely swappable. Standing in the open ecosystem is earned through contribution first, then formalized through membership — in that order.

01More than one real deployment running on the same OMAP contract, with the model swapped beneath it
02An open governance process: a contributor community shaping how the spec evolves
03Formalize standing with the Linux Foundation and the Agentic AI Foundation
04Co-development with the platforms that sit below the contract and the protocols that sit beside it

What building in the open commits us to.

Open is a discipline, not a label. Three commitments hold the roadmap honest — and answer, in advance, whether this is genuine contribution or a land grab in open clothing.

Neutral by design

The contract belongs in a foundation, not a vendor. Contributing OMAP to neutral governance is what keeps model choice real and lets the standard outlive any one company — including OnePgr.

Above, not against

OMAP sits above the protocols and platforms enterprises already trust. It drives demand on them rather than competing with them. Partnership is the default posture, end to end.

The substrate stays yours

What we contribute is the contract at the boundary — never the substrate behind it. You can build against OMAP without learning anything about how anyone has built to it. That line never moves.