WEBSITE ALPHA · AI-assisted, source-reviewed documentation · Full-stack docs reconciled 2026-08-26
64x64base

Current Project Truth

Canonical public authority, evidence order, beta status, and current limitations for x64base.

Canonical public source

The public main branch is authoritative for collaboration, CI, licensing, releases, and public technical claims.

Local implementation trees, recovery branches, staging mirrors, generated manual trees, and this website may contain newer experiments. They do not supersede public main until source, tests, and documentation are promoted through a reviewed public change.

Evidence order

  1. Tagged release, checksum, release notes, and known limitations.
  2. Green main CI for the referenced commit.
  3. Repeatable CTest or runtime proof stored with that commit.
  4. Source evidence labeled active beta or canary.
  5. Design work labeled planned.

Documentation, SelfDoc, MDO, and website prose explain evidence. They do not create runtime truth by themselves.

Current documentation publication

The 2026-07-18 documentation checkpoint completed nine of nine controlled gates. The accepted Markdown manual, 183-page command-reference snapshot, and 11-path website projection are public and live-verified. The following Pinocchio benchmark and documentation-closeout delta remains development evidence pending source-history promotion; the website labels it rather than silently treating it as current public runtime truth.

See Documentation Progress.

2026-08-26 update -- full-stack documentation flush (DOCFLUSH-20260825-001)

The current full-stack run refreshed HELP and the canonical HELP/META harvest, then re-derived the website catalogs. The development tree now projects 239 central-shell command keys and 75 function rows (73 core FunctionDoc rows plus 2 self-registering extension examples). HELP contains 670 reachable topics and 29,480 line rows, while the canonical harvest matches all 14 required tables. These are development and local-site measurements, not public runtime truth. The public main figures remain those of the last promoted release until this work passes its distinct source-staging, website-signoff, publication, and live readback gates.

Current status

DotTalk++ / x64base is active beta research and education software, not a finished commercial database product.

The public baseline contains a C++20 DBF-family runtime, DotTalk++ command shell, work areas, fields and records, memo architecture, index lanes, relations, scripts, HELP/metadata work, and optional UI experiments. Each lane must carry its own test and maturity status; the existence of source does not prove production readiness.

An identity / AI-BBS lane has since landed in source, using libsodium for Argon2id password hashing and a CSPRNG (linked as a required build library). A standalone BBS agent-server daemon (dottalk_bbsd) can run this lane headless, bound to loopback (127.0.0.1) only. Both are active-beta source evidence on the development side, not a promoted public guarantee.

Important limitations

  • No atomic transaction guarantee spans DBF, memo, and index persistence. The buffered table-lane did gain a scoped, proof-backed write-ahead redo log (2026-07-19) that rates its Atomicity and Durability Partial, but that is a single-lane gain and does not extend across the direct/non-buffered paths or a multi-store DBF + memo + index transaction (see ACID and the Glass-Box Engine).
  • x64 widening is backend- and command-path-specific, not universal unlimited scale.
  • GUI/TUI, Python, SelfDoc, and Laboratory Campus work are optional research or education lanes around the public core.
  • The project is dual-licensed (decided 2026-08-08): GPLv3 for open-source, educational, and personal use, plus a separate commercial license for closed or proprietary use. See Licensing and the repository LICENSE / LICENSING.md.
  • Binary artifacts are supported only when published as a versioned GitHub release with checksums.
  • Pinocchio navigation improvements are historical development evidence, not a tagged-release performance guarantee; the original run transcripts did not self-record the machine (the machine is now maintainer-attested — all runs on one Alienware m16 R2 / Core Ultra 9 185H), and the post-correction raw transcript was not located.
  • The separate DotTalk++ artifact domain is not promoted while its HTTPS certificate is unhealthy.

See Current Work Lanes, Getting Started, and Downloads.

← Academic Positioning
Recursive Co-development →