<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Map :: Choria Configuration Manager</title><link>https://choria-cm.dev/design/codemap/</link><description>A guided deep-dive into the CCM codebase.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://choria-cm.dev/design/codemap/index.xml" rel="self" type="application/rss+xml"/><item><title>Architecture</title><link>https://choria-cm.dev/design/codemap/architecture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://choria-cm.dev/design/codemap/architecture/</guid><description>Package layering and the three seams that keep the engine composable: the model contracts, the provider registry, and the manager.</description></item><item><title>The Resource-Provider Model</title><link>https://choria-cm.dev/design/codemap/resource-provider-model/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://choria-cm.dev/design/codemap/resource-provider-model/</guid><description>How a concrete resource type is built, and how one resource is driven to its desired state: decide, act, and verify.</description></item><item><title>The Apply Engine</title><link>https://choria-cm.dev/design/codemap/apply-engine/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://choria-cm.dev/design/codemap/apply-engine/</guid><description>How a manifest of many resources is parsed, resolved against data, and executed in order, with require as a gate and events as the shared state.</description></item><item><title>The Agent</title><link>https://choria-cm.dev/design/codemap/agent/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://choria-cm.dev/design/codemap/agent/</guid><description>The background loop that applies manifests on a timer, watches remote sources, refreshes facts and data, and remediates failing health checks.</description></item><item><title>Data, Facts, and Templates</title><link>https://choria-cm.dev/design/codemap/data-and-templates/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://choria-cm.dev/design/codemap/data-and-templates/</guid><description>How facts are gathered, how Hiera layers a hierarchy into resolved data, and how templates render that data into resource fields.</description></item><item><title>Registration and Discovery</title><link>https://choria-cm.dev/design/codemap/registration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://choria-cm.dev/design/codemap/registration/</guid><description>How stable resources announce themselves into a JetStream store keyed by subject, and how other nodes look them up or watch them live.</description></item><item><title>Observability</title><link>https://choria-cm.dev/design/codemap/observability/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://choria-cm.dev/design/codemap/observability/</guid><description>How each apply becomes a recorded event, a Prometheus counter, and a session summary, and how health checks feed remediation.</description></item><item><title>Reference and Map</title><link>https://choria-cm.dev/design/codemap/reference/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://choria-cm.dev/design/codemap/reference/</guid><description>The CLI command surface, a source map of every package, the key types and where they are explained, and a glossary.</description></item></channel></rss>