Build glossary

The words a contributor meets that a user never does. The user's words are in the user glossary; a word in neither is not allowed in a page, a flag or a message.

core — packages/world-core, @volter/world-core: the state kernel and shared runtime libraries. One entry model, checkpoints, parent-position branches and head execution; vendor semantics stay in the packages. See architecture.

kernel — packages/world-*: the runtime (world-runtime), the remote (twins-host), the dev-only tooling, the shared UI assets. Vendor-agnostic; few writers; kernel process.

pack — a twin's package as the build sees it: packages/twin/<vendor>/, born from scaffold-pack.ts, driven by the recipe, admitted by §9. A user says twin, or package.

catalog — every pack, as packages/twin/* in this checkout or as the installed @volter/twin-* packages in an app.

census — a pack's record of what it serves against the vendor's published spec: the source of the coverage percentage. spec-refresh, spec-census-record, spec-census-probe keep it current; the run date is the package's last verified.

ladder — the ranked roster of real application repositories measured against the catalog (generated/ladder.json); the build queue is derived from its uncovered vendors.

dossier — what the line gathers about a vendor before a pack is built: its spec, its SDK, its hosts.

line — the pack-build pipeline: line.ts, spec-dossier.ts, spec-compile.ts, sdk-compile.ts, scaffold-pack.ts, pack-shape-check.ts, merge-check.ts, land.ts.

§9 — the mandatory adversarial review every pack passes before it lands.

T0, T1, T2 — the verification tiers: a pack's own gate; the kernel suites and typecheck; the whole catalog. See gates.

door — an HTTP endpoint a twin or a remote serves beside the vendor's API. A user reads "HTTP API".

backing — which of local and remote stands behind a vendor on a remote. A user reads local and remote as nouns.

shape — a vendor's wire, as the code names it. A user reads "the vendor's API".

placeholder — the default data's origin, as the code names it (PLACEHOLDER_REMOTE, placeholder-pull). A user reads "default data".

observed — vendor state admitted through observeResource into a root’s log; default seeding supplies inherited state through the seed window.

landing — an entry added to the parent with a receipt; its branch copy is not applied twice.

admission — the reservation of memory and disk up makes before starting; refused by name.

instance — the running world's record: instance.json and the directory around it.

manifest (world) — the document a world publishes for attachments: vendors, CA, proxy, env. manifest (capability) — a pack's enumeration of the vendor's surface with a verify() per capability; the completeness number's denominator. manifest (pack) — a derived pack's src/manifest.ts: its descriptor, the vendor facts no spec carries, and the surfaces outside the spec.

derived pack — a pack with src/manifest.ts and src/generated/: its wire, schemas, generic CRUD, perform, refresh and coverage are generated from the vendor's spec; only its semantics are hand-written.

semantics — a derived pack's hand-written behaviour: state machines as data and handlers by operationId. Write semantics run wherever the head does not perform a write now; read semantics run under every head.

cell — a value of a state field paired with an operation on its resource; the unit a derived pack's completion is counted in.

attestation — a signed judgment (a journey's plausibility, a transition's source, a ruling on a cell, a review), keyed by the hash of what it depends on and stale when that changes.

attachment — applying a world's vendor map to one consumer. A user reads run, activate, shell.

narration — a changeset's generated summary, as the code names it. A user reads "summary".

basis — a change’s recorded assumptions, as compatibility code names them. A user reads "base" for the branch’s parent position.

sealed — the mode a user reads as "sandbox"; also a credential at rest on the remote.

recipe (cookbook) — a runnable example, as the cookbook's tooling names it. A user reads "example". recipe (the twin recipe) — adding a twin.

skin — the composed front a remote presents: one URL, every twin a path.

R-numbers (R2a, R14, …) — identifiers retained in the invariant runners and older design records. Current implementation rules live in architecture, and unresolved work lives in the roadmap.

history descriptor — an immutable view's verified segment ranges, storage generations and projection layout. The descriptor's content hash identifies it; its dependencies participate in World cleanup. Local views share payloads; a remote cache deduplicates complete entry contents.