Core rule
D:\code\ccode is the implementation truth.
D:\dev\x64base-site is the public publication surface.
The site should present reviewed, provenance-aware derivatives of the runtime, contracts, HELP, metadata, manuals, and diagrams. It should not invent technical truth on its own.
Public source
- Public GitHub repo: deraldg/x64base
- Local implementation tree:
D:\code\ccode - Local site tree:
D:\dev\x64base-site
Shared document model
Use this split:
- Runtime/source/contracts/manual truth lives in
D:\code\ccode - Public website framing and navigation live in
D:\dev\x64base-site - Shared diagrams and publication artifacts should be promoted from reviewed SelfDoc/manual outputs, not rewritten from memory
Front-end naming rule
ArcticTalkis the public umbrella brand for the front-end familyFoxtalkand fox-derived names remain valid lineage/subsystem names- Classic FoxPro-style syntax may remain for historical and educational reasons
- DotTalk++ should not be described as a clone
Educational goal
The stack is meant to teach full-stack thinking from beginning to end:
- engine and file/runtime behavior
- command shell and automation
- HELP, metadata, and contracts
- manuals and diagrams
- GUI/TUI/front-end work
- public website publication
LabTalk is the natural education-facing frame for this goal.