Skip to main content
Shared memory is what makes a Project’s work products connect. As you upload evidence and generate drafts, Parley logs the case’s key details from your version history — the working index, the exhibit list, the names and dates that recur across filings. The result: create a draft one week and an exhibit packet the next, and the index, the petition, and the packet all match one to one. You don’t re-establish the case every time you start something new.

​
Why this matters

Without shared memory, every work product starts from zero. You re-upload the same evidence, re-explain the same facts, and reconcile the inconsistencies afterward — which is where filing errors come from. With it, the second work product inherits the decisions made in the first. Exhibit 7 is Exhibit 7 in both documents.

​
How to use it

The main thing is to work inside a Project rather than a general chat.
1

Create a Project and upload the evidence

Everything you add becomes part of what the Agent can draw on.
2

Produce a work product

Draft the petition, complete a form, or build an index. Parley logs the key details as it works.
3

Build the next one on top

Ask for the exhibit packet. It comes back matching the draft you already have.

​
Notes as deliberate memory

Shared memory captures what Parley observes. Project Notes capture what you want it to know. Use a Note for context that isn’t in an evidence document: what the client said on the call, which argument you’ve decided to lead with, what evidence is still outstanding. The Agent reads Notes when it works and can write back to them. A case strategy note written early — outlining the petition and citing the key evidence — pays for itself across every draft that follows.

​
Keeping threads fast

When you reopen a long idle thread, Parley offers to continue in a fresh thread from a summary, carrying your files and work products across. The Project’s memory persists either way, so nothing is lost and the Agent stays quick.