Lifecycle

The lifecycle architecture is the part of CodeAlmanac that creates, improves, queues, and validates wiki-writing work. The lifecycle topic covers build, ingest, garden, sync, queued runs, operation execution, and mutation safety [@topics]. Read this hub when changing how CodeAlmanac turns local inputs and scheduled triggers into durable wiki changes.

Build, ingest, and garden are lifecycle operations because they bind packaged Yoke agents to typed tasks for wiki source under almanac/ [@workflows] [@lifecycle-concept]. Sync is nearby but separate: it scans local transcripts and queues ingest work instead of writing pages itself [@workflows] [@run-queue-sync].

Reading Order#

Start with Lifecycle workflows. It explains what build, ingest, garden, and sync each own, and it states the boundary between operation-specific context and shared execution [@workflows].

Then read Operation runner when the change touches harness invocation, run events, final validation, or terminal run state. The runner is the shared path used after a page-writing workflow has prepared its context and prompt [@operation-runner].

Use Run queue and sync when changing queued ingest, scheduled Garden, worker drain, or transcript sync. That page connects lifecycle work to durable run specs and the worker that drains queued records [@run-queue-sync].

Use Mutation safety when changing allowed files, auto-commit instructions, final validation, or any future runtime enforcement for out-of-tree edits [@mutation-safety].

Neighboring Pages#

Run states and events is the exact reference for run kinds, statuses, queued specs, cancellation, attach, and logs [@run-states]. Lifecycle operation is the concept page for the page-writing operation family [@lifecycle-concept].