- Manifest
- Identity, version, compatibility and metadata
- Integrity
- Signature binds content and material metadata
- Concurrency
- Instance lock prevents overlapping installation
- Journal
- Authenticated lifecycle and recovery evidence
- Failure
- Restore prior files or enter degraded state
- Rollback
- Return to identified prior product version
A governed registry for AVC products.
Versions, signatures, compatibility, install state and rollback boundaries remain explicit.
A package becomes an active product only after every boundary passes.
Failure leaves a recoverable journal rather than an optimistic success record.
- Catalog identitypassed
Resolve product, version and declared capabilities.
- Signature and integritypassed
Verify content plus material metadata against the trusted signer.
- Compatibility reviewactive
Check runtime, schema and capability compatibility.
- Atomic install or updatepending
Acquire instance lock and journal the transition.
- Health and rollbackpending
Promote only after health; restore the prior version on failure.
The Product Catalog records versioned, installable product identity.
Product metadata, capabilities, compatibility and package integrity are reviewed before an instance may be created or updated.
Install and update preserve a recoverable prior state.
Instance locks, journals, atomic begin/commit behavior and rollback keep interrupted operations from becoming ambiguous half-installs.
A signature binds both content and material metadata.
Integrity evidence cannot be preserved while silently extending expiry, compatibility or authority-bearing metadata.