plresearch-org · edit-ai-opportunity-spaces-r3 · round 3

Round 3: generalize to all 4 areas + array-field editing

@daviddao

Follow-up to r2's remaining work items. All 15 opportunity-space records across all four focus areas (AI & Robotics, Digital Human Rights, Neurotech, Economies & Governance) now have working admin editors that cover both prose and array fields, backed by a single shared <OpportunitySpaceEditor> component.

Date: 2026-04-20 · Target: neural-augmentation (Neurotech) · Previous: r2 (pass) · pass

---

Headline result

What changed (the fix)

Two commits: the main generalisation, plus a one-line fix for the opacity bug discovered during testing.

File	Change
src/components/OpportunitySpaceEditor.tsx	New. Client component that accepts areaSlug + areaLabel + slug. Fetches the record via the API route, renders an inline editor covering all 13 fields, and PUTs on save. Replaces 200+ lines of duplicated editor code.
src/app/areas/{ai-robotics,digital-human-rights,neurotech,economies-governance}/opportunity-spaces/[slug]/edit/page.tsx	All four are now thin 10-line wrappers that forward params.slug and their areaSlug/areaLabel to the shared editor.
src/app/areas/{dhr,neuro,eg}/opportunity-spaces/page.tsx	List pages for the three remaining areas switched to fetchOpportunitySpaces(areaSlug) with the static JSON as a build-time fallback (mirrors r2's AI change).
src/app/areas/{dhr,neuro,eg}/opportunity-spaces/[slug]/page.tsx	Detail pages for the three remaining areas switched to fetchOpportunitySpace(rkey) + static fallback, and render <EditPageButton/> pointing at the per-area edit route.
src/components/OpportunitySpaceEditor.tsx (commit 2)	Remove buttons for string-array items and field-signal cards no longer rely on opacity-0 group-hover:opacity-100; they are now always visible in a faint gray that darkens on hover.

Walkthrough

Captured on production, signed in as satyam2.climateai.org. To exercise a different area than r2, the primary test target is Neurotech / Neural Augmentation (BCI) rather than AI & Robotics. Full flow: list page → detail page → edit button → editor → save → PDS → indexer → public page.

PDS verification (xrpc)

After the add-signal save, the record on plresearch.org’s PDS shows the new 6th entry:

$ curl -sG "https://leccinum.us-west.host.bsky.network/xrpc/com.atproto.repo.getRecord" \
    --data-urlencode "repo=did:plc:pgwr6hkosgznfl5nz7egajei" \
    --data-urlencode "collection=org.plresearch.opportunitySpace" \
    --data-urlencode "rkey=neuro--neural-augmentation" | jq '.value | {tagline, tippingSignals, updatedAt}'
{
  "tagline": "… [edited via pi-eval r3]",
  "tippingSignals": [
    "FDA clearance of a standardized API/software layer for a commercial BCI device",
    "Successful launch and adoption of the first third-party app for a BCI device",
    "Off-label BCI implants commencing for non-medical consumer use",
    "Non-invasive or minimally invasive devices proven safe, effective, and scalable",
    "Robotic surgery enabling 20-minute outpatient BCI implantation procedures",
    "Added via pi-eval r3 test — verifying array-field editing works"
  ],
  "updatedAt": "2026-04-20T20:07:25.824Z"
}

After the revert (remove 6th signal & restore tagline):

{
  "tagline": "Low-cost, scalable, high-bandwidth bidirectional interfaces …",
  "tippingSignals": [… 5 items, original content …],
  "updatedAt": "2026-04-20T20:14:09.603Z"
}

Findings

Reproducing