← Portable Mind MapsCONTENT HISTORY

Update to Portable Mind Maps

Snapshot Sep 30, 2026 · 23:14 UTC · version 2.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Author, import, revise, safely merge, diff, reorder, preview, repair, and validate portable mind maps as JSON, rich Markdown, OPML, FreeMind XML, Mermaid, and GraphML. Use for mind maps, concept maps, brainstorming trees, and nested outlines.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 256
    },
    {
      "relative_path": "references/canonical-v2.schema.json",
      "size_in_bytes": 1923
    },
    {
      "relative_path": "references/format-compatibility.md",
      "size_in_bytes": 1596
    },
    {
      "relative_path": "references/mindmap-contract.md",
      "size_in_bytes": 1327
    },
    {
      "relative_path": "references/reorder-v1.schema.json",
      "size_in_bytes": 835
    },
    {
      "relative_path": "references/v2-contract.md",
      "size_in_bytes": 2823
    },
    {
      "relative_path": "scripts/create_mindmap.py",
      "size_in_bytes": 15634
    },
    {
      "relative_path": "scripts/mindmap_tool.py",
      "size_in_bytes": 67649
    }
  ],
  "name": "portable-mindmaps",
  "skill_md_contents": "---\nname: portable-mindmaps\ndescription: Author, import, revise, safely merge, diff, reorder, preview, repair, and validate portable mind maps as JSON, rich Markdown, OPML, FreeMind XML, Mermaid, and GraphML. Use for mind maps, concept maps, brainstorming trees, and nested outlines.\n---\n\n# Portable mind maps\n\nUse one canonical rooted tree with stable node IDs, then export only the portable representations the user needs. Run `scripts/mindmap_tool.py` for deterministic operations. Read `references/v2-contract.md`, validate canonical inputs against `references/canonical-v2.schema.json`, and validate explicit reorder requests against `references/reorder-v1.schema.json`.\n\n## Routes\n\n- New map: author canonical v2 JSON and run `create`.\n- Existing JSON, generated Markdown, OPML, `.mm`, GraphML, or generated Mermaid mind-map source: run `import`, revise the canonical document, then `export` it.\n- Focused work: use `extract` for a subtree, `diff` for a machine-readable comparison, and `reorder` for an explicit order-only change.\n- Merge: route to `merge-safe`, which merges by stable ID and defaults conflicts to `error`. Use `--conflict base|incoming` only when the user states that policy. The legacy `merge` command remains deprecated compatibility behavior that replaces a matching subtree; warn before any explicit legacy use.\n- Diagnosis: run `lint`; use `repair` only to normalize into canonical v2 without inventing hierarchy.\n- Preview: run `preview --format svg|html --layout right|down|radial` for a deterministic, script-free structural preview.\n\nDefault exports remain Markdown, OPML, and FreeMind-compatible XML. Select JSON, Mermaid mind-map source, or GraphML with `--formats`. Generated Markdown round-trips supported metadata through deterministic comments while remaining a readable outline. Preserve hierarchy and stable IDs; report deterministic metadata loss whenever a target cannot represent notes, links, tags, status, priority, or cross-links.\n\nAll imports and transformed results pass through the same canonical validator. Reject DTD/entity-bearing XML, invalid URLs or priorities, duplicate IDs, dangling cross-links, excessive depth/count, duplicate output formats, symlink paths, and overwrite attempts.\n\nDo not generate proprietary archives, automate desktop applications, or modify an application's library. Static checks do not prove native import fidelity or layout.\n"
}

SHA-256 of public snapshot: 90b7a6f5e0a63e778042f38f62a87ec3a07265f850849b217bd04cc3f50598c6