Memory for legal teams

You are building an assistant for legal teams that tracks matters, clients, deadlines, instructions and call notes. You choose how to map people to users, for example one id per client. Each person's memory is separate. Your server sends notes and documents to the Memory API. The assistant recalls what it needs before it answers.

• People stay apart. Each person's memory is separate, and each app's data is separate. Every request is checked against the key.
• Facts change. Instructions, deadlines and counterparties move. A changed value with a newer timestamp becomes the current value, and the earlier value stays answerable by date.
• Results can name sources. Recall results include sources, with a source id, a date and a label. Your team can check where a statement came from.

• Private memory per person. Send with X-Harny-User set to your id for the person, or use a user key (fsk_) that names its own user.
• Audiences. A named group of users: a fixed list, or a rule over user traits.
• Dated recall. Use queryTimestamp to ask what was true as of a date, and occurredFrom and occurredTo to bound a period.
• Deletes on request. DELETE /v1/memory/data-points/{sourceId} removes a data point and the memories built on it. DELETE /v1/users/{user_id}/data erases a person. Deletes are free.

• Recall what a person said most recently, with its sources.
• Recall what a value was at an earlier date, using an as-of recall with queryTimestamp.
• When a person has said two things that cannot both be true, Harny keeps both and picks no winner. The API returns the conflict as data, and your app may ask the person at most once.
• Hand off a step a person must do outside Harny, such as a call, a signature or a judgment, as a manual action.

1. Create the app and keep its key (starts fsa_) on your server, for example in .env. Call from a server, never a browser.
2. Send matter notes with POST /v1/memory/ingest, with content, id, label and a timestamp in ISO 8601 with zone. Poll GET /v1/memory/ingest/{ingestionId} until status is completed.
3. Recall with POST /v1/memory/recall, passing query and identity. Show the sources with each answer where results carry them.
4. Group your app's users into audiences if you need groups. Erase a person with DELETE /v1/users/{user_id}/data when asked.