Roadmap
A four-phase path from a trustworthy Python foundation to a guarded recovery ecosystem—without ever granting ambient production authority.
The phase model
The roadmap develops reusable contracts, reference adapters, optional packages, test utilities, and relatable examples in four phases. Phase numbers describe capability maturity—they do not imply separate services, a hosted account, or a commitment to implement every named integration in core.
| Phase | Sprints | Outcome | Status |
|---|---|---|---|
| Phase 1 — trustworthy Python foundation | 0–6 | Stable, secure, documented Python contracts and independently usable reference paths. | Complete; releasing as 0.1.0 |
| Phase 2 — model, prompt, and bounded agents | 7–11 | Replayable provider-neutral reasoning and read-only evidence planning with hard budgets. | Next |
| Phase 3 — intelligence, memory, and integrations | 12–17 | Explainable cross-system context, quality-aware memory, and optional integration packages. | Planned |
| Phase 4 — guarded recovery and ecosystem | 18–23 | Portable recovery protocols and a mature, multi-language-friendly ecosystem with no default executor. | Planned |
Phase 1 — what shipped
- Strict domain, application, port, adapter, config, CLI, security, and testkit boundaries.
- Legacy text rules and structured all/any/not rules with explanations and fixture testing.
- Bounded evidence collection, Markdown and versioned JSON reports, and local SQLite memory.
- Plugin SDK with static manifests, metadata-only discovery, and explicit load policy; independent PostgreSQL memory and HTTP JSON evidence packages.
- Typed playbooks, default-deny policy, evidence-linked proposals, idempotent approvals, verification records, conservative learning, and replay evaluation.
- Stable lumis.dev/v1 configuration with a deterministic migration CLI, a public API stability inventory, and a compatibility policy.
- Supply-chain hardening: SBOMs, signed attestations, reproducible builds, secret scanning, and a recorded security review.
The working agreement
- Core remains deterministic-first, local-first, model-optional, vendor-neutral, and useful with no plugins installed.
- A provider, framework, protocol, database extension, cloud, or heavy dependency belongs in an optional package behind a stable port.
- Models may classify, rank, plan evidence, and suggest allowlisted playbooks—they may not verify their own work or gain execution authority.
- SaaS tenancy, hosted secrets, billing, UI ownership, and enterprise administration remain in Lumis, the managed product—never in the SDK.