The two public sites share an upstream evidence spine but serve different readers and publication duties. They are complementary, independently versioned sites, not mirrors.
Roles updated 2026-08-11 (owner ruling; AIF-107). x64base.com is the
development and conception site -- the owner's imagination, inspiration, and
reality merge space, kept honest by evidence discipline. dottalkpp.com is the
lean public entry surface for the rest of the world: static HTML, six nav
items, an evidence-tiered status board, no glamour -- the same principle as the
engine's lean release on main. The earlier "technical library / artifact
room" plan for dottalkpp.com (which the diagrams below still depict) is
superseded; the diagrams are retained as design history until redrawn.
Inspect the diagrams: select any diagram to open its full-resolution SVG and use browser zoom for detailed labels and flows.
x64base.com
x64base.com is the main ecosystem and engine website. Its public surface owns:
- engine, DBF-family, memo, index, relation, and API documentation;
- DotTalk++, DotScript, workbench, and related product framing;
- Laboratory Campus, cases, education, evidence, and collaboration entry points;
- project truth, development lanes, standards, DFDs, and publication governance;
- selected public media, evidence summaries, and curated download routes.
Its technical claims derive from implementation, runtime, HELP, metadata,
contracts, proof, SelfDoc, MDO/manualgen, and reviewed manual/diagram evidence.
Its maintained website source tree produces a versioned GitHub Pages publication
in deraldg/x64base.
dottalkpp.com
dottalkpp.com is the lean public entry surface (role updated 2026-08-11,
AIF-107). Its public surface owns:
- a six-item navigation: About, Documentation, Status, Downloads, Schemas, Contact -- adding a seventh means removing one;
- the evidence-tiered status board (the only place growth rates live, with unstarted work listed);
- a changelog instead of news;
- plain vocabulary, gate-enforced (
check_site.py), with every capability claim carrying its evidence tier.
Its maintained source is build_lean_site.py in deraldg/dottalkpp -- the
generator is the source of truth, emitted HTML is never hand-edited -- and it
publishes through GitHub Pages to dottalkpp.com.
Connections Between The Sites
| Connection | Direction | Rule |
|---|---|---|
| Technical evidence | Upstream to both sites | Source/runtime/HELP/metadata/contracts/proof remain authoritative. |
| Ecosystem navigation | x64base.com -> dottalkpp.com | Send general readers to the lean entry site: current status, documentation, downloads. |
| Project context | dottalkpp.com -> x64base.com | Send readers to engine, products, Laboratory Campus, history, and governance context. |
| Artifact notices | Reviewed duplex | dottalkpp.com may contribute reviewed route summaries and downloadable-artifact notices to x64base.com. |
| Manual/website reverse flow | Blocked by default | Public prose does not become runtime or manual truth. |
| Public-only exception | Review gate | A separately owned, non-derivable artifact may flow upstream only with provenance. |
| Release history | Independent | Each site keeps its own source tree, build, routes, and version history. |
The shared rule is simple: one evidence spine, two publication roles. x64base.com is the development and conception space; dottalkpp.com is the lean front door for everyone else. Neither site replaces source or runtime authority.
See SelfDoc Website Publication, Website Documentation Matrix, and Important Documents.