Think inside your AI world.
Box through Unl
Box will hand back every file in the folder, its metadata and the text inside it on request. Whether the set is complete enough to leave your building is a checklist question, and Box doesn't keep the checklist.
Box through Unl reads folder contents, file details and document text against the hand-off checklist you have ratified, so 'is this deliverable ready to send' comes back verdict-shaped with the file still missing.
What Box holds
Naked, Box through Unl reads what's actually stored, not a status report:
- Search files by keyword, with metadata and file-extension filters
- Search files using SQL-like metadata queries
- Search folders by name
- List files, folders and web links inside a folder, paginated
- Retrieve file content, plus detailed file metadata, permissions and version details
What the naked read gives you
Point Box through Unl at a client's 'Delivery' folder and it lists every file, opens the ones that matter, and reports who last touched each version. That's a complete inventory. It doesn't know that a hand-off needs four specific files with an 'Approved' metadata field set - Box will happily hand over three files and stay silent about the missing fourth.
The frame judges the data it is given; it does not verify the source’s accuracy.
What changes when Box is read measured
Tomas, the delivery lead on client engagements, ratified in Unl that a folder counts as hand-off ready only when it holds a signed statement of work, a final deck, a data file and a sign-off note, each carrying the metadata field 'status: Approved' - because a client once received a deck still marked 'Draft'.
'Is the client's delivery folder ready?' returns, measured: unmet - three of the four required files carry 'status: Approved', but the data file is still tagged 'status: Review', so the set isn't complete against the rule. Box supplied the folder contents and metadata; the ratified checklist supplied the four-file condition that turns an inventory into a verdict.
And back again
When the data file's status flips to 'Approved' in Box, Tomas confirms the change in Unl, and the next 'is this delivery ready' question for that client returns a met verdict instead of re-counting the same four files.
The answer comes back measured against what you already decided, and why.
The lane is live and open to this tool today: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Questions people ask
What decides whether a Box folder is 'ready' rather than just full?
The hand-off checklist your team ratified, not the file count. In this case, four named files each need an 'Approved' metadata field before the folder counts as ready - Box shows what's in the folder, the ratified rule decides whether it's the right four.
How do I connect Box to Claude?
Box hosts a remote MCP endpoint at mcp.box.com. An admin enables MCP in the Box Admin Console, you authorise access via OAuth from your MCP-compatible client, and then link that connection into Unl so folder and file reads run against your ratified checklist.
Does Unl send messages or change files in Box?
Unl reads through Box, and can write back on your explicit gesture — it never acts as a side effect of a read.
What this is
Think inside your AI world — you stay in command
Save the thoughts, decisions and targets worth keeping, each with its reasoning, carried into every AI session the moment they matter. A new unit of exchange between you and your AI: the Settled Why with standing that travels. Unprompted.
Your whole AI world. What you decided at the epicentre. It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector — quick to connect, in a couple of steps.
MCP native·Human settled·Model agnostic·Your data
Measured Context
Connect Unl to bring the right information into the moment.
Your sources, read against the criteria you set.
The full product, open. Free at launch.