Read the 'Artifact types: use Document as universal fallback' rule from playbook 'Playbook for Playbooks'. Slug: artifact-types-use-document-as-universal-fallback. always_apply: true. Mimir's artifact type field has a restricted set of valid values that is not documented in the MCP schema. When creating artifacts for datasets, models, code, or other non-document outputs, use type "Document" as the universal fallback. Capture the true nature (dataset, trained model, etc.) in the artifact description instead.

Read the 'Goals go in descriptions' rule from playbook 'Playbook for Playbooks'. Slug: goals-go-in-descriptions. always_apply: true. Goals are not a separate entity. They live in the description field of the Playbook, Phase, or Workflow they motivate. Every Phase and Workflow must have a description that answers "why does this exist?"

Read the 'Granularity rule' rule from playbook 'Playbook for Playbooks'. Slug: granularity-rule. always_apply: true. A Phase groups workflows that share a strategic purpose. A Workflow is a coherent sequence of activities with a defined output. If in doubt, prefer Workflow over Phase — phases can be merged later.

Read the 'Make implicit agents explicit — only when useful' rule from playbook 'Playbook for Playbooks'. Slug: make-implicit-agents-explicit. always_apply: true. If the source has named roles, define them as Agents. If roles are implicit, use source-type heuristics: - Books/notes: define at minimum the practitioner role - Scientific papers: infer from implementation team structure (ML Engineer, Data Engineer, Researcher) If all activities would share the same agent, omit agents entirely — undifferentiated agents add no value. Agents are useful only when they differentiate who does what.

Read the 'Naming convention' rule from playbook 'Playbook for Playbooks'. Slug: naming-convention. always_apply: true. Every workflow gets a 3-letter uppercase abbreviation (e.g. PIN, EKN, ASP). Use it consistently in activity references and Mimir workflow names.

Read the 'No release without intern test' rule from playbook 'Playbook for Playbooks'. Slug: no-release-without-intern-test. always_apply: true. Do not release a playbook until Run intern test has passed. Pass means a capable intern or coding agent with no prior domain knowledge, given only an activity packet (name, guidance, and that activity's linked skills, artifacts, rules, and agent), can tell what to do or at least find pointers to the pieces they need. Oral briefings, hidden files, and author memory do not count. Sample at least one activity per workflow, including the hardest assembly step — not only the easy ones. Failures are fixed on the activity (guidance and links) and re-tested.

Read the 'Single-pass extraction preferred' rule from playbook 'Playbook for Playbooks'. Slug: single-pass-extraction-preferred. always_apply: true. Work through the source sequentially and drop content into the appropriate bucket as you encounter it. Do not make separate passes per bucket — that wastes time and loses the flow context that helps with correct categorization. The Extraction Worksheet template is designed to accept content in any order.

Read the 'Source fidelity' rule from playbook 'Playbook for Playbooks'. Slug: source-fidelity. always_apply: true. Every item in the Extraction Worksheet must include a reference to where it came from in the source (chapter, section, page, bullet). This enables traceability and future PIPs.

Read the 'Loose mapping for unmappable content' rule from playbook 'Playbook for Playbooks'. Slug: unmappable-content-becomes-a-rule. always_apply: true. When source content doesn't map cleanly to any Mimir entity, use loose mapping: find the nearest ontology type and capture the nuance in the description field. Nothing should be dropped — it just lands at the right level of fidelity. Loose mapping guide: - Background / Related Work → summarize in playbook or phase description - Problem / task definitions → map as a Rule with the formal definition in the content field - Mathematical or formal content → summarize in activity guidance or rule content; transcribe verbatim only if the exact formulation is operationally critical - Motivating examples → skip, or include as an illustrative note in activity guidance - Conclusions / discussion → extract any constraints or rules; discard the rest