Skip to content
YewForge Digital / Engineering

Dependency-aware direction

Roadmap and end state

Koda's roadmap is a status map, not a release calendar. It records dependencies and boundaries without inventing dates or converting intent into delivery claims.

CurrentLast reviewed: 15 July 2026Publisher: YewForge Digital

Roadmap categories

DirectionStateDependency / boundary
Workshop refinement and truthful operational surfacesNextBuild on existing tested interface and read-only state work; retain fixture separation.
Core Shard and Shard-family progressionActiveContinue bounded runtime and interaction evidence; do not imply complete desktop behaviour.
Shard FieldDependentRequires approved field-specific progression beyond current family and runtime proofs.
Organs and specialist nodesDependentNeed stable contracts, capability boundaries and evidence before broader orchestration claims.
Nano-model, Dataset Foundry and Experiment ForgeResearchA corrected R1.1 corpus and sealed holdout passed defined checks, but the candidate remains below frozen qualification thresholds; any continuation or holdout access needs fresh authority.
ObservabilityActiveKeep native, local read-only instrumentation primary; optional tooling stays optional.
Mobile integrationDeferredFuture relationship to desktop and evidence systems; no current mobile implementation claim.
Security and R&D environmentResearchDormant, controlled branches require dedicated safety and authority review.

Long-term system vision

The intended end state is a local-first operating environment in which interfaces, models, bounded tools, evidence records and human decisions can coexist without obscuring authority or provenance. It is a direction of travel rather than a declaration that the environment already exists.

That end state depends on real, inspectable relationships between components. It cannot be reached by decorating incomplete connections or treating a visual map as proof of a working system.

What is intentionally not scheduled

No dates are assigned here. The current record does not support reliable delivery dates for the Shard Field, a mobile runtime, model training, research campaigns or a completed operating environment. Publication of a roadmap does not authorise those activities.

Sources: KPCF-009 to KPCF-014, KPCF-016 to KPCF-020; public casefile overview and evidence-gap records.