Skip to content

Add createdBy to the changes profile. #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dmitrizagidulin merged 1 commit into from
Jul 10, 2026
Merged

Add createdBy to the changes profile. #57

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3135,6 +3135,7 @@ Response body:
"updatedAt": "2026-01-15T12:00:00.000Z",
"version": 1,
"metaVersion": 3,
"createdBy": "did:key:z6MkpBMbMaRSv5nsgifRAwEKvHHoiKDMhiAHShTFNmkJNdVW",
"data": { "message": "hi" },
"custom": { "tags": ["greeting"] }
}
Expand All @@ -3156,6 +3157,12 @@ Each entry in `documents` describes one changed Resource:
it.
* `metaVersion` - a monotonic metadata version, present only once metadata has
been written for the Resource, and bumped by a metadata-only edit.
* `createdBy` - the [=did=] of the Resource's creator, as defined in
[[[#resource-metadata-data-model]]]. A server that records `createdBy` SHOULD
surface it here, so that a replica learns each Resource's creator from the feed
rather than dereferencing the `meta` sub-resource of every Resource it pulls.
Present only when recorded; a client MUST treat an absent `createdBy` as "not
recorded". It is server-managed and read-only, as it is everywhere else.
* `data` - the stored JSON body verbatim. The body is nested under `data` (rather
than spread onto the entry) so that a non-object JSON body round-trips
faithfully. Omitted on a tombstone.
Expand All @@ -3166,7 +3173,9 @@ Each entry in `documents` describes one changed Resource:

**Tombstones.** A soft-deleted Resource surfaces as
`{ "id", "_deleted": true, "updatedAt", "version" }` with no `data` member;
the deletion bumps `version`.
the deletion bumps `version`. A tombstone retains its `createdBy`, where one was
recorded, so that a deletion replicates together with the attribution of the
Resource it removes.

**Ordering and resumption.** Entries are ordered by an ascending `(updatedAt, id)`
keyset. The top-level `checkpoint` echoes the position of the last entry in
Expand Down Expand Up @@ -3202,6 +3211,7 @@ Content-type: application/json
"_deleted": false,
"updatedAt": "2026-01-15T12:00:00.000Z",
"version": 1,
"createdBy": "did:key:z6MkpBMbMaRSv5nsgifRAwEKvHHoiKDMhiAHShTFNmkJNdVW",
"data": { "message": "hi" }
}
],
Expand Down