@polycode-projects/the-mechanical-code-talker 2.5.0 → 2.5.2

package/README.md

@@ -193,7 +193,7 @@ under a guard that proves the protected spans came through byte-for-byte.
 
 A frozen regression suite plays out full multi-turn dialogues built from these
 phrasings, from a single question up to a messy, typo-ridden real user.
-Tier-by-tier detail is in `HANDOVER.md` and `ROADMAP.md`.
+Tier-by-tier detail is in `HANDOVER.md`.
 
 ## How it guides you
 
@@ -994,7 +994,7 @@ bench-smoke lane replays:
 ```bash cwd=repo
 node chatbench/run.mjs --stamp smoke --only g-a1-naming-1 --out /tmp/chatbench-smoke
 node infbench/generate-cases.mjs --out /tmp/infbench-cases.jsonl
-node infbench/run.mjs --cases /tmp/infbench-cases.jsonl --only inf-a1-lookup-subClassOf-001 --stamp smoke --out /tmp/infbench-smoke
+node infbench/run.mjs --cases /tmp/infbench-cases.jsonl --only inf-1-lookup-subClassOf-001 --stamp smoke --out /tmp/infbench-smoke
 node agentbench/run.mjs --stamp smoke --driver stub --only ab-a0-describe-widget --out /tmp/agentbench-smoke
 ```
 
@@ -1023,8 +1023,8 @@ cross-version-stable fact-id contract has exactly one definition.
 tmct began as a whole-package lift of the seonix chat surface (v0.1.0, then
 published as `@polycode-projects/mct`), and was then reshaped. The LLM
 fallback, the code-extraction stack, and the MCP server were all removed. The
-naming, license, and memory model were reset to the vision above. See
-`ROADMAP.md` for the phase plan.
+naming, license, and memory model were reset to the vision above. See the
+`PLAN_*.md` design docs for what's planned next.
 
 ## Standards and bibliography
 

package/bin/tmct.mjs

@@ -26,7 +26,7 @@
 // tmct began as a whole-package lift of an earlier chat surface (see README
 // provenance): internal module filenames and symbols were kept to preserve the
 // shape and the green test suite. See README.md for what tmct is and
-// deliberately is NOT, and ROADMAP.md for where it is going.
+// deliberately is NOT, and the PLAN_*.md docs for where it is going.
 
 // The verb list itself is data (src/domain/cli-verbs.mjs) and both the Usage
 // block below and the unknown-invocation line read it, so a new verb is one

package/corpus/README.md

@@ -1,9 +1,9 @@
 # corpus/ — committed corpus data
 
-The corpuses tmct ships so that an **empty** tmct still has a vocabulary
-(ROADMAP Phase 2). Everything here is plain, diffable data; the loaders live
+The corpuses tmct ships so that an **empty** tmct still has a vocabulary.
+Everything here is plain, diffable data; the loaders live
 in `src/adapters/corpus/`. Related committed data lives in `data/` (response templates
-+ the SE phrase book — items 4+7).
++ the SE phrase book).
 
 ## The tiering policy (tier-1 / tier-2 / tier-3)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polycode-projects/the-mechanical-code-talker",
-  "version": "2.5.0",
+  "version": "2.5.2",
   "private": false,
   "type": "module",
   "description": "The Mechanical Code Talker (tmct) — a tolerant, offline, $0 chat surface that guides you toward precision queries about a software repository. ELIZA/PARRY-style but domain-obsessed with code. No model calls; no codebase index of its own.",
@@ -63,7 +63,6 @@
     "!src/domain/schemaorg/turtle.mjs",
     "!src/domain/version-stamp.mjs",
     "README.md",
-    "ROADMAP.md",
     "LICENSE",
     "corpus/",
     "!corpus/wordnet/generate.mjs",
@@ -133,6 +132,7 @@
     "audit": "npm audit --audit-level=high",
     "audit:fix": "npm audit fix",
     "demo:build": "node scripts/build-demo-site.mjs",
+    "roll": "node scripts/roll.mjs",
     "build:ask-bundle": "node scripts/build-ask-bundle.mjs",
     "build:demo-graph": "node scripts/build-demo-graph.mjs",
     "build:demo-memory": "node scripts/build-demo-memory.mjs",
