This page keeps active lanes visible without crowding the homepage. Status is intentionally conservative.
| 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. |
| 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 GUI API | Active architecture lane; wxWidgets, Python/Tk, Turbo Vision/TUI, and browser surfaces should share engine services rather than duplicate table mechanics. |
| 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/LabTalk commands | Active; ASCII, BBOX, RETRO, SHELLO, IDX, BOOLEAN, CASE, COBOL, CODASYL, and related commands should feed LabTalk curriculum with proof labels. |
| Security | Active diagnostics/policy lane; SECURITY and security policy/runtime headers exist. |
| 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. |
| POSIX/macOS builds | Active requirement lane; WSL/Ubuntu/macOS requirements are documented, but each build result should be tagged with compiler and OS evidence. |
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.