ZAK_CORE

This page shows what has been tested, how it behaved, and where the limits are.

VERIFICATION

Proof, not promises.

You can point to hashes, schemas, and reruns — not vibes.
Intended for: Security, Compliance, Platform Engineering, Procurement, Regulators

NOTICE: This section is intentionally plain: what was tested, what passed, and what still has limits.

THIS_SECTION_DOES_NOT:

  • Assert intelligence or reasoning superiority
  • Compare model quality against competitors
  • Guarantee correctness of user intent
  • Replace organizational security policy

TRY_IT

See proof in 90 seconds

Send a request through the governance gate. Watch the verdict, inspect the receipt, and verify the hash yourself.

ATTACK_THE_SYSTEM
Try prompt injection, data exfiltration, or prohibited domains. Watch enforcement happen before delivery.
receipt_hash: —
Run the demo to generate a cryptographic receipt-shaped response.
GOVERNANCE_RECEIPT
Receipt-shaped proof (verify locally)
hash
—
Verification pending.
RECEIPT_JSON
Run the demo above to generate a receipt.
FULL_RESULT
—

12

Test Suites

94/98

Test Cases Passed

3/3

Existential Passed

38/39

Critical Passed

TEST_GROUPS

What we test

Context Integrity

CRITICAL

Verifies that context mechanics are deterministic, accurate, and resistant to manipulation.

  • +Particle field analysis is deterministic
  • +Project condensation extracts structure without LLM calls
  • +Cross-project synthesis does not leak or conflate
  • ...and 2 more

5/5

verified

CD-001
CD-002
CD-003
CD-004
CD-005

Trust and Governance

EXISTENTIAL

Verifies that trust boundaries and constitutional rules are enforced under adversarial conditions.

  • +Organization isolation prevents cross-org data access
  • +Revoked access is enforced immediately
  • +Constitutional conflicts are resolved deterministically
  • ...and 2 more

2/2

verified

CD-006
CD-007

Institutional Safety

CRITICAL

Verifies that human intervention and audit requirements are satisfied.

  • +Human corrections preserve full provenance
  • +Moderator annotations affect synthesis appropriately
  • +Human errors are recoverable without data loss
  • ...and 3 more

2/2

verified

CD-008
CD-009

Model Independence

CRITICAL

Verifies that ZAK value is substrate-level, not dependent on specific LLM capabilities.

  • +Facts are preserved across model swaps
  • +Constraints are enforced regardless of model
  • +Decisions are consistent across model variants
  • ...and 1 more

1/1

verified

CD-010

Economic and Abuse Resistance

CRITICAL

Verifies that the system cannot be exploited to inflate costs or exhaust resources.

  • +Max-radius retrieval attacks are capped
  • +Condensation bombs are rate-limited
  • +Token inflation is detected and bounded
  • ...and 2 more

1/1

verified

CD-011

Temporal Integrity

CRITICAL

Verifies that context evolves correctly over time without fossilizing errors.

  • +Newer information dominates older contradictions
  • +Old mistakes decay and lose influence
  • +Temporal weighting is smooth (no cliff)
  • ...and 2 more

1/1

verified

CD-012

VERIFIED_CONSTITUTIONS

Pre-built governance profiles

Each test validates a specific governance profile. Pick the one closest to your use case, then review the evidence behind it before you deploy.

View Constitution Library →

DOCUMENTED_LIMITS

Known limitations

3 test suite(s) have documented limitations. All limitations are bounded and non-blocking for production use.

View all limitations →

REPRODUCIBILITY

Test Execution

  • Tests are deterministic and produce identical results on identical inputs.
  • Tests are re-runnable internally against the same particle corpus.
  • External reproduction may require licensed access to test infrastructure.
  • Passing a test defines a system guarantee for the tested conditions.
Request verification details under NDA

EXECUTOR_AGNOSTIC_COMPLIANCE

Governance as Physics, Not Policy

ZAK's compliance features apply to any execution environment — AI models, API calls, workflows, or infrastructure operations.

Proof-of-Denial Receipts

Cryptographic receipts for denied executions with violated invariants

  • • No sensitive payloads stored
  • • Forbidden transition classification
  • • Immutable denial evidence

Deterministic Replay

Re-execute historical requests with pinned constitution + inputs

  • • Hash-verified outcomes
  • • Constitution version pinning
  • • Divergence analysis

Execution Timeline

Append-only, ordered execution events for audit inspection

  • • Unified across all event types
  • • Links authority → constitution → receipt
  • • Chronological ordering guaranteed

Constitution Pinning

Explicit version enforcement, no silent upgrades

  • • Every execution references snapshot
  • • Drift detection warnings
  • • Explicit migration path

Audit Export Bundles

Machine-verifiable ZIP with receipts, hashes, Merkle proofs

  • • Batch verification via Merkle root
  • • Legal discovery format
  • • 7-day expiration for security

Proof Journal

Immutable, append-only ledger of constitutional events

  • • Hash chain anchors
  • • Single-writer semantics
  • • Tamper-evident by design

ADDITIONAL_RESOURCES

Receipt Schema

Cryptographic proof format specification

Verification Guide

How to verify receipts offline

Panel Specification

UI contract for governance panels