Repository documentation
Manager and engineering overview
This is the reproducible authoring package for the current manager and engineering
document pair: a presentation member (Google Slides deck) and a narrative member
(Google Doc), per component://literate-ai/literate-ai-overview's declared realization.
1.3.0 edition. This package carries the verified local 1.3.0 edition: reviewed original-source first binding, target-bound Python source projection, FreeBSD worker and target foundations, native SDK tree custody, and retained execution hardening on the 1.2 repair, cross-host worker, Mix, and forge foundation. The stable Google Workspace pair below carries the same 1.3.0 edition after an account-bound in-place update and successful export-back verification.
Published presentation: Literate-AI — Application Foundry Vision
Published narrative: Literate-AI — Application Foundry Narrative
Start with the current deliverables, then read the deck specification, narrative specification, source notes, and QA ledger. The local regeneration skill describes the update workflow. Its model-facing inputs are the deck-authoring prompt and image prompts.
The deck builder, narrative builder,
slide rasterizer, Google Workspace publisher,
and regeneration launcher derive the PowerPoint and Word outputs
from this reviewed package using python-pptx and python-docx. Image assets are
retained because they are authored presentation inputs, not generated application source.
regenerate.sh prefers the pinned OBJ_DIR toolchain from make doc-toolchain-bootstrap
so a vanilla worker with no Codex plugin can rebuild. The prior
build_deck.mjs path remains a discovered fallback only (see
source notes's "Codex-independent rebuild" entry). That backend choice
was always project-local, never a dependency of the generic Literate-AI authoring skill,
and was never copied into initialized projects.
Release Policy source status
The source package and both regenerated members now document writable Free/Pre-release
main, exact-main RC tags, release-line lockdown and README Release Engineer authority,
per-project strict/loose patch authority, mandatory Literate-AI-Release pull-request
classification, safe marker-based branch collection, continuous contribution
disposition, document-pair preflight, and the implemented 0.9 multi-entrypoint,
durable-service, host-path, and native-install boundaries plus release closure. The
current edition also carries the implemented doctor/status/onboard operator front door,
explicit brownfield authority stages, native SDK and compiled-library custody, retained
source lifecycle progress, exact worker-routing/remote-receipt slices, bounded action-DAG
scheduling, shared-cache authority, real local Debian packages, native CLI and gRPC
acceptance, repository-owned worktree placement, bounded candidate repair, cross-host
action workers, native Mix builds, and forge-default coordination. Local acceptance and
the state of the 1.3.0 publication receipt are recorded in
the QA ledger.
Visual inputs: cover, manager section, engineering section, one specification to many implementations, legacy transformation, lifecycle gates, generation key, gate failure, isolation containment, and evidence artifact. The application-scale sequence uses the application foundry, living portfolio visual.
