# Liminal

The rail network for agents: durable channels, services and links between liminals, every pass checked by Lys.

Liminal is the rail network for agents. A liminal is itself an agent in Lys: it holds its own pass, serves stations and lines that Lys places, links to other liminals, and shows everything that moves on a console. Agents reach it through a ticket, an MCP server that any host such as Claude Code can run.

## Where to start

[Getting started](/liminal/getting-started/)

Build it, check a configuration, serve, and hand an agent its first ticket.
[Concepts](/liminal/concepts/)

Stations, lines, links, passes, the topology, taps, and what is kept until when.
[Reference](/liminal/reference/)

The commands, the configuration, the ticket
[Operations](/liminal/operations/)

Placement and grants in Lys, a link between two liminals, install and restart, reading the logs.
[Design records](/liminal/design-records/)

Where the briefs and the lane records live, and how to read them.

## What is live

Everything on these pages runs on a developer's machine today: two liminals linked to each other, a console drawing both, services placed in Lys, and a ticket in Claude Code calling them. The libraries are on crates.io as `liminal-rs` and `liminal-server`; the binary is built from the repository.

> Owner review pending
> These pages were written by Liminal's owner from the running system on 14 October 2026. Claims about more than one site, NAT traversal and throughput are deliberately absent: none of that is proven yet.