Interface and architecture map

Use this map to move from a user-facing interface to its owning contract and the mechanisms underneath it. The interface chooser compares entry points; the component directory identifies the libraries and executables that implement them. Each linked reference states its supported operations, types, configuration and failure behavior.

Public entry points

Start with data, computation and policies to choose the data representation, computation lifetime and observations you need. The interfaces below expose different portions of that lifecycle through shared owners.

Interface	Usage and limits	Exact owner or description	Mechanisms
Local supervisor and console	CLI, configuration, console	Installation, configuration	Execution and recovery, service sessions
Native SQL HTTP/TLS and Unix sessions	SQL sessions, statements	SQL session contract	Service interfaces, query engine
PostgreSQL and MySQL	Database protocols, local login	Wire adaptation	Service interfaces
Application language SDKs	SDKs, caller semantics, examples	Station ABI, native protocol	Client/framework boundary
Signed native HTTP	Native protocol, permissions	HTTP carriage, native operations	System model, execution
Original-subject Table mediation	Tables, Table service	Declarative catalog, messages	State model, query engine
Application HTTP publication	Serving, OpenAPI	Serving contract	Service interfaces
SSE and WebSocket	Reactive sessions, AsyncAPI	Reactive contract	Service interfaces
Board and operator inspection	Board guide, Board OpenAPI	Board schema	Observed state and authority
Arrow IPC/C, Flight SQL and ADBC	Arrow, Flight compatibility	Flight contract, query contract	Query engine
Outbound HTTP, gRPC and Flight	Connectors	HTTP effects, gRPC effects, Flight effects	Effect lifecycle

SQL HTTP, signed native HTTP, application Serving and Board are different interfaces with different authentication and ownership. A native SQL session handle does not authenticate a Board or Serving request. A transport's ability to encode a type does not establish query execution support for that type.

Runtime foundations

Subject	Current behavior	Technical account
Ownership, fencing, process turns and delivery	Processes, streams	System model, execution model
Grants, credentials and resource lifetime	Security, retention	Execution model, state model
KV, Tables, Documents and associations	State, Tables, Documents	State model
Station calls, supervision and host boundaries	Station, callers	Client/framework boundary
Planning, snapshots, typed batches and result publication	Queries, SQL types, Arrow	Query engine
Page storage, immutable bulk data, concurrency and cleanup	Storage, retention	Storage runtime
Installation, replacement and physical deployment	Applications, deployment	Execution model
Logs, metrics, diagnostics and measured cost	Observability, performance, benchmarks	Verification method, storage runtime

Compatibility and evidence

Contract downloads provides machine-readable descriptions from their authoritative sources. Versioning explains why a v1 name alone does not establish compatibility between builds. Verification limits separates current guarantees from the scope of executed checks; the repository's proof ledger owns those execution records.

The handbook documents the checked-out source revision. References and guides describe use; Internals explains models, invariants, tradeoffs and evidence. Neither a published page nor a successful documentation build certifies a new runtime profile. Component API guides remain beside their implementations and are included or linked from these owners.