Concept

The Moat: Policy-Aware Reasoning with Receipts

The same module vocabulary connects architecture policy, episodic memory, and workflow contracts (lex.yaml), letting assistants answer "why" with citations.

Why this matters

Single Vocabulary

Modules in Frames match modules in lexmap.policy.json and workflows in lex.yaml. No drift, no guesswork.

Explainability

Answers come with receipts: timestamps, blockers, policy edges, and workflow context that explain blockers.

Org Scale

Frames across teams align with org policy to provide consistent, auditable reasoning.

Contract Stability

With Lex 2.0.0 and AX guarantees, the contract surfaces are stable. Agents and runners can depend on Frames, policy, and lex.yaml without surprises.

The Contract Surface

Lex 1.0.0 provides three stable contract surfaces that form the moat:

  • Frames: timestamped work session snapshots with module_scope that matches policy vocabulary.
  • lexmap.policy.json: machine-readable architecture boundaries using the same module IDs.
  • lex.yaml: intent-level workflow contracts describing what work exists and what policies apply.

Because all three use the same vocabulary, an assistant can cite which policy rule was violated, which Frame observed it, and which workflow it is blocking — all with receipts.

Lex 2.0.0

About Lex — policy + memory + contracts with shared vocabulary and AX‑native guarantees.

lex.yaml Contracts

lex.yaml — intent-level workflow contracts for your repo.