LawY

Finalizes one prepared add Document Operation, which adds a new document to an existing folder of the matter. It never creates a folder (create_folder does that, under its own capability) and never overwrites an existing file: a file with the same name in the folder returns conflict and saves nothing. Finalization uses temporary naming and conflict-safe compensation, and a dispatched provider step is never retried. The result is final and carries the canonical destination, a status of saved, conflict, or not_saved, and a plain-language message to relay to the user. Nothing needs to be checked or polled afterward, and a write is never resent.

add_document

Append the next ordered base64 chunk of at most 512 KiB to the same Document Operation.

append_document_upload_chunk

Assemble exact ordered fallback bytes for the same Document Operation.

complete_document_upload_chunks

Chunk fallback is enabled only after DNS, TCP, TLS, or network-policy failure for the exact expected upload host. HTTP, CORS, checksum, and signature failures do not qualify.

confirm_document_upload_egress_failure

Create one new folder inside an existing folder of a granted matter. The parent is one exact folder_id and folder_path pair returned by list_granted_folders for the same matter_id, carried unchanged into parent_folder_id and parent_folder_path; the matter root is the pair whose folder_path is "/". matter_id is not a folder id, a folder_path list_granted_folders did not return is rejected, and other values are not guessed. name is one folder name without "/" or "\". idempotency_key is a stable key for this folder creation. When verified, the response returns the new folder's exact folder_id and folder_path, usable as a move_document destination or through a fresh list_granted_folders call. conflict means a folder with that name already exists in the parent, and that existing folder is the target. Requires the Create Folders capability. The returned matter, destination, and exact status are reported to the user afterward: only verified means the change is proven in the live folder tree; conflict means nothing was changed; accepted, in_progress, acceptance_unknown, verification_mismatch, and verification_timed_out mean the change is not yet proven and never authorize a new idempotency_key. One of those statuses is re-checked by repeating the identical call with the same idempotency_key: the re-check re-reads the tree and never dispatches a second write. A different folder value is never substituted.

create_folder

List currently authorized documents in one granted matter. Each call inspects at most 20 candidates; limit is a maximum, not a promised page size. Pagination continues through next_cursor: each subsequent call carries the same limit and the returned next_cursor until next_cursor is absent, including after an empty page. An invalid_cursor error means the candidate set or request context may have changed, and pagination restarts from a call without a cursor.

list_granted_documents

List exact selectable folder_id and folder_path pairs for an authorized add, move destination, or new-folder parent. The matter root is returned last as folder_path "/" paired with its exact provider folder_id. Each returned pair is carried unchanged into later calls and is never edited or constructed. When more than one pair is returned and the user has not named a folder, the folder selection needs a user decision. An empty result means no valid add target is currently available.

list_granted_folders

List only matters currently authorized for this Connected Agent Connection.

list_granted_matters

Move one existing document into a different existing folder of the same matter. The document keeps its content, versions, and name; only its folder changes, and moving it back restores the previous place. document_id comes from list_granted_documents or search_granted_documents. The destination is one exact folder_id and folder_path pair returned by list_granted_folders for the same matter_id, carried unchanged. matter_id is not a folder id, a folder_path list_granted_folders did not return is rejected, and other values are not guessed. The move covers documents the user asked to organize; when the user has not named the document and destination, the planned document and destination are stated to the user before the move. idempotency_key is a stable key for one intended move. A document already in the destination returns verified without a change. conflict means the destination already holds a document with that name. Requires the Move Documents capability. The returned matter, destination, and exact status are reported to the user afterward: only verified means the change is proven in the live folder tree; conflict means nothing was changed; accepted, in_progress, acceptance_unknown, verification_mismatch, and verification_timed_out mean the change is not yet proven and never authorize a new idempotency_key. One of those statuses is re-checked by repeating the identical call with the same idempotency_key: the re-check re-reads the tree and never dispatches a second write. A different folder value is never substituted.

move_document

Read current Document Text directly. Document Text is the default for all read-only work, including analysis, extraction, comparison, summarization, and derivative work; when the text is empty or not enough, for example an image, scan, or diagram, the original bytes are available through Read Original Document instead. The response includes one opaque source_reference that binds this connection, matter, document, text revision, content digest, and read time. A source_reference is provenance evidence, not authorization; it is valid only as an unchanged source_references entry in a request_document_upload operation that this document supported, and it cannot be decoded or constructed.

read_document_text