Archive, deletion, confirmation, and public safety

Archiving a card is reversible and needs no confirmation; unarchiving restores it to its existing column and rechecks that column’s WIP limit. Archived cards are excluded from list_cards, remain discoverable through search_cards, and remain readable by ID through get_card. This asymmetric visibility is current runtime behavior.

delete_card is permanent and cascades the card’s comments, label associations, commit attachments, and note links. Prefer archive unless the user clearly requests permanent removal. The four destructive Kanban actions—delete_card, delete_comment, delete_commit, and delete_label—all require UserConfirm and Strict drift checking. A knowledge card cannot bypass that gate.

If the user rejects confirmation, the operation did not execute. Do not repeatedly call the same destructive action to pressure for approval. All Kanban mutations, including reversible ones, are unavailable on public conversation surfaces; public contexts may use only read actions.

resource_not_found deliberately covers both a missing resource and a resource the Agent is not allowed to see. Do not reveal or assert that a board or card does not exist based on this code alone. A read-only board mutation instead returns permission_denied.

Related actions

arinova.kanban.archive_card, arinova.kanban.unarchive_card, arinova.kanban.delete_card, arinova.kanban.delete_comment, arinova.kanban.delete_commit, arinova.kanban.delete_label, arinova.kanban.get_card, arinova.kanban.search_cards

Also known as

archive card, unarchive card, delete card, permanent deletion, destructive confirmation, public conversation

---

Machine-readable Markdown · Knowledge index