Roadmap and release gates

0.0.1: establish the native core

Local GGUF discovery, exact loading options, memory admission, private runtime ownership, streamed conversations, Stop/recovery, local persistence and Windows packaging form the current foundation. The installed smoke test establishes functionality on one declared artifact/hardware tuple.

The baseline is ordinary layer offload and can be slow. Performance is the next priority; more interface surface does not solve a residency or kernel bottleneck.

Next: explain and improve execution

Compare identical artifacts and workloads before changing defaults. Investigate architecture-aware dense/expert placement, then bounded residency and transfer strategies where compatible. Preserve weights, exact context and correctness. Record applied options, resource peaks, first-token latency and decode separately.

An experimental result must remain experimental until reproduced and integrated through the native load contract. Do not call a CPU-expert flag Strata, a predictive cache or universal support.

Model discovery and controls

Add immutable online artifact discovery, complete shard/projector grouping, resumable verified transfers and fit-before-download ranking. Expand presets, prompt templates, sampling, cache precision and other controls only with an actual backend mapping and effective-configuration report.

Recommendations should show quality/storage/latency tradeoffs without silently selecting a lower-quality artifact. “Metadata inspected,” “memory estimate,” “runtime qualified,” “generation tested” and “quality evaluated” remain distinct states.

Public platform

Implement and test the public API before publishing SDK and CLI installation instructions. Add authenticated remote-device linking only after pairing, scoped policy, ownership and transport recovery exist. Cross-platform support needs real binaries, packaging and model qualification per platform, including ARM and MLX where applicable.

Agentic workstation

Replace atlas simulations with real scoped repository/editor/terminal/browser tools. Implement RegesMode permissions, durable run state, MCP transport/authentication, reviewable skills and module lifecycle. Verify complete tasks, errors and recovery rather than displaying invented tool results.

How a capability becomes ready

1. Define its user behavior and trust boundary.
2. Implement actual host/runtime effects.
3. Validate unsupported inputs and failure paths.
4. Exercise the packaged end-to-end workflow.
5. Record exact limits and evidence.
6. Update release status and docs.

No dates or universal speed multipliers are promised here. A solo developer’s advantage is a focused, reproducible improvement—not a large set of unsupported badges. These docs will expand as the implementation earns each claim.