fable-domain

fable-domain

This skill extends the fable-method problem-solving loop to non-code sectors by producing a domain adapter bundle. A bundle is four deliverables that together let fable-loop/fable-judge run against a new domain with its own nouns, authorities, and evidence rules - instead of falling back to coding defaults.

Use when a user asks to "create a domain adapter for X", "extend fable to marketing/research/ops", or "build a trap fixture for sector Y".

What a bundle is

A bundle is all four of these, or it is not done:

1. Domain workflow - ordered steps a practitioner follows in the sector, with a mermaid flowchart.
2. Adapter - a file conforming to the adapter template (applies-when, minimum evidence set, evidence sources, authority order, verification by observation, fraud table, done-by-example, sources with fetched links).
3. Trap fixture - an eval/scenarios/<scenario>/ directory with GROUND-TRUTH.md defining the task, the trap, scoring caps, and ideal behavior.
4. Smoke eval - 1-2 control-vs-adapter runs judged by diff + execution, labeled smoke-grade: pass|fail|partial.

No bundle = no claim. Partial output (only adapter, only workflow) is rejected at Stage 4.

Process

flowchart TD
 A[Stage 1: Discuss] -->|red-line hit| R[Refuse + stop]
 A -->|scope stop: nouns == coding default| S[No adapter needed]
 A -->|approved scope| B[Stage 2: Research]
 B -->|no web access| STOP1[No trustworthy bundle, stop]
 B -->|evidence gathered| C[Stage 3: Generate]
 C -->|duplicate adapter exists| DUP[Merge or abort]
 C -->|4 deliverables written| D[Stage 4: Verify]
 D -->|smoke + judge pass| DONE[Bundle complete]
 D -->|smoke fail| FIX[Patch + re-verify]
 FIX --> C

 R -.-> END[End]
 S -.-> END
 STOP1 -.-> END
 DUP -.-> END
 DONE --> END[Report outcome-first]

Stage 1 - Discuss

Ask the user, in plain questions, before generating anything:

• Use case: what task in this domain should the loop solve? One concrete example.
• What good looks like: what does a correct answer look like? What does a wrong answer look like?
• Trusted authorities: which orgs, standards, regulators, or practitioners does the user defer to?
• Must-nevers: what outputs are unacceptable, illegal, or harmful?
• Desired outputs: artifact shape - report, plan, checklist, data file, copy draft.