Current stageR12-R20 local foundations
Live development scope

What is in motion now

updated from the public state
  • R4.1-R10Protocol + conformanceGuarded / conforming
  • R12Worker boundaries + permission receiptsImplemented locally
  • R13A2A / ACP transport + adaptersImplemented locally
  • R14Model Atlas + usage ledgerImplemented locally
  • R15Control rooms + private projectionsImplemented locally
  • R16Library intake + progressive onboardingImplemented locally
  • R18Trusted devices + recoveryFoundation / gated
  • R19Authenticator + mobile approvalsFoundation / gated
  • R20Multi-authority queues + routingFoundation / gated
  • M5Hosted tenancy + external operationsNot enabled

Green means the local contract or conformance work is implemented. Yellow marks a foundation whose production boundary is still gated. Red means the capability is intentionally not enabled.

Menu
Public project journal

Relay updates

Short, public-safe notes about what changed, what was verified, and what remains guarded. These notes are not a substitute for the repository history or release gates.

See releasesView commit historyGet support
Release notes

Recent public milestones.

0.1.16Candidate

Unified local-client workspace

The Windows Library/client now brings round-table chat, local GGUF Overseer mode, persistent readable transcripts, compact runtime controls, and guarded mobile foundations into one review workspace.

internal preview · unsigned · production gates remain
R12–R20Implemented

Local contract foundation

Tested local boundaries for framework adapters, A2A/ACP, Model Atlas, private projections, guided onboarding, Jira, trusted devices, mobile approvals, and multi-authority queues.

implemented locally · production gates remain
R4.1–R10Implemented

Guarded interoperability

Policy evaluation, archive lifecycle, provider-neutral adapters, MCP apply/rollback, and the Adapter Conformance Kit remain bounded and human-gated.

guarded / conformance
Journal format

Every note should answer three questions.

What changed?

Name the user-visible feature, document, or contract boundary.

What was verified?

Link the test, build, artifact, or status source instead of implying more certainty.

What remains guarded?

Keep hosted services, credentials, private data, and production authority claims explicit.