For AI agents: the complete documentation index is available at https://a3s-lab.github.io/Use/en/llms.txt, the full documentation bundle is available at https://a3s-lab.github.io/Use/en/llms-full.txt, and this page is available as Markdown at https://a3s-lab.github.io/Use/en/guide/roadmap.md.
A3S Use
  • English

      • Roadmap

      This page is a product summary. The repository's ROADMAP.md is the source of truth for priority and completion status.

      Current baseline

      As of 2026-07-31, main contains:

      • named schema-v3 Tool Task/Service, MCP, Skill, and UI contracts;
      • signed catalog v1–v3, offline verification, metadata-only search, and planning targets;
      • immutable operation plan, permission ceiling, grant, and provider evidence contracts;
      • exact-generation workspace grant storage and a recoverable journal;
      • typed Runtime Task/Service binding, invocation, receipt, and observation adapters;
      • dependency-gated Surface Reconciler, planner evidence, and capability snapshots;
      • the M0K-A a3s.use.okf-bundle.v1 descriptor, bounded v0.2/v0.1 inspector, and canonical fixtures.

      The stable v0.2 package foundation remains independently usable. The plugin-platform baseline above is in development on main and is not a complete production plugin product.

      The latest product scope also adds OKF (Open Knowledge Format) as a first-class cognitive surface. Its shared content contract is frozen but is not yet part of the schema-v3 surface baseline. Manifest, catalog, plan, receipt, projection, lifecycle, and A3S Knowledge atomic-index protocols must be completed before OKF can be described as an installable surface.

      Milestones

      MilestoneStatusOutcome
      M0 — Contract freeze and fixturesCompleteIdentity, surface, permission, plan, grant, and release fixtures frozen
      M0K-A — OKF bundle contractCompleteExact content identity, bounded conformance, and canonical fixtures
      M1 — Signed searchable catalogCompleteTUF-signed catalog, bounded search, planning bundle, and cache
      M2 — Shared Plugin ManagerIn progressUnified CLI/Web/MCP lifecycle, durable plan/apply/replay, and parent saga
      M3 — User plugin UXPendinga3s plugin vocabulary, on-demand Science/OKF packages, and E2E
      M4 — Agent read-only managementContracts completeSearch, inspect, list, status, and plan tools
      M5 — Permission/runtime enforcementIn progressProduction grant, secret, egress, filesystem, process, and Gateway adapters
      M6 — Authorized agent lifecyclePendingAuthorized apply, hot use, upgrade, disable, and uninstall
      M7 — Supply chain/platform gatesPendingRegistry operations, rollback/GC, Windows parity, and release gates

      Current critical path

      1. Connect the host Runtime Broker and canonical grant changes to the shared Plugin Manager's final plan.
      2. Coordinate package, grant, Runtime, Gateway, projection, capability, and drain checkpoints in one recoverable parent saga.
      3. Complete CLI, Web, and agent install → use → upgrade → uninstall E2E with production providers.
      4. Add the general package dependency solver, deterministic lock graph, retained-generation rollback, and garbage collection.
      5. Freeze the remaining OKF manifest, receipts, host projection, atomic index generation, and uninstall semantics around the shared content contract.
      6. Extend Agent, prompt, hook, memory, and context-provider contributions only after each host contract is frozen.
      7. Complete official registry operations and Windows platform gates.

      Completion definition

      The cognitive plugin platform is production-ready only when all of these are true:

      • one package identity covers discovery, planning, authorization, install, enable, upgrade, disable, and uninstall;
      • required Tool/MCP/Skill/UI/OKF surfaces become visible atomically for one generation;
      • package, grant, Runtime, Gateway, and projection recover after crashes without duplicate side effects;
      • signed catalog, plan digest, permission, provider, and runtime observations are auditable end to end;
      • CLI, Web, and agent management MCP share one manager and receipt format;
      • Linux, macOS, and Windows support claims have automated release gates.

      Development principles

      • Freeze contracts and fixtures before implementing adapters.
      • Complete the production lifecycle before adding new cognitive surface types.
      • Do not hide missing provider, authorization, or readiness evidence with fallback.
      • Do not duplicate an existing manager, store, selector, registry, or protocol.