Agent NAS v0.2
English

Roadmap

The roadmap is ordered as now, next, later and not planned, with no year-by-year promises: a three-year schedule written in 2026 would most likely be rewritten by facts within the first year.

v0.2 Draft specification Updated

Now, next, later

  1. Now (Q4 2026) In progress

    Concept, draft specification and website

    The concept and draft specification v0.2, and the website in 8 languages. Gathering feedback: interview 3 to 5 real users who already combine AGENTS.md with Git, to test bets B1 to B7.

  2. Next (target: first half of 2027) Next

    Reference implementation v0 and specification v0.3

    Reference implementation v0 (Lite and Overlay): Git and file-system snapshot backends, lease issuance, records and read manifests, a CLI, and a conformance suite for L0 to L1; specification v0.3 (Core, Lease & Record). One demonstrable scenario: an agent works on a branch overnight, and in the morning you approve the merge on a Gate Card.

  3. Later (depends on feedback) Later

    Memory, Guard, the control room and Sync

    The Memory layer and the MCP tool surface (L2); Guard: labels, taint and cascade forgetting (L3); the control room; the Team and Cloud forms; Sync (L4).

Not binding

This is intent, not a promise. What defines “compatible” is the conformance levels, not the calendar.

The stage gate (what would prove us wrong)

The bar for finishing “next” is not a feature list. It is: running for a week in at least three real workflows; a gate approval rate below 95%; and at least one real problem caught. If we cannot meet it, we go back and change the concepts instead of piling on features.

Not planned

  • Our own storage engine.
  • Our own vector database.
  • Model hosting.
  • A skill marketplace.
  • Tokens and blockchains.
  • Dedicated hardware.

Questions left open on purpose

  • How does the free-text purpose in a lease evolve into structured intent that machines can check?
  • How are semantic mergers registered and trusted?
  • Should the granularity of labels be the file or the paragraph?
  • In multi-tenant settings, how is the label vocabulary governed?
  • How should the propagation delay of revocation between nodes be described to the outside world?
  • How do we measure memory quality? What is the regression standard when the model or the embeddings change?
  • For a fact inferred from several sources, how does Cascade Forget define the affected scope?
  • Under high throughput, how are the storage cost and granularity of read manifests traded off?
  • What is the best interface for batch and tiered review? How are the thresholds for automatic merging measured and tuned?
  • How are cross-organization roots of trust distributed and revoked?

Cite this page

Stable addresses and a suggested citation for people, search engines and agents.

Suggested citation
Agent NAS project. “Roadmap.” agentnas.com, 2026-11-11. https://agentnas.com/roadmap/