Jira progress: loading…

OPCODE

Opcode Registry and Artifact Templates

Two registries make ZAMG scalable:

• Opcode Registry
• Artifact Type Template Registry

Opcode Registry

The opcode registry defines semantic operation meanings.

Examples:

• OP_0400 → compute_metric
• OP_0300 → validate_signal
• OP_0510 → dispatch_workflow
• OP_0610 → export_xbrl

Artifact Type Template Registry

Artifact templates define defaults for classes such as:

• micro_engine
• validator
• exporter
• workflow_dispatcher

These defaults cover:

• domain
• routing mode
• trust thresholds
• audit requirement
• retention class
• allowed opcode families

Why opcodes do not replace rulesets

Opcodes define intent.
Rulesets define governed execution logic.

This separation avoids opcode explosion and keeps operations reusable across frameworks, geographies, and trust profiles.

---