plresearch-org · edit-ai-opportunity-spaces-r5 · round 5

Round 5: per-page edit history via editEvent + drawer UX

@daviddao

Answers the question “who edited what on this page?” Each admin edit now writes an org.plresearch.editEvent record to the editor’s own PDS (not plresearch.org’s), cryptographically binding authorship to the DID that performed the edit. Detail pages surface this as a byline under the breadcrumb; clicking it opens a right-side drawer with the full timeline.

Date: 2026-04-20 · Target: open-compute-networks · Previous: r4 (pass) · pass

---

Headline result

UX design

Three surfaces, progressive disclosure. None of them change how the page reads; history is peripheral by default.

Surface	Where	What it answers
Byline	One line under the breadcrumb on every detail page	“Who last touched this, and when?”
Drawer	Right-side slide-in, opens from the byline’s “View history (N)” button	“Show me the full timeline — editors, times, what fields changed.”
Editor context	Same byline is rendered inside the inline editor	“Before I start editing, am I stepping on someone’s work?”

Editor handles in both surfaces link to their bsky.app/profile/<handle> for community identity; timestamps are relative with absolute on hover.

Architecture

[Editor browser]  ---PUT /api/opportunity-spaces/[rkey]-->  [Next.js route]
                                                               |
                                                 putRecord as plresearch.org
                                                 (app password) → content updated
                                                               |
                                                 createRecord as editor
                                                 (OAuth agent) → editEvent on editor's PDS
                                                               |
                                       (indexer firehose sees both records)
                                                               |
                       [Indexer (Railway)] — lex-gql → GraphQL (orgPlresearchEditEvent)
                                                               |
         [Browser] --GET /api/edit-history?target=at://…--> [Indexer GraphQL] → byline + drawer

Writing to the editor’s own repo means plresearch.org can’t forge an attribution — app-password access only controls plresearch.org’s own data.

Walkthrough

Verification (xrpc)

Each edit lands on the editor’s PDS, not plresearch.org’s:

$ curl -sG "https://climateai.org/xrpc/com.atproto.repo.listRecords" \
    --data-urlencode "repo=did:plc:cpoagodpqrgs4t7thi5z37uf" \
    --data-urlencode "collection=org.plresearch.editEvent" | jq '.records[].value | {editedAt, changedFields}'
{ "editedAt": "2026-04-20T21:25:38.359Z", "changedFields": ["tagline"] }
{ "editedAt": "2026-04-20T21:05:16.820Z", "changedFields": ["uri", "tagline", "rkey"] }

Indexer query via our API:

$ curl -s "https://www.plresearch.org/api/edit-history?target=at://did:plc:pgwr6hkosgznfl5nz7egajei/org.plresearch.opportunitySpace/ai--open-compute-networks" | jq '.count, .events[0]'
2
{
  "uri": "at://did:plc:cpoagodpqrgs4t7thi5z37uf/org.plresearch.editEvent/3mjxenxasrk2e",
  "did": "did:plc:cpoagodpqrgs4t7thi5z37uf",
  "target": "at://did:plc:pgwr6hkosgznfl5nz7egajei/org.plresearch.opportunitySpace/ai--open-compute-networks",
  "editor": "did:plc:cpoagodpqrgs4t7thi5z37uf",
  "editorHandle": "satyam2.climateai.org",
  "changedFields": ["tagline"],
  "editedAt": "2026-04-20T21:25:38.359Z"
}

Findings

Reproducing