Reference
Object reference
The operator-facing first-class objects and the substrate objects beneath
them, condensed from the canonical object specifications (OBJ-1.7). Every
authored object carries a stable id and a content hash; a version is
immutable once recorded; activation moves a pointer.
| # |
Object |
What it is |
Lifecycle |
| 1 |
Capability |
The unit of customer invocation and of publication; composes Actions and Recipes. |
inline → promoted → evaluated → published → deprecated → sunset |
| 2 |
Configuration |
A typed parameter set an Action needs: Prompt, Knowledge (with Documents), Tool Binding, Memory Scope, Review Policy. Reusable across Capabilities. |
inline → promoted → published → archived |
| 3 |
Action |
One step in a composition, bound to one primitive and its Configurations. |
shares its composition's lifecycle |
| 4 |
Recipe |
A reusable, published sub-composition of Actions. |
draft → published |
| 5 |
Solution |
The sold package: one client tenant, Capability references pinned to versions, per-client configuration. |
ACTIVE → SUSPENDED → RETIRED (retired rows persist) |
| 6 |
Example |
A recorded input/output pair used for authoring and testing. |
— |
| 7 |
Test Set |
Versioned, hashed cases run against a Capability version; produces Evidence. |
versioned |
| 8 |
Customer |
The client organisation (the tenant, in operator vocabulary). |
active / suspended |
| 9 |
Subscription |
The commercial relationship; independent of Entitlement. |
Stripe-backed states |
| 10 |
Credential |
Hashed API identity issued to a Customer; rotatable with a grace window; revocable. |
ACTIVE → ROTATED → REVOKED |
| 11 |
Run |
One invocation of a Capability; composed of Node Runs. |
running → completed / waiting / failed |
| 12 |
Review |
A paused Run awaiting a human decision; the decision (with optional edit) resumes it. |
requested → decided |
| # |
Object |
What it is |
| 13 |
Grant |
(platformSourceId, capabilityId): explicit, ledgered permission to retrieve from a platform-owned source. |
| 14 |
Usage Event |
Append-only, correlation-keyed record of a Capability invocation for metering. |
| 15 |
Audit Ledger Entry |
Append-only, actor- and correlation-stamped record of an architecturally meaningful change. |
| 16 |
Run Cost Record |
Append-only record of what a Run used, when, at what rate; corrections are new rows. |
- Ids are lowercase ASCII matching
^[a-z][a-z0-9._-]{0,127}$.
- Operator-facing version = an integer per publication. Substrate version =
a content hash. Republishing identical content is idempotent and returns
the existing version.
- Inline Configurations within a composition are content-hash
deduplicated; anonymous Configurations are archived, never deleted, when
their parent is sunset, and remain readable for replay.
- A Capability version locked into a published Solution version remains
replayable while that Solution version exists.
- Capability publication is a substrate transaction whose atomic commit is
the Workflow Pointer's conditional write; failure before it leaves
idempotent partial substrate, and retry resumes from the failed step.
documentId is stable across re-ingest; versionId is a per-upload
content hash and changes on every content change.- Lifecycle:
uploaded → ingested → available → deletion_requested → tombstoned → purged | retained_metadata_only.
- Tombstoned entries are excluded from retrieval on every query; audit
entries keep
documentId and versionId even after bytes are purged.
matterandgas-com/docs/architecture/object-specifications.md (OBJ-1.7).matterandgas-com/docs/architecture/architectural-truths-v1.md §5 —
the classification of every operator-visible concept.