# Ablative documentation

> Release and preview builds use the committed documentation snapshot.

## Lys (0.3.1)

- [Lys](https://docs.ablative.com.au/lys/): Identity, permission and verifiable records for people, agents and the services they use.
- [Plugins](https://docs.ablative.com.au/lys/plugin/): Install the Lys plugin in Claude Code or Codex and authenticate its remote MCP connection.
- [Getting started](https://docs.ablative.com.au/lys/getting-started/): Connect to an existing Lys service, inspect the installed command and understand an agent start.
- [Connect to Lys](https://docs.ablative.com.au/lys/getting-started/connect/): Inspect the installed CLI and connect to the intended identity service.
- [Read an agent setup](https://docs.ablative.com.au/lys/getting-started/agent-setup/): Understand the reviewed settings, machine and seat behind an agent start.
- [Concepts](https://docs.ablative.com.au/lys/concepts/): Understand who acts, what they may do and what the resulting records prove.
- [Identity](https://docs.ablative.com.au/lys/concepts/identity/): Separate a directory identity, a key and one execution of an agent.
- [Grants](https://docs.ablative.com.au/lys/concepts/grants/): Understand resource actions, delegation and the revision behind an access decision.
- [Runtime and sessions](https://docs.ablative.com.au/lys/concepts/runtime-and-sessions/): Understand profiles, seats, runners and the records of an agent execution.
- [Verifiable artifacts](https://docs.ablative.com.au/lys/concepts/verifiable-artifacts/): Understand the claims made by attestations, certificates and transparency proofs.
- [Secrets](https://docs.ablative.com.au/lys/concepts/secrets/): Keep private values behind their declared scope and distinguish permission from disclosure.
- [Operations](https://docs.ablative.com.au/lys/operations/): Resolve access problems, observe agent work and plan lifecycle changes with separate evidence.
- [Access and refusals](https://docs.ablative.com.au/lys/operations/access-and-refusals/): Use the server refusal to distinguish missing sign-in, a mismatched key and missing authority.
- [Monitoring](https://docs.ablative.com.au/lys/operations/monitoring/): Read health, session, usage and receipt evidence and follow changes through signals.
- [Installation lifecycle](https://docs.ablative.com.au/lys/operations/installation-lifecycle/): Inspect the installed deployment commands and their preconditions without changing the running service.
- [Reference](https://docs.ablative.com.au/lys/reference/): Look up the installed CLI, MCP tools, HTTP operations and artifact formats.
- [Command line](https://docs.ablative.com.au/lys/reference/cli/): All installed Lys CLI help entries, grouped by purpose, plus the version command.
- [MCP](https://docs.ablative.com.au/lys/reference/mcp/): The four MCP tools, remote plugin connection and signed local agent bridge.
- [HTTP operations](https://docs.ablative.com.au/lys/reference/http/): Look up Lys HTTP methods, paths and operation summaries by purpose.
- [Configuration](https://docs.ablative.com.au/lys/reference/configuration/): Distinguish deployment TOML from the running directory's rendered JSON and private files.
- [Wire formats](https://docs.ablative.com.au/lys/reference/wire-formats/): Understand frozen artifact encodings and the inputs required for independent verification.
- [Check your connection](https://docs.ablative.com.au/lys/reference/verification/): Distinguish the local CLI, public service health and the authority of an MCP connection.

## Liminal (unversioned)

- [Liminal](https://docs.ablative.com.au/liminal/): The rail network for agents: durable channels, services and links between liminals, every pass checked by Lys.
- [Getting started](https://docs.ablative.com.au/liminal/getting-started/): Install the binary, serve, hand an agent its first ticket, host an agent and build a service on a construction site.
- [Install and serve](https://docs.ablative.com.au/liminal/getting-started/install/): Install the binary from crates.io, validate a configuration, serve it and read the health page.
- [The first ticket](https://docs.ablative.com.au/liminal/getting-started/first-ticket/): Give Claude Code a seat on the network and call a service from it.
- [Host an agent](https://docs.ablative.com.au/liminal/getting-started/agent/): Run a coding agent as a station on the network, talk to it from the console's assistant panel and approve what it asks for in Lys.
- [Build a service](https://docs.ablative.com.au/liminal/getting-started/build-a-service/): Propose a construction site, bind a builder, follow its plan and approve the template that runs.
- [Concepts](https://docs.ablative.com.au/liminal/concepts/): The vocabulary of the network: stations, lines, links, passes, the topology, taps, and what is kept until when.
- [Stations and lines](https://docs.ablative.com.au/liminal/concepts/stations-and-lines/): A service is a station; the subjects it serves and the channels that carry messages are lines.
- [Links](https://docs.ablative.com.au/liminal/concepts/links/): Two liminals joined over an authenticated wire, exports named at configuration, every open checked by pass.
- [Passes and placement](https://docs.ablative.com.au/liminal/concepts/passes/): Lys issues the passes, places the subjects and decides every grant; liminal enforces and never decides.
- [Taps and the topology](https://docs.ablative.com.au/liminal/concepts/taps/): What the console draws, what a tap records, and the outcome of every call on a service.
- [What is kept](https://docs.ablative.com.au/liminal/concepts/durability/): Durable until delivered and acknowledged, then pruned. Liminal is not the system of record.
- [Reference](https://docs.ablative.com.au/liminal/reference/): The commands, the configuration, the ticket tools and their notification lines, and the health page.
- [Commands](https://docs.ablative.com.au/liminal/reference/cli/): The liminal binary: serve with a configuration, check one, serve the ticket, print the identity.
- [Configuration](https://docs.ablative.com.au/liminal/reference/configuration/): The server configuration and the seat configuration, section by section.
- [Ticket tools and lines](https://docs.ablative.com.au/liminal/reference/ticket-tools/): Every tool the ticket serves, grouped by what it does, and the shape of a notification line.
- [Health](https://docs.ablative.com.au/liminal/reference/health/): The health page: status, the ephemeral sweep and every link with its counters.
- [Operations](https://docs.ablative.com.au/liminal/operations/): Placement and grants in Lys, a link between two liminals, install and restart, and reading the logs and counters.
- [A link between two liminals](https://docs.ablative.com.au/liminal/operations/link-two-liminals/): Enrol both liminals in Lys, name each to the other, export a subject and prove the open on the health page.
- [Install and restart](https://docs.ablative.com.au/liminal/operations/install-and-restart/): Check the configuration with the new binary before stopping anything, restart, and prove the second boot.
- [Reading the logs](https://docs.ablative.com.au/liminal/operations/reading-the-logs/): The lines in the server log that answer the questions an operator asks first.
- [Design records](https://docs.ablative.com.au/liminal/design-records/): Where the briefs and the lane records live, and how to read them.

## Haematite (unversioned)

- [Haematite](https://docs.ablative.com.au/haematite/): A versioned record store with branches, checked queries, relations, vectors and configurable history retention.
- [Install and run](https://docs.ablative.com.au/haematite/getting-started/install/): Install the haematite command, create a store and start the service.
- [Write your first records](https://docs.ablative.com.au/haematite/getting-started/first-records/): Define a collection, write two records on the main branch and read them back.
- [Connect an agent](https://docs.ablative.com.au/haematite/getting-started/connect-an-agent/): Use the stdio or HTTP MCP server, the repository plugins or an installed bundle with the agent's own Lys proof.
- [Studio and the door](https://docs.ablative.com.au/haematite/getting-started/studio-and-the-door/): Serve Studio, sign in through Lys and use the store, query, graph, history and configuration areas.
- [Use the assistant](https://docs.ablative.com.au/haematite/getting-started/use-the-assistant/): Talk to your store's assistant from Studio, decide what it asks to change, and come back to earlier conversations.
- [Records, collections and versions](https://docs.ablative.com.au/haematite/concepts/records-collections-versions/): What a record is, how collections hold them, and why every write makes a new version instead of changing an old one.
- [Branches](https://docs.ablative.com.au/haematite/concepts/branches/): Fork a line of versions, write on it, review the difference and merge it back at the version the review read.
- [Reclaim](https://docs.ablative.com.au/haematite/concepts/reclaim/): How the vacuum finds versions nobody can reach and gives their space back, without ever deleting something still referenced.
- [The query pipeline](https://docs.ablative.com.au/haematite/concepts/query-pipeline/): A query is a chain of stages checked word by word before anything is read, so a wrong stage is refused by name instead of answered wrongly.
- [Sign-in and permissions](https://docs.ablative.com.au/haematite/concepts/sign-in-and-permissions/): Place a store behind Lys, grant access to its database and present each caller's own pass.
- [Relations and the graph](https://docs.ablative.com.au/haematite/concepts/relations-and-the-graph/): Declare relations, write and delete edges, and walk two directed hops through patients, wards and nurses.
- [History and time](https://docs.ablative.com.au/haematite/concepts/history-and-time/): Read retained versions, understand release policy and use the offline history and generation tools.
- [Query language](https://docs.ablative.com.au/haematite/query-language/): Short pipelines in jq's shape, checked before they run.
- [Served words](https://docs.ablative.com.au/haematite/query-language/stages/): Every word the query service accepts, generated from the service's own word table.
- [Reading records in](https://docs.ablative.com.au/haematite/query-language/sources/): The stages that bring records into a pipeline, and the shape that chooses fields.
- [Searching](https://docs.ablative.com.au/haematite/query-language/search/): Text search with rg and grep, meaning search with similar, and reordering a bounded set with rerank.
- [Finishing](https://docs.ablative.com.au/haematite/query-language/bounds/): Ordering, limiting and windowing a pipeline, and the stages that turn it into one answer.
- [Command line](https://docs.ablative.com.au/haematite/reference/cli/): Every subcommand of the haematite command, in the command's own words.
- [MCP tools](https://docs.ablative.com.au/haematite/reference/mcp-tools/): The eleven tools an agent sees over MCP, with the inputs each one needs.
- [Studio templates and actions](https://docs.ablative.com.au/haematite/reference/studio-templates-and-actions/): The places a document template may use, and the shape of an action declared on an object, as the Studio reads them.
- [Configuration](https://docs.ablative.com.au/haematite/reference/configuration/): Every service, door and HTTP MCP setting, with its type, default, limit and refusal.
- [Refusals](https://docs.ablative.com.au/haematite/reference/refusals/): Caller refusals, their meaning and the next act, grouped by where they are met.
- [Diagnostics](https://docs.ablative.com.au/haematite/reference/diagnostics/): Library and internal diagnostic names carried in a storage failure's cause.
- [Storage and vacuum](https://docs.ablative.com.au/haematite/operations/storage-and-vacuum/): Measure a store, read what is live and what is reclaimable, and sweep safely.
- [Install bundles](https://docs.ablative.com.au/haematite/operations/install-bundle/): Write a self-contained install bundle for a service, with the Lys schema checked before anything is written.
- [Backup, restore and migration](https://docs.ablative.com.au/haematite/operations/backup-restore-and-migration/): Copy a stopped store, verify the restored copy and distinguish chunking migration from opening a current store.

## Aion (0.31.0)

- [Aion](https://docs.ablative.com.au/aion/): Durable workflows in AWL or Gleam, with recorded history, remote activities and an operator console.
- [Install Aion](https://docs.ablative.com.au/aion/getting-started/install/): Install the public command, enable JWT support and distinguish the published release from main.
- [First workflow](https://docs.ablative.com.au/aion/getting-started/first-workflow/): Create a typed greeting workflow, verify its bytecode locally, start it and read its recorded outcome.
- [First Gleam workflow](https://docs.ablative.com.au/aion/getting-started/gleam/): Scaffold typed Gleam workflow code, build it and deploy its package.
- [AWL in your editor](https://docs.ablative.com.au/aion/getting-started/editors/): Configure the stdio language server, Zed extension or Neovim integration.
- [Workflows and runs](https://docs.ablative.com.au/aion/concepts/workflows-and-runs/): Understand execution identity, namespace scope, recorded status and worker queues.
- [Durability and replay](https://docs.ablative.com.au/aion/concepts/durability-and-replay/): Learn what history preserves and where activity idempotency is still required.
- [AWL](https://docs.ablative.com.au/aion/concepts/awl/): Understand the document families and the local check, compile and deploy loop.
- [Workers and SDKs](https://docs.ablative.com.au/aion/concepts/workers-and-sdks/): Choose the workflow authoring language and the worker or caller SDK for each process.
- [Signals, schedules and waits](https://docs.ablative.com.au/aion/concepts/signals-schedules-waits/): Distinguish a durable wait inside a run from a schedule that starts new runs.
- [The console](https://docs.ablative.com.au/aion/concepts/console/): Find authoring, launch, run history and operational views in the embedded console.
- [The assistant](https://docs.ablative.com.au/aion/concepts/assistant/): Use one ACP conversation with shared console context and explicit document edits.
- [Workloops](https://docs.ablative.com.au/aion/concepts/workloops/): Model continuing work with carried state, cadence, invariants and explicit retirement.
- [Command line](https://docs.ablative.com.au/aion/reference/cli/): Find every command in the installed Aion 0.31.0 command tree.
- [Server and store commands](https://docs.ablative.com.au/aion/reference/cli-server/): Captured help for the server launcher, local controls, update and offline store operations.
- [Authoring commands](https://docs.ablative.com.au/aion/reference/cli-authoring/): Captured help for project generation, AWL, bytecode packaging and deployment.
- [Worker commands](https://docs.ablative.com.au/aion/reference/cli-workers/): Captured help for supplied worker processes and managed worker control.
- [Run and routing commands](https://docs.ablative.com.au/aion/reference/cli-runs/): Captured help for every execution operation and loaded-package routing command.
- [MCP tools](https://docs.ablative.com.au/aion/reference/mcp-tools/): All fourteen public tools and three conversation tools, with links to their complete schemas.
- [Public MCP read schemas](https://docs.ablative.com.au/aion/reference/mcp-read-schemas/): Complete input and output schemas for public mcp read schemas.
- [Public MCP write schemas](https://docs.ablative.com.au/aion/reference/mcp-write-schemas/): Complete input and output schemas for public mcp write schemas.
- [Assistant conversation schemas](https://docs.ablative.com.au/aion/reference/mcp-assistant-schemas/): Complete input and output schemas for assistant conversation schemas.
- [AWL reference](https://docs.ablative.com.au/aion/reference/awl/): Find every AWL construct, word examples and the compiler boundaries.
- [AWL types and values](https://docs.ablative.com.au/aion/reference/awl-types/): All value forms, schema doors, constants and expression precedence.
- [AWL workers and placement](https://docs.ablative.com.au/aion/reference/awl-workers/): Action contracts, delivery policy, declared bodies, harnesses and relative node selection.
- [AWL steps and decisions](https://docs.ablative.com.au/aion/reference/awl-steps/): Step dependencies, expressions, guards, terminal routes and list pipelines.
- [AWL parallel work and loops](https://docs.ablative.com.au/aion/reference/awl-parallel/): Fork/join, multi-step regions, tolerant collection and bounded iteration.
- [AWL children, waits and failure](https://docs.ablative.com.au/aion/reference/awl-waits/): Child and subflow contracts, durable waits, sleeps and failure handlers.
- [AWL signals and queries](https://docs.ablative.com.au/aion/reference/awl-queries/): Declare sent and received signals and expose typed live query answers.
- [AWL commands](https://docs.ablative.com.au/aion/reference/awl-commands/): Declared command syntax, arguments, capture, working directories and exports.
- [AWL recipes, walls and artifacts](https://docs.ablative.com.au/aion/reference/awl-recipes/): Assembly parameters, dependency steps, artifact digests, preconditions and execution receipts.
- [AWL workloops](https://docs.ablative.com.au/aion/reference/awl-workloops/): Every workloop word, cadence, state, invariant, detached-start and retirement form.
- [AWL roles and bindings](https://docs.ablative.com.au/aion/reference/awl-bindings/): Compose portable role contracts with venue queues and harness settings at deploy time.
- [Configuration](https://docs.ablative.com.au/aion/reference/configuration/): Configuration discovery, starter settings and the complete field references.
- [Engine and storage settings](https://docs.ablative.com.au/aion/reference/configuration-engine/): Every engine and storage settings field served by the server configuration types.
- [Access and authoring settings](https://docs.ablative.com.au/aion/reference/configuration-access/): Every access and authoring settings field served by the server configuration types.
- [Worker and stream settings](https://docs.ablative.com.au/aion/reference/configuration-workers/): Every worker and stream settings field served by the server configuration types.
- [Environment variables](https://docs.ablative.com.au/aion/reference/environment/): Every server override from the current allowlist and the separate CLI and worker settings.
- [HTTP, gRPC and event streams](https://docs.ablative.com.au/aion/reference/api/): Find the server transport families, payload forms, cursors and route gates.
- [Operational HTTP API](https://docs.ablative.com.au/aion/reference/http-operations/): Inspect dead letters, unserved queues, failed recovery and releases; drain or stop workers.
- [Workflow packages](https://docs.ablative.com.au/aion/reference/packages/): Understand workflow.toml, archive contents, content-hash versions and immutable module names.
- [Worker deployment HTTP API](https://docs.ablative.com.au/aion/reference/http-worker-deployments/): Create, read, replace and remove durable builtin worker deployments.
- [Gleam aion_flow SDK](https://docs.ablative.com.au/aion/reference/gleam-sdk/): Find typed workflow, activity, codec, signal, query, child and testing APIs.
- [Gleam workflow API](https://docs.ablative.com.au/aion/reference/gleam-workflow-api/): Read every public workflow function signature and its execution rules.
- [Gleam activity API](https://docs.ablative.com.au/aion/reference/gleam-activity-api/): Read typed activity construction, policies, routing, introspection and contract declarations.
- [Gleam supporting APIs](https://docs.ablative.com.au/aion/reference/gleam-support-api/): Read codecs, signals, queries, children, durations, typed errors and workflow test helpers.
- [Python SDKs](https://docs.ablative.com.au/aion/reference/python-sdks/): Install the local caller and worker packages, start workflows and serve typed activities.
- [TypeScript SDKs](https://docs.ablative.com.au/aion/reference/typescript-sdks/): Read workflows through the TypeScript HTTP caller and serve gRPC activities, with current transport limits.
- [Releases and public resources](https://docs.ablative.com.au/aion/reference/sources/): Find public packages and understand which features require an authorized main build.
- [Running the server](https://docs.ablative.com.au/aion/operations/running-server/): Choose the active configuration, read build and readiness evidence and shut down deliberately.
- [Set up a cluster](https://docs.ablative.com.au/aion/operations/cluster/): Configure three Haematite-backed nodes with explicit membership, shards and peer addresses.
- [Create namespaces](https://docs.ablative.com.au/aion/operations/namespaces/): Create a durable namespace explicitly when automatic creation is closed.
- [Auth and Lys](https://docs.ablative.com.au/aion/operations/auth-and-lys/): Choose Lys passes or JWT validation and protect each transport with the correct grants.
- [Upgrading](https://docs.ablative.com.au/aion/operations/upgrading/): Install and hand over deliberately, preserving store-layout and config-migration evidence.
- [Backups and restore](https://docs.ablative.com.au/aion/operations/backups/): Preserve a consistent stopped store, configuration, packages and authoring source.
- [Deploying and routing](https://docs.ablative.com.au/aion/operations/deploying/): Deploy immutable versions, read batch receipts and route new starts deliberately.
- [Operating workers](https://docs.ablative.com.au/aion/operations/workers/): Serve document-defined work, inspect admission and commission managed supervision.
- [Cancel and steer an activity](https://docs.ablative.com.au/aion/operations/activity-control/): Use worker cancellation and capability-gated agent intervention with the full attempt identity.
- [Run Norn activities](https://docs.ablative.com.au/aion/operations/norn/): Configure a declared Norn harness and serve its queue through an agent worker.
- [Operating schedules](https://docs.ablative.com.au/aion/operations/schedules/): Create, replace, pause, resume, read and delete namespace-owned schedules through the API.
- [Troubleshooting](https://docs.ablative.com.au/aion/operations/troubleshooting/): Read refusals and recorded evidence without losing the failure to a reflex restart.

## Cambium (0.1.0)

- [Cambium](https://docs.ablative.com.au/cambium/): Messaging, project work and shared records for people and agents.
- [Plugins](https://docs.ablative.com.au/cambium/plugin/): Install the Cambium plugin in Claude Code or Codex and connect an enrolled seat.
- [Getting started](https://docs.ablative.com.au/cambium/getting-started/): Find the running service, check its installed command and connect a private agent seat.
- [Open Cambium](https://docs.ablative.com.au/cambium/getting-started/open-cambium/): Connect to an existing service and understand what sign-in and readiness each prove.
- [Connect an agent seat](https://docs.ablative.com.au/cambium/getting-started/agent-seat/): Attach the installed MCP server using an existing enrolled seat file.
- [Concepts](https://docs.ablative.com.au/cambium/concepts/): Understand the records and relationships behind conversations and project work.
- [Conversations](https://docs.ablative.com.au/cambium/concepts/conversations/): Understand posts, threads, mentions and the difference between reading and acknowledgement.
- [Projects and fields](https://docs.ablative.com.au/cambium/concepts/projects-and-fields/): Read the item tree, stable field declarations and task lifecycle separately from board display.
- [Workflow connections](https://docs.ablative.com.au/cambium/concepts/workflow-connections/): Connect project fields to workflow inputs and outputs and read each run as evidence.
- [Shared records](https://docs.ablative.com.au/cambium/concepts/shared-records/): Use notes, canvases, files, events and huddles as records beside the conversation.
- [Operations](https://docs.ablative.com.au/cambium/operations/): Operate an existing installation using configuration checks, named refusals and recovery records.
- [Configuration](https://docs.ablative.com.au/cambium/operations/configuration/): Understand the TOML configuration, required identity values and the boot-plan check.
- [Access and refusals](https://docs.ablative.com.au/cambium/operations/access-and-refusals/): Preserve the exact resource, action and state named by a refused operation.
- [Notifications](https://docs.ablative.com.au/cambium/operations/notifications/): Receive live changes and distinguish a wake from acknowledgement of the underlying work.
- [Backup and recovery](https://docs.ablative.com.au/cambium/operations/backup-and-recovery/): Understand the stopped-store backup contract and preserve the identity material needed for restore.
- [Reference](https://docs.ablative.com.au/cambium/reference/): Look up installed command shapes, MCP tools, record vocabulary and connection checks.
- [Command line](https://docs.ablative.com.au/cambium/reference/cli/): Inspect the installed Cambium server and its sibling MCP executable.
- [MCP tools](https://docs.ablative.com.au/cambium/reference/mcp-tools/): All 26 tools returned by the installed Cambium MCP server.
- [Record vocabulary](https://docs.ablative.com.au/cambium/reference/records/): The objects shared by conversations, projects and attached records.
- [Check your installation](https://docs.ablative.com.au/cambium/reference/verification/): Distinguish the installed executable, MCP preflight and workspace admission.