This page keeps active lanes visible without crowding the homepage. Status is intentionally conservative.
Some omissions on the public site are genuine documentation deficiencies. Others are under-development lanes that should remain labeled alpha, planned, canary, or review-needed until they have proof. The site should not turn every unfinished lane into a negative claim; it should show what exists, what is being shaped, and what kind of review is needed next.
| Lane | Current position |
|---|---|
| x64base table runtime | Active beta; DBF-style DbArea runtime, cursor state, record operations, fields, and structure inspection are runtime-evidenced. |
| DBF flavor trinity | Active; classic/MS-DOS DBF, VFP DBF, and x64 DBF_64 are all represented in the current headers and runtime flavor detection. |
| RAM DBF / VDISK | Active development lane; the in-process virtual disk can host X64 DBF tables and native CDX-V64 indexes entirely in RAM. VDISK UNMOUNT, OFF, and CLEAR destroy resident files, so the public contract treats it as process-local transient storage rather than durable persistence. |
| x64 and VFP storage formats | Active; VFP field/data type compatibility and x64 DBF metadata/type extension work have source and probe evidence. |
| Vectored names | Active; x64 metadata owns longer table/field vectors with fallback mangling policy evidence. |
| Workspaces and areas | Active; workspace commands wrap active DbArea objects and preserve area/table/session state. |
| Memo subsystem | Active/canary mix; memo manager/object/reference/store architecture is source-evidenced and command-visible through memo/display/browser surfaces. |
| Index subsystem | Active; INX/CNX/CDX/LMDB surfaces are command-visible, with Open Index API boundaries still needing careful public API wording. |
| SET family | Active; session/output settings, path slots, table buffering, filters, relations, locale, SET INDEX, SET ORDER, SET CNX/CDX/LMDB, and SET UNIQUE are command-visible. |
| Record locking | Active; LOCK/UNLOCK and lock cleanup have command and source evidence. |
| Buffered editing | Active; dirty state, table buffer, COMMIT, ROLLBACK, REPLACE, and CALCWRITE are runtime-evidenced. |
| Triggers/rules/validation | Active; TRIGGER, RULE, constraints, and validation hooks are present, but public copy should distinguish proof level by command. |
| DDL/schema | Active; DDL FETCH, DDL VALIDATE, and DDL CREATE DBF are command-visible with filesystem, network, DBF, sidecar, and seed caveats documented by contract. |
| Data Dictionary/DDICT | Active; DDICT is a read-only inspection lane for DD* aliases and DATA_DICTIONARY_* catalog evidence. |
| DotTalk++ command shell | Active; command catalog is harvested from registry/usage contracts and should be regenerated after command changes. |
| DotScript | Active; command files, variables, IF/ELSE/ENDIF, LOOP/ENDLOOP, WHILE/ENDWHILE, UNTIL/ENDUNTIL, SCAN/ENDSCAN, comments, line continuation, and one-level subscript nesting are now a product lane. |
| Messaging and errors | Active; message catalog, output routing, and error/status command surfaces are present. |
| Locale/language | Active/integration lane; locale and message-spine docs exist and should be described as integration work unless runtime proof is specific. |
| Open Index API | Active architecture lane; INX, CNX, CDX, and LMDB-backed indexing should share clear public boundaries for attach, rebuild, order, seek, and backend diagnostics instead of leaking implementation-specific mechanics into every caller. |
| Open GUI API | Active architecture lane; wxWidgets, Python/Tk, Turbo Vision/TUI, and browser surfaces should share engine services rather than duplicate table mechanics. |
| Application UI DSL / UIDEF (AIF-120) | Alpha project in progress. A DBF/FPT design-table contract, importers, manifest/refusal checks, and wxWidgets, Tk, HTML, and character-cell consumers exist in development. Generated wx frontends reach real engine data and locks. The user-facing CREATE WINDOW / DEFINE BUTTON text commands remain planned, and known target limits stay explicit. |
| Historical source lineage | Active preservation lane; xBase, XDLL, xBase2/DotTalk, recovery folders, AI-assisted false starts, and modern DotTalk++ should be inventoried with checksums, proof labels, and feature tags. |
| SmartList/table/browser family | Active; SMARTLIST, SMARTBROWSE, SM, SMART, SIMPLEBROWSE, SB, BROWSE, BROWSER, BROWSETUI, and relation browsers are command-visible. |
| SQL/import/export | Active; SQL-like commands, SQLite wrapper, CSV import/export to and from DBF, copy, and tuple export are command-visible. |
| External app/network commands | Active; EDIT, TEXT, IMAGE, WEB, SFTP, PSHELL, shell, and ZIP surfaces need explicit external-app/network/filesystem risk wording. |
| Education / Laboratory Campus commands | Alpha/active mix; ASCII, BBOX, RETRO, SHELLO, IDX, BOOLEAN, CASE, COBOL, CODASYL, and related commands should feed campus curriculum with proof labels. Some campus material is implemented, some is planning, and some is intentionally open for collaboration. |
| AI Portal | Alpha/Experimental; current orientation documents, registries, launcher, and MAINT AI readback are useful seeds. Typed graph validation, bounded task-context compilation, guarded execution, x64base round trips, recovery, and evaluation remain promotion gates. It is not production autonomous memory or an authority source. |
| Identity, authentication, and RBAC | Active development lane; persisted HUMAN/AI/SERVICE members, roles, permissions, direct and request-based grants, login sessions, acting identity, AI/service tokens, owner-gated administration, degraded read-only boot behavior, and host-shell/runtime enforcement chokepoints have source and runtime proof. Public promotion remains gated by the open M4/M5/M6 closeout work. |
Legacy SECURITY diagnostics | Active compatibility lane; SECURITY LOGIN selects only the command's legacy diagnostic role and grants no authenticated identity or RBAC access. USER LOGIN, LOGOUT, WHOAMI, and CAN own the authenticated model. |
| SelfDoc/help/manualgen/maintenance | Active; source contracts, comments evidence, HELP, CMDHELP, CMDHELPCHK, MAINT, DDICT, MANUAL, BBOX, SelfDoc reports, and manualgen are curated procedurally with report-only defaults. |
| Full-stack documentation flush | The 2026-07-18 nine-gate public checkpoint remains sealed. Current run DOCFLUSH-20260825-001 is closed in the development tree and review-needed: 1,082 tracked source files carry the universal file contract; 231 files carry usage contracts; HELP has 670 reachable topics and 29,480 lines; the canonical harvest matches 14/14 required tables; and the local website catalogs project 239/239 command keys plus 73 core and 2 extension functions. Entry rows E0-E7 are proven. E8 remains the owner gate for manual acceptance, source staging, and website publication; no public mutation is implied. |
| Comments collection and mutation audit | Active governance lane; current-source comment and contract snapshots establish an audit trail for unauthorized mutation. Reharvest follows major source changes, while snapshot mutation remains review-gated. |
| Pinocchio stress and benchmark lane | Phase 1 and the ordered-navigation timing closeout are runtime-proven at 1M/5.5M scale. An eight-row historical ledger and machine-capture rule are validated in development; historical machine identity is now maintainer-attested (Alienware m16 R2 / Intel Core Ultra 9 185H) rather than per-run auto-captured, the post-fix raw transcript was not located, and Phase 2 fault injection is deferred. |
| Messaging normalization | Active development lane; large source changes passed regression without obvious canaries, followed by a guarded COMMENTS reload, HELP rebuild, CMDHELPCHK, and focused command canaries. Public-source promotion remains a later review gate. |
| METACOLLECT-238 | Separate backlog mission; 238 metadata-collection findings were intentionally kept outside the completed documentation vertical so they can be triaged and resolved without silently rewriting accepted evidence. |
| POSIX/macOS builds | Active requirement lane; WSL/Ubuntu/macOS requirements are documented, but each build result should be tagged with compiler and OS evidence. |
| Academic collaboration | Opening soon; the project is seeking input from CS professors, database professors, technical writing teachers, general education specialists, and multiple schools of learning to shape lessons, best practices, campus structure, proof standards, and curriculum quality. |
| AI-BBS agent server | Active alpha; a loopback-only bulletin board over the DBF store (SYSBOARD/SYSTHREAD/SYSPOST), token-authenticated with Argon2id via libsodium. Six rooms including governance, a lounge, a guestbook, and the agent worklog. Per-board post permissions are enforced against the identity catalog, and board writes take the same cross-process table lock the engine uses for records. Runtime-evidenced; not exposed beyond 127.0.0.1. |
| Pseudo-chat and local inference | Active alpha; BBS CHAT bridges to a local Ollama model on 127.0.0.1:11434, gated by a chat.invoke permission. The design point is that it answers while network egress is blocked -- an AI member was runtime-observed being refused NET EGRESS OPEN, and loopback is exempt. Local inference over project material with nothing leaving the machine. The model is a service, not a member: it holds no identity and cannot act on its own. |
| Agent worklog and handoff | Active alpha; board.worklog is a simplex drop-point where an agent records what it did, what is open, what the next agent should pick up, and the risk. Structured as a single pipe-separated line carrying a run id, so a handoff resolves back to the run registry. Lets working context survive a session ending, since an agent's memory does not. An idle-connection timeout keeps one stuck client from wedging the single-threaded accept loop. |
| Agency model | Source-defined; names the frame the identity and RBAC work already implemented -- agency as the capacity to act plus accountability for having acted, standing on identity, authority, authentication, and accountability. The useful part is the exclusions: capability is not agency (a local model that writes good code is still a service), and influence is not authority (an external AI can plan a subsystem it has no right to commit). Feeds a student lesson. |
| Run traceability and source contracts | Active; every tracked C++ source file carries a @dottalk.file block naming its subsystem, layer, lane, and accountable owner -- 1,034 of 1,034, with a coverage gate that can fail a build on regression. A run registry records the author / planner / owner / committer split that git structurally cannot express, since one name lands on every commit. |
| Evidence layer | Active; proof transcripts, session closeouts, and the artifacts the proof registry cites are version-controlled, after a blanket ignore rule was found to be hiding them. A validator now checks that every registry citation resolves and is tracked, so a claim of runtime evidence can be checked from a clean clone rather than taken on trust. |
| Commit coordination (Hot Potato) | Design-intended; an advisory lock answering "who may commit next" on the shared development branch, mirroring the engine's own cooperative file locking -- one holder at a time, passed explicitly, force-released when stale. Models the real asymmetry that some agents hold direct repository access and others deliver through the maintainer. Not started. |
Website policy
Lanes can be public when they are useful and evidence-backed. They should not be flattened into a single “finished product” story. Public copy should preserve proof level and point readers toward the command catalog, feature crosswalk, and generated manual artifacts.
See also Documentation Progress, Pinocchio Engine Benchmarks, and Site Improvement Plan.