Naming
- Use x64base for the platform name.
- Use DBF_64 and FPT64 exactly as written.
- Use product names consistently (DotTalk++, DotTalk++ Workbench, TupTalk, TableTalk, RelTalk, Parallel GUI/TUI, LabTalk).
- Use DotTalk++ Workbench as the family name for GUI, TUI, browser, and workbench surfaces.
- Use Arctic as the code name for the TUI surface, not as the family umbrella or a main product.
- Use TableTalk for table buffering, dirty/stale state, and commit/rollback workflows, not generic table browsing.
- Keep Foxtalk and related fox-derived names for lineage/subsystem references only where the source/evidence supports them.
- Preserve classic FoxPro-style syntax/history where true, but do not describe DotTalk++ as a clone.
Tone
- technical
- educational
- historically grounded
- modern and minimal
Style
- short sentences
- define terms once
- prefer examples over rhetoric