map-init

# /map-init Install or remove the Map Your Knowledge (MYK) route on explicitly selected directive surfaces. Never touch vault content. ## Managed block Use these marker strings exactly. Adapt placement only. ```markdown <!-- map-init:begin --> Before reasoning about whether Markdown is organized, unstructured, or a candidate for organization, or assessing, planning, creating, editing, naming, moving, linking, mapping, checking, or maintaining it, load `map-rules` and every reference it selects. Use `map-this` for bounded organization and zero-write assessment. If either skill or required content is unavailable, stop. Never reconstruct it from memory. <!-- map-init:end --> ``` Parse only exact marker-only lines outside fenced code. One begin followed by one end, without nesting, is managed. Zero marker lines means absent. Every other marker arrangement is `MALFORMED` and stops. ## State model Classify each selected existing directive file before proposing a change: - `INSTALL`: install requested; no markers, legacy clause, or untagged equivalent exists. - `UPDATE`: install requested; exactly one well-formed managed block is stale, or exactly one legacy `[myk.routing]` clause is present. - `REMOVE`: removal requested; exactly one well-formed managed block or one legacy clause is present. - `NO-OP`: the requested end state already matches exactly. - `CONFLICT`: an untagged equivalent, competing route, unsupported placement, missing directive file, or unresolved target au...