Documentation

Domains / base

Base domain

The minimal kernel: universal rules, disciplines, and meta scaffolding, with no business pillars.

Use it when: You want to design your own domain from scratch.

cumaru install agent <agent> --domain base

Pillars

None. This domain ships no content pillars.

Roles

  • Admin: full read and write access across .cumaru/ and the project. Domains extend this set.

Lifecycle

  • There is no predefined flow.
  • Declare your own pillars in config.yaml under root, create each <pillar>/index.md from templates/any-index.md, and run cumaru doctor.
  • The loading rule then follows the structure you build.

Skills

No domain-specific skills. The universal skills apply.

Bootstrap

The domain bootstrap is the universal rules only: ask one topic at a time, write only confirmed answers, use the CLI, and report with doctor.

Domain rules

  • base is an alias for __base. It is the default when install has no --domain.
  • With no pillars, Admin loads only what the task names.

Example: Add a first custom pillar

  1. Declare a notes pillar as a child of root in .cumaru/config.yaml.
  2. cumaru fs notes create, then cumaru fs notes/index.md create.
  3. Give notes/index.md a summary: in its frontmatter.
  4. Run cumaru doctor until it passes.

Source: domain.md, config.yaml, roles, skills at revision 37ad79f. The example is a summary of the shipped recipes, not CLI output.

Back to the comparison