This matrix documents how the website is fed by the documentation system. It is not a claim that every page is fully automated today. The current site is a reviewed publication surface with a growing set of repeatable feeds from source, HELP, metadata, SelfDoc, manualgen, diagrams, and runtime proof.
Read this first for website maintenance (entry gate). Reading this matrix and classifying every page you will touch is the first step of the website phase -- the entry half of the matrix gate, paired with the closeout re-audit below. This matrix is itself
maintained_current: before editing any page, classify it here (static / maintained / maintained_current / derived / generated / reported) and honor the Direction Gates below. Never hand-edit ageneratedorderivedregion -- fix the source and regenerate. Closeout gate: on every full-stack push, once the website is approved, this matrix must be updated and re-audited to match the signed-off site (advanceLast audited, reclassify any changed pages, record new diagrams and feeds). The run does not close until the matrix is current -- a stale matrix is a fail-closed condition on the website signoff. Last audited: 2026-08-21 (Document FullStack push v5, DOCFLUSH-20260812-001. Writeback reconciliation: three pages carried "the writeback cycle is still chartered", which the 2026-08-21 both-toolchain proof made false. Corrected in/docs/engine/proven-capabilities,/docs/engine/ecosystem-feature-comparisonand/docs/engine/regression-and-proof-testing. Also/products/parallel-gui-tui, which gained the DotTalk++ Workbench description it had never carried -- written from owner-supplied runtime screenshots of a 2026-08-20 build, so the claims are runtime-observed rather than source-inferred. The preceding audit was 2026-08-10; the preceding owner-approved full-stack pass 4 was 2026-08-06. Next scheduled run: Document FullStack push v6).
Current local reconciliation -- pending owner website signoff: v6 (
DOCFLUSH-20260825-001) was audited on 2026-08-26 across every row below. Unblocked generated and maintained-current surfaces were refreshed from source; the exact disposition ledger remains in the owning run.current-workis deferred because its task-registry authority contains unrelated uncommitted work. This note does not advance Last audited: that stamp moves only after the owner reviews and signs off the rendered site revision.
Proof Rules
| Status | Meaning | Promotion Rule |
|---|---|---|
| runtime-evidenced | Source and runtime output or screenshots show the behavior. | Can be described as current behavior with conservative wording. |
| source-evidenced | Source, headers, registries, or contracts show the behavior. | Can be documented as implemented/source-defined, but should avoid runtime claims until tested. |
| help-catalog-evidenced | HELP, CMDHELP, command catalog, or metadata lists the surface. | Can seed catalog pages, then requires source/runtime review. |
| generated-reviewed | A report, matrix, manual section, or diagram was generated and reviewed before publication. | Can be promoted to website/manual copy with provenance. |
| manual-reviewed | A manual or reference artifact passed its documented review and acceptance gate. | Can be published with its pinned source snapshot, counts, and regeneration boundary. |
| planned-or-in-progress | The lane is real planning or active development, but not complete. | Keep under development docs and avoid product-complete wording. |
| review-needed | A scanner, memory note, or draft found something not yet verified. | Do not promote as a stable website claim. |
Maintenance Classes
| Class | Rule |
|---|---|
static | Deliberate website-owned copy; human review only. |
maintained | Hand-authored page that tracks a named subject; review when that subject changes. |
maintained_current | Permanent route with a replaceable present-state region; expose as_of_date, evidence state, and next gate while preserving event history. |
derived | Regenerate or review when its source evidence changes. |
generated | Regenerate from its authority; do not hand-edit generated regions. |
reported | Append-only measurement or checkpoint with pinned provenance. |
Direction Gates
| Flow | Gate | Website / Manual Rule |
|---|---|---|
| implementation checkout -> website | Simplex default | Most website data should be derived, harvested, calculated, or reviewed from source/runtime/HELP/metadata/SelfDoc/manualgen evidence. |
| implementation checkout -> manual | Simplex default | Manuals should consume the same upstream evidence rather than copying website prose. |
| manual -> website | Duplex reviewed | Reviewed manual sections may feed website summaries when proof labels and source anchors are preserved. |
| website -> manual | Blocked default | The manual should not consume from the website unless the website artifact is not derivable elsewhere and is maintained separately. |
| website-owned artifact -> manual | Exception | Allowed for curated screenshots, public-only media, branding, hosted-download metadata, or contact/navigation artifacts with provenance. |
Matrix Authority: Website Design and Retention
This matrix is not only a page-classification table. It is the authority of record for two website policies: design (how pages are structured and what each must carry) and retention (what must be preserved and how). A design or retention decision that is not reflected here is not yet policy. Both route through the same entry/closeout gate as any other website change: read the matrix before the pass, re-audit it at signoff.
Design authority
- Page structure follows maintenance class. The class decides how a page may be
edited and what it must expose:
maintained_currentcarries a present-state region withas_of_date, evidence state, and next gate;generated/derivedregions are produced by their authority and never hand-shaped. - Evidence before ornament. Every page must answer the Proofed Site Checklist below. Design may frame and organize evidence; it must not manufacture technical truth or hide the proof level.
- Diagrams. Conceptual/architectural diagrams are hand-authored
maintainedand kept in sync; data-carrying diagrams aregeneratedfrom the harvest (AIF-032). Source and generated image are kept together. - Naming and routes. Visible titles, nav labels, and prose use
DotTalk++; short route buckets may stay stable for continuity but are not the public brand. - New page types, hero/diagram placement conventions, and nav/section changes are design decisions and must be classified and recorded here when adopted.
- Image assets must be license-clean and watermark-free before publish. A
website-owned image is only publishable with a clear license and no stock
watermark. Open for the next push (v5):
public/images/talk-family/arctic-fox.png(the Arctic mascot) may carry a faint stock watermark -- verify its license and replace it with a clean copy at the same path before or during the v5 flush. Also open for v5:public/images/story/x64base-glass-engine.png(origin-story figure) has embedded number plaques that conflict and read as noise -- photoshop or Firefly them out (content-aware / generative remove; the in-environment image tools cannot do object removal), keeping the same path.
Retention authority
The website preserves history rather than overwriting it. The retention rule for a page or artifact is set by its class and by these gates:
maintained_current-- preserve event history. The present-state region is replaceable, but prior events and dates are retained, not erased.reported-- append-only. Measurements and checkpoints are appended with pinned provenance; a new run adds evidence, it does not replace the baseline.- README / orientation artifacts -- versioned. Preserve the prior version before replacing it; README history is project provenance.
- Historical source lineage -- byte-preserved. SHA-256-bound, read-only, private roots omitted; checksums and truth-level labels retained.
- Diagram sources retained with images. Never discard the
.mmd/.drawiosource when publishing a generated image. - Publication checkpoints -- pinned. Accepted manual/reference snapshots and the commits that served them are recorded and kept recoverable.
Retention is enforced at closeout: the matrix re-audit confirms that nothing which should have been preserved was overwritten during the pass.
2026-08-26 Site-Wide Freshness Sweep
This sweep examined the website page and content sources as a set, including dated claims, feeds, pages named current or live, and stable download links. The disposition is recorded even when the correct action was to retain a snapshot or defer regeneration. This prevents a broad route-bucket row from hiding a stale child page.
| Route or surface | Class | Freshness disposition | Enforced relationship |
|---|---|---|---|
Shared layout, /, /docs/dev/project-truth, /docs/dev/documentation-progress, /docs/dev/full-stack-documentation-push, /docs/dev/current-lanes | maintained_current | CURRENT -- reconciled through 2026-08-26; the shared banner reads the documentation-progress authority. | Layout and route copy bind to documentation-progress-v1.json; production build verifies the rendered tree. |
/news | maintained / generated feed | REFRESHED -- the current working log now leads the page, and three proof-written 2026-08-26 milestones cover the documentation closeout, MINIDB hydration, and the Alpha UIDEF lane. Older announcements and milestones remain intact below it. | news-current-status binds the working-log date and documentation measurement to the documentation-progress authority; news-current-status-first enforces its position above older announcements. |
/docs/dottalk/command-reference | maintained_current | REFRESHED -- current local snapshot moved first; prior snapshots retained. | command-reference-current-snapshot binds visible counts, date, candidate, and open gate to the progress artifact. |
/docs/dev/application-ui-dsl-lane, /docs/engine/in-memory-databases, /docs/engine/workspaces, related Workbench and MemoTalk product pages | maintained | REFRESHED_ALPHA -- current implementation and screenshots are featured; recursion and nesting remain early Alpha rather than completion claims. | Reviewed source/runtime evidence and the production build; no generated region is hand-edited. |
/docs/labtalk/current-work | maintained_current envelope / generated body | DEFERRED_SOURCE_DIRTY -- the 2026-08-05 body is retained but now visibly labeled as a stale registry snapshot. Regeneration waits for its independently modified authority. | current-work-freshness-disclosure binds the reason and the current documentation-status date. |
/docs/labtalk/agent-sync | maintained_current | RELABELED_SNAPSHOT -- the 2026-08-15a page no longer claims to be a live feed and points to current documentation status. | agent-sync-snapshot-disclosure rejects a return to undated live-current wording. |
/lab, /lab/* | maintained, local-only | FIXED_LOCAL_ROUTE -- the optional catch-all now emits an explicit empty-slug parameter, so the Lab index and its nested pages work under static export. | generateStaticParams() includes slug: []; the production export must contain both out/lab/index.html and each nested Lab page. Publication strips lab, and the publisher aborts if it survives. |
/docs/getting-started/faq | maintained | UPDATED -- reviewed 2026-08-26 against the changed MINIDB, multi-workspace, UIDEF, local gateway, and Lab-route claims. Future reconciliations must record UPDATED or NO_CHANGE. | faq-reconciliation-check binds the visible review date and required coverage markers to the documentation-progress authority. |
/downloads, /docs/dev/developer-manual, /docs/dev/manual-assembly | maintained envelope / reported artifacts | RELABELED_STAGED_SNAPSHOT -- stable links remain, but their 2026-07-23 manifest date and measurements are visible; the surrounding pages no longer claim automatic freshness. The immutable staged manual still contains period wording such as "live current"; replacing that artifact is blocked on the open owner acceptance/publication gate, not suitable for hand-editing. | Two manual-snapshot contracts bind visible date and counts to DEVELOPER_MANUAL_LATEST.json; retained artifact hashes remain unchanged. |
| Historical announcements, press material, benchmark checkpoints, accepted manual snapshots, historical source pages | reported / static | HISTORICAL_BY_DESIGN -- dates are retained as provenance, not rewritten to look recent. | Retention policy, pinned manifests, and ordinary link/build validation. |
The build runs check:freshness before page generation. Its self-test corrupts
one required marker in every contract and must observe every deliberate stale
variant fail.
Website Section Matrix
| Website Area | Public Pages | Primary Feed Lanes | Proof / Data-Mining Inputs | Current Publication State |
|---|---|---|---|---|
| Home and top-level positioning | /, /about, /products | Project truth, product naming, licensing, contributor review | content/docs/dev/project-truth.mdx, product pages, brand rules, local source review | Reviewed framing; not intended to carry detailed proof tables. 2026-08-10: homepage ecosystem cards gained SQLsel (the house SELECT; shipped operators oracle-proven, joins future) and a per-card maturity note + "latest state in ..." pointer to a maintained target (runtime evidence / docs progress / curriculum) -- labels stay stable, current state lives behind the pointer, per the no-perishable-claims rule. RelTalk card notes core runtime-proven (Cascade 58-relation traversal, 2026-08-10) with join/browse surfaces explicit-run; LabTalk labeled an alpha campus with proof-backed shipped lessons (deliberate hybrid, owner wording). 2026-08-11 tone-downs (owner ruling: x64base.com is the development/conception site, dottalkpp.com the lean public face): site-wide light mode added as DEFAULT with dark and system options (ThemeToggle in navbar; preference in localStorage; no-flash script in layout.tsx; palettes in globals.css via :root/html.dark); brand image on /brand reduced 75% to a reference figure (owner correction: the /brand social card, not the hero image -- hero panel restored to full size); hero CTA row gained the dottalkpp.com link; trademark references removed site-wide (no ™, no registration claims -- /brand/trademarks is now neutral "Project Names" attribution); licensing page cites GPL-3.0-only committed 2026-08-11. |
| Proven capabilities | /docs/engine/proven-capabilities | Engine regressions, session transcripts, source contracts | cmd_regression.cpp curated specs (MEM, INDEX_X64_CNX, CASCADE_ENV, SQLSEL_SELECT_V1), AIF-105 lane doc, src/memo/memo_ref.cpp, virtual-workspaces intake | maintained. The under-explained-features list (owner ask, 2026-08-10): proven behavior promoted to named features, EACH entry stating its evidence tier (runtime-proven / source-evidenced / chartered) and citing its regression or source. Hero stays modest by design; this page is where the cool gets explained. Entries demote the day their evidence tier says so. 2026-08-11: "Payload-agnostic memos" REWRITTEN and promoted source-evidenced -> runtime-proven (memo_zoo seeded harness: 6 driver personas, embedded-NUL payloads, shadow-model oracle, 20,500 generations / 104,044 ops / 4 seeds / ~215 reopen cycles / 0 divergences; contention and RAM-VFS residency explicitly NOT claimed); new entry "A database posture that lives inside the database" (runtime-proven via REGRESSION RUN WORKSPACE_MEMO: 43 areas + 58 relations saved into and restored from a memo, both walkers agreeing; catalog carries attribution, timestamp, env roots, append-history; memo-resident mini-databases stay chartered). Both entries name their unproven neighbors on purpose. 2026-08-11 (afternoon): the posture entry EXTENDED with the second increment -- the table-of-workspaces catalog (v2: auto-id, instance identity, measured dims, lineage), self-locating v3 postures (13 areas restored from a deliberately mis-set environment), timed memo->RAM hydration (24 files / 92 KB / 71-94 ms, census agreeing byte-for-byte, dismissal proven), and v3 session snapshots (cursors + selection + refresh restored; regressions WORKSPACE_V3 / WORKSPACE_RAM / WORKSPACE_SESSION); the entry also carries the day's recorded correction (memo sidecar landed on real disk -- the "zero disk writes" claim was measured false and corrected in place; RAM memo-store coverage chartered) plus the still-chartered writeback cycle. 2026-08-10 (late): added "Self-measuring governance" (runtime-proven on the project itself -- the rulings report caught the maintainers' hand-kept count drifted 20 vs measured 18; retirement sentinel + parser recognition, commit 7a38c7fb8). 2026-08-21 (flush v5): the posture entry's closing "still-chartered writeback cycle" PROMOTED chartered -> runtime-proven. WORKSPACE WRITEBACK closes the RAM/memo -> disk return leg; spec 44 WORKSPACE_WRITEBACK, twelve markers, each new arm shown to FAIL before its green was accepted. Recorded honestly rather than smoothed, because the page's own standard failed first: this claim was briefly published as "proven on both toolchains" when one transcript was a FALSE GREEN -- a run that wrote to one directory and asserted against another, closing green because it never read its own output. The claim was withdrawn, relative-path resolution was routed through paths::resolve_in_slot so one token names one directory to writer, reader and teardown alike, and the SECOND toolchain was only re-proven on 2026-08-21 (Windows/MSVC cac02a8b, 12/12, log workspace_writeback_windows_postfix_20260821.log, beside the post-fix Linux log from 2026-08-12). Still chartered and named on purpose: LMDB carriage, out of the RAM filesystem's scope by its own contract. |
| Schemas: a table of databases | /schemas (closing section) | AIF-070 catalog + MINIDB | WORKSPACES catalog; MEMO_RESIDENT_MINIDB_V1.md; build_vectors.cmake (area budget) | maintained. NEW 2026-08-11 (owner audit): documents the INVERSION at the end of the schema catalog -- every schema above is a database made of tables; this one is a table whose rows are databases (posture ~1 KB, or mini-database ~94 KB carrying the tables themselves). Includes "Why there is a Cascade-sized limit": the three real budgets (eager work-area slots, RAM doubling at transfer, LMDB's real-file contract) and the house growth doctrine -- strict first, then dynamic; a stated ceiling that refuses beats an elastic one that degrades. Cascade is the measuring stick. |
| Ecosystem feature comparison: new rows + oddball table | /docs/engine/ecosystem-feature-comparison | engine capabilities vs family | regression registry; the workspace lane docs | maintained. 2026-08-11 (owner audit): eight rows added to the Relational section (text snapshot, self-locating snapshot, session state, workspace-in-a-table, database-in-a-memo, RAM hydration, and the honest NO on simultaneous residency). NEW closing section "Unique and oddball features" -- behaviors with no column to sit in because no family member appears to claim them, each with an evidence tier, including the deliberately odd ones (the zoo harness, doctrine-carrying regressions, tests that record when they were wrong, the startup verse as a live carrier check). Rule for this section: it is not a reason to choose this project over a mature one, and says so. |
Docs landing (/docs) section cards | /docs | docs navigation surface | app/docs/page.tsx, config/sidebars.ts | 2026-08-11: adopted four missing section cards (Historical family tree, Historical source files, RAM DBF/VDISK, Identity & RBAC) from a stale duplicate site worktree -- held 2026-07-28 UI work, triaged per widows-and-orphans: this was the only unique content; the rest of its 18-file diff was already present via later sessions or superseded. The diff was preserved as a patch file beside the working tree before the duplicate was retired. |
| Engine Specifications | /docs/engine/specifications | engine source, gates, regressions | normalization gate output (command/function counts); build_vectors.cmake; AIF-078 measured slot cost; capacity-gate + realtime-index lanes; zoo + MINIDB measures | maintained. The page names count boundaries instead of presenting one ambiguous total. Reconciled 2026-08-26: 245 canonical runtime registrations, 239 central-shell website keys, 212 SYSCMD rows, 75 implemented function specs/SYSFUNC rows, and a 73-core-plus-2-extension website projection. If a figure disagrees with a current gate transcript, the transcript wins and this page is corrected. |
| x64base Engine product page | /products/x64base-engine | all engine doc pages | the pages it panels to | maintained. REBUILT 2026-08-11 (owner: the flagship page was "woefully crappy... not up to the standards of the rest"; owner design call: "maybe it just panels to link to the good pages"): now a hub -- a short honest overview plus panel tables (Start here / Storage / Runtime / Verification / Context), each row one page with a one-line promise of what it covers. Detail lives in the linked pages per pointer-over-copy. Closes with the evidence-tier reading guide so the status language travels with the map. |
| Workspaces (engine) | /docs/engine/workspaces | engine command surface + AIF-070 lane | src/cli/cmd_workspace.cpp; WORKSPACES catalog; regressions CASCADE_ENV / WORKSPACE_MEMO / WORKSPACE_V3 / WORKSPACE_RAM / WORKSPACE_SESSION / WORKSPACE_MINIDB; docs/maintenance/MEMO_RESIDENT_MINIDB_V1.md | maintained. NEW 2026-08-11 (owner audit): the whole WORKSPACE surface in one place -- keyword table (MEMO/V3/RAM/MINIDB, all opt-in, bare forms unchanged), what v3 adds and why v2 stays the default, the catalog's columns and supersede history, and the read-from-the-field oracle. Carries the HONEST multi-workspace section: many workspaces exist, one is live (load is a swap, not co-residency), and the four measured blockers -- first-match name resolution returning wrong rows, flat RAM residency, engine-wide relation scope, shared eager area budget -- stated as entry conditions for the multi-workspace lane rather than as a to-do list. 2026-08-26: the page now distinguishes runtime-proven MINIDB hydration from active Alpha work on concurrent, recursive and nested workspace management. Sharing is necessarily write-or-send because the RAM disk is in-process, which is why locking belongs at the disk boundary. |
| Coined vocabulary (glossary) | /docs/dev/coined-vocabulary | AI portal glossary lane | labtalk/ai_portal/AI_GLOSSARY_V1.md (maintained source; recall node doc.ai_glossary), developer manual README reading order | maintained pointer page, non-perishable by construction: describes the glossary's role and section families, deliberately does NOT copy entries (a copied glossary is a stale glossary). The glossary is global: manuals, website, and AI portal all point at the one maintained source. Registered in sidebars under Development. 2026-08-11: the learning-doctrine family line gains the house learning motto, "the iterative example" ("we regroup, go back and amend, and move forward"), promoted from the maintained glossary per the owner's "it needs promotions" -- one-line summary here, definition and founding instance live in the glossary, per this page's own pointer-over-copy rule. |
| DotTalk AI development history | /about/timeline, /about/ai-assisted-history | AIF-106 historical evidence publication; website history retention | Supplied DOTTALK-AI-EVIDENCE-V1; pyxbase.zip manifest and SHA-256; archive-member timestamps and hashes; private mailbox preservation metadata | reported. The page publishes the reviewed finding and evidence limits without republishing private messages or archives. Public convention: August 2, 2025 is direct; July 21 is probable. A new source discovery appends or revises the record explicitly; it must not silently erase the prior finding. |
| Public database schema catalog | /schemas/ | Historical database migration, database ecology, Cascade dual-carrier, HELP/metadata/SelfDoc lanes | labtalk/registries/database_ecology.yaml, DOTTALKPP_LABTALK_DATABASE_ECOLOGY_INVENTORY_V1.md, Cascade dual_schema_contract.json, Mermaid sources and SVG provenance | maintained. Public, navigation-visible schema-family catalog. Cascade gets detailed relational diagrams; MCC, HELP, metadata, governance, documentation, application, and fixture schemas receive a measured catalog section. Counts must be re-measured before update; derived indexes and replicas are not promoted as independent logical schemas. |
| ECO: ecoschema drill-down map | /eco/index.html (raw artifact, linked from top nav) | Ecosystem/lane structure; AIF claims; source-tree scan | tools/fullstack_docs/ecoschema_map.py (the generator) reading labtalk/registries/projects.yaml, labtalk/registries/proofs.yaml, coordination/aif/*.claim, and a scan of src/* | generated -- experimental skeleton, the house term (precedent: TUPLEDELTA, classified on the experimental inventory that moved to private development on 2026-08-17; public stub at /docs/dev/experimental), meaning it EXISTS AND RUNS while its completion is gated. Not "conceptual" and not "pre-alpha": the map is live and drills down today. What is incomplete is the ROUTE, not the artifact. DO NOT HAND-EDIT public/eco/index.html -- re-run the generator, re-copy, and compare hashes; a hand edit is silently reverted on the next generation and the site then disagrees with the tree. Shipped 2026-08-13 as the raw map on an owner ruling, with the teaching wrapper (edu_eco: prose classed maintained around the generated map, plus framing for the 4-of-41 registered-proof reading) kept as a possible improvement rather than chartered. TWO KNOWN GAPS carried openly: the artifact has NO <html> element, so Pagefind skips it and ECO is absent from site search (generator-side fix); and the 4-of-41 figure is published unframed, which reads as "the engine is 90 percent unproven" when the measured finding is that proofs.yaml indexes the PORTAL rather than the engine -- 57 records, 2 naming a path under src/ or include/, against 104 run transcripts and 51 registered REGRESSION specs on disk. |
| LMS proposal (received) | /lms-proposal/ (deck route; 13 slides under public/lms-proposal/slides/) | External-AI intake lane | docs/maintenance/external_ai_intake/specialty_lms_ecosystem_2026-08-09/MANIFEST.md (AIPR-20260809-COPILOT-001) | static. Received Microsoft Copilot proposal, preserved unchanged as prior art and authored with NO repository access. Names an "xBridge Protocol" that exists nowhere in the tree; RBAC matrix and KPI grid are proposals, KPI values are placeholders. Carries a standing unverified-proposal banner and links to the assessment. Never promote to manual or website copy as technical truth. Retitled "Specialty NON LMS Ecosystem" (owner, 2026-08-10; unhyphenated ruled the more professional form): deliberately fun, true, and not true -- no grading or management (true), while the system drifts toward a Learning Memory System (the other LMS). Scope is the shell x64base authors -- route metadata, iframe title, and deck.html's chrome label + tab title. Copilot's received slides are UNTOUCHED, so the cover hero still reads "The Unified Specialty LMS Ecosystem"; the contradiction between frame and content is intended. Amended 2026-08-10 evening (owner: "the user can't see it"): the chrome-only retitle was invisible in practice -- deck.html's top bar renders at opacity 0 until the pointer nears an edge, so the visible page affirmed "LMS" while only the tab title negated it. deck.html now carries an always-visible brand strip ("Specialty NON LMS Ecosystem -- our title") stacked with the unverified-proposal banner, above the still-untouched slides; the strip yields to the top bar on hover. Originals preserved at docs/maintenance/external_ai_intake/specialty_lms_ecosystem_2026-08-09/received_slides/. |
| LMS architecture assessment | /lms-architecture/ (deck route; slide documents under public/lms-architecture/sections/) | AI Portal onboarding lane, LabTalk campus/registry lane | AI_README.md, labtalk/ai_portal/AI_TIER1_SEED_V1.md, labtalk/ai_portal/TIER0_STATE.md, labtalk/portal/README.md, labtalk/registries/*.yaml counts | static. Report-only assessment by an AI partner, baselined at development @ 648967b74; source-evidenced, not runtime-proven. Carries no AIF claim and no ai-report-audit-v1 envelope, and is not repo authority -- every slide says so. Contradicts the aspirational Specialty LMS proposal deck by design; do not reconcile the two. |
| x64base Engine docs | /docs/engine/* | Source/runtime lane, SelfDoc feature crosswalk, DBF headers, index/memo lanes, ecosystem research | include/xbase.hpp, include/xbase_vfp.hpp, include/xbase_64.hpp, command source, labtalk/reports/selfdoc/x64base_engine_feature_crosswalk_v1.*, x64 canary scripts | Partly generated and reviewed. Feature crosswalk and x64 capacity math carry explicit evidence labels. |
| DotTalk++ docs | /docs/dottalk/* (stable route bucket for DotTalk++ docs) | HELP/CMDHELP lane, command registry, usage contracts, DotScript/manualgen lane | command source, @dottalk.usage blocks, CMDHELP, CMDHELPCHK, manualgen dry-runs, command/function catalog generators | Reviewed derivatives. Reconciled 2026-08-26: command catalog 239/239 with zero fallback; function catalog 73 core plus 2 extension rows; the count-bound command-harvest diagram carries the same 239/239. Route bucket stays stable and visible branding remains DotTalk++. Regenerate these artifacts when their source authorities change. |
| Command-reference snapshots | /docs/dottalk/command-reference | full-stack documentation, HELP/CMDHELP, usage contracts, manualgen candidate and accepted-publication lanes | public/artifacts/documentation-progress-v1.json, command catalog, manualgen run and accepted-artifact manifests | maintained_current. The newest local snapshot appears first and historical snapshots remain below it. scripts/check-site-freshness.mjs binds its visible date, command/contract coverage, fallback count, HELP measures, manual run, and first open publication gate to the progress artifact. A stale snapshot fails the production build. Added 2026-08-26 after a route-bucket audit refreshed the catalog but missed this child page. |
| Data mutator safety | /docs/dottalk/data-mutators (DotTalk++ route bucket), SET/buffer docs | Mutation audit lane, TableTalk buffer lane, stale/dirty proof, scalar function review | REPLACE, CALC, CALCWRITE, MULTIREP, COMMIT, ROLLBACK, SET TABLE BUFFER, dirty/stale runtime transcripts | Current page is explicitly mutation-sensitive and should be refreshed after mutator or scalar-evaluator changes. |
| DotTalk++ Workbench / Parallel GUI/TUI | /docs/talk-family/*, product pages | GUI/TUI boundary lane, Arctic TUI code-name lane, workbench naming lane | runtime screenshots, GUI source docs, BROWSETUI, BROWSETV, BROWSE, SMARTBROWSE, SB, workbench pages | Reviewed naming corrected: family is DotTalk++ Workbench; Arctic is the TUI code name. UIDEF is an active Alpha project with a design table and four consumers; its proposed text verbs remain planned. 2026-08-26: classified Alpha and featured paired runtime evidence for posture-only refusal versus complete MINIDB inspection and rebuild (94,200 container bytes; 24 members; 92,139 hydrated bytes; 13 tables; 11 index containers). Early multi-workspace recursion and nesting are discussed without being claimed complete. |
| Laboratory Campus | /docs/labtalk/* | Education lane, runtime evidence lane, campus planning lane | education commands, screenshots, SDLC diagrams, portal screenshots, lab/curriculum pages | Alpha/collaboration area. Pages must preserve the difference between existing features, planned labs, and collaboration proposals. 2026-08-10: cases-storyboard gained the first same-day runtime-proven live case (the pipeline that audited its own maintainers) plus the demonstrated-negation teaching method (glossary term); the case cites commit 7a38c7fb8 and the proven-capabilities self-measuring-governance entry. |
| Local-only Lab | /lab, /lab/* (local preview only) | website-owned experiments and review-needed drafts | content/lab/*.mdx, optional catch-all route, local-only navigation and output-strip guards | maintained, local-only. The root listing must be returned by generateStaticParams() as the empty optional slug as well as every nested page. Fixed and export-proven 2026-08-26 after /lab/ returned a development-server 500 while /lab/experimental was the only emitted static parameter. The route is noindex, removed from publication output, and guarded by publish abort if removal fails. |
| Getting Started FAQ | /docs/getting-started/faq | product terminology, current engine/workspace/UI lanes, contributor preview operations | current-lanes, UIDEF, MINIDB/workspace evidence, website route and startup contracts | maintained. Refreshed 2026-08-26 to explain MINIDB as whole database carriage rather than metadata, keep multi-workspace recursion/nesting Alpha, advance UIDEF from planned-only to Alpha implementation, and document the local 3000 -> 3002 gateway, local-only Lab, optional-root static parameter, restart, and export-readback rules. Matrix check: every full-stack reconciliation records UPDATED or NO_CHANGE; the visible FAQ review date must equal the documentation-progress as_of_date, or the site build fails. |
| Current tasks and projects | /docs/labtalk/current-work, /artifacts/current-work-v1.json | AI Portal project registry, governed task registry, Pseudo-Chat return lane | project/task status, owner, proof state, next gate, public review routes | maintained_current; regenerate at full-stack pushes and governed task closeouts. V6 disposition: DEFERRED_SOURCE_DIRTY because ai_portal_tasks.yaml contains an unrelated uncommitted correction. Do not publish a generated page from an uncommitted authority or absorb another lane's work. Pseudo-Chat remains an inbox, not a competing authority. |
| Staged developer-manual downloads | /downloads, /docs/dev/developer-manual, /docs/dev/manual-assembly, /downloads/current/* | manualgen staging and accepted-publication lanes | DEVELOPER_MANUAL_LATEST.json, staged artifacts and checksums, current documentation-progress candidate | Stable links are not an automatic freshness claim. The staged candidate is dated 2026-07-23 and remains distinct from the newer review-needed local candidate. Visible date and counts are freshness-contract bound to the download manifest. Period "live current" wording inside the hash-bound staged artifact is a recorded BLOCKED_PUBLICATION_GATE disposition until a new candidate is accepted; do not patch the artifact in place. |
| LMS communications lane | /docs/labtalk/lms-integration-lane | LabTalk LMS registry, provider-neutral message contract, local queue/CLI, portal execution lane | labtalk/lms/README.md, labtalk/registries/lms.yaml, src/labtalk/lms/pipe.py, src/labtalk/lms/cli.py, message schema, status transcript | Reserved/local-only integration slice. Local status and queue behavior are documented; Moodle remains a future candidate with live delivery disabled and no credentials or student data stored. |
| Runtime evidence gallery | /docs/labtalk/runtime-evidence | Evidence curation lane, screenshot/media lane | public/images/evidence/*.jpg, screenshot captions, runtime transcript notes | Curated website proof surface. Screenshots are evidence artifacts and should be replaced when current UI changes. |
| Important documents shelf | /docs/dev/important-documents | MDO lane, AI-friendly summaries, manual publication lane | SelfDoc/MDO summaries, diagrams, manualgen reports, reviewed document inventory | Current public shelf. The accepted Markdown manual and 183-page command-reference snapshot are linked with pinned provenance. |
| Documentation progress | /docs/dev/documentation-progress, /artifacts/documentation-progress-v1.json | Full-stack documentation lane, publication closeout, follow-up lane registry | gate ledger, progress milestones, accepted manual metadata, live-verification record, separate-mission state | maintained_current. Reconciled 2026-08-26 to v6 development closeout, HELP/harvest measurements, catalog regeneration, accepted-review-needed manual candidate, local website build, and E8 publication boundary. The site-wide banner reads this artifact's as_of_date and labels it "Full-stack docs reconciled"; it is not a per-edit or publication stamp. The sealed 2026-07-18 public checkpoint remains separate and unchanged. |
| RAM DBF and VDISK | /docs/engine/ram-dbf-vdisk | in-process RAM filesystem, X64 DBF, CDX-V64, path-state lane | src/cli/cmd_vdisk.cpp, HELP/CMDHELP, current command reference and assembled manual | Local reviewed derivative; transient lifetime and destructive unmount boundaries must remain explicit. |
| Identity, authentication, and RBAC | /docs/engine/identity-security | identity DBF store, sessions, roles/permissions, authorization, runtime-policy lane | src/cli/cmd_user.cpp, identity store/runtime headers, enforcement proofs, HELP/manual | Local reviewed derivative; development proof must not be promoted into a tagged-release claim, and SECURITY LOGIN remains a legacy diagnostic selector. |
| Pinocchio benchmarks | /docs/engine/pinocchio-benchmarks | Pinocchio stress-test lane, navigation performance closeout, historical benchmark ledger | retained Phase 1 closeout, navigation closeout, eight-row ledger, machine-profile contract | Historical development evidence is preserved in public source commit 853937f1. Machine identity is now maintainer-attested (Alienware m16 R2 / Intel Core Ultra 9 185H) rather than per-run auto-captured; the post-fix raw transcript was not located, and runtime-release status remains unproven. |
| dottalkpp.com lean entry site (external; role updated 2026-08-11, AIF-107) | https://dottalkpp.com (About/Documentation/Status/Downloads/Schemas/Contact) | AIF-107 low-key entry surface lane | deraldg/dottalkpp repo: build_lean_site.py (source of truth), check_site.py (link/vocabulary/metadata gate), CHANGELOG.md | External to this tree; recorded here because x64base.com links to it and describes its role. The earlier "artifact/manual room" plan is superseded: dottalkpp.com is the lean public entry surface (static HTML, evidence-tiered status board, changelog instead of news). x64base.com is the development/conception site. Never hand-edit the lean site's emitted HTML. |
| SelfDoc publication path | /docs/dev/selfdoc-feed-pipeline, /docs/dev/selfdoc-website-publication | Source-to-website feed lane, manualgen lane, contract scan lane, simplex/duplex publication gates | tools/manualgen, tools/selfdoc, comments/contracts scanners, generated reports, promotion rules, website-owned artifact exceptions | Reviewed process docs. Automation is partial; the rules are intentionally stricter than the current tooling. |
| Historical source lineage | /docs/dev/historical-source-lineage, /docs/dev/historical-family-tree, /docs/dev/historical-source-files | Preservation lane, provenance lane, historical source inventory | SHA-256-bound xbase.zip, 10-node family tree, 21-file byte-preserved source manifest, checksums, source review notes | Active preservation pages with proof labels and inspectable read-only files. CSV/JSON are downloads; historical code is evidence, not automatic current product behavior. |
| Application UI DSL / UIDEF lane | /docs/dev/application-ui-dsl-lane | AIF-120 charter and status index, UIDEF contracts, gui/uidef/*, APPGUI launcher source contract | DBF/FPT design-table fixtures; FoxPro importers; manifest/refusal reports; wxWidgets, Tk, HTML, and character-cell consumers; engine integration probes | 2026-08-26 matrix check: refreshed from planned-only copy to the current Alpha implementation. Preserve the distinction between the implemented design-table/generator system and the still-planned CREATE MENU / CREATE WINDOW text syntax. Keep the known wxWidgets splitter teardown and native MSVC proof boundaries visible. |
| Coding standards and safeguards | /docs/dev/coding-standards | Contract lane, comments collection lane, mutation/risk annotations | header standards, @dottalk.usage, @dottalk.contract, scanners, command safety review | Reviewed policy. Should become an enforcement checklist for source comments and website promotion. |
| News announcements (proof-written) | /news, /news/announcements/* | Milestone lanes; auto-discovered announcements plus the generated working log from content/news/milestones.json | session transcripts, regression runs, harness output, documentation-progress artifact | maintained. Freshness sweep 2026-08-26 moved the current working log above older announcements and added concise proof-written status for the documentation closeout, MINIDB hydration, and Alpha UIDEF work while retaining prior milestones. Freshness contracts require a working-log entry matching the current documentation reconciliation date and keep that log first. House rule: an announcement is written from proof or it is not written. |
| News, licensing, brand | /news, /licensing, /brand | Human review, third-party acknowledgement, naming/license lane | package manifests, local dependency review, license notices, brand usage notes | Reviewed manually. These sections should not be generated from code scanners alone. News reframed 2026-08-10 (owner): announcements lead (written from proofs and transcripts), press releases MINIMIZED to a dashed-border archive footnote that states honestly a real press surface is an open TO-DO -- "built when there is a release to press about, not before." First proof-written story: the Cascade double-milestone announcement. |
| AI views and process diagrams | /AI/ (gallery index.html, BBS boards, AI portal reports, PROCESS_DIAGRAMS.html) | Reports gateway governed set, conceptual/architectural diagram lane | tools/reports/*, labtalk/diagrams/*.mmd, stage_public governed public set | maintained gateway-served AI views. Process diagrams (BBS ERD/DFD/PFD, M4.x, the pass-4 doc-push DFD) are hand-authored from .mmd and kept in sync; never hand-edit a rendered SVG or the gallery HTML copy. |
| AI Portal professional model | /docs/labtalk/ai-portal, /docs/labtalk/ai-portal-schemas | AI Portal professional model, identifier model, feed contract, DBF schema registry | tracked MDX pages; generated PFD/DFD SVGs and provenance; 19 registered DBF schemas across identity/RBAC, BBS, rulings, tracking, and SelfDoc; typed identifier/feed/assertion/status schemas | maintained, public Alpha projection. The matrix check requires the overview, schema inventory, normalized AIF/R/run/task/proof/report hierarchy, generated diagrams, source-derived provenance, and public-boundary language to refresh together. Local /portal/* working references remain excluded and are not public dependencies. |
| Frontal Memory (private working reference) | /memory/* (overview, team-model, roadmap) -- unlisted, noindex | Persistent-memory thesis lane, AI coordination team model, triage optimization PDLC lane | content/memory/*.mdx, architecture SVG (public/images/memory/frontal-mem-architecture-v1.svg), upstream frontal_mem:thesis_persistent_memory.md and ccode:tools/memory/* | maintained, private/unlisted BY DESIGN (robots noindex; not in nav/sitemap); working draft. Promotion to public navigation is a deliberate later step. |
| Site search (Pagefind) | /search (public, in nav) + generated /pagefind/* index | AIF-097 Part A -- client-side static search | app/search/page.tsx + SearchClient.tsx, config/nav.ts (Search item), package.json (pagefind --site out build step) | maintained; browser-side Pagefind index built after next build, indexes PUBLIC pages only. Privates excluded: /memory and /portal via data-pagefind-ignore; the /AI gateway reports are excluded automatically -- Pagefind runs in opt-in data-pagefind-body mode (layout <main>), and those non-Next pages do not carry that marker (and are stripped from the public build besides). Do NOT add data-pagefind-ignore to the /AI <body>: the gateway matches <body><div class="wrap"> exactly to inject its LIVE banner. No server; not available under next dev. |
Data-Mining Feed Matrix
| Data-Mining Feed | Extracts | Website Targets | Proof Gate |
|---|---|---|---|
| Command registry and HELP scan | command names, aliases, usage, HELP text, mutation risk | command catalog, command families, DotScript guide, data mutators | CMDHELPCHK clean enough for reviewed promotion. |
| Publication-entry freshness | engine executable provenance, canonical HELP producer state, HELP/META harvest freshness, catalog projection | every generated or maintained-current documentation consumer | Fail closed. website_matrix_check.py must pass docpush_preflight.py. The present cheap fallback compares executable/store order and therefore treats a later recompile as E2-open; this is conservative, not a claim that unrelated code changes HELP. The intended refinement is a content-addressed HELP-producer fingerprint. A clean site build cannot override a failed relationship. |
| Source contract scan | @dottalk.usage, @dottalk.contract, comments, mutates/risk fields | coding standards, command/function pages, API docs | Source path and reviewed status preserved. |
| Engine feature crosswalk | feature families, evidence status, source/HELP anchors | engine feature crosswalk, current lanes, product capability summaries | Runtime/source/help status labels retained. |
| Manualgen inventory/validate/dry-run | manual sections, missing anchors, boundary warnings | important documents, generated manuals, downloadable manual artifacts | Validation result and Python/tooling version recorded. |
| Runtime transcript and screenshot curation | command output, GUI/TUI proof, website proof screenshots | runtime evidence gallery, Laboratory Campus proof pages, workbench pages | Caption includes product name, date, proof target, and known staleness. |
| Documentation progress registry | gate status, public commits, manual counts, benchmark proof state, separate missions | documentation progress, current lanes, downloads, project truth | Completed publication facts remain distinct from public-source evidence, local evidence, and runtime-release proof. |
| Documentation reconciliation date | documentation-progress-v1.json as_of_date after the full-stack run is reconciled | site-wide banner at the top of the main page and every shared-layout route | Required website-matrix step: advance the artifact date only when reconciliation is complete; the shared layout must read that field rather than the current-work or publication date; run the production build and verify the rendered homepage says Full-stack docs reconciled <as_of_date>. The 2026-08-26 run completed this step locally. |
| Website freshness contracts | dated authority fields and manifest counts | news working log, command-reference snapshot, current-work and agent-sync disclosures, manual download surfaces, this sweep ledger | Fail closed. scripts/check-site-freshness.mjs expands required values from the owning JSON authorities and rejects missing or stale visible markers before the production build. Its self-test must reject deliberate staleness for every configured contract. |
| FAQ reconciliation | documentation-progress date plus changed product, command, interface, workspace, and contributor-operation claims | /docs/getting-started/faq and its matrix disposition | Required website-matrix step: review the FAQ on every full-stack reconciliation, record UPDATED or NO_CHANGE, and stamp the visible review date from the documentation-progress authority. faq-reconciliation-check fails the site build when the date or required current-coverage markers drift. |
| AI Portal current-work registry | registered projects, tasks, tickets, owners, status, proof state, next gates, Pseudo-Chat returns | current tasks and projects, AI Agent Sync | Registry references validate; local paths are removed from the public projection; as_of_date advances only after reconciliation. The current-work date measures registry reconciliation only and does not drive the site-wide documentation banner. Publish dates belong to the release metadata (/artifacts/site-release.json). |
| Pinocchio benchmark ledger | dataset size, operation, before/after timing, speedup, machine binding, transcript state | Pinocchio benchmarks, engine progress summaries | Historical limitations remain visible; a fresh run appends evidence instead of replacing the baseline. |
| Diagram promotion | Mermaid, Draw.io, SDLC visuals, workflow diagrams | SelfDoc lane diagrams, important documents, publication pipeline pages | Diagram source and generated image kept together. Conceptual/architectural diagrams stay hand-authored and in sync; data-carrying diagrams are generated. V6 reconciliation 2026-08-26: command_reference_harvest_v1.svg and its provenance sidecar were regenerated by command_catalog_sync.py from the central registry, usage contracts, and retained template. Diagram, provenance, and command catalog now agree at 239 registered keys / 239 parsed contracts; the prior 236/215 drift is closed locally. Regenerate rather than hand-edit whenever either authority changes. |
| Artifact/manual-room manifest (RETIRED 2026-08-11) | manual bundles, reference exports, generated report packets, proof packets, accessibility text versions, archive snapshots | superseded by the dottalkpp.com lean-entry role (AIF-107); x64base.com downloads summaries, important documents shelf | Retired with the artifact-room plan: dottalkpp.com serves HTTPS as the lean entry site and carries no bulk-artifact manifest. Row kept as record per the widows-and-orphans policy (RETIRE recorded, not silently deleted). Large artifacts belong on GitHub Releases. |
| Historical source inventory | path, size, timestamp, checksum, source family, truth level | historical source lineage, source museum artifacts | Checksums and truth-level labels preserved. |
| Historical archive browser | exact archive members, byte size, archive timestamp, SHA-256, read-only text projection | historical family tree and source files | Required members fail closed; private roots are omitted; projected bytes retain the archive-member SHA-256. |
| Ecosystem research matrix | outside product capability comparisons, current x64base status | ecosystem context, feature comparison, x64 capacity lesson | External claims separated from x64base source/runtime proof. |
Publication Matrix Check
Before source push or deployment, run the governed matrix checker from the ccode authority tree against this website source tree. It is a hard publication gate, not an advisory report.
The checker requires all of these relationships to pass together:
- every MDX route is classified exactly once;
- the full-stack publication entry passes, including engine -> canonical HELP build/store order and HELP/META producer freshness;
- the command and function catalogs match current source;
- error-code rows match current source; and
- locale rows match current source; and
- the FAQ has an
UPDATEDorNO_CHANGEmatrix disposition and a review date matching the documentation-progress authority.
Today the second relationship uses a roughly one-second timestamp check because the HELP store does not yet carry a content-addressed producer fingerprint. That fallback conservatively treats a later engine recompile as E2-open. It is cheap to run but can require an unnecessary HELP rebuild after an unrelated code change. The gold refinement is to stamp the HELP build with a digest of the catalogs, extracted HELP contracts, and HELP generator implementation, then compare that digest here. Until that provenance exists, publication fails closed even when the website itself builds successfully.
2026-07-18 Publication Checkpoint
The current manualgen publication was validated with Python 3.12.9 and
accepted from public source commit
be935053.
- Developer manual: 4,118 lines, 237 headings, 24 sections, four appendices.
- Command reference: sealed 183-page public checkpoint; current 191-page local candidate comprising 164 reader-linked, 19 supplemental, and 8 post-baseline repair pages, with 4,604 lineage rows.
- Proof labels:
manual-reviewedfor the accepted reader/reference andgenerated-reviewedfor this website projection. - Website publication: source commit
43f120a4, GitHub Pages commit0ef77ea9, followed by cache-bypassed live route verification. - Closeout: all nine gates passed; the accepted 11-path website projection and exact manual digest were verified live.
- Follow-up delta: Pinocchio benchmark metadata and documentation closeout
artifacts are preserved in public source commit
853937f1. Comments-audit records remain in the development lane pending separate review.METACOLLECT-238remains a separate mission.
The feed is still only partly automated. Acceptance and website promotion keep their explicit human review and source-provenance gates.
Proofed Site Checklist
A website page is proofed when the page can answer four questions:
- What source or document lane fed this page?
- What proof level is being claimed?
- What artifact, command, report, screenshot, or source path backs it?
- What needs to be regenerated when the underlying command, function, or lane changes?
The site currently meets this standard best for engine feature crosswalks, data mutators, x64 capacity math, runtime evidence, historical source lineage, and the SelfDoc publication pages. The accepted manual/reference checkpoint is now public in site source; the weaker area remains the fully automated regeneration loop, which is documented as partial rather than complete.