Jira progress: loading…
ZAMG
ZAMG Overview
ZAMG is the ZAYAZ Artifact Manifest Generator.
It generates canonical artifact manifests for executable and governable artifacts inside the ZAR framework.
Why ZAMG exists
Without ZAMG, teams would end up manually maintaining:
- documentation metadata
- API exposure metadata
- routing metadata
- opcode bindings
- manifest structure
- policy defaults
That creates duplication and drift.
ZAMG avoids this by compiling manifests from:
- source metadata
- code metadata
- ZAR-backed registries
- deterministic rules
- controlled AI suggestions where ambiguity exists
Core principle
Humans describe the artifact once.
The platform resolves, enriches, validates, and compiles the canonical manifest.
What ZAMG produces
ZAMG produces a compiled artifact contract used by:
- ZAR operational tables
- ZCP operation binding
- ZSSR routing validation
- docs generation
- future OpenAPI/SDK projections
ZAR-native architecture
ZAMG is not a parallel registry system.
It is a compiler inside the ZAR framework that resolves:
- CMI from
zar.cmi_registry - CSI from
zar.signal_csi_binding - component and module topology from existing ZAR tables
- candidate and proposal states from proposal/result tables
Output
Approved canonical manifests are stored in zar.artifact_manifest_registry.