SelfDoc outputs
Generated reports from runtime, command, metadata, help, and source-contract layers.
Manual room for the x64base command surface
DotTalk++
Command shell, script language, and self-documenting database workbench for the x64base system.
DOTHELP MANUALS CMDHELP COMMANDS SELFDOCCHECK STATUS publication lane: source/runtime truth -> HELP and metadata -> SelfDoc collection -> MDO curation -> versioned public docs
Site roleFocused documentation home
Current stateStaging skeleton
Publication ruleProof labels required
Source postureGenerated docs must be reviewed
What This Site Handles
`dottalkpp.com` is not a second marketing site. It is the deeper technical library for DotTalk++ manuals, references, generated documentation, proof reports, and downloadable documentation bundles.
What Stays at x64base.com
`x64base.com` remains the ecosystem home for the engine, DBF_64 and FPT64 specifications, product family overview, Laboratory Campus, project history, and selected public evidence.
Manuals
Curated and Versioned Manuals
DotTalk++ User Manual
DotScript Language Guide
Command Reference
Function Reference
Developer Manual
SelfDoc Manual
MDO Manual
Versioned manual snapshots
DotScript
Readable Scripts for Repeatable Work
DotScript is the script form of the DotTalk++ command language. It should document variables, comments, continuation, IF/ELSE/ENDIF, LOOP/ENDLOOP, WHILE, UNTIL, SCAN, nesting limits, examples, smoke scripts, and mutation-safe automation.
* Inspect a current lab table. USE students STRUCT LIST IF recno() = 1 ? "first record" ENDIF
Reference
Command and Runtime Reference Lanes
CommandsFunctionsSET familyData mutatorsWorkspaces and areasTable bufferingRelationsIndexingMemosSemantic field hooksDDLImport/exportExternal app commandsHELP / CMDHELP / CMDHELPCHK
Generated Docs
Generated First, Reviewed Before Trust
MDO curation
Curated report and manual lanes that turn generated material into public documentation.
Command contracts
Source-derived command metadata, usage contracts, proof labels, and review status.
Proof reports
Runtime transcripts, canary outputs, CMDHELPCHK reports, and generated proof indexes.
Manualgen outputs
Inventories, validation results, dry-run manuals, accepted sections, and publication manifests.
Relationship
Companion Site, Not a Replacement
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.
source/runtime evidence -> HELP, metadata, comments, contracts -> SelfDoc and MDO collection -> manualgen inventory and validation -> reviewed manual sections -> x64base.com summaries and DotTalk++ manual-room pages
Developer
Rules for Public Documentation
Public pages must avoid private local paths, unsupported feature claims, and private artifacts. Each generated document should carry a date, source snapshot label, generator name, proof level, and review status.
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
Publication Gates
Rules That Prevent Documentation Drift
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
Planned Lanes
Design Work That Must 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.
Downloads
Artifact Policy Before Bulk Uploads
Large PDFs, generated reports, and release documentation bundles should be classified before publication. Public pages can describe private or local artifacts, but should only link reviewed public assets stored in the site, release system, or approved object storage.