-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
tassadarPsionic Tassadar roadmap workPsionic Tassadar roadmap work
Description
Summary
- close both the named hard-Sudoku claim and the benchmark-wide Sudoku claim
Roadmap Position
- Phase: Phase 6. Close demos and benchmark claims
- Sequence: article-gap closure after
TAS-156A - Owned-route boundary: any canonical article route referenced here means the
psionic-transformer-based route established byTAS-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
- add a canonical Arto Inkala fixture
- build the declared hard-Sudoku benchmark suite that stands in for "these
benchmarks" - require exactness and declared runtime/time floors on the canonical fast
route
Why This Matters
- the article names one hard instance and also claims benchmark-wide accuracy
Primary Surfaces
psionic-transformer(canonical owned article-route base for this issue)psionic-datapsionic-runtimepsionic-evalpsionic-servepsionic-research
Validation
- exact-solve artifacts
- benchmark-wide exactness gate
- runtime summary
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
- Arto is green
- the declared hard-Sudoku benchmark suite is green
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
tassadarPsionic Tassadar roadmap workPsionic Tassadar roadmap work