1. Keep Lex boring and dependable.
Lex remains the public memory and policy substrate: stable CLI behavior, useful MCP coverage, deterministic JSON, local SQLite, and better instructions generation.
Status snapshot • June 27, 2026
The roadmap is moving from tools to an operating stack.
Lex and AXF are usable today. LexThority is now public as the authority preview. LexSona and LexRunner remain controlled while the behavior and containment boundaries settle.
The near-term work is not another prompt pattern. It is the layer that lets agents remember, discover workspace capabilities, ask for authority, inherit behavior, and coordinate bounded work.
Current public surface
| Project | Status | Package | Source |
|---|---|---|---|
| Lex | Public MIT core for memory, policy, recall, instructions, CLI, MCP, and API. | npm latest | GitHub |
| Lex MCP | Public MCP wrapper for Lex surfaces. | npm latest | NPM package |
| AXF | Public source-available alpha for workspace capability contracts. | npm latest | GitHub |
| LexThority | Public source-available preview for authority envelopes and effect receipts. | Not published on npm yet. | GitHub |
| LexSona | Controlled-access behavioral constraint engine. | Not public npm. | Concept page |
| LexRunner | Controlled-access flow layer for gates, receipts, containment, and swarm-ready coordination. | Not public npm. | Concept page |
Near-term roadmap
2. Make AXF the workspace capability layer.
AXF should make local repo know-how discoverable and runnable without turning every capability into raw shell improvisation. Expect more adapter examples and lifecycle hardening.
3. Mature LexThority around effect decisions.
The authority layer should classify attempted effects, evaluate them against envelopes, and produce allow, escalate, or deny receipts without pretending to replace enterprise IAM.
4. Separate LexSona behavior from LexRunner flow.
LexSona should return deterministic behavioral constraints. LexRunner should consume those constraints, not become the persona engine.
5. Add contained swarm execution to LexRunner.
Parallel agents need contained, worktree-like execution roots, per-agent envelopes, explicit mounts, and gated promotion back into canonical work.
6. Prove the stack outside development.
Analyst, product, support, security, and operations workflows should use the same surfaces: memory, capability, authority, behavior, flow, and receipts.
Design principles
Use existing brokers
The stack should cooperate with OAuth, cloud IAM, GitHub permissions, and enterprise security tooling. It should not invent a shadow identity provider.
Fail with operator-ready detail
When a credential, policy, or tool blocks work, the agent should be able to tell an operator what was attempted, what failed, and what permission or action is needed.
Preserve agent autonomy
The goal is bounded agency, not bureaucracy. Agents should reason freely inside a workspace while effects are gated, receipted, and recoverable.