feat: multi-tape and nondeterministic Turing machines (TM+) #73
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add multi-tape and nondeterministic Turing machines by extending the existing
Tmtype in place — authorized contract break (owner, 2026-10-24): the service went live today with no users, and one type is tidier than a parallelTmX. After this lands, the new shape becomes the frozen one and is documented indocs/reference.md.Core (
crates/rgxr-core/src/tm.rs)Tmgainstapes: usize(serde default 1); transitions becomestate → read-tuple ("0,_") → Vec<TmAction>; list length > 1 ⇒ nondeterministicexplored, config cap,truncated= inconclusive, shortest accepting path) whentapes > 1or any action list > 1Machine::Tmgrade variant charges both paths to the shared work budget;TmRunResultgainsexplored+truncatedAPI: same endpoint
POST /api/v1/tm/run, extended schemas in openapi.yaml; regenschema.d.ts; round-trip test updatedWeb: same TM mode on the machines page + variant controls (tapes 1–4, ND via repeated transition lines); DSL:
tapes Ndirective, per-tape transitionsq0, 0, _ -> q1, X, R | _, R, repeated LHS allowed; multi-row tape UI; explored/truncated display; per-tape diagram edge labels; all strings bilingual (en+es)Dojo: 2–3 verified
tmLibrary.tsentries — {ww} via 2-tape copy-compare, palindromes via 2-tape, one ND machine with pruning — JS oracle tests extended, bilingual fieldsTests: old-shape shim, 2-tape ≡ 1-tape equivalence, ND pruning/truncation/timeout, adversarial budget test, API round-trip, DSL parse tests
CI: add
bun run checkto the web job (enforces Spanish coverage)Other objects: if any other frozen shape would force duplicity or a messy design, breaking it is pre-authorized — document the break in the PR.
Constraints: no
v*tags (test env tracks master; prod stays on the initial plan)