Acknowledgments
Lineage for Merlon Docs documentation philosophy. Not operative rules — follow the parent skill QA principles and shard-responsibility.md.
| Source | Adapted into Merlon Docs |
|---|---|
| Single responsibility (software design) | One reason to change for documentation shards |
| Library / information architecture | Classify and shelve settled concepts for trustworthy retrieval |
| Diátaxis (Daniele Procida, 2020) | Documentation needs (tutorial, how-to, reference, explanation) as a job axis when judging splits |
| Cynefin (Dave Snowden and collaborators) | Settled vs emergent: durable shards hold current truth; probes stay in planning tools |
| Product practice (epics, stories, BDD, TDD) | Discovery in process tools; durable shards describe the product as it works now |