@@ -144,8 +144,8 @@
     "extract:facts": "node bin/tmct.mjs extract"
   },
   "devDependencies": {
-    "esbuild": "^0.28.1",
-    "ink-testing-library": "^4.0.0",
+    "esbuild": "0.28.1",
+    "ink-testing-library": "4.0.0",
     "playwright": "1.61.1",
     "publint": "0.3.21",
     "yaml": "2.9.0"

package/src/domain/grammar/lexicon-core.json

@@ -1,5 +1,5 @@
 {
-  "comment": "tmct's starter lexicon (ROADMAP Phase 2, item 2), now covering BOTH the original software domain and the default 'human-world' persona's everyday people/places/objects/nature/time/body/mind vocabulary. Every word the ACE-OWL sub-fragment parser (src/domain/grammar/ace.mjs) is allowed to understand is DECLARED here — tmct never guesses a word's category. Nouns may declare a possessive property typing ('data' or 'object', pattern 7) or an irregular 'plural' (WordNet-sourced human nouns like 'man'/'child' need this — the morphology fold only handles regular -s/-ies/-es endings); adjectives MUST declare a type ('subclass' forms a class, 'data' asserts a boolean-ish datatype property, pattern 8); verbs may declare a preposition ('depend' + 'on' → dependsOn). The human-domain additions are flat and simple (breadth over depth — no gender/kinship taxonomy, no formal role hierarchy), matching corpus/tier2/generate.mjs's CORPUSES.human.lexicon sub-key, which --verify drift-checks against. Extend via loadLexicon(extra) with this same shape.",
+  "comment": "tmct's starter lexicon, now covering BOTH the original software domain and the default 'human-world' persona's everyday people/places/objects/nature/time/body/mind vocabulary. Every word the ACE-OWL sub-fragment parser (src/domain/grammar/ace.mjs) is allowed to understand is DECLARED here — tmct never guesses a word's category. Nouns may declare a possessive property typing ('data' or 'object', pattern 7) or an irregular 'plural' (WordNet-sourced human nouns like 'man'/'child' need this — the morphology fold only handles regular -s/-ies/-es endings); adjectives MUST declare a type ('subclass' forms a class, 'data' asserts a boolean-ish datatype property, pattern 8); verbs may declare a preposition ('depend' + 'on' → dependsOn). The human-domain additions are flat and simple (breadth over depth — no gender/kinship taxonomy, no formal role hierarchy), matching corpus/tier2/generate.mjs's CORPUSES.human.lexicon sub-key, which --verify drift-checks against. Extend via loadLexicon(extra) with this same shape.",
   "nouns": {
     "module": {},
     "class": {},

package/src/services/chat.mjs

@@ -10519,8 +10519,8 @@ async function runCommand(line, { config, source, graph, focus, memoryDir, trace
     return mk(`narrate mode ${next ? "on" : "off"}.`, { narrateNext: next });
   }
 
-  // /memory [verbose] — what tmct remembers, as text (the ROADMAP "Memory
-  // inspection" surface; the same renderer serves the `tmct memory` CLI).
+  // /memory [verbose] — what tmct remembers, as text (the same renderer
+  // serves the `tmct memory` CLI).
   if (name === "memory") {
     note(trace, "goal: inspect tmct's memory store (facts/utterances/sessions)");
     if (!memoryDir) return mk("no memory store here — /memory works inside a repo session.", { miss: true });

package/src/services/init.mjs

@@ -85,7 +85,7 @@ export function renderTomlConfig(config = defaultConfig()) {
   const base = `# tmct.toml — the mechanical code talker, project configuration.
 # Written by \`tmct init\`. An ABSENT file means shipped defaults (this file
 # just makes them explicit and editable). Documented in the repository-interface
-# onboarding surface (ROADMAP Phase 8, "Distribution: tmct init").
+# onboarding surface.
 
 # Where the code-graph JSON artifact lives, relative to this file. The
 # TMCT_GRAPH_FILE environment variable overrides it at runtime.
@@ -99,7 +99,7 @@ ${Array.isArray(c.graphFiles) && c.graphFiles.length ? `
 graph_files = ${JSON.stringify(c.graphFiles)}
 ` : ""}
 [corpus]
-# Corpus-tiering policy (ROADMAP Phase 4). The $0-offline default is inviolable;
+# Corpus-tiering policy. The $0-offline default is inviolable;
 # higher tiers are ADDITIVE and never required to answer.
 #   "tier1" — committed slice only. Offline, $0. The default.
 #   "tier2" — also fetch growable corpora at seed time (network, once, cached).

package/src/surfaces/web/memory-ask-browser.bundle.js

@@ -10919,7 +10919,7 @@ ${codeblock}`, options);
   var init_lexicon_core = __esm({
     "src/domain/grammar/lexicon-core.json"() {
       lexicon_core_default = {
-        comment: "tmct's starter lexicon (ROADMAP Phase 2, item 2), now covering BOTH the original software domain and the default 'human-world' persona's everyday people/places/objects/nature/time/body/mind vocabulary. Every word the ACE-OWL sub-fragment parser (src/domain/grammar/ace.mjs) is allowed to understand is DECLARED here \u2014 tmct never guesses a word's category. Nouns may declare a possessive property typing ('data' or 'object', pattern 7) or an irregular 'plural' (WordNet-sourced human nouns like 'man'/'child' need this \u2014 the morphology fold only handles regular -s/-ies/-es endings); adjectives MUST declare a type ('subclass' forms a class, 'data' asserts a boolean-ish datatype property, pattern 8); verbs may declare a preposition ('depend' + 'on' \u2192 dependsOn). The human-domain additions are flat and simple (breadth over depth \u2014 no gender/kinship taxonomy, no formal role hierarchy), matching corpus/tier2/generate.mjs's CORPUSES.human.lexicon sub-key, which --verify drift-checks against. Extend via loadLexicon(extra) with this same shape.",
+        comment: "tmct's starter lexicon, now covering BOTH the original software domain and the default 'human-world' persona's everyday people/places/objects/nature/time/body/mind vocabulary. Every word the ACE-OWL sub-fragment parser (src/domain/grammar/ace.mjs) is allowed to understand is DECLARED here \u2014 tmct never guesses a word's category. Nouns may declare a possessive property typing ('data' or 'object', pattern 7) or an irregular 'plural' (WordNet-sourced human nouns like 'man'/'child' need this \u2014 the morphology fold only handles regular -s/-ies/-es endings); adjectives MUST declare a type ('subclass' forms a class, 'data' asserts a boolean-ish datatype property, pattern 8); verbs may declare a preposition ('depend' + 'on' \u2192 dependsOn). The human-domain additions are flat and simple (breadth over depth \u2014 no gender/kinship taxonomy, no formal role hierarchy), matching corpus/tier2/generate.mjs's CORPUSES.human.lexicon sub-key, which --verify drift-checks against. Extend via loadLexicon(extra) with this same shape.",
         nouns: {
           module: {},
           class: {},

package/ROADMAP.md

@@ -1,130 +0,0 @@
-# ROADMAP — tmct's current shape and what's next
-
-Forward-looking at a **feature level**: what tmct is capable of right now, and what's planned next.
-No session narrative, no dated diary, no "shipped/DONE" history — that's what git log and the
-`archive/`/`BENCHMARK_*.md`/`CAPABILITIES_*.md` records are for. For **task-level** pickup (specific
-open items, session-scoped), see `HANDOVER.md` instead — this file doesn't duplicate that list.
-
-## What tmct is
-
-A tolerant, ELIZA/PARRY-style chat surface over a codebase, obsessed with software the way PARRY was
-obsessed with the mafia — deterministic, zero-cost, **no LLM anywhere in the product path**. Guides a
-user toward precision queries rather than guessing; every answer is grounded, restates every genuine
-reading it finds in full, or is an honest miss when nothing grounds it at all. Its visual surfaces —
-the ledger explorer with its in-browser chat (`tmct viz`), the animated plan page
-(`chat --prompt … --render blocks`), and the Pages homepage hero — are the same graph read out loud:
-same engine, same provenance, no LLM.
-
-## Ambition
-
-Declared, forward-looking goals — not yet achieved, stated here so they steer future work instead of
-getting silently traded away by inherited caution:
-
-- **Reach for Llama-3-level natural language fluency.** by growing rich
-  template/surface-realization variety, so an answer shape has many valid phrasings instead of one
-  fixed slot-fill.
-- **Resolve ambiguity breadth-first, always.** Every genuinely valid reading gets its own real answer
-  restated in full, never a bare "could mean X or Y — try rephrasing" punt, bounded only by existing
-  clipping/pagination limits. L
-- **Paraphrase alongside the original, verified, never instead of it.** A surface-realization variant
-  sits next to the literal grounded answer, never replacing it, and its accuracy is checked, not
-  assumed — by running tmct's own deterministic inference/consistency machinery (`src/domain/syllogise.mjs`)
-  against both the original and the paraphrase: they must entail the same conclusions, and neither may
-  contradict the other sentence-by-sentence..
-
-
-## What's next (feature-shaped — see `HANDOVER.md` for the current task-level list)
-
-- **`PLAN_ADVENTURE.md`** — a text-adventure architectural stretch. Its world-state and
-  actions-as-data substrate shipped generically with the planning lane (action rule kinds,
-  per-step board snapshots, legal-move enumeration); what remains its own is the imperative
-  command grammar ("go north", "take the key"), the NPC turn scheduler, the Ashcombe Hall
-  corpus, and the room-look digest.
-- **`PLAN_SYLLOGIST.md`** — the reasoning engine's research horizon. The single-justification
-  retraction slice shipped (`retractSubClassOf`, justification persistence and cascade across all
-  five rules); still open there: the ATMS generalization (alternate justification sets per fact),
-  incremental matching (§2), and relevance under budget (§4).
-- **`PLAN_GUESS_NUMBER.md`** — closed-loop planning over hidden state (belief-interval bisection,
-  thinker-mode secret commitment, observation folding) on top of the shipped planner substrate.
-  Design-only.
-- **`PLAN_CODE.md`** — small JS-function and HTML/CSS-fragment synthesis, plus goal-directed
-  program repair (tests as the goal state, mutation templates as planning actions), via a sandboxed
-  headless browser (Track 1, rule/frame synthesis, already shipped). Blocked on a sandbox
-  dependency decision.
-- **`PLAN_AGENTS.md`** — the governing plan for tmct's broader multi-repo arc (marginalia, seonix,
-  a pluggable LLM rung for Claude Code/Bedrock/Copilot). Check its own sequencing table for current
-  phase status, not this file.
-
-
-## Research horizon
-
-*(2026-07-08 research pass — a direction recorded so it isn't re-discovered from scratch, not a
-committed build plan. Nothing below is scheduled.)*
-
-**Before the horizon — known-how, no research risk**, just scheduling: `PLAN_CODE.md` Tracks 2-4
-(mutation search/repair, JS/HTML/CSS synthesis — APR and CEGIS are established techniques);
-RETE/incremental forward-chaining (`PLAN_SYLLOGIST.md` §2 — Forgy 1982, a citable algorithm not yet
-ported); contingent/conformant planning under initial-state uncertainty (Bonet & Geffner 2000,
-Hoffmann & Brafman 2006, Petrick & Bacchus 2002 all have working algorithms, none yet applied here).
-
-**After the horizon — genuinely unsolved in the field**, named as real research targets with
-citations, not stop signs:
-- **The frame problem / relevance realization** (open-world planning boundary). McCarthy & Hayes
-  1969 named it; Jaeger, Riedl, Djedovic, Vervaeke & Walsh (2024) argue it may not be algorithmically
-  solvable in the general case. Speculative angle: bounded (N+1) goal recognition — recognize
-  declared goal 1..N, or reject to an explicit "escalate" class, via parse-shape membership.
-- **Bounded, incremental, trust-tiered, retraction-safe justification tracking** — `PLAN_SYLLOGIST.md`
-  §3. Doyle's JTMS (1979) and de Kleer's ATMS (1986) solve retraction; DRed/RDFox's Backward-Forward
-  solve incremental Datalog maintenance; nobody's published the combination with tmct's
-  multi-trust-tier, hard-budget requirement. The JTMS-lite slice shipped (one persisted
-  justification per entailed fact, VERIFY-backed retraction, all five rules); the open piece is the
-  ATMS generalization — alternate justification SETS per fact (see that doc's 2026-07-15 addendum).
-- **A shared ~2M-word cross-domain ontology** (general-English + technical/scientific/programming).
-  Merging collides senses of lexically-shared words (`class`, `cache`, `thread`, `field`, `state`)
-  across registers; knowledge-based WSD is real but weaker than supervised/neural WSD (Lesk 1986;
-  Raganato, Camacho-Collados & Navigli, EACL 2017). BabelNet proves cross-resource sense merging is
-  achievable at scale but solves the cross-*lingual*, not cross-*domain*, axis, and carries a
-  non-commercial licence. Speculative angle: mutual disambiguation from already-resolved neighbouring
-  terms in tmct's own closed graph (a bounded reading of Gale/Church/Yarowsky's "one sense per
-  discourse" regularity) — not published anywhere found for this application. Fresh live instance
-  (2026-07-11): `"tail"` (Unix process vs. animal body part) collides under `normFactTerm`'s
-  cross-corpus flattening, `src/adapters/memory/core.mjs:1109-1134`.
-
-**Tier-4: learn-on-miss acquisition**. The strongest
-miss signal tmct can emit: lexicon term recognized, query built cleanly, zero matches anywhere — the
-question was well-formed and the knowledge is simply absent. Web search on the resolved term → clean
-the fetched text into the ACE-OWL controlled grammar → store with source provenance → answer the
-original question, citing what was just learned. Strictly opt-in, offline default inviolable.
-Prerequisites: the provenance-trust policy must extend to `via:"learned:web"`, never silently
-blending web-sourced facts with graph/operator facts.
-
-## Design docs
-
-Every substantial design lives in its own `PLAN_*.md` at the repo root; `archive/` holds the shipped
-and closed ones. This file points to them, it doesn't repeat their content. Each plan states its own
-status in its opening lines — read it there, because a status quoted here would rot.
-
-| Plan | What it's for |
-| --- | --- |
-| [PLAN_ADVENTURE.md](PLAN_ADVENTURE.md) | a text adventure as an architectural stretch: imperative command grammar, NPC turn scheduler, room-look digest |
-| [PLAN_AGENTS.md](PLAN_AGENTS.md) | the governing plan for the multi-repo arc (marginalia, seonix, a pluggable LLM rung), with its own phase sequencing |
-| [PLAN_CHILD_CORPUS.md](PLAN_CHILD_CORPUS.md) | a wider default seed corpus, chosen by age of acquisition |
-| [PLAN_CLASS_QUERY.md](PLAN_CLASS_QUERY.md) | "list/count all X of class Y", reconciled against what already shipped |
-| [PLAN_CODE.md](PLAN_CODE.md) | program synthesis over tmct's closed DSLs, plus JS/HTML/CSS fragments and goal-directed program repair |
-| [PLAN_CONSISTENCY_CHECK.md](PLAN_CONSISTENCY_CHECK.md) | tmct as a consistency service for an LLM tool loop |
-| [PLAN_DIALOGUE_ACTS.md](PLAN_DIALOGUE_ACTS.md) | naming tmct's turn types to ISO 24617-2 dialogue acts, deterministically |
-| [PLAN_EMBEDDINGS.md](PLAN_EMBEDDINGS.md) | the semantic-similarity axis, and the way back to it |
-| [PLAN_GRAPH_SCAN.md](PLAN_GRAPH_SCAN.md) | seed and query cost at `init:xl`/`init:xxl` corpus scale |
-| [PLAN_GUESS_NUMBER.md](PLAN_GUESS_NUMBER.md) | closed-loop planning over hidden state, via belief-interval bisection |
-| [PLAN_MUD.md](PLAN_MUD.md) | persistent, shared tmct worlds over a `server:` memory backend |
-| [PLAN_NLU_BENCHMARKS.md](PLAN_NLU_BENCHMARKS.md) | scoring tmct on the CLINC150 and HWU64 intent sets |
-| [PLAN_OPEN_ITEMS.md](archive/PLAN_OPEN_ITEMS.md) | delivered — the 2.0.3-cycle build order, archived |
-| [PLAN_PARAPHRASE_VERIFICATION.md](PLAN_PARAPHRASE_VERIFICATION.md) | checking a paraphrase against the graph before it prints |
-| [PLAN_PURGE.md](archive/PLAN_PURGE.md) | delivered — promoted the load-bearing code, deleted the dead weight, archived |
-| [PLAN_REPO_INDEX.md](PLAN_REPO_INDEX.md) | tmct grows its own code parsers, ported from seonix |
-| [PLAN_SYLLOGIST.md](PLAN_SYLLOGIST.md) | the reasoning engine's incrementality and retraction horizon |
-| [PLAN_SYLLOGIST_EL_DL.md](PLAN_SYLLOGIST_EL_DL.md) | beyond OWL 2 RL: an EL classifier, then a DL tableau prover |
-
-`SKILL_*.md` docs specify the repeatable measurement and build cycles (the benchmarks, the capability
-audit, the background strategy advisor, plain-prose writing). `HANDOVER.md` is the single
-current-open-items list.