Source of truth
Use D:\code\ccode as the authoritative local source tree for DotTalk++ / x64base work.
Use D:\dev\x64base-site as the website publication tree.
The site content was updated from a scan of:
- CMake build configuration.
- command reference docs.
- GUI docs under
docs/gui. - database safety docs under
docs/database. - source directories under
src/xbase,src/xindex,src/memo,src/cli,src/datadict, andbindings/pydottalk.
See Current Project Truth. See SelfDoc Website Publication.
Working principles
- Preserve the difference between runtime-proven, active, partial, experimental, and canary features.
- Treat DotTalk++ as the canonical runtime and command surface.
- Treat x64base as the engine/runtime/data layer, not as a separate polished product unless the source tree proves that packaging.
- Keep GUI descriptions top-down over the existing runtime. Do not imply wxWidgets, Tk, or TUI lanes own database semantics.
- Treat the website as downstream of SelfDoc, contracts, manuals, and reviewed runtime docs.
- Keep public GitHub links current where the site describes public work.
- Avoid placeholder CLI commands when the local command reference has real commands.
Shared document workflow
- Runtime/engineering truth belongs first in
D:\code\ccode. - Publication-ready manuals, contracts, and diagrams should be reviewed there before site promotion.
- The website should mirror or curate those reviewed materials, not replace them.
- If a technical claim diverges between the two trees, fix
D:\code\ccodefirst and then republish the site.
Education goal
One explicit project goal is to learn front-end work through the x64base / DotTalk++ / LabTalk stack.
That means learning:
- how runtime truth feeds UI truth,
- how CLI, TUI, GUI, and website layers align,
- how SelfDoc and manuals feed public-facing documentation,
- how to build a full-stack educational database system from source to site.
Build boundaries
Do not mutate DBFs, HELP data, metadata catalogs, or generated publication artifacts unless the task explicitly asks for that and the mutation path is understood.
The local CMake metacollect block calls out a safety boundary: no HELP DATA rebuild, no CMDHELPCHK mutation, and no DBF writes.
Contributing
See: Contribution Guide