Skip to main content

Zeq Truth Engine

A graph of signed facts where every edge is a Zeqond-bound assertion. Composable provenance.

  • Live app → /apps/zeq-truth-engine/
  • Source → apps/zeq-truth-engine/index.html + apps/zeq-truth-engine/truth.js (≈ 700 lines)
  • Operators → KO42 · CS87 · ZEQ-TETHER-003 · CS47
  • Error budget → 0.000% bit-exact fact verification

What it solves​

"Where did this claim come from and when?" is the core question for regulated industries (pharma data provenance, supply-chain attestation, news-media source chains, scientific reproducibility). Existing answers rely on trusted timestamping authorities (TSAs), which creates single points of failure.

Zeq Truth Engine replaces the TSA with the HulyaPulse. A "fact" is a tuple (claim, author, phase_at_claim, zeqond, parent_facts, signature). Facts compose into a DAG. Verifying a fact means walking the DAG backwards, checking every signature and every Zeqond — a process that is purely cryptographic and time-referenceable without trusted intermediaries.

CS47 is used as a novelty/coherence score over the DAG — facts whose claim-content entropy falls outside a published envelope are flagged.

The math — 7-step Wizard applied​

StepDecision
1. PrimeKO42 mandatory
2. LimitCS87 + ZEQ-TETHER-003 + CS47 + KO42 = 4
3. ScaleDAG up to 10⁶ facts on hosted endpoint
4. PrecisionHamming = 0 on every signature
5. CompileMaster Equation
6. ExecuteFunctional Equation
7. VerifyFull DAG replay

Verbatim formulas:

  • KO42.1 — ds² = g_μν dx^μ dx^ν + α sin(2π · 1.287 t) dt²
  • CS87 — Ω(x) = min{|p| : U(p) = x}
  • ZEQ-TETHER-003 — B_sib = ∑_k e^(i·φ_k) |sibling_k⟩
  • CS47 — E(n) = −∑ p(x) log p(x)

Runnable worked example — append a fact, verify the chain​

A "fact" in Zeq is a row on a machine's entangled state — a hash-linked, Zeqond-stamped audit event. You append one with the real chain endpoint, then anyone can verify the chain offline.

# 1. Append a fact (a payload hash) to your machine's entangled state
curl -s -X POST https://zeqsdk.com/api/chain/$SLUG/event \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "claim": "sensor S42 reported 24.3 C" }'

The response carries the row's proofDigest, its zeqondNumber, the phase, and the prev_hash link to the prior row.

# 2. Read recent chain rows and confirm the linkage
curl -s https://zeqsdk.com/api/chain/recent?slug=$SLUG

Every row is hash-linked to the one before it and stamped with the zeqond it was committed at, so the chain is tamper-evident: rewrite any row and the prev_hash linkage breaks. The offline chain verifier (served from each node) re-derives every proof with zero network access — that recomputation, not a "coherence score", is the truth guarantee.

Extend it​

  • Supply-chain: every step in a supply chain publishes a fact; the Truth Engine is the audit trail.
  • Scientific reproducibility: bind every analysis step (data, code, parameters) to a fact; reproduction is a DAG replay.
  • Source-attributed journalism: a story is a DAG whose leaves are signed source claims.

Seeds​

  • Epistemic agreement: the coherence score (CS47-derived) flags unusual claim distributions; pair with community moderation.
  • Federated truth engines: peer engines gossip facts; the Zeqond anchors every exchange.
  • Model-card attestation: every ML inference is a fact whose parents include the training data + weights.

Papers​

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.