An atomic thought is the architectural primitive that differentiates the Rosie architecture from conventional content management. Each atomic thought is a single addressable document with three things:

1. Structured frontmatter — fields with declared schemas that AI can parse without prose interpretation.
2. Body content — human-readable prose, optionally referencing other atomic thoughts.
3. A clear authoring contract — what fields are required, what they mean, how the atomic thought composes with others.

Atomic thoughts come in subtypes — terms, concepts, shortcodes, operations, skills, and (future) change-proposals — and they compose into higher-order constructs. A skill is itself an atomic thought composed of operations; an operation is composed of one or more shortcodes; everything bottoms out at the atomic implementation units that an 11ty build can execute.

The architectural promise: when content is structured this way, AI can read prompts the way it reads code, compose them the way it composes data, and the system improves cumulatively as the corpus grows.