Concepts

Concept pages define CodeAlmanac vocabulary that appears across architecture, guides, decisions, and reference pages. The topic graph defines concepts as the neighborhood for core vocabulary and mental models, and this hub routes readers to the term that explains the subject before they follow implementation details [@topics].

Use this page when a term is familiar enough to appear in several places but specific enough that a future agent should not infer its meaning from raw code.

Wiki Model#

Local repo wiki is the starting concept for this repository. It explains why the committed wiki source is the almanac/ Markdown tree and why derived indexes, run records, and scheduler state live under local machine state instead [@local-repo-wiki].

Page graph explains the derived model that connects pages, topics, links, file references, sources, backlinks, and health checks [@page-graph]. Why concept, guide, decision, and reference vocabulary exists today without being a validated frontmatter field is a product decision; see No page-kind field. For the implementation pages behind that derived model, continue to the Wiki architecture hub.

Lifecycle And Inputs#

Lifecycle operation defines build, ingest, and garden as the page-writing operation family [@lifecycle-operation]. Source material defines the raw input selected for ingest and keeps that input separate from page sources: evidence [@source-material].

Run ledger explains the durable records, queued specs, events, worker locks, and codealmanac jobs inspection surface used by lifecycle work [@run-ledger].

Product-story and launch-demo framing is not a concept: it lives in Demo CodeAlmanac in a launch video in guides/, since it is task-oriented copy for a specific piece of work rather than vocabulary this repo's code depends on.