TAS-186: Final article-equivalence claim checker and audit

[AtlantisPleb]

Summary

• combine every prerequisite into one machine-readable checker and one final
  audit

Roadmap Position

• Phase: Phase 9. Final closeout
• Sequence: article-gap closure after TAS-156A
• Owned-route boundary: any canonical article route referenced here means the psionic-transformer-based route established by TAS-156A / TAS-160, not a reintroduced mixed implementation spread across model or runtime crates.
• Claim posture: necessary for article-equivalent closure, but not sufficient by itself to widen public capability claims

Description

• aggregate:
  • canonical Transformer stack audit
  • non-fixture article-model artifact requirement
  • article frontend/compiler gate
  • article-interpreter-breadth gate
  • Transformer-backed reference-linear direct proof
  • Transformer-backed reference-linear exactness gate
  • anti-memorization gate
  • dataset-contamination and evaluation-independence audit
  • tokenization and representation invariance gate
  • fast-route gate
  • demo/benchmark gate
  • no-spill operator gate
  • interpreter-ownership gate
  • KV-cache and activation-state discipline verdict
  • route-minimality audit
  • reproducibility matrix
  • publication verdict
• publish one disclosure-safe but fully explicit final audit that answers:
  • what article lines are now truly matched?
  • what is the mechanistic verdict?
  • what is the behavioral verdict?
  • what is the operational verdict?
  • what model is canonical?
  • what weight artifact is canonical?
  • what route is canonical?
  • what machine matrix is in scope?
  • what still remains excluded?

Why This Matters

• the whole purpose of this roadmap is to answer this question exactly

Primary Surfaces

• psionic-transformer (canonical owned article-route base for this issue)
• psionic-eval
• psionic-research
• psionic-provider
• docs/audits
• scripts/

Validation

• final claim-checker script
• negative tests for every missing prerequisite
• source-to-claim audit

Claim Discipline

• Keep machine-legible boundaries explicit; partial progress must not be presented as full article equivalence.
• Preserve typed refusal, fallback, blocked, and suppressed posture where closure is still incomplete.
• Keep public language bounded to the declared article envelope rather than implying generic arbitrary-program closure from a partial green result.

Done When

• there is one binary article-equivalence gate
• and one final audit that cites only green machine-readable prerequisites

[AtlantisPleb]

Implemented on main in 9d1d520.

Summary:

• added the new TAS-186 article-equivalence claim checker and final audit surfaces in psionic-eval, psionic-provider, and psionic-research, plus the new final-audit checker script and audit doc
• moved the article-equivalence blocker matrix and acceptance gate to the fully green public-claim posture, and refreshed the downstream route-minimality, reproducibility, ownership, KV-discipline, and final-audit reports/summaries/publications they feed
• fixed the direct-model proof binding bug exposed during validation: the report now keeps the canonical published Transformer descriptor digest at the top level while allowing receipt-level execution descriptor digests to differ, and it instead enforces shared model id, weight-bundle digest, primary-artifact digest, route digest, and lineage contract across all proof receipts

Validation run:

• cargo test -p psionic-eval tassadar_article_equivalence
• cargo test -p psionic-provider article_equivalence
• cargo test -p psionic-serve article_route_minimality_publication_verdict
• cargo test -p psionic-research article_equivalence_final_audit_summary
• cargo run -q -p psionic-serve --example tassadar_direct_model_weight_execution_proof_report
• cargo run -q -p psionic-eval --example tassadar_article_interpreter_ownership_gate_report
• cargo run -q -p psionic-research --example tassadar_article_interpreter_ownership_gate_summary
• bash scripts/check-tassadar-article-kv-activation-discipline-audit.sh
• bash scripts/check-tassadar-article-cross-machine-reproducibility-matrix.sh
• cargo run -q -p psionic-eval --example tassadar_article_route_minimality_audit_report
• cargo run -q -p psionic-research --example tassadar_article_route_minimality_audit_summary
• cargo run -q -p psionic-serve --example tassadar_article_route_minimality_publication_verdict
• bash scripts/check-tassadar-article-equivalence-final-audit.sh