Skip to content
mif-docs
One artifact, two readers A single source document fans out to a human-readable Markdown panel (amber) and a machine-parseable JSON-LD panel (cyan), joined by a lossless round-trip, under the chevron-M mark and a mif-validate conformance badge. MIF ONE SOURCE ARTIFACT --- frontmatter --- human-readable # A decision, in prose Markdown · a person reads machine-parseable { "@type": "Decision", "entity": { … } } JSON-LD · a parser resolves mif-validate · lossless round-trip · L1→L3

mif-docs

One skill per document genre. Every doc, two readers — written once, read by a person and a parser.
Get started Skill catalog by purpose One artifact, two readers MIF home

These docs follow the Diátaxis framework — four modes, each matched to a different need — plus the architecture, the decision records, and the operational runbooks. Every page is itself authored with the suite’s skills and validated by mif-validate: the same artifact a person reads and a parser resolves.

New here? Start with the tutorial Learning-oriented. Install the suite, then author and validate your first MIF document step by step.
Skill catalog by purpose Information-oriented. Every skill in the suite — orchestrator, authoring helpers, the four Diátaxis quadrants, architecture, decisions, specs, operations, and changelog — each with detailed exposure.
Genre & CLI quick reference Information-oriented. The terse lookup: genres, doc-set recipes, and every script in scripts/ with its arguments and exit behavior.
How-to guides Task-oriented. The recipe for authoring, validating, and converting a document between Markdown and JSON-LD.
Explanation Understanding-oriented. Why each document is at once a human artifact and a machine-conformant unit.
Architecture The suite's own arc42 and C4 architecture — how the engine, genres, and MIF substrate fit together.
Decisions (ADRs) The architecture decision records — the context and consequences behind each choice.
MIF ecosystem docs The broader MIF ecosystem documentation, served at the org root. The normative spec lives at mif-spec.dev.