Jira progress: loading…

ZAR-TBLS

ZAYAZ Artifact Registry Framework Tables

1. Introduction

The ZAR tables is not registered in the SSSR overview, but is itself a part of SSSR.

2. List of Tables

Schema	Name	Type	Owner	Persistence	Access method	Size	Description
zar	api_route_binding_registry	table	zar_admin	permanent	heap	16 kB	Canonical registry of API route bindings that map external or internal API requests to ZCP semantic execution intent, including operation_key, opcode, artifact targeting strategy, contract mapping, and ZSSR routing requirements.
zar	artifact_manifest_approval_evidence	table	zar_admin	permanent	heap	8192 bytes	Stores structured review and approval evidence for artifact manifests. Each row records a review, approval, rejection, quarantine, field confirmation, or override decision taken by the system, an artifact reviewer, a governance reviewer, or a registry authority. Used for auditability, governance traceability, and replay of manifest approval history.
zar	artifact_manifest_projection_log	table	zar_admin	permanent	heap	8192 bytes	Stores projection and publication events for approved artifact manifests. Each row records an attempt to publish, refresh, validate, remove, or reproject a manifest into downstream targets such as ZCP bindings, ZSSR routing, docs, OpenAPI, SDK outputs, analytics, or other ZAR-linked operational consumers.
zar	artifact_manifest_registry	table	zar_admin	permanent	heap	8192 bytes	Stores the compiled artifact manifests generated by ZAMG inside the ZAR framework. Each row represents a generated candidate or approved canonical operational contract for a ZAR-registered artifact, linked to its CMI and optionally its ZAR code. Used as the source for ZCP bindings, ZSSR routing validation, documentation projection, and other downstream governed projections.
zar	artifact_manifest_review_queue	table	zar_admin	permanent	heap	8192 bytes	Stores review queue items for artifact manifests that require human or governance review before promotion. Used to manage manifest review workflow, assignment, priority, escalation, and resolution status within the ZAR framework.
zar	cmi_artifact_name_registry	table	zar_admin	permanent	heap	48 kB	Registry of canonical artifact naming patterns and controlled artifact-name definitions used in CMI construction, validation, normalization, and publication workflows.
zar	cmi_completeness_rule_registry	table	zar_admin	permanent	heap	16 kB	Registry of completeness and structural validation rules used to determine whether a CMI proposal or canonical CMI record contains all required identity parts, bindings, and governance metadata.
zar	cmi_document_binding	table	zar_admin	permanent	heap	8192 bytes	Binding table that links canonical managed identifiers (CMIs) to documentation assets, source pages, MDX documents, generated references, and other authored documentation contexts.
zar	cmi_kind_registry	table	zar_admin	permanent	heap	16 kB	Controlled vocabulary registry for valid CMI kind values, including their descriptions, usage intent, and governance constraints for managed identifier generation and validation.
zar	cmi_proposal_results	table	zar_admin	permanent	heap	608 kB	Staging table for generated CMI proposals before canonical publication. Stores proposal payloads, confidence, rationale, review state, approval status, and publish linkage metadata.
zar	cmi_registry	table	zar_admin	permanent	heap	8192 bytes	Canonical registry of approved CMIs used across ZAYAZ to represent managed identities for signals, tables, artifacts, documents, routes, schemas, and other governed platform objects.
zar	codex_automation_runs	table	zar_admin	permanent	heap	16 kB	Audit log of Codex-driven automation executions, including run scope, inputs, orchestration metadata, status, timing, and operational outcomes across registry enrichment and classification workflows.
zar	codex_datatype_results	table	zar_admin	permanent	heap	16 kB	Stores Codex-generated datatype classification results for candidate fields, signals, or registry records, including inferred datatype, confidence, rationale, and review metadata.
zar	codex_kind_results	table	zar_admin	permanent	heap	16 kB	Stores Codex-generated kind classification results for governed records such as CMI, CSI, registry entities, or semantic platform objects, including confidence and rationale.
zar	codex_module_results	table	zar_admin	permanent	heap	16 kB	Stores Codex-generated module classification results that map candidate records, components, or assets to canonical ZAYAZ modules and related governance context.
zar	codex_signal_name_results	table	zar_admin	permanent	heap	16 kB	Stores Codex-generated signal naming results, including normalized signal names, naming suggestions, rationale, confidence, and review metadata for signal authoring workflows.
zar	codex_signal_registry_working	table	zar_admin	permanent	heap	16 kB	Working table used during Codex-assisted signal registry generation and enrichment. Holds intermediate signal candidates, transformations, classifications, and reviewable outputs before promotion.
zar	codex_validator_results	table	zar_admin	permanent	heap	16 kB	Stores validation outputs produced by Codex-assisted review or rule-checking workflows, including pass/fail assessments, flagged issues, rationale, and remediation guidance.
zar	component_module_binding	table	zar_admin	permanent	heap	328 kB	Canonical normalized binding table linking components to modules in ZAYAZ. Each row represents one governed component-to-module relationship and supports deterministic module derivation, lineage, routing, and CSI generation.
zar	component_module_map	table	zar_admin	permanent	heap	168 kB	Canonical mapping between registered components and their primary or associated ZAYAZ modules. Used for deterministic module derivation, routing, lineage, and CSI/CMI generation.
zar	component_module_map_staging	table	zar_admin	permanent	heap	168 kB	Staging table for proposed or imported component-to-module mappings before canonical approval and promotion into zar.component_module_map.
zar	component_omr_module_map	table	zar_admin	permanent	heap	232 kB	Mapping table that links documented components to OMR module identifiers extracted or derived from documentation and module governance metadata.
zar	component_registry	table	zar_admin	permanent	heap	1120 kB	Canonical registry of ZAYAZ components, including engines, micro-engines, services, modules, and governed platform units used for lineage, routing, identity, and documentation binding.
zar	csi_kind_registry	table	zar_admin	permanent	heap	16 kB	Controlled vocabulary registry for valid CSI kind values used in Canonical Signal Identifier generation, review, validation, and publication workflows.
zar	csi_proposal_results	table	zar_admin	permanent	heap	56 kB	Staging table for generated CSI proposals linked to signal proposals or published signals. Stores proposed CSI values, rationale, confidence, review status, and publish linkage metadata.
zar	documented_component_registry	table	zar_admin	permanent	heap	384 kB	Registry of components discovered and documented from specs, MDX pages, or generated docs artifacts, used to reconcile authored documentation with canonical component records.
zar	documented_component_staging	table	zar_admin	permanent	heap	8192 bytes	Staging table for newly discovered or extracted documented component records before reconciliation and promotion into documented_component_registry or component_registry.
zar	engine_registry	table	zar_admin	permanent	heap	128 kB	Canonical registry of engines documented and governed within ZAYAZ, including engine identity, ownership, module alignment, source metadata, lifecycle status, and semantic classification.
zar	execution_audit_event	table	zar_admin	permanent	heap	8192 bytes
zar	external_opcode_access_grant	table	zar_admin	permanent	heap	16 kB	Client-controlled grant layer that allows a registered financial institution to use a shared ESGX/external opcode binding under a governed purpose, validity window, output policy, and constraint profile.
zar	external_opcode_binding_registry	table	zar_admin	permanent	heap	48 kB	Registry of ESG Exchange Code (ESGX) bindings that define reusable governed external execution profiles backed by canonical core opcodes. Access is typically controlled through zar.external_opcode_access_grant.
zar	financial_institution_registry	table	zar_admin	permanent	heap	16 kB	Registry of approved financial institutions, such as banks and lenders, that may receive ESGX-based access through governed grant flows.
zar	global_data_lifecycle	table	zar_admin	permanent	heap	16 kB	Master policy table for default lifecycle, operational, and contract behavior of ZAYAZ data products.
zar	kind_registry	table	zar_admin	permanent	heap	16 kB	Controlled vocabulary registry for generic kind values used across ZAYAZ registries to classify governed records, artifacts, components, and semantic entities.
zar	metric_category_registry	table	zar_admin	permanent	heap	16 kB	Controlled vocabulary registry for valid metric category values used in signal and registry classification, including categories such as Environmental, Social, Governance, Financial, and Cross-cutting.
zar	micro_engine_registry	table	zar_admin	permanent	heap	224 kB	Canonical registry of micro-engines, including MEID identity, classification, domain, category, API metadata, source payloads, and governance status for MICE-aligned execution units.
zar	module_alias_registry	table	zar_admin	permanent	heap	16 kB	Registry of valid module aliases, alternate names, abbreviations, and normalization mappings used to resolve incoming module references to canonical module codes.
zar	module_registry	table	zar_admin	permanent	heap	16 kB	Canonical registry of ZAYAZ modules, including module code, domain, description, governance role, and platform positioning used for deterministic classification and lineage.
zar	opcode_artifact_type_binding	table	zar_admin	permanent	heap	72 kB	Strict compatibility bindings between opcodes and artifact types. Used by ZAMG to validate whether an artifact type may expose or execute a given opcode.
zar	opcode_category_registry	table	zar_admin	permanent	heap	16 kB	Registry of top-level semantic opcode categories used by ZCP and ZAMG, such as intake, transformation, validation, computation, workflow, export, governance, lineage, agent, and integration.
zar	opcode_proposal_results	table	zar_admin	permanent	heap	8192 bytes	Stores draft and reviewable opcode proposals before they are published into zar.opcode_registry and related normalized binding tables. Supports deterministic and AI-assisted proposal generation, review workflow, and publish traceability.
zar	opcode_registry	table	zar_admin	permanent	heap	48 kB	Canonical registry of semantic operation codes used by ZCP and referenced by ZAMG-generated manifests. Opcodes define executable intent, while rulesets define governed execution behavior.
zar	opcode_registry_change_log	table	zar_admin	permanent	heap	8192 bytes	Stores lifecycle, compatibility, policy, and semantic change history for opcode definitions in zar.opcode_registry. Used for governance traceability and compatibility review.
zar	opcode_ruleset_profile_binding	table	zar_admin	permanent	heap	8192 bytes	Stores required, recommended, or optional ruleset family/profile guidance for each opcode, optionally scoped by artifact type and environment. Used by ZAMG and routing validation to narrow ruleset selection.
zar	registry_sync_runs	table	zar_admin	permanent	heap	16 kB	Audit table for registry synchronization executions. Records source, target registry, run timing, counts, success or failure status, and operational diagnostics for registry sync jobs.
zar	signal_binding_registry	table	zar_admin	permanent	heap	48 kB	Canonical registry of signal-to-source bindings that map approved signals to source tables, columns, schemas, storage locations, and physical access characteristics.
zar	signal_component_binding	table	zar_admin	permanent	heap	16 kB	Canonical relationship table linking signals to producing, consuming, transforming, validating, or publishing components within the ZAYAZ platform graph.
zar	signal_component_flow	table	zar_admin	permanent	heap	8192 bytes	Observed or derived flow table capturing signal movement between source and destination components, including traffic counts, timing, and lineage of component-to-component signal transfer.
zar	signal_csi_binding	table	zar_admin	permanent	heap	8192 bytes	Canonical binding table linking approved signals to their published CSI identities, including CSI structure parts, versioning, and publish provenance.
zar	signal_domain_registry	table	zar_admin	permanent	heap	16 kB	Controlled vocabulary registry for valid signal domain values used in signal classification, such as ENV, SOC, GOV, CORE, REF, and other governed semantic domains.
zar	signal_engine_binding	table	zar_admin	permanent	heap	8192 bytes	Binding table linking signals to engines that produce, consume, transform, validate, or otherwise operate on them in governed execution contexts.
zar	signal_family_registry	table	zar_admin	permanent	heap	16 kB	Controlled vocabulary registry for signal family values used to classify signals into identity, metric, text, code, classification, audit, time, geo, and related semantic families.
zar	signal_proposal_results	table	zar_admin	permanent	heap	128 kB	Staging table for generated signal proposals before publication. Stores proposal outputs, deterministic enrichments, rationale, confidence, review state, and publish linkage to canonical signal records.
zar	signal_registry	table	zar_admin	permanent	heap	56 kB	Canonical registry of approved signals used across ZAYAZ, including semantic identity, datatype, governance metadata, module or engine usage, and links to source and identity bindings.
zar	signal_role_registry	table	zar_admin	permanent	heap	16 kB	Controlled vocabulary registry for valid signal role values used in signal classification, such as KPI, input, output, identifier, descriptor, benchmark, flag, audit, and classification.
zar	signal_uso_type_binding	table	zar_admin	permanent	heap	8192 bytes	Definition-time binding between a canonical signal and its approved Universal Signal Ontology Type. This table classifies what semantic origin type a signal definition belongs to; runtime USO instances are stored separately in zar.uso_instance.
zar	sssr_global_config	table	zar_admin	permanent	heap	16 kB	Global configuration table for SSSR and related ZAYAZ registry services, storing canonical platform settings, default values, URL bases, generation policies, and deterministic runtime configuration.
zar	table_prefix_registry	table	zar_admin	permanent	heap	48 kB	Registry of approved table prefixes and their semantics, used to construct canonical table names, infer domains, and enforce governed naming policy for dataset tables.
zar	table_registry	table	zar_admin	permanent	heap	64 kB	Canonical registry of approved tables and datasets in ZAYAZ, including naming, ownership, storage, schema, module usage, documentation linkage, and signal-generation metadata.
zar	table_registry_proposal_results	table	zar_admin	permanent	heap	80 kB	Staging table for generated table registry proposals before approval and publication into the canonical table_registry. Stores proposal rationale, confidence, review state, and promotion metadata.
zar	trustgate_telemetry_event	table	zar_admin	permanent	heap	16 kB	TrustGate telemetry event table capturing assurance, validation, policy, and decision telemetry linked to USO instances, CSI, CMI, and canonical signals.
zar	uso_instance	table	zar_admin	permanent	heap	8192 bytes	Runtime lineage table for Universal Signal Ontology instances. Each row represents a specific signal birth event with an immutable uso_id linked to CSI, CMI, and origin-chain telemetry.
zar	uso_trustgate_telemetry_binding	table	zar_admin	permanent	heap	8192 bytes
zar	uso_type_level_registry	table	zar_admin	permanent	heap	16 kB	Controlled vocabulary registry for the six-level Universal Signal Ontology Type taxonomy. Defines approved ontology segments for domain, origin, signal class, method/subtype, scope/category, and detail.
zar	uso_type_registry	table	zar_admin	permanent	heap	56 kB	Canonical registry of approved Universal Signal Ontology Types. Each USO Type is generated from controlled level references and classifies the semantic origin of a signal definition.

