Repository documentation

QA ledger

2026-10-24 1.3.0 retained-source and native-custody edition published

• Regenerated both required members after the 1.3 contribution sweep reached a closed, machine-readable disposition. The edition records reviewed original-source binding, target-bound Python projection, FreeBSD worker and target foundations, native SDK tree custody, and retained execution hardening while keeping incomplete Windows, FreeBSD, remote-package, and production-dispatch work explicitly deferred.
• Independent document-pair acceptance passed all 11 scenarios: 26 slides at 1280x720, zero escaping elements, zero overlapping text-bearing frames, notes on 26/26 slides, 73 narrative headings with no skipped level, no unresolved placeholders, and no credential material.
• Inspected the complete 26-slide contact sheet and full-resolution slide 23. Also rendered the DOCX with the bundled LibreOffice/Poppler toolchain and inspected all 13 pages at full resolution. No clipping, overflow, broken pagination, unintended overlap, or title-rule residue remains. The Google Docs title sanitizer passes with zero changes required.
• Local artifact identities:
  • PPTX: sha256:e84b0819f7ed6858da3171ac44d6a3778a6e631fdc28fa0801e7f7ba55b7ca7f
  • DOCX: sha256:f2ffee56a4adc3877798e28287e638ba9773d8b1f3ca01d29aeaca6f7d5ca0f9
• Google Workspace preflight passed after removing legacy anonymous-reader grants from both stable resources. The pair now exposes only the NVIDIA-domain reader and owner grants, matching the declared organization-restricted audience. The focused publisher regression passes and the live pair-wide preflight identity is sha256:c82c59db7d0e5393d6d253afc33df8d16ba57b6b8ecca1b0fd33c7377ca93a08. In-place publication from exact source revision eb5b82bfa2b03f042c9f2b65dfccfa5184bccd26 completed. Export-back matched 26 slides, 26 notes pages, and 73 narrative headings. Export identities are sha256:d4bc6d332940b2355434f7cc89b2267a777582757d995acd001a470b86d5b460 for the presentation and sha256:5bc192a528b92d77d273ad845c47ce3b958d90e06efe489b27ee6d4b7627f131 for the narrative. The complete release-bound receipt identity is sha256:e38fd2edbfab5be38eeb4c73369cae735a9eea640989ee4b858bd717d08a831a.

2026-10-11 1.2.0 (public) edition published

• Read-only preflight confirmed the active account and both stable resources. The authorized in-place update (--release-version 1.2.0, source revision 04abf951) completed both members; export-back read 26 slides / 26 notes pages and 73 headings, matching the accepted local members. The release-bound receipt is complete.

2026-10-11 1.2.0 (public) repair, cross-host worker, and Mix edition accepted

This is the public repository's 1.2.0 edition. It is distinct from the private repository's 2026-09-26/27 "1.2.0" entries below, whose content shipped publicly as 1.1.0.

