# Records, links and values

Everything in Remiq is one of a few kinds of thing. Knowing them tells you what to save and which read to call.

## Records

A record is one saved message, note, document or web clip, kept as written. It has an id (`M41`), its memory space (`user`) and, when you send them, its readers (`acl`), when it was said (`at`), where it came from (`source`, `thread`, or `url` + `title` + `anchor` for a web clip) and when it ends (`expires_at`).

Save records with `POST /v1/memories`, or many at once as a job with `POST /v1/imports`. Browse them with `POST /v1/memories/list`.

## Events

An event is a typed change, saved exactly: a ticket moved to done, an approval, an assignment. Each has a `type`, an `object`, the value it changed `to`, an `actor` and a `time`. Save them with `POST /v1/events`. Events make the current state and the timeline exact.

## Values that change

Where someone works, a launch date, a ticket's status: `POST /v1/state` returns the current value with its history, so your model never mixes up an old value and a new one. `POST /v1/timeline` gives a subject's events over time, oldest first.

## Links

Prism links the names in your records:

- **people:** who owns or knows about something, with the records that show it (`POST /v1/people`);
- **decisions:** what was decided, by whom, when and why (`POST /v1/decisions`);
- **terms:** your team's words and what they mean (`POST /v1/glossary`);
- **structure:** the organisation tree (`POST /v1/hierarchy`) and, for a code base, the code map (`POST /v1/map`).

## Notes and feedback

- **Notes** are what your model wrote (`POST /v1/notes`). They are kept, but never used as evidence.
- **Feedback** corrects the memory (`POST /v1/feedback`): mark a record `wrong` or `outdated`, `pin` it, `verify` it, or say two names are the `same_person` or `different_people`.