Format Model
Purpose
Section titled “Purpose”This page defines the cross-cutting format rules shared by all Domain Bundle artifacts.
File Anatomy
Section titled “File Anatomy”Every Domain Bundle artifact uses:
- Opening
--- - YAML frontmatter
- Closing
--- - Markdown body
Semantics:
- Frontmatter is the machine-readable contract.
- Markdown body is human and LLM guidance.
Design Principles
Section titled “Design Principles”- One file, two parts: YAML frontmatter plus Markdown body.
- Bundle structure should support progressive disclosure.
- Source references should support local first, remote later.
- Substrate-definition artifacts should declare the leaf lamina only; parent laminae are inferred.
- Modulator ownership belongs to lamina contracts and is inherited upward.
Pre-v1 Schema Policy
Section titled “Pre-v1 Schema Policy”- The schema may change quickly while the model is still being refined.
- Once a standard is chosen, the reference pages should switch to that standard immediately.
- Do not preserve compatibility aliases for superseded markdown key shapes unless explicitly required.
Naming Convention
Section titled “Naming Convention”All markdown config keys and identifiers in this format must use kebab-case.
Rules:
- Use kebab-case for frontmatter keys, reference keys, and artifact identifiers.
- Do not introduce new snake_case keys in markdown config files.
- Do not preserve or add snake_case compatibility paths for markdown keys unless explicitly required.
Examples:
domain-idnotdomain_idrequired-corticesnotrequired_corticesmodule-pathnotmodule_path
Exceptions:
- Python import values and symbol values are not reformatted.
- Free-form payloads inside
metadataor downstream config payloads may use snake_case when required by external systems.
Progressive Disclosure Model
Section titled “Progressive Disclosure Model”The intended loader flow is:
- Read the root artifact frontmatter only.
- Select candidate substrate-definition references through explicit root artifact lists.
- Load only the selected substrate-definition artifacts.
- Validate and compile launch inputs from the selected set.
This keeps parse cost and context small while still scaling to larger bundles.