Everything the platform does, in one place.

Durable knowledge is held as entities, observations and typed relations. Entities are unique by name, facts accumulate as observations, and structure accumulates as relations. Nothing is physically deleted: retirement is a lifecycle state, and retired knowledge can revive with its original creation evidence intact.

Tasks carry an explicit lifecycle (not started, in progress, done, archived, cancelled), and every transition preserves history rather than overwriting it. Notes use the same storage without actionable state. Digests and ready views compile the current work set deterministically.

Context is compiled by the platform: ready and prime views, digests, session recall and context packs. Compilation is deterministic, so the same state produces the same orientation for any client.

Agents can queue clarifications for humans and record the answers as durable material. Structured debate captures competing positions; quorum records an agreement with named participants. Inbound material can require review before it becomes agreed state.

Each profile is an independently authorised storage and security boundary. A connection selects one profile at handshake and the session stays bound to it. Inside a profile, principals hold an explicit project grant list; ungranted content reads as absent rather than denied, so foreign projects cannot be probed by name.

Jobs are claimable units of work with explicit completion and release. Lanes group work into reviewable streams with their own state and merge step. Recurring timers and delivery jobs are materialised by a separate mechanism that transports work but makes no decisions.

Reflection runs as an explicit pipeline: audit, start, status, decide, apply, review, with cancel, archive and discard paths. Proposals are separate from application, so consolidation is a reviewed action rather than a background rewrite.

Durable objects move between lifecycle states rather than being physically deleted, and transitions record an audit/history event. Operations either complete or fail atomically, so partial state is not left behind.

Status reporting exposes the visibility marker and project list for the current session, which usually distinguishes a scope surprise from an outage. A fuller diagnostic pass reports service health in detail.