Handbook
Packs and domains
Operators and integrators working with domain-specific intelligence — curated policies and reasoning paths for named problem families.
Updated
Who is this for?
Operators and integrators working with domain-specific intelligence — curated policies and reasoning paths for named problem families.
What problem does it solve?
Different domains need different deterministic guards, legal break-in actions, and evidence shapes. Domain packs bundle those rules so sessions stay governed and auditable per family.
What can you do?
| Domain family | Operator use |
|---|---|
| Human-Life | Use the audited v4.1 capability set for life-domain reasoning overlays (39 general + life intelligences). |
| MathGenesis | Work with math knowledge ingestion, validation, and concept discovery under clean-room policy. |
| PhysicsGenesis | Work with physics knowledge, simulation validation, and model discovery (handbook coverage growing). |
| Other packs | Select from the problem-class catalog when a registered pack matches your case. |
Each pack runs under an intelligence policy with a reasoning ladder, token caps, and closed break-in actions.
What can you not do?
- Assume every cataloged capability is domain-validated — many entries are I1 contract adapters.
- Mix pack policies arbitrarily — problem class selects the governing policy.
- Import vendor prompt packs as end-user features — those are maintainer tooling, not operator workflows.
Limitations
Pack maturity varies. Human-Life v4.1 is the most complete audited import. MathGenesis has narrative handbook coverage; PhysicsGenesis handbook pages are newer. Backlog intelligences (e.g. IRS/MO) are tracked in maintainer registries, not operator workflows.
Next steps
- Concept documentation — how intelligences within a pack are documented
- Sessions and audit
- System depth: paired system page, Human-Life pack v4.1