---
{
  "id": "platform.mindmap.delete-restore-and-archive",
  "topic": "mindmap",
  "title": "Mindmap delete, restore, archive, and retention",
  "locale": "en",
  "version": "2026-08-09",
  "summary": "Node deletion is a reversible batch, whole-map lifecycle has explicit archive controls, and JSON/PDF export writes bounded artifacts to File Center.",
  "content": "`delete_node` soft-deletes a subtree without action-level confirmation and returns `deleteBatchId`, `deletedNodeIds`, and former anchors. `delete_node_promote_children` deletes only that node and preserves direct-child order. The Action surface has no child-anchor argument, so promoted root children use vertically staggered fallback anchors; only the v1 REST surface accepts explicit anchors. Results include `updatedNodes` and changed `siblingSortKeys`.\n\nRestore uses `deleteBatchId`, never `nodeId`. Former anchors must still bound the position and promoted children remain a contiguous sequence; topology drift conflicts instead of performing a best-effort restore. The 2,000-active-node limit applies, and a root may be restored alongside other active roots. Soft-deleted nodes are retained for 30 days; the sweeper permanently purges tombstones and makes the batch unrestorable.\n\n`archive_mindmap` and `unarchive_mindmap` provide reversible whole-map lifecycle. `delete_mindmap` requires user confirmation and only accepts an already archived map; this hard delete purges version history and cannot be restored. `replace_outline` also requires confirmation.\n\n`export_mindmap` writes compact JSON or outline PDF to the user's personal File Center. JSON contains only `id`, `parent_id`, `label`, `color`, `icon`, `collapsed`, and `sort_key`; it is not a canonical backup and omits rich text, images, links, and layout. Dry-run creates no file, and PDF is not a pixel-identical canvas export.\n",
  "aliases": [
    "restore deleted branch",
    "delete batch id",
    "archive before delete",
    "promoted children",
    "soft delete retention"
  ],
  "tags": [
    "mindmap",
    "deletion",
    "restore"
  ],
  "relatedActions": [
    "arinova.mindmap.delete_node",
    "arinova.mindmap.delete_node_promote_children",
    "arinova.mindmap.restore_node",
    "arinova.mindmap.delete_mindmap",
    "arinova.mindmap.replace_outline",
    "arinova.mindmap.archive_mindmap",
    "arinova.mindmap.unarchive_mindmap",
    "arinova.mindmap.export_mindmap"
  ],
  "relatedActionPrefixes": [],
  "url": "https://docs.arinova.ai/en/kb/mindmap/delete-restore-and-archive/"
}
---

`delete_node` soft-deletes a subtree without action-level confirmation and returns `deleteBatchId`, `deletedNodeIds`, and former anchors. `delete_node_promote_children` deletes only that node and preserves direct-child order. The Action surface has no child-anchor argument, so promoted root children use vertically staggered fallback anchors; only the v1 REST surface accepts explicit anchors. Results include `updatedNodes` and changed `siblingSortKeys`.

Restore uses `deleteBatchId`, never `nodeId`. Former anchors must still bound the position and promoted children remain a contiguous sequence; topology drift conflicts instead of performing a best-effort restore. The 2,000-active-node limit applies, and a root may be restored alongside other active roots. Soft-deleted nodes are retained for 30 days; the sweeper permanently purges tombstones and makes the batch unrestorable.

`archive_mindmap` and `unarchive_mindmap` provide reversible whole-map lifecycle. `delete_mindmap` requires user confirmation and only accepts an already archived map; this hard delete purges version history and cannot be restored. `replace_outline` also requires confirmation.

`export_mindmap` writes compact JSON or outline PDF to the user's personal File Center. JSON contains only `id`, `parent_id`, `label`, `color`, `icon`, `collapsed`, and `sort_key`; it is not a canonical backup and omits rich text, images, links, and layout. Dry-run creates no file, and PDF is not a pixel-identical canvas export.