Skip to content

donaldfilimon/abi / .agents/skills/abi-claims-validator

abi-claims-validator

Verified

Validate ABI docs and external collateral against repo evidence and docs/contracts/external-claims-audit.mdx. Use when auditing claims, scanning docs for unsupported QPS/sharding/FHE/AES language, checking one claim before publish, or re-confirming the external-claims audit. Agent procedure only — not a CLI or slash command. Pair with abi-doc-claims-sync when editing docs.

ABI Claims Validator

Agent-side procedure to validate documentation, collateral, and public claims against the repository source of truth (Cargo.toml, src/, contract tests, docs/contracts/external-claims-audit.mdx). Use before publishing any external artifact. There is no /abi-claims-validator binary or slash command — follow the steps below (or dispatch the external-claims-auditor subagent).

For editing docs to stay claim-honest, prefer abi-doc-claims-sync.

Procedure (agent actions)

scan

  1. Open the target tree (default docs/, plus README/AGENTS/CHANGELOG/walkthrough as needed).
  2. Search for claim patterns (table below) with ripgrep or equivalent.
  3. For each hit, cross-reference source/tests/docs/contracts/external-claims-audit.mdx.
  4. In --strict mode, treat any unproven number or deployment claim as a fail.

Detects:

  • Performance numbers (QPS, latency, throughput, accuracy)
  • Deployment claims (Kubernetes, H100, multi-node)
  • Implementation language claims (Swift, Python, TensorFlow, PyTorch)
  • Security claims (AES-256, RBAC, certifications)
  • Distributed claims (sharding, multi-host)
  • Benchmark comparisons (SQuAD, CodeSearchNet, GPT)
  • Energy/GPU speedup claims

check-claim

Given one claim string, return SUPPORTED | UNSUPPORTED | PARTIAL plus the evidence path (source, test, or audit section). Prefer executable evidence over prose.

audit

Produce a short markdown report of flagged claims vs evidence. The durable ledger lives in docs/contracts/external-claims-audit.mdx — update that file when the audit changes reality, do not invent a parallel truth source.

Source of Truth Hierarchy

  1. Executable config: Cargo.toml, Cargo.toml.zon, rust-toolchain.toml
  2. Source implementation: src/, tests/golden/
  3. Contract tests: tests/golden/ (surface, mcp_tools, feature_modules, plugin_registry, public_docs)
  4. Explicit claim boundary: docs/contracts/external-claims-audit.mdx
  5. North-star mapping: docs/spec/wdbx-north-star.mdx §2 (Current/Partial/Proposed)
  6. Prose docs: README.md, docs/*.mdx — lowest priority, must reconcile upward

Common Claim Patterns to Flag

PatternLikely StatusCheck Against
`\d+\s*(QPSreq/sthroughput)`
\d+\s*ms\s*latency❌ Unsupported../wdbx/crates/abi-wdbx/tests/ artifact
`distributedshardingmulti-host
`AESRBACencryption
`SwiftPythonTensorFlow
`H100A100InfiniBand
`SQuADCodeSearchNetGPT
`energykWhefficiency

Replacement Wording

From docs/contracts/external-claims-audit.mdx §Reusable Delta:

Current ABI repo evidence supports a stable-Rust local AI orchestration framework with deterministic Abbey/Aviva/Abi profile routing, an in-process WDBX vector/key-value/block store, segment checkpoint plus WAL persistence with runtime recovery, a compatibility JSONL snapshot mirror, epoch reclamation helpers, snapshot-persisted temporal/causal graph records, MCP hybrid WDBX query ranking, HNSW-style cosine search, SHA-256-linked conversation blocks, 3D spatial search, feature-off stubs, CLI/MCP contract coverage, explicit connector live-mode boundaries, GPU capability reporting with CPU fallback, and a tested WDBX consensus RPC transport with shared-secret and optional peer-allowlist controls. The repo does not currently prove distributed sharding, production multi-host deployment, AES/RBAC WDBX storage, Swift/Python/TensorFlow implementation claims, Kubernetes/H100 deployment claims, regulatory certifications, QPS/latency/accuracy targets, GPU speedup figures, energy-efficiency metrics, or SQuAD/CodeSearchNet/GPT comparative scores.

Integration

Pre-publish gate (agent runs the scan procedure after code gates):

./tools/check.sh
./tools/check.sh
# then: scan docs/ + collateral per Procedure above (--strict)

No feature gates — procedural validation against source.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall