Skip to main content
Jira progress: loading…

ZAMG-REW

ZAMG Review and Approval Policy

Generated manifests do not all receive the same approval treatment.

Approval depends on:

  • field criticality
  • confidence
  • change class
  • compliance sensitivity
  • external exposure impact

Approval states​

  • draft_candidate
  • review_required
  • approved_canonical
  • rejected
  • quarantined_candidate
  • deprecated
  • superseded

Approval classes​

  • Class A — auto-approvable
  • Class B — reviewer approval required
  • Class C — governance approval required
  • Class D — reject or quarantine

Critical fields​

Examples:

  • artifact.cmi
  • artifact.artifact_type
  • operations[*].opcode
  • operations[*].input.csi
  • operations[*].output.csi
  • operations[*].routing.ruleset_cmi

Core rule​

Critical-field ambiguity outranks overall confidence score.

Evidence model​

All review and approval decisions should be stored as structured evidence in ZAR-backed approval tables or equivalent audit structures.



GitHub RepoRequest for Change (RFC)