Bundles

What a bundle is

A bundle is a group of documents inside a workspace that a row can point at instead of a single document. The row answers as the group. Everything else about the table is unchanged — same columns, same output types, same citations.

The citation is the reason this matters more than tidiness. “90 days, per Amendment 2” is a different claim from “90 days”, and only one of them can be checked.

Named and unnamed

Whether it has a name is the whole difference between the two kinds. Drop files straight onto a row and you get an unnamed bundle: private to that row, invisible as a concept, and it simply looks like a row with several documents in it.

Give one a name and it appears in the bundles column beside the files list, where it can back rows in any number of tables and outlives every one of them. Name a bundle when the same group is worth reaching for again — the same set of policy documents feeding a compliance table and a renewals table. A group that only ever backs one row does not need a name.

Making one

Select files in the panel and press Make Bundle, or drop a set of files onto the bundles column. Either way it is created immediately as “Untitled bundle” with the rename box already open — the selection has said everything the bundle needs to exist.

After that it is all dragging:

• A bundle dragged onto a row’s Documents cell makes that row adopt it.
• Dragged onto the add-row bar, or onto an empty table, it creates a row backed by it.
• Files dragged into a bundle join it; members dragged back out to the files list leave it.
• The × on a bundle in a Documents cell detaches just that row — it keeps the same documents as its own private copy, answers intact, and the shared bundle is untouched.

A bundle’s colour is stored with the bundle, so everyone in the workspace sees the same one.

How a bundled answer is produced

Each member document is read on its own first, producing one fact per document. A second pass resolves those facts against each other into the single answer the cell shows — which is where precedence gets applied, so a later amendment can override the master.

Order is part of that, and it is why members can be dragged up and down: the document in first position is the bundle’s primary one, so promoting a file means dragging it to the top. There is no separate “make primary” control, because a bundle that named one document as primary while listing it third would be answering the same question twice.

Editing one reaches every table using it

Adding a document to a shared bundle, removing one, or reordering it changes what every row backed by that bundle is about. Those rows do not silently rewrite themselves — their answers are marked stale instead, in every table at once, and rerunning stays your call. See running and reruns.

• The bundle’s own Run all re-extracts every row backed by it, wherever those rows live. It asks first, listing the tables and totalling the cells, because from the files panel that cost is otherwise invisible.
• Moving a row to a different bundle marks that row stale outright — its old answers describe a different set of documents entirely.
• Deleting a named bundle asks what to do with the rows using it: let each keep the documents privately, or delete those rows too.

What a bundle costs

Every member is read on its own, so a bundled cell costs more than a single-document one. The first three documents come with the column’s rate; each one after that adds to the cost of that cell. The cost preview totals it before you run.

A bundle holds up to 15 documents. That limit is about the answer as much as the cost: the second pass keeps one document’s fact, so past a point extra members add noise to reconcile rather than evidence to reconcile it with.

One exception worth knowing: on a row backed by a large bundle, a compositional column is the cheaper of the two options, and by some distance — gathering across the documents once costs less than reading each of them separately.

When not to use one

Do not bundle documents just because they are similar. Ten unrelated leases are ten rows; bundling them asks the model to reconcile ten documents that were never in conversation with each other, and you lose the per-document answer that made the table useful.

Bundle when later documents modify earlier ones: master agreements and amendments, a policy and its endorsements, a lease and its side letters.