Overview

Specifications are the normative reference for Gas City’s file formats and contracts: what the system accepts, what it does with it, and which behavior you can rely on. Each spec follows the same register — a status header table, normative keywords, numbered sections, and an “accepted but inert” section for surface the format parses but no runtime consumes. When a spec and any other page disagree, the spec wins; when a spec and the code disagree, the code wins and the spec has a bug.

Specification	Covers
Gas City Pack Specification	Pack format and loading semantics: directory layout, `pack.toml`, imports, patches, layers
Formula Specification — v1	The formulas v1 contract: file format and container semantics — the default when a formula declares nothing; molecule/wisp are the v1 materialization mechanism it compiles a formula into
Formula Specification — v2	The formulas v2 contract: file format, graph compilation, and the orchestrator-executed runtime constructs
Service Protocol — v0	The generic hosted-service wire protocol: how `gc login` authenticates to any conforming Gas City service (opaque bearer, well-known paths); `gascity.com` is only the default endpoint
Identity Separator Contract — v1	The qualified-identity encoding shared by gascity and beads: the two-axis separator table (`/`↔`--`, `.`↔`__`), and which side mints identities versus which side only compares them

New specifications land in this section. For the reasoning register — how to think about packs and formulas rather than what is normative — see the guides. For the canonical model these specs are normative over — the six primitives (Agent, Bead, Formula, Rig, Pack, Event) — start with How Gas City Works.

Getting Started

Tutorials

Guides

Troubleshooting

Reference