3. List of View Tables

Schema	Name	Type	Owner	Persistence	Size	Description
zar	v_cmi_ask_zara_queue	view	zar_admin	permanent	0 bytes	Queue of CMI records requiring AI (ZARA) assistance for completion, enrichment, or correction. Used as an input pipeline for automated artifact intelligence generation.
zar	v_cmi_binding_history	view	zar_admin	permanent	0 bytes	Historical record of CMI bindings across versions and lifecycle states. Enables traceability of artifact evolution and linkage changes over time.
zar	v_cmi_completeness_validator	view	zar_admin	permanent	0 bytes	Validation view assessing completeness of CMI records against required fields, taxonomy rules, and governance standards. Used to enforce registry quality.
zar	v_cmi_doc_drift_queue	view	zar_admin	permanent	0 bytes	Queue of CMIs where documentation has diverged from registry definitions. Supports detection and reconciliation of documentation vs implementation drift.
zar	v_cmi_primary_doc	view	zar_admin	permanent	0 bytes	Primary documentation mapping for each CMI, linking canonical artifacts to their authoritative documentation sources.
zar	v_cmi_proposal_review_queue	view	zar_admin	permanent	0 bytes	Review queue of CMI proposals awaiting human validation, approval, or rejection before promotion to the canonical registry.
zar	v_cmi_registry_with_docs	view	zar_admin	permanent	0 bytes	Enriched view of the CMI registry joined with documentation metadata, providing a complete artifact + documentation perspective.
zar	v_codex_signal_registry_export_ready	view	zar_admin	permanent	0 bytes	Subset of signal_registry entries that meet completeness and validation requirements for export to Codex or external systems.
zar	v_codex_signal_registry_latest	view	zar_admin	permanent	0 bytes	Latest active version of each signal in the registry, normalized for downstream consumption and Codex alignment.
zar	v_codex_signal_registry_review_queue	view	zar_admin	permanent	0 bytes	Queue of signal registry entries pending review for Codex publication readiness, including validation and governance checks.
zar	v_component_module_binding_integrity_gaps	view	zar_admin	permanent	0 bytes	Integrity monitor for component_module_binding. Detects missing component references, missing module references, and invalid primary module configurations (none or multiple primaries) for components.
zar	v_component_registry_integrity_gaps	view	zar_admin	permanent	0 bytes	Integrity monitor view showing component identifiers that appear in engine_registry, micro_engine_registry, or component_module_map but are missing from component_registry. Used to detect canonical component registry drift.
zar	v_component_registry_integrity_summary	view	zar_admin	permanent	0 bytes	Summary integrity monitor for the canonical component registry. Reports how many component identifiers exist in source registries, how many are missing from component_registry, how many are covered, and whether any orphan canonical rows exist.
zar	v_component_registry_orphan_registry_rows	view	zar_admin	permanent	0 bytes	Integrity monitor view showing component_registry rows that are no longer referenced by engine_registry, micro_engine_registry, or component_module_map. Useful for detecting stale canonical component records.
zar	v_documented_component_lookup	view	zar_admin	permanent	0 bytes	Lookup view resolving component identifiers to their documented metadata, including source files, documentation slugs, and ownership context.
zar	v_engine_registry_enriched	view	zar_admin	permanent	0 bytes	Enriched engine registry including derived fields, classification, component linkage, and normalized metadata for analytics and orchestration.
zar	v_micro_engine_registry_enriched	view	zar_admin	permanent	0 bytes	Enriched micro-engine registry providing normalized metadata, classification, and linkage to components and runtime capabilities.
zar	v_signal_component_binding_enriched	view	zar_admin	permanent	0 bytes	Enriched mapping between signals and components including roles, metadata, and derived attributes for graph-based analysis.
zar	v_signal_component_flow_enriched	view	zar_admin	permanent	0 bytes	Enriched signal flow relationships between components, capturing directional data movement and runtime propagation of signals.
zar	v_signal_component_graph_summary	view	zar_admin	permanent	0 bytes	Aggregated summary of the signal-component graph, including counts, connectivity, and high-level topology metrics.
zar	v_signal_registry_export	view	zar_admin	permanent	0 bytes	Flattened export view of signal_registry including bindings and metadata, designed for external systems, APIs, and documentation pipelines.
zar	v_trustgate_telemetry_enriched	view	zar_admin	permanent	0 bytes	Enriched TrustGate telemetry view joining telemetry events to signal registry and USO Type metadata for audit, assurance, ESG traceability, and AI explainability.
zar	v_uso_level_lookup	view	zar_admin	permanent	0 bytes	Lookup view exposing USO type level IDs, indexes, codes, and labels for UI selection, backend validation, and ontology generation workflows.
zar	v_zayaz_integrity_alerts	view	zar_admin	permanent	0 bytes	Action-oriented integrity alert view for core ZAYAZ registries and graph bindings. Produces one row per alert category with severity, issue count, current status, and recommended remediation.
zar	v_zayaz_integrity_overview	view	zar_admin	permanent	0 bytes	Platform-wide integrity summary view for core ZAYAZ registries and graph bindings. Aggregates component coverage, component-module binding quality, signal registry health, signal binding quality, and signal graph integrity into a single monitoring row.

---