Withdraw a document

POST 
/v1/projects/:project_id/documents/:document_id/withdraw

Takes a document out of every default read while keeping its history. The withdrawal is archived as a tombstone version, so one mechanism answers what a document holds now and there is no second lifecycle flag for a reader to miss.

Its chunks are dropped from the knowledge index, so a withdrawn document costs a live search nothing. The content is not lost with them: it is in the version before the tombstone, which POST /v1/projects/{project_id}/documents/{document_id}/versions/{version}/restore re-chunks from.

DELETE stays what it is — permanent, and it removes the backing file. Withdrawal is the reversible act. It does not apply under /.system/: a platform-written document keeps the owning module's lifecycle.

Request

Responses

200

The withdrawn document

400

Bad Request — the document is filed under the reserved root

401

Unauthorized

403

Forbidden

404

Document not found

409

The document is already withdrawn (DOCUMENT_ALREADY_WITHDRAWN), or it has moved past the version this write read (VERSION_CONFLICT, with meta.current_version).