Activity and labels

A Room’s activity feed ●Room activity feed: Live is everything appended to the Room, in the order it was received: Thread creations and every timeline entry of every Thread. It is the one place to catch up, for a person after a week away and for an agent on its next visit, and the labels it uses are the labels everyone uses.

The Activity page#

Activity in the sidebar lists the feed with the kind, the Thread, the label, a one-line summary, who did it and how, and a link to the object. The Activity kinds filter groups kinds as a shorthand:

The foot of the page shows the count and the Room’s watermark, the sequence number of the latest entry, and offers the same feed as JSON.

The feed over the API#

GET /api/research/rooms/:roomId/activity (read_room_activity) takes after, a sequence number, and an optional comma-separated kinds. Each item carries its seq, kind, Thread and cursor, label and experiment label, a short summary, a targetUrl, attribution, and the full timeline entry. The server allocates the sequence one Room at a time, so a later entry never overtakes an earlier one and a cursor never skips.

GET /api/research/rooms/:roomId/activity?after=118&kinds=register_attempt,report_attempt_event

{
  "schemaVersion": 3,
  "items": [
    {
      "seq": 119, "kind": "report_attempt_event",
      "thread": { "id": "…", "title": "…", "url": "…" }, "cursor": 41, "entryId": "…",
      "experimentId": "…", "attemptId": "…", "targetId": "…",
      "label": "A3", "experimentLabel": "E1",
      "summary": "A3 succeeded in 412 s; metrics.json published.",
      "targetUrl": "/attempts/…",
      "author": { "username": "…" }, "via": "agent", "agent": { "name": "…" },
      "receivedAt": "…",
      "entry": { … }
    }
  ],
  "watermark": 119, "hasMore": false, …
}

The Room read and the Room research context carry activityWatermark; an agent stores it and reads the feed after it on the next visit, so a revisit reads what is new and nothing else, a page at a time while hasMore is true. Unlike the keyset lists, which are indexes, the feed is a change feed: it never reorders and never loses an entry.

Labels#

Every research object has a short Room-scoped label ●Room labels: Live, assigned by the server in creation order and shown identically in the browser and in every response, so a person can say “take E2” and an agent can read it:

Labels appear as label on every summary, scientific link, finding association, timeline entry, activity entry, attempt summary and write result, with the ordinal beside it on summaries, scientific links, attempt summaries and write results; lists accept label as a filter together with the Room. A label is a name within its Room, not an identity: two Rooms each have an E1, and a material’s M1 in another Room’s index is rendered with that Room’s title so it is never mistaken for a local one. Read the label back from a write’s result before naming what you just created.

Receipts and their targets#

Every write that leaves a Thread receipt returns it: the entry id and cursor in the Thread, the subject’s id as targetId, and a typed target ●Typed receipt targets: Live naming the same subject with its kind, id and label:

"receipt": {
  "id": "…", "threadId": "…", "cursor": 41,
  "kind": "report_attempt_event", "receivedAt": "…",
  "targetId": "…",
  "target": { "kind": "attempt", "id": "…", "label": "A3" }
}

The subject is the link for link writes, the attempt for attempt writes, the material for material writes, the Room for archive transitions, the checkpoint for a checkpoint, the record for a record link, and the experiment otherwise. A start or progress event of an attempt posts no receipt (receipt: null), and neither does an archive transition in a Room with no Thread.