add_files
ChatGPTAdd a
.docx or .pdf the lawyer supplied to the firm's workspace. Give a path you can read from this session for each file; returns one command per file. Run each with your shell to move the bytes (the file content never passes through you), and each prints back an oid and size on success. Then, inside execute, record each file in the repository with docket add-file <path> <oid> <size> and commit, so it becomes a retrievable part of the case. Recording a file stores a REFERENCE, not its bytes, so it is still not readable in your working copy afterwards: to open one (read a PDF, or inspect a Word file's numbering and styles), list it in needs on the execute call that reads it — the oid for a file you just uploaded, or its repository path once recorded — and only then are its bytes there to read. .docx and .pdf are case content and are recorded this way. A .png or .jpg is also accepted, but it is a firm image (a signature, a letterhead mark) rather than case content: record it with docket add-asset <name> <oid> instead, which stores it in the firm's library for every document that references it. A .md is accepted only to hand a document to DocketDrafter, cited by its oid in send_feedback; it is never recorded and never read back, so firm knowledge in a .md belongs in the repository, written through execute. Nothing else is accepted. The commands are for you to run; the lawyer cannot run commands, so they are not something to show them. A command failing because your session cannot reach our host is the one case to involve them: tell them the file is ready but the transfer is blocked, and give them the domain to allow (where to allow it differs between assistants, so name the domain and let them find the setting).





