ZeqForensic

HITE encryption, TESC channels, ZeqProof, firewall primitives.

• Protocol ID — zeq-forensic
• Category — Security
• Endpoint — POST /api/zeq/forensic
• Auth — api-key
• Rate limit — 30/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Data forensic entropy analysis. Computes Shannon entropy, byte frequency distribution, SHA-256 hash, and HulyaPulse sync state. Classifies data as RAW (<6.0 bits/byte), COMPRESSED (6.0–7.5), or ENCRYPTED (>7.5). Includes pulse synchronization factor.

Signature

Request

POST /api/zeq/forensic

Param	Type	Required	Default	Description
data	string	✓	—	Base64-encoded data to analyze

Response

{ sha256, size, entropy, maxEntropy, entropyRatio, verdict, pulseSync, zeqond, phase }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "data": "<value>"
}' \
  "https://api.zeq.dev/api/zeq/forensic"

Integrate

1. E2E channel — pair with HITE/TESC for encryption that locks to the HulyaPulse.
2. Integrity stamp — hash-bind every message to its Zeqond for replay-resistant audit.
3. Key rotation — tie rotation windows to pulse multiples for deterministic policy.

Seeds

• Near — wrap /api/zeq/forensic in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqForensic alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqForensic as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

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