Glossary

Definitions of the core Amira platform terms used across these docs.

The terms you'll meet across the platform and this documentation. Where a term has a dedicated guide, its name links to it.

Agents#

Spec Agent — interviews you and produces a builder-ready specification (requirements, acceptance criteria, capability graph, gaps, decisions).
Build Agent — writes the application from an approved spec in a sandbox, wiring in the skills and data sources the spec references.
Deploy Agent — promotes a built application to a running URL, behind an approval gate.
Companion Agent — the agent every deployed app gets, so other apps and people can call it as a reusable capability.

Functional requirement (FR) — something the app must do.
Non-functional requirement (NFR) — a quality the app must have (performance, security, availability…).
Acceptance criterion (AC) — a measurable, testable condition that proves a requirement is met.
Capability graph — the structured map of the app's components and how they depend on one another, built alongside the requirements.
Gap — something the agent needs from you to finish a requirement. A critical gap blocks lock until answered; a config gap gets a sensible default and is flagged "confirm at build."
Decision point — a fork where you choose between options the agent lays out.
Readiness — the live view of whether the spec is complete: requirements specified, criteria measurable, no critical gaps open.

Lock / Route for E-Signature — freezing the spec's content into an immutable version and creating an approval request; the spec can no longer be edited in place.
Authorized Approver — the person permitted to approve (e-sign) a specification or a deployment.
Separation of duties — the default policy in team workspaces where the spec's author cannot sign their own spec; a different Authorized Approver must.
Audit ledger — the append-only record of who signed which immutable version, and when.

Skill — a reusable capability (data source, tool, or service) a spec can reference by name and the Build Agent wires in.
Knowledge base — files you attach to a spec (policies, schemas, docs) that the Spec Agent reads and grounds requirements in.
Compliance matrix — the scorecard that tracks a built application against its spec's acceptance criteria.