Domains / focus
Focus domain
Priority oversight of incoming work signals: directives set scope, threads keep evidence, outcomes keep results.
Use it when: You triage messages, tickets, and other signals against declared priorities.
cumaru install agent <agent> --domain focus Pillars
| Pillar | Lifetime | Holds |
|---|---|---|
directives/ | Durable | Priority scope and direction, one file per directive. |
threads/ | Durable | Source context with a dated state history; settled threads move to yearly archives. |
outcomes/ | Durable | Results grouped by adopter-declared area. |
sources/ | Durable | Read-only access to each data source. |
Roles
- Admin: the only role. Local document maintenance does not authorize edits to external services.
Lifecycle
- Read sources -> capture or update threads -> derive outcomes.
- Settled threads are archived under threads/archive-YYYY/, not deleted.
- An outcome is valued against the directives it serves.
Skills
Domain-specific skills, in addition to the universal ones: cumaru-directives,cumaru-sources,cumaru-thread,cumaru-outcome,cumaru-zoom.
Bootstrap
Ships a domain bootstrap: confirm sources reachable by your tools, then directives and outcome areas. Unreachable sources are reported, never written as active.
Domain rules
- New evidence does not silently redefine directive scope.
- Intake is declared per source in sources/.
Example: Triage a new request
- cumaru-sources reads the active sources under the active directives.
- cumaru-thread records the request with matched directives and a short rationale.
- cumaru-outcome records the result once the thread supports it.
Source: domain.md, config.yaml, roles, skills at revision 37ad79f. The example is a summary
of the shipped recipes, not CLI output.