Contract and policy memory

​

The scenario

​

Step 1 — Upload the agreements, tagged by counterparty

client.upload_file(
    space_id="contracts",
    file="acme-msa-2026.pdf",
    tags=["counterparty:acme", "type:msa"],
)

​

Step 2 — Ask with the scope pinned

res = client.retrieve_receipt(
    space_id="contracts",
    query="sublicensing rights",
    tags=["counterparty:acme"],
    receipt_detail="full",
    prefer_observations=False,
)
for row in res.memories:
    if row.get("document_id"):
        print(row["content"], "\n  from document", row["document_id"])

​

Step 3 — Keep the proof

receipt = client.get_receipt(res.receipt_id)
for cut in receipt["excluded"]:
    print("not shown:", cut["reason"], cut["detail"])

​

Evals

1. Load two versions of the same agreement, one superseding the other.
2. Ask a question the two answer differently. Check which one comes back, and whether the other appears in the receipt’s excluded list.
3. Ask about a counterparty you have no contract for. It must return nothing rather than the nearest other agreement.
4. Pick three answers and trace each to its document_id by hand. If any cannot be traced, stop using it for anything that matters.

​

Guardrails

• Superseded versions stay retrievable unless you say otherwise. That is usually right for contracts — but mark the old one explicitly with a correction and a reason so the status is recorded rather than inferred.
• Never paste a clause into a prompt from memory alone when the exact wording is operative. Use the result to find the document, then read it.
• A receipt carries ids and reasons, never content, which is what makes a receipt id safe to put in a ticket even when the underlying agreement is confidential.

​

Built from