TAS-185A: Route minimality audit and publication verdict

[AtlantisPleb]

Summary

• prove that the final route still matches the article in kind and publish the
  explicit final verdict over it

Roadmap Position

• Phase: Phase 8. Close route minimality, reproducibility, and publication
• Sequence: article-gap closure after TAS-156A
• Claim posture: necessary for article-equivalent closure, but not sufficient by itself to widen public capability claims

Description

• audit the final route for:
  • checkpoint dependence
  • spill/tape dependence
  • helper-module dependence
  • import mediation
  • planner or router indirection that materially changes execution ownership
  • extra orchestration layers that would make the route unlike the article's
    "transformer as computer" story
• publish one explicit operator-only vs public verdict over the final route

Why This Matters

• a portable route can still miss the article in substance

Primary Surfaces

• psionic-runtime
• psionic-router
• psionic-eval
• psionic-research
• psionic-serve
• psionic-provider
• docs/audits

Validation

• route-minimality audit
• publication verdict checker

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

• the repo has one green route-minimality audit
• and one explicit publication verdict for the final article-equivalent route

[AtlantisPleb]

Implemented TAS-185A in d2f9923 and pushed it to main.

Summary:

• added the canonical route-minimality audit in psionic-eval, plus research summary, provider receipt, served publication verdict, examples, fixtures, and the new checker script
• froze the canonical article claim route to tassadar.article_route.direct_hull_cache_runtime.v1
• made the audit explicitly check continuation boundaries, execution ownership, state-carrier minimality, orchestration exclusion, operator verdict, and public suppression posture
• advanced the article-equivalence frontier so BEQ-007 is closed and the next blocker is TAS-186
• updated the blocker matrix, acceptance gate, synced docs, and downstream article reports/scripts to the new frontier
• corrected the cross-machine checker to the current publication contract for selected_decode_mode

Validation:

• cargo test -p psionic-eval article_route_minimality -- --nocapture
• cargo test -p psionic-eval article_equivalence_acceptance_gate -- --nocapture
• cargo test -p psionic-eval article_equivalence_blocker_matrix -- --nocapture
• cargo test -p psionic-research article_route_minimality_audit_summary -- --nocapture
• cargo test -p psionic-provider article_route_minimality_audit_receipt_projects_report -- --nocapture
• cargo test -p psionic-serve article_route_minimality_publication_verdict -- --nocapture
• bash scripts/check-tassadar-article-equivalence-acceptance-gate.sh
• direct jq verification of the regenerated cross-machine and route-minimality publication artifacts after fixing the stale cross-machine checker expectation