Jira progress: loading…

ZAR-DMS

ZAYAZ Data Model Stack

SSSR · USO · TrustGate · Execution Audit

1. Overview

The ZAYAZ Data Model Stack defines how meaning, execution, lineage, and trust are handled across the platform.

It consists of four tightly integrated layers:

1. SSSR → Signal definition (what a signal is)
2. USO → Runtime lineage (how a signal instance was created)
3. TrustGate → Validation (whether the signal can be trusted)
4. Execution Audit → Reproducibility (how the signal can be replayed)

---

2. Core Principle

ZAYAZ does not invent meaning at runtime — it executes meaning defined upstream and validates it continuously.

---

3. High-Level Architecture

---

4. SSSR — Signal Definition Layer

Purpose

SSSR defines the canonical structure and meaning of all signals in ZAYAZ.

It is implemented as a composed registry layer:

---

4.1. Core Tables

Table	Purpose
zar.signal_registry	Canonical signal definition
zar.signal_binding_registry	Physical table/column mapping
zar.signal_csi_binding	Conceptual identity (CSI)
zar.signal_uso_type_binding	Ontological classification

---

4.2. Example Signal

example-signal.jsonGitHub ↗

{
  "signal_id": "sssr:compute_method_registry.created_at",
  "signal_name": "created_at",
  "signal_domain": "governance",
  "signal_role": "timestamp"
}

---

4.3. CSI (Conceptual Identity)

COMP.AIIL_CON.SIGNAL.CREATED_AT.V1

---

4.4. Conceptual Model

---

5. USO — Runtime Provenance Layer

Purpose

USO tracks every instance of a signal at runtime.

Each signal instance becomes a traceable digital twin.

---

5.1. Key Fields

• uso_id (ULID)
• signal_id
• csi
• cmi
• origin_chain
• execution_context
• input_hash, output_hash

---

5.2. Lifecycle

---

5.3. Example USO Instance

example-uso-instance.jsonGitHub ↗

{
  "uso_id": "0196F...",
  "signal_id": "sssr:compute_method_registry.created_at",
  "csi": "COMP.AIIL_CON.SIGNAL.CREATED_AT.V1",
  "cmi": "CMID-ZYZ-000001",
  "origin_chain": ["CMID-ZYZ-000001"],
  "execution_context": {
    "source": "signal_proposal_publish",
    "source_table": "compute_method_registry",
    "column_reference": "created_at"
  }
}

---

6. TrustGate — Validation Layer

Purpose

TrustGate evaluates:

• data correctness
• schema compliance
• policy adherence

---

6.1 Telemetry Table

zar.trustgate_telemetry_event

---

6.2. Example Event

example-event.jsonGitHub ↗

{
  "trustgate_event_id": "tg_evt_1777367236168_5p0nadnl",
  "trust_score": 0.9825,
  "policy_id": "TG-POLICY-SIGNAL-VALIDATION-v1",
  "validator_id": "trustgate.signal.required_fields.v1",
  "trustgate_decision": "pass"
}

---

6.3. Validation Flow

---

7. Execution Audit Layer (Optional but Strategic)

Purpose

Provides full reproducibility:

• replay computation
• verify transformations
• satisfy regulatory audits

---

7.1. Suggested Table

zar.execution_audit_event

---

7.2. Example Structure

example-structure-execution-audit-event.jsonGitHub ↗

{
  "audit_event_id": "exec_evt_01...",
  "uso_id": "0196F...",
  "input_hash": "...",
  "output_hash": "...",
  "engine_cmi": "CMID-ZYZ-000001",
  "replayable": true
}

---

8. End-to-End Flow

---

9. Real API Example

Signal Publish

BASH:

curl -X POST \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  https://zayaz-search-api.fly.dev/admin/signal-registry/proposals/publish

---

TrustGate Telemetry Ingest

BASH:

curl -X POST \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  https://zayaz-search-api.fly.dev/admin/trustgate/telemetry/ingest \
  -d '{
    "signal_id": "sssr:compute_method_registry.created_at",
    "trustgate_stage": "validation",
    "trustgate_decision": "pass",
    "trustgate_status": "observed",
    "trust_score": 0.9825,
    "policy_id": "TG-POLICY-SIGNAL-VALIDATION-v1",
    "validator_id": "trustgate.signal.required_fields.v1",
    "updated_by": "cto@viroway.com"
  }'

---

10. Design Principles

1. Signal-Centric Architecture
2. Separation of Meaning / Execution / Validation
3. Immutable Runtime Lineage
4. Validation as First-Class System Component
5. Composable Registry Model
6. Audit-Ready by Design

---

11. Summary

The ZAYAZ Data Model Stack transforms ESG data into:

• Defined signals (SSSR)
• Traceable instances (USO)
• Validated outputs (TrustGate)
• Reproducible computations (Audit)

---

Thus Spoke Zarathustra — and ZAYAZ executes.

---