---
title: "Glossary"
summary: "The vocabulary a caller meets in LatticeKit's APIs and documentation, defined in one place — the terms whose meanings are specific to this platform rather than generic."
---

# Glossary

Terms whose meaning here is specific rather than generic. Broad orientation is in
[what LatticeKit is](what-is-latticekit.md).

**Access rule** — a condition deciding whether a person may do something: enter a door,
book a particular offer, use a particular resource. Written as an [expression](expressions.md)
and evaluated fail-safe.

**Attendance** — the record that a person actually turned up for a booking, recorded per
person rather than per booking. What makes class registers and no-show policies work.

**Audience** — a set of people defined by a condition rather than by a list, so
membership is recomputed rather than maintained.

**Availability** — when an [offer](#offer) can be taken. Comes in five shapes: grid,
range, queue, open capacity, and external. See [scheduling](scheduling.md).

**Booking** — one reservation of an offer, moving through a lifecycle from pending to
confirmed to completed or cancelled.

**Bundle** — a whole business's configuration as one portable document. See
[tenant as code](tenant-as-code.md).

**Capability** — one named, typed action the platform can perform. What is exposed to a
given caller is declared rather than inferred, and hidden by default.

**Consent** — a person's recorded permission to be contacted a particular way.
Communications are checked against it and refused when it is absent, rather than sent and
apologised for.

**Grant** — the record an AI client's access hangs off: which business, which scopes,
which location, whether sandboxed. Revoking it stops the client. See
[agent API](agent-api.md).

**Group** — the universal "this person belongs to something" model. A household, a
membership tier, a staff roster and a team are all groups.

**Hold** — an exclusive, expiring claim on a resource. What makes concurrent booking safe:
two customers racing for the last court produce one booking and one clear failure.

**Idempotency key** — a caller-supplied value making a retried write safe. A repeated key
returns the original outcome rather than acting twice. See [errors](errors.md).

**Obligation** — something a booking owes before it can confirm: a deposit, a signed
waiver, a completed form. Tracked separately so a booking can say what it is waiting on.

**Offer** — something a customer can book or buy, plus its terms: duration, requirements,
deposit, cancellation policy.

**Order** — a live tab or cart. Opens, accumulates lines, is fired, and closes — and
closing is what produces the invoice, the ledger entries and the receipt.

**Plan** — the difference between a bundle and what is live, produced without writing
anything, and pinnable so that what was approved is what gets applied.

**Problem document** — the machine-readable shape every error takes. See
[errors](errors.md).

**Proposal** — a consequential action an agent has asked for but cannot perform. Waits
for a human decision.

**Remediation** — a structured hint on a failure naming the concrete next step, so a
program has something to do other than guess.

**Resource** — a physical thing that can be committed: a court, a room, a chair, a unit
of stock.

**Scenario** — a run against the real configuration with every side effect neutralised,
returning a structured verdict. How a configuration change proves itself.

**Scheme** — the recurring shape of a week plus its exceptions, from which grid
availability is generated.

**Sandbox** — a posture in which configuration is real but side effects are neutralised
and captured. Can be forced by a grant, and cannot be switched off by a request.

**Stored value** — a balance a customer holds: a gift card, an account credit, a loyalty
wallet. Moves through the ledger like anything else.

**Sub-tenant** — a location or business unit within a business. See [tenancy](tenancy.md).

**Tenant** — one business. The boundary nothing crosses.