Glossary

Active release
The immutable release currently receiving production traffic.

Actor
A human, system, external participant, or explicit anonymous persona that invokes or observes product behavior.

Add-on
A versioned prefab capability such as authentication, notifications, file upload, or audit trail.

Aggregate
A domain consistency boundary changed through its root and modeled actions.

Area
A product-facing grouping of a business capability, connected to subdomain and bounded-context structure.

Authority
The single owner of a particular kind of intent or state.

Candidate
A built release under isolated verification that does not yet receive active traffic.

Command
An actor or system’s intent to change state.

Configuration manifest
The non-secret declaration of runtime values a release requires.

Deterministic generator
A versioned compiler that produces semantically equivalent managed output from the same declared inputs.

Divergence
A mismatch between expected and observed managed files, schema, configuration contract, or release state.

Domain event
A past-tense fact emitted after successful domain behavior.

Evolution bundle
The versioned physical schema and migration history used to plan a later revision.

Evolutionary Model
A living, structured, versioned, and validatable representation of product intent.

Extension
User-owned code behind a stable contract that the generator never overwrites.

Fork
Exported generated code that the user chooses to evolve directly outside the regenerative contract.

Generated/managed code
Implementation owned by the generator and replaceable during regeneration.

Migration
An explicit, ordered transition of physical schema or stored values.

Model revision
An immutable accepted snapshot of product intent linked to its parent.

Preview
An ephemeral executable candidate environment used for validation.

Projection
A derived view of the model, such as canvas, Gherkin, application code, preview, MODEL.md, or DESIGN.md.

Promotion
The controlled transition that makes a verified candidate receive traffic.

Query
A modeled read question with sources, filters, sorting, permissions, and scope.

Reaction
An event-driven effect that executes another modeled command.

Reconciliation
Comparison of desired and observed operational state followed by repair or explicit divergence reporting.

Regeneration
Compilation of a model revision with a generator version into managed artifacts.

Regenerative Software
Software whose managed implementation remains reproducible from versioned intent and declared generation/evolution inputs.

Release ledger
The durable record linking revision, generator, artifacts, migrations, evidence, channel, and promotion state.

Rollback
A compatibility-aware traffic or release recovery action; not automatic reversal of data history.

SCM
Semantic Capture Model, the internal structured representation used by modelARch for the Evolutionary Model.

Scope
A row-level restriction applied within an actor’s permission to invoke a command or query.

Surface
A distinct application host or experience boundary serving selected personas.