Skip to content

Releases: BackendStack21/ai-verification-protocol

v5.2.6 — 5 Accuracy Fixes from Editorial Review

15 May 11:05

Choose a tag to compare

v5.2.6 — Accuracy Patch

Five independently verifiable accuracy fixes found during systematic editorial review of v5.2.5. Every fix is verified against the protocol document's own definitions — no speculation.

Changes

ai-verification-protocol.md

  1. §3.6six sub-signals (m, o, b, f, s, t)seven sub-signals (m, o, b, f, s, t, d)
  2. §8.2 — Same fix. Signal d (doc coverage) was added in v5.0 (§2.9, weight 0.05). Seven signals are defined in §3.1, but two sections still referenced "six."

index.html
3. Carousel slide 1 — η 0.94→0.97, ρ 0.04→0.03. Per §3.3, η ≥ 0.95 is required for AutoApprove. η=0.94 falls in the 0.80–0.95 band → HumanReviewRecommended. Cert now matches its verdict.
4. Carousel slide 4 — Removed false "PR size 1,892 LOC exceeds 1,500 hard cap". Per §0.3, the hard cap is 5,000 LOC; 1,892 falls in 1,501–5,000 (capped at HumanReviewRecommended). The actual CannotVerify trigger is ρ > 0.30.
5. Body text$0.0015$0.015 per-PR generation cost. $50 ÷ $0.0015 = 33,333:1, not the claimed ~3,300:1. Fixed to $0.015 (50/0.015 = 3,333 ≈ 3,300).

Version bumped across frontmatter, README badge, hero HTML, and JSON schema.

Verification

Fix Source of Truth Result
Signal count §3.1 defines 7 signals 7 ✓
η=0.97 verdict §3.3 η≥0.95 → AutoApprove Correct ✓
Size cap removed §0.3 hard cap at 5,000 Removed ✓
Math: $0.015 50/0.015=3,333≈3,300 Matches ✓

Full diff: v5.2.5...v5.2.6

v5.2.5 — The AI Verification Protocol

13 May 09:59

Choose a tag to compare

🚀 The AI Verification Protocol

Diagnose, repair, and measure — the operational answer to AI verification debt.

A multi-agent pipeline specification and system prompt that quantifies verification debt, derives η from observable signals, tracks Ci/Cv ratios, and orchestrates a five-agent review pipeline with provenance attestation.

📋 What It Does

Feature Detail
9 verification axes Semantic, behavioral, security, structural, fuzzing, dependency, provenance, adversarial, documentation
5 pipeline agents A (generator) → B (reviewer) → C (contract) → D (fuzzer) → E (certificate)
η from signals Mechanical efficiency score from 7 observable signals (m, o, b, f, s, t, d)
ρ correlation penalty Quantifies verifier-generator dependency; ρ > 0.30 → CannotVerify
Ci/Cv ratio Cost-to-Verify ÷ Cost-to-Implement per PR — the metric that matters
Active Repair Mode Auto-generates tests, docs, and type fixes with 5-gate verification
Machine-readable certificates JSON + in-toto attestation; markdown rendering for humans
Meta-audit loop 5% monthly sampling, Brier calibration, weight auto-recalibration

🌐 Landing Page

Live at vprotocol.21no.de — includes:

  • Certificate carousel showcasing all 4 verdict outcomes (AutoApprove → CannotVerify)
  • Five Whys root-cause analysis with whitepaper citations
  • Pipeline flow and feature cards

📖 Reads

📦 Contents

index.html · ai-verification-protocol.md · README.md · CNAME · og.svg · LICENSE