Jira progress: loading…

ZAR-CCIM

ZAR-native CMI and CSI Model

CMI and CSI are canonical ZAR-native identities. ZAMG and ZCP consume them. They do not replace them.

CMI source of truth

The canonical artifact identity source is:

• zar.cmi_registry

Key fields include:

• cmi
• module_code
• component_id
• cmi_kind
• artifact_name
• version_*
• zar_code
• runtime_class
• semantic_role
• status
• lifecycle_status

CSI source of truth

The canonical signal identity source is:

• zar.signal_csi_binding

Key fields include:

• signal_id
• csi_module
• csi_component
• csi_kind
• csi_name
• csi
• status

Resolution model

CMI

ZAMG should:

1. attempt exact resolution against zar.cmi_registry
2. fall back to deterministic proposal generation
3. write proposal-stage candidates where no approved match exists

CSI

ZAMG should:

1. resolve signal_id
2. join to zar.signal_csi_binding
3. prefer stable or approved statuses
4. flag ambiguity or missing mappings for review

Status guidance

For production use:

• CMI should normally be active
• CSI should normally be stable or explicitly approved experimental

Draft or deprecated identities should not be auto-promoted into production contracts.

---