A process's history
const url = 'https://api.asklucy.eu/v1/memory/processes/example/versions';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.asklucy.eu/v1/memory/processes/example/versions \ --header 'Authorization: Bearer <token>'Newest first. Members see the accepted and superseded versions of shared processes and their own proposals; admins and the owner of a process in their own scope see every version.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”OK
object
object
1, 2, … in order of creation, proposals included.
proposed: waiting for an admin.accepted: the current version.superseded: was current, replaced by a later version.rejected: an admin turned the proposal down.withdrawn: its author took it back or undid it.
When to use it (the requests or situations it is for).
The steps, in Markdown.
Types of entities and relations it reads.
Types of entities and relations it writes.
The entities it is about (IDs).
Why it was written or changed; empty when not given.
The version it was written from; null for a first version.
A person, or Lucy working for that person. The person is null once their memory was erased.
object
The person’s name.
The conversation Lucy wrote it in; given only to its author.
untrusted_input: Lucy wrote it after reading a file or a tool’s output, which may have steered her. Review it with care.
Example
{ "data": [ { "id": "prv_7Hc2Lw", "state": "proposed", "title": "Answer a custody-fee question", "when": "Someone asks why custody fees changed, or to check a custody invoice.", "reads": [ "company" ], "writes": [ "invoice" ], "applies_to": [ "ent_5Tq9Bm" ], "author": { "kind": "person" }, "flags": [ "untrusted_input" ], "decided_by": { "kind": "person" } } ]}Missing, expired or invalid token.
RFC 9457 problem details.
object
For quota-exceeded, the window that is used up.
object
Null for a rolling window that hasn’t started.
organization when the organization’s budget is closer to running out than the member’s own limit.
Field-level problems (400 only).
object
JSON pointer into the request body.
Example
{ "type": "https://docs.asklucy.eu/errors/answer-in-progress", "quota": { "window": "five_hours", "limited_by": "personal", "request": { "status": "pending" } }}Headers
Section titled “Headers”Unique per request; quote it to support.
The token is valid but lacks the role this needs.
RFC 9457 problem details.
object
For quota-exceeded, the window that is used up.
object
Null for a rolling window that hasn’t started.
organization when the organization’s budget is closer to running out than the member’s own limit.
Field-level problems (400 only).
object
JSON pointer into the request body.
Example
{ "type": "https://docs.asklucy.eu/errors/answer-in-progress", "quota": { "window": "five_hours", "limited_by": "personal", "request": { "status": "pending" } }}Headers
Section titled “Headers”Unique per request; quote it to support.
No such object in your organization.
RFC 9457 problem details.
object
For quota-exceeded, the window that is used up.
object
Null for a rolling window that hasn’t started.
organization when the organization’s budget is closer to running out than the member’s own limit.
Field-level problems (400 only).
object
JSON pointer into the request body.
Example
{ "type": "https://docs.asklucy.eu/errors/answer-in-progress", "quota": { "window": "five_hours", "limited_by": "personal", "request": { "status": "pending" } }}Headers
Section titled “Headers”Unique per request; quote it to support.