Governance

Source, Manual, Website, And Accessibility Gates

This site supports x64base.com by publishing reviewed DotTalk++ documentation without becoming detached from implementation evidence.

Coding standards
Command registration
Documentation contracts
SelfDoc feed
Public-content guard
Artifact policy
Manual release policy
README preservation
Planned lanes must stay labeled
Accessibility status

Cross-Site Relationship

x64base.com

Ecosystem home for the engine, product family, DBF_64/FPT64 specs, Laboratory Campus, project story, and selected evidence.

dottalkpp.com

Likely public identity for the focused technical library: manuals, command references, generated documentation, proof reports, and downloadable document bundles.

derald.com

Optional staging, storage, retrieval, and operator-facing organization surface. It should not become confusing product branding.

Source authority

Runtime behavior, command syntax, file formats, mutators, table buffering, HELP, metadata, SelfDoc, and MDO remain upstream of public prose.

Publication Gates

Implementation evidence -> reviewed manuals -> website summaries
Manual sections may feed this site after review and proof labeling
Website prose must not become manual truth unless the artifact is website-owned and non-derivable
README.* files are preserved as orientation and provenance artifacts
Domain ownership or WHOIS observations require owner verification before public claims
Downloads need artifact class, proof status, and accessibility status

Authority Flow

Technical claims should move through this chain before becoming public-facing documentation.

implementation/source evidence
-> HELP / metadata / comments / contracts
-> SelfDoc / MDO
-> manualgen
-> reviewed manuals
-> x64base.com summaries
-> DotTalk++ manual-room pages

Planned Lanes Stay Labeled

When the world changes your schema

Student lesson using Y2K, the Euro, ERP modernization, and PRONOUNS semantic fields to ask whether a system can adapt safely before it is replaced.

PRONOUNS semantic field hook

Design lane for character-backed semantic metadata, validation, normalization, and optional SEX relationship rules. Not a current runtime claim.

Custom field behaviors

Future handlers should resolve through metadata/DDICT/FIELDMGR and prove behavior across REPLACE, MULTIREP, CALCWRITE, buffering, import/export, FIELDS, STRUCT, and SelfDoc.

Domain split

dottalkpp.com is the intended reviewed public manual/reference face; derald.com can remain staging, storage, and retrieval support. dottalk.com should only be discussed publicly after owner verification.