• Revalidated source-notes.md against the merged 1.2 line (1d22e1c1). Corrected counts: Makefile RELEASE_GATES 14 → 15 (public-export-check); build-system Flavors 5 → 6 (build-mix). Package providers stay nine; Hex is recorded as a build-mix toolchain constraint and pinned dependency input, not a package provider.
• Revised slide 23 (and its narrative counterpart, a new 8.1.3 heading) to the 1.2 slices: bounded candidate repair with redacted diagnostic excerpts, cross-host action workers and the reference standard receiver, Elixir/Mix with checksum-pinned Hex, and forge issues/PRs as the default coordination channel. Production DAG dispatch with LAN cache qualification (#4) and three-way update merging (#2) are labelled as deferred to 1.3. Slide 19 now draws all 15 gates; slides 4, 18, 20, and 25 and their notes carry the updated counts, tiered local-first qualification, and 1.2 labels. 26 slides kept.
• Independent document-pair acceptance passed all 11 scenarios: 26 slides at 1280x720, zero escaping elements, zero overlapping text-bearing frames, notes on 26/26 slides, 73 narrative headings with no skipped level, no unresolved placeholders, and no credential material.
• Inspected the complete 26-slide contact sheet plus full-resolution slides 4, 19, 23, and 25. Slide 23's first title draft wrapped into its subtitle and was shortened to one line. No new clipping, overflow, unintended overlap, or broken connector remains.
• Independent agent review against the code at 041b3f09 confirmed the counts, help list, repair limit, receiver, ADR 0050/0017 amendment, prompt-task@2, SemVer and tiered qualification claims, and corrected three things: slide 23's REPAIR line and the specs no longer imply that litai rebuild feeds raw redacted excerpts to repair (the repair prompt carries a sanitized failure fact; excerpts are a conformance-harness record); "plan-only update reviews" now says conflict review is plan-only and apply preserves conflicts, since litai update --apply exists; and slide 23 gained a header wash so the title and subtitle stay legible over the photograph. Slide 18 notes now scope Debian construction to compatible Linux hosts. Acceptance re-passed 11/11.
• Local artifact identities:
  • PPTX: sha256:ee7b402c7675d151f331e98517627d22229047d01df31959f68fb2788bc169e3
  • DOCX: sha256:6a0d4a8f0e4c2e67ca214ea2aa1b5abb565bd1f5c3fd26672864554a03cad58c
• Google Workspace preflight, in-place publication, export-back verification, and the release-bound publication receipt are pending and were not attempted in this pass.

2026-09-27 1.2.0 published in place and export-back verified

• Repeated the pair-wide Google Workspace preflight as the configured authorized publisher against source revision d590b2e7002a5ecefedceffb85161315e82943b2; both exact stable resources retained edit, export, sharing, and organization-reader access.
• Updated both stable resources in place without changing their IDs or widening access. The narrative is named Literate-AI — Application Foundry Narrative (1.2.0 edition).
• The resumable publication receipt is complete for release 1.2.0, with identity sha256:ec9423d765837b5ebd80a83462038464e261604dbd8328b712e43ea026c49443.
• Export-back verification matched the required structure: 26 slides, 26 notes pages, and 72 narrative headings. Export identities are sha256:0d1429f6fa33cf9d0dd8b9208694ce80ba779099056fd1679815b8eb01e9364a for the presentation and sha256:55b3041a5995de06836eed573d747f30be2b762956e98c60dba6f04265376829 for the narrative.

2026-09-26 1.2.0 throughput and native-acceptance candidate accepted; publication pending

• Regenerated both required members after reconciling the 1.2 contribution ledger. The content names the implemented bounded scheduler/cache, real local Debian, native CLI, native gRPC, and worktree-placement slices while retaining explicit boundaries for production dispatch, real LAN cache proof, remote package custody, complete native-CLI lifecycle proof, and legacy-worktree retirement.
• Independent document-pair acceptance passed all 11 scenarios: 26 slides at 1280x720, zero escaping elements, zero overlapping text-bearing frames, notes on 26/26 slides, 72 narrative headings with no skipped level, no unresolved placeholders, and no credential material.
• Inspected the complete 26-slide contact sheet plus full-resolution slides 23 and
  25. The revised 1.2 capability boundary and investment decision are legible, with no visible clipping, overflow, unintended overlap, or broken connector.
• Content-review result: the mechanism sequence remains slides 7-11 and 19-23; the deck shows real specification, plan, gate, and evidence artifacts; forward-looking production claims are isolated to the horizon and decision slides; no measured throughput, ROI, cost, or unqualified publication claim was introduced.
• Local artifact identities:
  • PPTX: sha256:33a0c0782858e7bd7691107c4fef945fdc65d2b7cd469e69fec2a3c6604dfdad
  • DOCX: sha256:a44535da53757a7ae1dc309f70cdaee30c8033a9a4b39d0c246b60bafaacb04f
• Google Workspace preflight as the authorized publisher reported ready: true for both stable resources, including edit, export, sharing, and organization-reader access (sha256:44b471ffb79dcf7739f812ba90b3e9988258feeebea5168981e136d256162cf7). It must be repeated against the exact committed revision before the in-place update; export-back verification and the final source-bound receipt remain pending.

2026-09-17 1.1.0 final blocker candidate regenerated; publication pending

• Regenerated both required members after integrating the remaining 1.1 release blockers at source revision 5375e46956ea9efb6d011740a4e8f2dc719bf4af. The document content remains bounded to the reviewed 1.1 native-custody claims; publication will bind the final merge revision after hosted CI succeeds.
• Independent document-pair acceptance passed all 11 scenarios: 26 slides at 1280x720, zero escaping elements, zero overlapping text-bearing frames, notes on 26/26 slides, 72 narrative headings with no skipped level, no unresolved placeholders, and no credential material.
• Inspected the complete 26-slide contact sheet plus full-resolution slides 23 and
  25. The native-custody sequence, implementation/open-boundary distinction, and final decision line remain legible without clipping or overlap.
• Local artifact identities:
  • PPTX: sha256:6b8401fb86b688d41d03227e60eb8dcc519bd34682d793e9269e004397bd237d
  • DOCX: sha256:0da72d5679e33504f4e7ea0bf04d009ea80a607f2ea82a8e07bbafed16ee09fb
• Google Workspace preflight as the authorized publisher reported ready: true for both stable resources, including edit, export, sharing, and organization-reader access. In-place update, export-back verification, and the final source-bound publication receipt remain pending the exact merge revision.

2026-09-15 1.1.0 native-custody candidate accepted; publication pending

• Regenerated both required members from the checked-in Python authoring path for the 1.1.0 major/minor cadence. The edition preserves the release/operator boundaries and adds only bounded implemented claims for native SDK and compiled-library custody, retained-source lifecycle progress, Component worker-routing primitives, and selected SSH retained-receipt execution. It explicitly leaves complete DAG dispatch, full remote evidence import, production containment, and native application packages open.
• Independent document-pair acceptance passed all 11 scenarios: 26 slides at 1280x720, zero escaping elements, zero overlapping text-bearing frames, notes on 26/26 slides, 72 narrative headings with no skipped level, no unresolved placeholder, and no credential material.
• Inspected the complete 26-slide contact sheet plus full-resolution slides 23 and 25. The revised native-custody sequence is legible, its implementation/open-boundary distinction is visible, and the final decision line is not clipped.
• Local artifact identities:
  • PPTX: sha256:1a182a54e934845be527e05225cb92b755c663bf61af734feea9fe7661bcece9
  • DOCX: sha256:8ac76abc110f561474ce116026ee2a44a3881eb914e466fdd919a7c07a988dd3
• Google Workspace preflight, in-place update, export-back verification, and the source-bound publication receipt remain pending an explicit operator-selected Google account. Stable resource IDs are unchanged.

2026-09-05 0.10.0 operator-adoption candidate accepted; publication pending

• Regenerated both required members after implementing the 0.10.0 operator front door: project-independent doctor, composed status, acknowledged create/adopt plans, explicit evidence-bound brownfield stages, and installed-wheel golden paths. Production containment, deployment automation, and native application formats beyond pip/Conan remain future work.
• The independent document-pair oracle reports 11 pass, 0 fail, 0 not-applicable: 26 slides, 26 non-empty notes pages, zero geometry escapes, zero overlapping text-bearing frames, 71 narrative headings with no skipped level, and no unresolved placeholders or credential material.
• Inspected the contact sheet and full-size slides 23 and 25. The first render ambiguously labeled implemented operator rows as horizon work and clipped the decision-bar suffix. The corrected render labels only HARDEN as the target horizon and shows the complete downstream-adoption decision without clipping.
• Exact local artifacts: PPTX 1,375,129 bytes, sha256:c1ec9226fbdc3e8dd8dbe4450db289f86eb2708fec5c5a95306e7e5c925b6441; DOCX 48,430 bytes, sha256:d48cc5778c89d29b3f02041f7b4ba1fa53ead083134439c18a9da4e466f61dde.
• The stable Google Workspace IDs remain unchanged. Publication preflight, in-place update, export-back, and the release-bound receipt remain pending until this exact source candidate is committed.

2026-09-04 0.10.0 local edition accepted; published in place

• Regenerated both members for the required 0.10.0 major/minor publication cadence. Claims keep the implemented 0.9 application loop and add executable release closure (ADR 0034), Standard lifecycle rebind, and issue-first upstream work. The edition explicitly does not claim a published v0.10.0, operator-visible status/convert/onboard, production containment, or native application package formats beyond the shipped pip/Conan proof.
• The independent document-pair oracle reports 11 pass, 0 fail, 0 not-applicable: 26 slides, 26 non-empty notes pages, zero geometry escapes, zero overlapping text-bearing frames, 71 narrative headings with no skipped level, and no unresolved placeholders or credential material.
• Inspected the contact sheet and full-size slides 18, 20, 22, 23, and 25. The Release Policy caption names the 0.10 contribution sweep and document-pair preflight; slide 23 lists ADOPT first as the next horizon; slide 25's decision bar asks for operator-adoption investment.
• Exact local artifacts: PPTX 1,375,168 bytes, sha256:eaa42b3f0b8b0d7189a254f65e6c9429f04dce6beaf7ff06fd8a5d572805c7ee; DOCX 48,303 bytes, sha256:0f9da61e5f3a8df849103b4f0a7e03e8953dfa25cfe5523085d6aca1631de303.
• Publication preflight with the configured organization account reported ready: true with edit, download, and organization-reader access on both stable resources.
• In-place update and export-back completed. Receipt _build/literate-ai-manager-overview/publish-receipt.json is complete for release 0.10.0 at source be7d44e82df958402ff22dbdefbe461697910722, identity sha256:2ff3c12822e842cd3fb6314ed4fe6f2181afa94ade30a0a1ff3d60dd8815ee08. Export-back: 26 slides / 26 notes pages; 71 narrative headings. Narrative renamed to the 0.10.0 edition. Stable IDs unchanged.

2026-09-03 0.9.0 local edition accepted; publication pending

• Regenerated both members for the required 0.9.0 major/minor publication cadence. Claims cover the implemented multi-entrypoint lifecycle, durable split-service topology, deterministic Python application services and skill catalog, centralized platform path policy, native host-prerequisite SBOM selection, and safe uninstall. The edition explicitly does not claim a published v0.9.0, a complete private Windows qualification receipt, production containment, or native application package formats beyond the shipped pip/Conan proof.
• The independent document-pair oracle reports 11 pass, 0 fail, 0 not-applicable: 26 slides, 26 non-empty notes pages, zero geometry escapes, zero overlapping text-bearing frames, 70 narrative headings with no skipped level, and no unresolved placeholders or credential material.
• Inspected the contact sheet and full-size slides 4, 5, 13, 15, 18, 22, 23, and 25. The real four-boundary durable DAG, six-role inventory caveat, complete CLI surface, and post-0.9 hardening horizon remain readable. A second render confirmed removal of literal Markdown backticks on slide 18 and that slide 25's decision bar fits.
• Exact local artifacts: PPTX 1,375,022 bytes, sha256:bfb90a1541416803461c5344ff6ad63c78c6425ae1a1419e35e7551511c852bf; DOCX 47,994 bytes, sha256:ad2de2e5504f781915f72d5a60c4f045e16856f3d18629557c38006b50bc21f1.
• The first publication attempt made no remote change because gcloud had neither an active account nor application-default credentials. Published-resource versions, export-back structure, geometry, and access remain pending and must be appended here only after credentialed publication succeeds.

2026-08-30 Release Policy source revision (pending regeneration)

• Updated the deck/narrative specifications, source notes, authoring prompt, package guidance, and both Python builders for the mandated Release Policy while retaining the 26-slide sequence by replacing slide 20's content rather than renumbering.
• Source now distinguishes writable Free/Pre-release main, exact-main RCs, release-line lockdown, README Release Engineer authority, strict/loose trunk-first patch authority, required pull-request trailers, marker-based safe GC, and LitAI enforcement versus separately configured forge protection.
• git diff --check and Python compilation of build_deck.py and build_narrative.py passed. make documentation-check was attempted but stopped while staging OpenSpec because Puppeteer found an incomplete cached Chrome Headless Shell; the documentation checks themselves did not run. Documentation-authority marker refresh, PPTX/DOCX regeneration, rendered-slide inspection, document-pair oracle execution, and Google publication were not requested and remain pending. Checked-in binaries and published resources were not changed.

2026-08-30 vanilla regenerate without Codex plugin (DOC-TOOLCHAIN-001)

• regenerate.sh prefers the pinned OBJ_DIR python-pptx / python-docx toolchain and keeps Codex setup_artifact_tool_workspace.mjs discovery as fallback only.
• Empty CODEX_HOME plus make doc-toolchain-bootstrap regenerated both members from the checked-in package into a temp output (checked-in PPTX/DOCX bytes unchanged). Independent document-pair oracle: 11 pass, 0 fail, 0 not-applicable.
• Tests: tests.e2e.test_doc_toolchain_regenerate (plugin discovery retained, bootstrap-directed failure without plugin or toolchain, checked-in package oracle, vanilla regenerate + oracle) and tests.smoke.test_doc_toolchain_bootstrap.
• Live Google Slides were not regenerated.

2026-08-28 document-pair layout authority (DOC-PAIR-001)

• Encoded the overview overflow pass as catalog process: geometry-escape is not an overflow gate; overlapping text-bearing frames fail the document-pair oracle; workflow pages stay picture-led; Google Arial substitution and real paragraphs in the shape text frame are recorded in the authoring skill and the Google Workspace binding. Init-template copies match. Historical QA entries that named geometry-escape as the applicable gate are left as written.

2026-08-27 cover and thesis-cell overflow (slides 1 and 3)

• Slide 1 title was a 625 px box over the hero graphic, so "rebuild itself from intent" wrapped into the image. Cover copy is now a 380 px left column with an explicit three-line headline.
• Slide 3 body copy lived in separate text boxes on top of the INTENT / REGENERATE / PROOF shapes. Google treated \\n as one overflowing line. Copy now lives in each shape's text frame as real paragraphs, in three equal 340 px cells with 18 px insets and text-to-fit.
• Ran ./regenerate_python.sh. Independent document-pair oracle: 10 pass, 0 fail. Inspected full-size slides 1 and 3; title stays in the wash, cell copy stays inside the rounded rects. Published in place as Drive version 134.

2026-08-28 0.8.0 edition, both members published (DOC-DECK-003)

• Major/minor document-pair regeneration required before the 0.8.0 cut. main is 0.8.0 Unreleased. Claims limited to current implementation (Job Object remaining spawn sites, agent-owned patch content, tag-pinned changelog README links). Did not claim FLAVOR-005, TEST-CACHE-001 designed pin/dispatch, ADR 0010 dotted-alias close, --target local fleet fan-out, or a published v0.8.0 tag.
• Encoded the post-Slides read-and-improve pass in docs/presentations/literate-ai-manager-overview/SKILL.md step 6 and the deck specification's visual direction: geometry-escape is not enough; overlapping text boxes fail; workflow slides are picture-led.
• Replaced remaining paragraph-led workflows: slide 4 is a plan→receipt chevron pipeline; slide 17 INDEX/DRAFT/QUALIFY is label-only beside the legacy-transform image; slide 20 keeps the dual-target diagram and one caption. Slides 8, 10, 11, and 12 remain image-led mechanism pages; slide 7 keeps the verbatim specification excerpt.
• Ran ./regenerate_python.sh. Independent document-pair oracle: 10 pass, 0 fail, 0 not-applicable. 26/26 notes pages; 0 geometry escapes; 0 text-frame overlaps; 66 narrative headings with no skipped level. The PPTX embeds cover-fitted JPEG at slide resolution so it stays under the 16 MiB documentation per-file limit; authoring assets remain high-resolution PNG. Report: ../../../_build/literate-ai-manager-overview/acceptance.json.
• Inspected the contact sheet plus full-size slides 4, 8–12, 17, 19, 20, and 22. No remaining title/subtitle/footer collisions. Overlay text on image slides sits on an opaque wash.
• Publication was authorized by the request to execute DOC-DECK-003 for the 0.8.0 edition. Obtained a fresh bearer token with gcloud auth print-access-token; it was neither persisted nor logged. Updated native Slides resource 1V9mt1JpEst_2ucC0eJIIw7dff64MrtFRfut8MSiukeE in place (Drive version 129) and the existing Google Doc in place, renamed to the 0.8.0 edition. Export-back: 26 slides / 26 notes pages; 66 narrative headings; 0 text-frame overlaps on the published PPTX export. Organization-restricted nvidia.com reader access with link discovery disabled is unchanged.

2026-08-27 visual layout pass (DOC-DECK-003) on the published 0.7.1 edition

• Pixel inspection of the 0.7.1 local renders found title boxes overflowing into subtitles (slides 2, 5, 9, 19, 25), the RELEASE ENGINEERING tag colliding with the brand pill, and bottom captions colliding with the footer (slides 11, 12, 21, 22, 26). Geometry-escape was clean; painted overflow is a separate defect.
• Reserved a two-line title band and moved the footer below y=696. Section tags now size to their label. Added a text-frame overlap scan in render_slides.py.
• Replaced paragraph-led workflow pages with picture-led layouts: generation-key, gate-failure, isolation-containment, and evidence-artifact images on slides 8, 10, 11, and 12; engineering-section on 23; living-portfolio on the close. Slide 7 keeps the verbatim specification excerpt. Slide 22's evidence closure is a chevron chain.
• Ran ./regenerate_python.sh. Independent document-pair oracle: 10 pass, 0 fail, 0 not-applicable. 26/26 notes pages; 0 geometry escapes; 0 text-frame overlaps; 63 narrative headings with no skipped level. Report: ../../../_build/literate-ai-manager-overview/acceptance.json.
• Inspected the contact sheet plus full-size slides 2, 5, 7–12, 19, 21–23, 25, and
  26. Remaining title/subtitle/footer collisions are gone. Overlay text on image slides sits on an opaque wash, matching the established half-bleed pattern.
• Publication of this layout revision was authorized by the request to improve the live Slides resource. Obtained a fresh bearer token with gcloud auth print-access-token; it was neither persisted nor logged. Updated native Slides resource 1V9mt1JpEst_2ucC0eJIIw7dff64MrtFRfut8MSiukeE in place (Drive version 124) and the existing Google Doc in place. Export-back: 26 slides / 26 notes pages; 63 narrative headings. Organization-restricted nvidia.com reader access with link discovery disabled is unchanged.

2026-08-27 0.7.1 edition catch-up, both members published

• Encoded the durable cadence: full regeneration on every major or minor cut; patch cuts keep README citations on the last major/minor edition. 0.7.1 is the catch-up because 0.7.0 skipped the refresh. Authority: docs/architecture/project-releases.md and both release-project skills (catalog and template remain byte-identical).
• Revalidated source-notes.md against current code. Slide 19 now draws the current 14-gate RELEASE_GATES list (no codegraph). Slide 20 carries the prepare-creates-the-line claim. Slide 4 reports 6 languages / 4 build systems / 3 OS families / 6 package providers as catalog surface area. The narrative member is realized locally with python-docx.
• Ran ./regenerate_python.sh. Independent document-pair oracle: 10 pass, 0 fail, 0 not-applicable. 26/26 notes pages; 0 geometry escapes; 63 narrative headings with no skipped level; no credentials or unresolved placeholders. Report: ../../../_build/literate-ai-manager-overview/acceptance.json.
• The host has no LibreOffice. render_slides.py (python-pptx/Pillow) wrote ../../../_build/literate-ai-manager-overview/rendered-slides/slide-01.png through slide-26.png and contact-sheet.png. Inspected the contact sheet plus full-size slides 4, 7, 19, 20, 21, and 22 for clipping, overflow, overlap, broken connectors, stale citations, and unreadable type. No remaining defect on those pages.
• Content-depth review: a skeptical practitioner can reconstruct the control model from slides 7–11 and release engineering from slides 19–22 plus the narrative. Mechanism pages outnumber claim-only pages. The durable authority is shown as a real specification excerpt on slide 7. Cost, failure, containment, and the evidence-ledger boundary are answered. No invented ROI figures.
• Publication was authorized for this 0.7.1 edition. Obtained a fresh bearer token with gcloud auth print-access-token; it was neither persisted nor logged. Updated native Slides resource 1V9mt1JpEst_2ucC0eJIIw7dff64MrtFRfut8MSiukeE in place (Drive version 118). Created Google Doc 1fMxy0NTT54MV4T9AwmA8F0VahNet93Xhp0d0pszI6GA. Both carry type=domain, domain=nvidia.com, role=reader, allowFileDiscovery=false.
• Drive files.export rejects this PPTX (exportSizeLimitExceeded). Read-back used the authenticated https://docs.google.com/presentation/d/{id}/export/pptx URL instead: 11,326,534-byte round trip, 26 slides, 26 notes pages. The Doc exported through Drive files.export as .docx with 63 headings. Local presentation SHA-256 2408b898189d5e4fe443ba572013c416… (ZIP timestamps make rebuilds non-byte-stable).

2026-08-26 0.7.0 evidence-closure refresh and visual corrections

• The initial refresh record was corrected after pixel inspection found two issues: slide 20 had orphaned/occluded target connectors, and slide 22 cited the removed src/literate_ai/adapters/intelligence/codegraph.py path. Updated the presentation specification before the corresponding build_deck.py slide functions: slide 20 now uses one anchored source/trunk with visible gate-boundary endpoints, and slide 22 uses a current pin-check output and declared implementation paths.
• The refreshed slides retain hierarchical release evidence closure and failure custody, qualify the single-host/no-fleet path, and correct GitLab to recognized-but-fail-closed rather than dispatched.
• Ran ./regenerate_python.sh. The rebuilt 26-slide artifact passed the independent document-pair oracle with 9 pass, 0 fail, 1 not-applicable; all pages carry non-empty notes, all elements remain inside 1280 × 720, and no credentials or unresolved placeholders were found. Report: ../../../_build/literate-ai-manager-overview/acceptance.json.
• The host has no LibreOffice or retired presentation-plugin renderer, so the python-pptx/Pillow fallback rendered every slide to ../../../_build/literate-ai-manager-overview/rendered-slides/slide-01.png through slide-26.png, plus the contact sheet at ../../../_build/literate-ai-manager-overview/contact-sheet.png. The complete contact sheet and full-size corrected slides 20 and 22 were inspected for clipping, overflow, overlap, broken connectors, stale citations, and unreadable text; none remains. The document-pair geometry-escape check is the applicable geometry gate for this python-pptx path; pixel inspection specifically caught what that check cannot catch.
• No Google Slides import or publication was requested or authorized.

2026-08-19 codex-independent rebuild, 26-slide release-engineering revision

• Rebuilt the deck through the new build_deck.py/python-pptx path (see source-notes.md's "Codex-independent rebuild" entry), reproducing the prior 22-slide edition losslessly and adding the four release-engineering slides (19-22) deck-specification.md already called for since 2026-08-18.
• The independent document-pair oracle (scripts/verify_document_pair.py, unmodified) reports 9 pass, 0 fail, 1 not-applicable (narrative correctly not-applicable — that member is not realized by this rebuild). All 26 pages carry non-empty speaker notes; all elements remain inside 1280 × 720; no credential material; no unresolved placeholder tokens. Full report: ../../../_build/literate-ai-manager-overview/acceptance.json.
• Local artifact: literate-ai-manager-and-engineering-overview.pptx, 11,140,847 bytes. python-pptx's ZIP container embeds a per-entry write timestamp, so re-running build_deck.py reproduces byte-identical slide content but not necessarily the same SHA-256 as an earlier build — see the acceptance report for the digest of the exact committed artifact.
• Not imported to Google Slides in this pass — no publication was requested or authorized. current-deliverables.md records the published copy (22 slides, 2026-08-11) as stale relative to this local artifact.
• Content-depth review: slides 19-22 each carry a real diagram or a real, shortened CLI output excerpt (the 15-gate RELEASE_GATES names from the Makefile, the actual --target local|github dispatch shape, a representative litai perf JSON-Lines span, and scripts/review_lifecycle_driver.py --record's real output shape) rather than restating the claim in prose alone, matching this package's own "show the mechanism" guardrail.

2026-08-11 flattened sample catalog revision

• Updated the one repository-path citation from the removed nested service-Component directory to components/money-calculation/ and regenerated the maintained 22-slide PowerPoint through regenerate.sh.
• The independent document-pair oracle reports 9 pass, 0 fail, 1 not-applicable. All 22 pages retain non-empty notes and all elements remain inside 1280 × 720. No Google Slides publication was requested for this path-only correction.

2026-08-11 native wheel and Conan sample revision

• Regenerated the maintained 22-slide deck after native package construction landed. Slides 4, 5, and 18 now distinguish the six-provider planning catalog from the two implemented native providers: deterministic pip wheels and portable Conan cache archives. The sample slide describes verified package bytes; Homebrew remains clearly labeled as selected/planned authority rather than constructed output.
• The independent document-pair oracle reports 9 pass, 0 fail, 1 not-applicable. All 22 pages carry speaker notes; all elements remain inside 1280 × 720; no unresolved placeholder ships. The complete contact sheet and changed slides 5 and 18 were reviewed at full resolution with no clipping, unintended overlap, wrapping, or unreadable text.
• Content-depth review: 16 of 22 slides carry mechanism or concrete evidence, while six serve as opening, transition, consequence, vision, decision, or close. Slide 7 shows a real Component specification and public contract. The deck answers ordering, cost bounds, failure containment, model egress, Component-DAG context containment, CLI delegation, OS fan-out, and package publication separation. Remaining native apt, Homebrew, WinGet, and Chocolatey adapters and production containment stay visible as limits rather than implied completion.
• Obtained a fresh bearer token with gcloud auth print-access-token; it was neither persisted nor logged. Updated native Slides resource 1V9mt1JpEst_2ucC0eJIIw7dff64MrtFRfut8MSiukeE in place. Drive reports version 28, application/vnd.google-apps.presentation, and the existing organization-restricted resource identity is unchanged.
• Exported the published resource back to PPTX with authenticated redirect following. The 11,122,291-byte round trip contains 22 slides and 22 notes pages and passes ZIP integrity. Visible slide text matches exactly on 22/22 slides with SHA-256 74cc49692f9f74f620f8a0a1ad12708678d5681939eec8f30c8658e83a11f799; speaker notes match exactly on 22/22 with SHA-256 ca27fcdff2c2908fc6ac89584eef57a0039491fc5ab70e159bb8c9184ae4cd3e.

2026-08-11 packaging and platform-sample revision

• Regenerated the durable 22-slide deck from the current repository. The implementation overview now reports five language Flavors, two build-system Flavors, three OS families, and six package-provider Flavors. The sample, Flavor, CLI, and fan-out slides now show pip, Conan, Homebrew, Swift, and OS-pinned scheduling without claiming that native package construction is already complete.
• The independent document-pair oracle reports 9 pass, 0 fail, 1 not-applicable. All 22 pages carry speaker notes; all 524 elements remain inside 1280 × 720. The complete montage plus the five materially changed slides were inspected at full resolution with no clipping, overlap, broken connector, or unreadable type found.
• Obtained a fresh bearer token with gcloud auth print-access-token immediately before publication; the token was neither persisted nor logged. Updated native Slides resource 1V9mt1JpEst_2ucC0eJIIw7dff64MrtFRfut8MSiukeE in place. Drive now reports version 23, while the resource remains application/vnd.google-apps.presentation.
• Exported the published resource back to PPTX. The 11,122,180-byte round trip contains 22 slides and 22 notes pages. After ignoring empty XML text runs inserted by Google, visible slide text matches exactly on 22/22 slides with SHA-256 978d2dd6456468b903d5d751611db57aca8ed3a344e86b6687d9c99d822a626e; speaker notes match exactly on 22/22 slides with SHA-256 45879960f875a31d6d7462068f153a7cc67e48dfd033507771a97522801e6a89.
• Rechecked access after publication. Organization-restricted nvidia.com reader access with link discovery disabled remains unchanged alongside the owner grant.

2026-08-10 regeneration and in-place publication

• Regenerated the durable 22-slide authoring package through regenerate.sh. The independent document-pair oracle reports 9 pass, 0 fail, 1 not-applicable; all 22 pages carry non-empty speaker notes and all 524 elements remain inside 1280 × 720.
• Removed elapsed-development-time and predecessor-product claims. Replaced them with current repository evidence: four language Flavors, two build-system Flavors, three OS families, four configured private runner roles, real end-to-end samples, the arbitrary Component DAG, the litai command surface, and checkpointed parallel fan-out.
• Inspected every rendered slide. No unintended overlap, clipping, broken connector, unresolved placeholder, or unreadable type was found. The presentation plugin's Python overflow helper still cannot run in the host Python because numpy is absent, so the complete artifact-tool geometry scan and full rendered-slide review remain the recorded fallback.
• Obtained a fresh bearer token immediately before publication with gcloud auth print-access-token; no token was persisted or logged. Drive confirmed that the supplied native Slides resource was editable before mutation.
• Updated presentation 1V9mt1JpEst_2ucC0eJIIw7dff64MrtFRfut8MSiukeE in place with a Drive v3 resumable files.update. It remains application/vnd.google-apps.presentation and now reports Drive version 18.
• Exported the published Slides resource through its authenticated /export/pptx URL. The 11,122,266-byte round trip contains 22 slides and 22 notes pages. Visible slide text matches exactly on 22/22 slides; speaker notes match exactly on 22/22 slides, with 8,970 characters and concatenated SHA-256 011f2e5c89e88c8ac3ea06f22e42a9258703516c69122dafc8162760b8b410a9 on both sides.
• Rechecked access after publication: domain-restricted nvidia.com reader access with link discovery disabled remains unchanged alongside the owner grant.

2026-08-09 acceptance contract becomes executable

• The document-pair acceptance contract was prose; the checks in it were being run by hand. scripts/verify_document_pair.py now executes them as an independent oracle.
• The builder emits a literate-ai/document-pair-manifest@1 into its render workspace and regenerate.sh runs the oracle against it. Geometry, page count, and notes coverage come straight out of the OOXML package, not from build-time exports, so the oracle does not depend on the program it is checking.
• Current realization: 9 pass, 0 fail, 1 not-applicable (no narrative member is claimed). The report is written to <workspace>/qa/acceptance.json.
• The oracle was adversarially checked before being trusted. Ten mutations of a conforming realization were each required to be rejected — widened audience, credential material, unauthorized publication, undeclared member, missing artifact, missing package element, missing notes page, an element outside the surface, a surface disagreeing with the declaration, and an unresolved placeholder. All ten were caught, and a control confirms the unmutated realization is still accepted. These are retained as tests/critical/test_document_pair_oracle.py (14 tests).

2026-08-09 publication of the 22-slide revision

• Published to Google Slides by updating the existing file in place rather than creating a new one, so the roadmap document's Executive Summary link continues to resolve.

• Upload path: Drive v3 resumable files.update with the PPTX converted to application/vnd.google-apps.presentation.

• Verified server-side: Drive PDF export of the published file has 22 pages, and the file now carries 2 revisions — revision 1 is the prior 20-slide edition, retained in Drive version history.

• Access realized as type=domain, domain=nvidia.com, role=reader, allowFileDiscovery=false, matching the declared organization / view record. The Component's declared audience was widened from named-principals to organization first; the realization never widened beyond the declaration.

• Round-trip verified against the published Google copy. The full 13,012,452-byte PPTX was exported back out of Slides and compared with the local source:

  Property	Google (published)	Local (source)
  Slides	22	22
  Notes slides	22	22
  Non-empty notes	22	22
  Total notes characters	8,359	8,359

  Per-note exact match 22/22; concatenated notes digest e1af237fbe3bcd3a on both sides. Speaker notes survived the PPTX-to-Slides conversion without loss. Mechanism content was spot-checked in the published deck: both HOW IT WORKS bookends, the verbatim specification excerpt, the generation-key refusal column, the invalidation rules, the isolation ladder, the source-bundle rule, and the design intent label all present.

• Two API paths were unusable and are recorded so the working route is not rediscovered: the Slides API demands a quota project this account has no rights on (serviceusage.services.use denied, and no project available to grant on), and Drive API files.export fails at its 10 MB cap. The docs.google.com/presentation/d/<id>/ export/pptx endpoint accepts a Bearer token and is not subject to that cap, which is the verification path for any artifact over 10 MB.

• No credential material was written to the repository, the authoring package, or any recorded manifest.

2026-08-08 Component model for documentation artifacts

• This deck is now component://literate-ai/literate-ai-overview, a terminal document Component requiring the reusable literate-ai.document-pair capability.
• litai project validate passes with 19 Components, both documentation Flavors resolving on the documentation.ecosystem axis, and the new document-pair specification-to-source skill in the catalog.
• A freshly initialized project was created and validated end to end: it carries the document-pair Component, its interface and acceptance contracts, the generation skill, and both ecosystem Flavor bindings, and the Component locks cleanly at init.
• Corrected during this work: the prior ledger claim that "validation reports 15 Components" was inaccurate. The former 15/29 figures were sample behavior specifications and generation recipes, which are unaffected by documentation Components.
• Unit suite: 1488 tests, 1 failure and 1 error, both reproduced on a clean HEAD worktree and therefore pre-existing. Six count and taxonomy assertions were updated for the new Component and skill; two tests that were already failing at HEAD now pass.
• Deck content and rendering were unchanged by this work; no regeneration was required.

2026-08-08 technical-depth revision

• Restructured from 20 to 22 slides. Removed the redundant "Describe / Inspect / Launch" and "guarded path" slides, which restated a lifecycle already carried by slides 3 and 12, and removed the skill-propagation slide; its documentation-Flavor claim now sits on the Flavors slide where it belongs.
• Added a labeled five-slide technical sequence (slides 7–11): the durable authority shown as a verbatim specification excerpt, the generation-key binding boundary and its blast radius, layered execution with bounded concurrency and exact budgets, the failure path, and the model-egress trust boundary.
• Image-led slides carrying only a headline and a paragraph fell from 9 of 20 to 5 of 22.
• Added speaker notes to all 22 slides carrying each slide's supporting authority and its recorded limits. Verified 22 notesSlides parts in the exported PPTX.
• Corrected an unsupported claim: the portfolio-execution slide previously implied hundreds or thousands of demonstrated concurrent tasks. It now states the reproducibility and ordering properties and labels portfolio-scale concurrency as design intent.
• Reframed the week-one figures caption to say plainly that the four numbers measure surface area rather than maturity.
• Regenerated successfully through regenerate.sh: 22 slides, three iterations.
• Geometry scan over all 22 exported layout files found zero elements outside 1280 × 720.
• PPTX ZIP integrity check passed with no errors; 22 slide parts present.
• Two defects found by full-size render inspection and fixed: the reworked half-bleed slides 15 and 17 initially rendered as flat dark panels, and slide 17's step numbers wrapped mid-token.
• Toolchain finding worth retaining: the artifact-tool build in use ignores the shape opacity option, so the wash() helper renders fully opaque. The original deck was unaffected because it only ever placed washes over the typography side of an image. A wash placed over the subject side erases the photograph entirely. build_deck.mjs now carries this warning at the helper definition.
• The presentation plugin's Python overflow and montage helpers remain unavailable in the host Python (numpy and pdf2image missing). Artifact-tool renders plus the complete layout-boundary scan were used instead, consistent with prior editions.

2026-08-08 initial 27-slide edition

• Regenerated successfully through regenerate.sh: 27 slides.
• Artifact-tool rendered every slide at 1280 × 720 and exported layout JSON for every slide.
• Inspected the complete 27-slide contact sheet and representative full-size slides, including all image-led dividers and the densest engineering diagrams.
• Geometry scan found zero objects outside the 1280 × 720 slide frame.
• PPTX ZIP integrity check passed with no errors.
• The presentation plugin’s Python overflow and montage helpers could not run in the host Python because numpy and pdf2image were unavailable. The equivalent artifact-tool renders, ImageMagick contact sheet, and complete layout-boundary scan were used instead.
• Independent LibreOffice round-trip rendering was unavailable because the host soffice wrapper points to an absent application bundle. Native artifact-tool exports were therefore the visual authority for this edition.
• No unintended clipping, overlap, broken connectors, or unreadable text was found in the final contact-sheet review.

2026-08-08 unified application-foundry revision

• Replaced the three-audience structure with one 20-slide cumulative narrative.
• Added the then-current predecessor mock-Studio evidence and application/sample claim audit; that evidence was retired after the predecessor was replaced.
• Added dedicated application-foundry and living-portfolio visuals.
• Added the inherited presentation/document authoring skill and the Google Workspace / Microsoft 365 documentation Flavor choice to the capability-propagation story.
• Regenerated successfully through regenerate.sh: 20 slides.
• Inspected the complete 20-slide contact sheet and the revised ecosystem slide at full 1280 × 720 resolution; no unintended overlap, clipping, broken connectors, or unreadable text remained.
• Geometry scan found zero objects outside the 1280 × 720 slide frame.
• PPTX ZIP integrity check passed with no errors.
• Published the final native Google Slides revision and verified that the roadmap document's summary link resolves to it.