status and direction

Useful today. Room to build.

The live pods demonstrate the idea. The specification defines a common contract. The Kotlin modules give developers a place to start. Each has its own state and its own next steps.

Available in Kotlin 0.2.0

• HTTP CRUD, read-only SPARQL, Context permissions and graph retrieval.
• A JVM HTTP client with separate RDF4J and media adapters.
• Delegated OAuth access and experimental service registration with owner consent.
• Per-pod MCP, a hosted multi-pod MCP service, and an OIDC identity service.
• Reusable modules and a local development/evaluation composition.

The release notes record breaking changes, deprecations and known limitations. The migration guide covers consumers moving from 0.1. A release does not identify the version running on every public host.

A development specification with normative requirements

Core and optional modules are currently labeled 0.1-dev. Their source commit identifies a particular revision. Their versions are independent of Kotlin releases and of each other.

The normative chapters already determine the contract. Implementation behavior does not override them. A product conformance suite remains unfinished, and Kotlin 0.2 does not yet serve the required conformance discovery endpoint. No certification is claimed.

Read the development specification Read governance

A smaller common interface

The vision is a framework that composes existing standards while leaving implementations free to choose their storage and policy mechanisms.

Authorized data access proposes ordinary access without Context setup. Context discovery and selection remain part of that proposed interface. Adoption is tracked in specification issue 68. The current contract still uses Contexts as its authorization boundary.

Easier paths into the ecosystem

Better retrieval adapters, semantic app contracts and clients in more languages could make more use cases practical. Their public issues own scope and progress; a direction here promises no delivery date.

Concrete distributions with fixed configurations and verified upgrade procedures would also make operation easier. The current composition supplies development building blocks and has no supported upgrade path.

Use what is available Specification work Implementation work