File Storage & Transfer Rules

- Confirm the Filesystem MCP connector is live and the canonical path is registered (see Connectors & Capabilities). A connector that responds is not the same as one that can access the project directory.
- Read `admin\AGENT_INSTRUCTIONS.md` for an existing canonical path and drop folder. Reuse whatever is already defined.
- Check whether a `#drop\` folder exists at the project root.

- If no canonical path is defined: list the directories the Filesystem MCP connector can access and ask "Is your project directory on this list?" If yes, use it. If no, provide the add-directory steps below and wait.
- Otherwise nothing to ask.

Create the `#drop\` folder at the project root if it does not exist. Then add this section to `admin\AGENT_INSTRUCTIONS.md`:

```
* FILE STORAGE & TOOLING

| Layer                | Location      | Purpose                         |
|----------------------|---------------|---------------------------------|
| Project Files        | Claude panel  | Reference, brand, instr. mirror |
| Canonical Repository | [path]        | Working files, outputs, records |
| Drop Folder          | [path]\#drop  | All incoming files land here    |

Two storage layers, two jobs:
- Project Files (Claude panel): the agent's desk. Always visible.
  Cloud-based. Reference docs, brand assets, sanitized profiles.
- Local File System (via Filesystem MCP): the real filing cabinet.
  Permanent. Yours.

FILESYSTEM CONNECTOR DIRECTORY CONFIRMATION -- REQUIRED BEFORE ANY FILE OP
Being connected and having a working directory accessible are two
different things. Before any file read or write:
1. Verify the connector is live
2. List the directories registered/accessible through the connector
3. Ask: "Is your project directory on this list?"
4. If YES: proceed using the confirmed path
5. If NO: stop file operations and give add-directory steps:
   Settings (gear, top right) -> Integrations/Connectors -> Filesystem MCP
   -> Configure/Manage -> Add Directory -> enter [path] -> Save -> return
Hard rule: do not attempt file operations on an unconfirmed path.

FILE TRANSFER RULE -- NON-NEGOTIABLE
Files move from Claude to the file system one way: presented inline in the
conversation with a download button. Click it. Save it.
NEVER convert, encode, split, or reconstruct files using base64 or any
other workaround. A split file is a corrupted file.
If a file can't write cleanly: "Download this and drop it in #drop\. Let
me know when it's there and I'll move it into place."

Do not type bank account numbers, passwords, or SSNs into the chat.
EIN is a public business identifier and is fine to include in
conversations and documents. Fill sensitive fields on the downloaded file
after saving locally.
```

Confirm: your storage layers and transfer rules are in the agent instructions -- canonical path [path], drop folder [path]\#drop, and the no-base64 transfer rule are locked in. Want to install another, or is that everything for now?