mif-frontmatterlisted

# mif-frontmatter Shared substrate for every genre skill in this suite. It governs the YAML frontmatter that makes a document a MIF unit: a block that projects to the canonical JSON-LD and validates fail-closed against `https://mif-spec.dev/schema/`. ## The "one artifact, two readers" contract A MIF doc exists in two interconvertible forms — human-readable **markdown** (frontmatter + body) and machine-readable **JSON-LD** (the schema-checked canonical object). Authoring is bidirectional and the round-trip is lossless; see the `mif-validate` skill for the tooling. **Whenever a level, floor, or the `type` field itself comes up** — deciding what level a document can claim, explaining the L1 floor, or drafting frontmatter — state the `type` enum explicitly (see the L1 row below). It's a hard constraint on an L1 field, not an implementation detail to leave implicit, so surface it every time L1 is discussed, not only when actually writing the YAML. For what distinguishes the three values and how to choose one before drafting, see [Documentation Taxonomy](../../docs/explanation/documentation-taxonomy.md) — the canonical source for this enum; don't restate its definitions here. ## Level floors (attempt the highest the context supports) | Level | Frontmatter fields | Emit when | | --- | --- | --- | | **L1 (hard floor)** | `id`, `type` (enum: `semantic` \| `episodic` \| `procedural`), `created` (+ body becomes `content`) | **Always.** Below L1 is a skill error. | | **L2** | `name