Every engine function, every API contract, every threat vector — tested.
Last run: 2026-07-10 07:59 UTC4D entropy scoring: micro-timing variance, noise residual, frequency entropy, biological perturbation.
Particle level system, visual tiers, decay mechanics, entropy gain with streak multipliers.
PoP generation, entropy proofs, ZK-SNARK composite proofs, full proof pipeline.
7 threat classes, 8 attack signatures, 4 cost tiers. Adversarial classification engine.
Entropy gap theorem verification, AI ceiling projections 2026–2040, Nyquist-limit guarantees.
Proof aggregation across time windows, multi-device fusion, stability scoring, trend detection.
Transaction verification with 7 rule checks: entropy, expiry, clock skew, version, PES consistency, device revocation.
MediaPipe → SST joint mapping (33→18), coordinate normalization, bone topology validation.
Device salt generation, local identity creation, presence session binding, clearing.
Presence value computation, scarcity (PES×PSS), authenticity (PRS), cap enforcement.
Reputation scoring with decay, device diversity bonus, drop-rate penalties.
Three-class classification benchmark. Each dimension independently separates human from AI.
Four AI-generation strategies tested against the same PES pipeline. All AI sources score below human floor (0.40).
Full pipeline: WASM engine → signature extraction → enrollment → verification. Human passes, AI fails.
Stage transitions, reputation tiers, eligibility gates, DTO mapping, narrative builder.
Zod schema shape validation, backward compatibility, protocol version enforcement.
Genesis minting eligibility matrix, decision algorithm, cohort cap invariants.
Deterministic tier/stage/rights/eligibility snapshots for all boundary cases.
Windowed rate limiting, IP isolation, pruning, reset mechanics.
Input validation, rate limiting, Supabase env-var guard.
Module integrity: every engine file exports expected functions.
Think PES fails under a specific condition?
Challenge BM-001 →All benchmarks run via npx vitest run on every commit. Results above from 2026-07-10. No failing tests. 5 pending tests are live-integration checks that require a running Supabase instance (skipped in CI).