Jira progress: loading…

ZAMG-ZCP

ZCP + ZAMG within the ZAR Framework

This document set explains how ZAYAZ governs executable artifacts, operations, routing, and manifest generation inside the ZAR framework.

Purpose

The ZAR framework is the canonical registry backbone for artifact identity, signal identity, routing context, and related metadata. The ZAYAZ Command Protocol (ZCP) and The ZAYAZ Artifact Manifests Generator (ZAMG) do not replace ZAR. They operate within it.

• ZAR provides canonical identities and registry-backed metadata.
• ZCP provides the internal command protocol for governed execution.
• ZAMG generates compiled canonical artifact manifests from ZAR-backed data, source metadata, deterministic rules, and controlled AI assistance.
• ZSSR validates and routes execution based on approved contracts, rulesets, and policy.

Reading order

1. ZCP Overview
2. ZAMG Overview
3. ZAR-native CMI/CSI Model
4. Canonical Manifest Schema
5. Deterministic Resolution Rules
6. Opcode Registry and Artifact Templates
7. Resolution Pipeline
8. Review and Approval Policy

Core principles

• Developers should work in one system, not two.
• CMI and CSI remain canonical in ZAR.
• ZCP expresses executable intent.
• Rulesets govern execution behavior.
• ZAMG compiles manifests from ZAR-backed identities and metadata.
• Only approved canonical manifests may drive production routing.

Key definitions

• CMI — Canonical Module Identifier for an artifact.
• CSI — Canonical Signal Identifier for a signal contract.
• ZCP — ZAYAZ Command Protocol.
• ZAMG — ZAYAZ Artifact Manifest Generator.
• ZSSR — Routing and validation gate.
• Ruleset — Versioned execution logic and policy envelope.

---