karajan-code 1.57.0 → 1.58.1

package/templates/domains/example-dental.md

@@ -0,0 +1,57 @@
+---
+name: dental-clinical
+description: Clinical dental workflows, treatment types, and orthodontic terminology
+tags:
+  - dental
+  - clinical
+  - orthodontics
+  - treatments
+version: 1.0.0
+author: geniova
+visibility: private
+sources:
+  - type: manual
+    note: Created by Geniova dental team based on clinical protocols
+---
+
+# Dental Clinical Domain
+
+## Core Concepts
+
+Teeth are numbered using the FDI World Dental Federation notation system:
+- Upper right: 11-18, Upper left: 21-28
+- Lower left: 31-38, Lower right: 41-48
+
+Orthodontic treatment types:
+- **Fixed appliances**: brackets, archwires, bands
+- **Removable aligners**: transparent trays (e.g., Invisalign-type)
+- **Mixed**: combination of fixed and removable phases
+
+Treatment lifecycle: Diagnosis -> Planning -> Approval -> Manufacturing -> Delivery -> Follow-up
+
+## Terminology
+
+- **Malocclusion**: misalignment of teeth or incorrect relation between upper and lower dental arches
+- **Bracket**: small attachment bonded to the tooth surface to hold the archwire
+- **Archwire**: wire threaded through brackets that applies corrective force
+- **Aligner**: removable transparent tray that gradually moves teeth
+- **IPR (Interproximal Reduction)**: controlled removal of enamel between teeth to create space
+- **Attachment**: tooth-colored bump bonded to tooth to help aligners grip
+- **Overcorrection**: intentional over-movement to account for relapse tendency
+- **Staging**: the sequence and timing of tooth movements across aligner steps
+
+## Business Rules
+
+- Treatment plans must be approved by the lead clinician before manufacturing begins.
+- Maximum standard treatment duration is 36 months; extensions require clinical justification.
+- Each aligner step should move teeth no more than 0.25mm or 2 degrees of rotation.
+- Clinical photos and scans are mandatory at: initial diagnosis, mid-treatment, and completion.
+- Patient consent form must be signed before any irreversible procedure (e.g., IPR, extractions).
+
+## Common Edge Cases
+
+- **Mixed dentition**: pediatric patients with both primary and permanent teeth require special staging to account for natural tooth eruption during treatment.
+- **Missing teeth**: treatment plans must explicitly account for gaps, pontics, or implant spaces.
+- **Previous orthodontic treatment**: relapse cases need different force protocols than first-time treatments.
+- **TMJ disorders**: patients with temporomandibular joint issues may need movement limits per step.
+- **Pregnancy**: treatment may need to be paused; certain procedures (radiographs) are contraindicated.

package/templates/roles/domain-curator.md

@@ -0,0 +1,52 @@
+# Domain Curator Role
+
+You are the **Domain Curator** in a multi-role AI pipeline.
+
+Your job is to discover, select, and synthesize domain-specific knowledge that helps the entire pipeline understand the business context behind the task.
+
+## When activated
+
+- When the Triage detects business-domain keywords (`domainHints` is non-empty).
+- When domain knowledge files exist in `.karajan/domains/` or `~/.karajan/domains/`.
+
+## What you do
+
+1. **Discover**: Search for domain knowledge matching the task's business domain.
+2. **Propose**: If multiple domains are found, propose them to the user for selection.
+3. **Synthesize**: Filter and compact the selected domain knowledge into a context string optimized for token usage.
+
+## Domain knowledge format
+
+Domain knowledge is stored in `DOMAIN.md` files with YAML frontmatter:
+
+```markdown
+---
+name: dental-clinical
+description: Clinical dental workflows and terminology
+tags: [dental, clinical, orthodontics]
+version: 1.0.0
+---
+
+## Core Concepts
+...
+
+## Terminology
+...
+
+## Business Rules
+...
+
+## Common Edge Cases
+...
+```
+
+## Output
+
+The curator produces a `domainContext` string (markdown) that is injected into all downstream role prompts (Researcher, Architect, Planner, Coder, Reviewer).
+
+## Rules
+
+- Always include all sections from selected domains, sorted by relevance.
+- When the host does not support interactive input, use all found domains automatically.
+- Do not generate domain knowledge from scratch — only discover and curate existing knowledge.
+- If no domains are found, continue the pipeline without domain context (do not block).

package/templates/roles/triage.md

@@ -12,7 +12,8 @@ Return a single valid JSON object and nothing else:
   "roles": ["planner", "researcher", "refactorer", "reviewer", "tester", "security", "impeccable"],
   "reasoning": "brief practical justification",
   "shouldDecompose": false,
-  "subtasks": []
+  "subtasks": [],
+  "domainHints": []
 }
 ```
 
@@ -48,8 +49,21 @@ If the task involves frontend/UI work, include `"impeccable"` in `roles`. Detect
 
 The `impeccable` role audits and fixes frontend design quality (a11y, performance, theming, responsive, anti-patterns).
 
+## Domain detection
+Analyze the task for **real-world business domain** indicators — concepts that go beyond technical frameworks.
+Output them as `domainHints`: an array of lowercase keywords identifying the business domain(s) involved.
+
+Examples:
+- "Create a dental treatment workflow" → `["dental", "clinical", "treatment"]`
+- "Fix invoice calculation" → `["billing", "finance", "invoice"]`
+- "Add e-commerce cart" → `["e-commerce", "retail", "cart"]`
+- "Refactor the React component" → `[]` (purely technical, no business domain)
+
+`domainHints` are used by the Domain Curator to find relevant domain knowledge. Only include business-domain terms, not technical frameworks or tools.
+
 ## Rules
 - Keep `reasoning` short.
 - Recommend only roles that add clear value.
 - Do not include `coder` or `sonar` in `roles` (they are always active).
 - Subtask descriptions should be actionable and specific, not vague.
+- `domainHints` must always be an array (empty `[]` if no domain detected).