pliuzv0.1.x

Govern

Audit & compliance

A signed audit trail is useful only when completeness and signer identity are independently verifiable. Pliuz exports bind both into portable evidence.

Complete versus partial verification

A complete run returns verified. If the requested limit is reached first, the result is explicitly partial and is never displayed as green. A broken link or hash returns broken.

Signed JSONL and manifest v2

The JSONL body is accompanied by a canonical signed manifest binding the tenant, exact SHA-256 digest, count, range, pagination state and chain head from the same database snapshot. PostgreSQL produces the canonical evidence strings so large integers and decimals are not rounded by JavaScript.

offline verification
pip install cryptography

python verify_pliuz_export.py export.jsonl \
  --manifest export.manifest.json \
  --trusted-public-key <PINNED_ED25519_PUBLIC_KEY>

# Strongest mode: verify a complete signed receipt archived outside Pliuz
python verify_pliuz_export.py export.jsonl \
  --manifest export.manifest.json \
  --trusted-keyring trusted-keyring.json \
  --anchor-receipt archived-anchors.json
Pin the key independently
A public key delivered inside the same export can prove self-consistency, but not signer identity. Store the fingerprint or keyring through your security onboarding channel. Without that pin, the verifier deliberately refuses to print VERIFIED.

External anchoring

Archive signed chain-head receipts outside Pliuz. The verifier checks the receipt's signature and binds its tenant, sequence, hash and signing time to the export snapshot.

signed chain-head receipt
GET /api/v1/events/chain-head
{
  "format": "pliuz-chain-head-v1",
  "tenant_id": "...",
  "sequence_no": "5541",
  "hash_current": "...",
  "signed_at": "...",
  "algorithm": "ed25519",
  "public_key_hex": "...",
  "signature": "..."
}

Tools & principles