Fable Artifact

Turn requirements and evidence into a standalone artifact whose content, structure, diagrams, links, and rendered output can all be checked independently.

Mission

An artifact is not successful because the Markdown parses or the diagram looks polished. It must communicate the right claims to the right audience, preserve source truth, make assumptions visible, and render in the medium the user will actually consume.

Activate When

• producing RFCs, architecture proposals, technical reports, runbooks, decision records, diagrams, or rich standalone documentation;
• packaging analysis/results into a durable document;
• creating a diagram or interactive explanatory artifact from established requirements/evidence.

Do Not Activate When

• a one-paragraph answer is sufficient;
• application logic itself needs modification (fable-execute);
• the main work is numerical chart selection (fable-dataviz);
• facts required by the artifact have not been researched/discovered yet.