Internal · not indexed

RSP spec checklist

Verifies each of the 9 canonical routes against the RSP site spec and flags remaining gaps. Update as pages change — this view is not linked from public navigation.

24
Met
4
Partial
5
Gaps
9
Routes audited
Landing /rsp
Partial

What RSP is, why it exists — a trust document as much as a spec.

  • ✓Plain-language lead (consent + coordination layer, not jargon)
  • ✓Explicit "what RSP is not" trust section#what-rsp-is — not surveillance / not data-selling / not silent.
  • ✓Links out to all sub-sectionsArea menus + in-page links.
  • ◑Established RSP brand (metallic red ring, Orbitron/IBM Plex, circuit aesthetic)Uses DM Serif / DM Sans + red ring mark. Orbitron/IBM Plex + circuit motif from the brand kit not applied.
Core principles /rsp/principles
Met

Each principle stated plainly, one paragraph each.

  • ✓Synchronisation without coercion
  • ✓Presence without surveillance
  • ✓Consent as living/revocable state
  • ✓Minimisation by default
  • ✓Law of Vibration Who/What/Where frameworkSpec says default to keeping this internal unless directed — intentionally omitted (by design).
How it works /rsp/how-it-works
Met

Plain-language mechanics with a concrete worked example.

  • ✓Walkthrough of grants, identity context, revocation, presence
  • ✓At least one concrete worked example"Worked example" block present.
  • ✓Technical deep-dive link to /rsp/for-developers
Dimensions /rsp/dimensions
Gap

Structured reference table: dimension · governs · example · revocability.

  • ✓Structured reference table (not just prose)#reference table with revocability column.
  • ✕Grant schema pulled from actual @rsp/core source@rsp/core is not vendored in this repo; dimensions are described from the spec, not verified against the live grant schema.
Implementations /rsp/implementations
Partial

Where RSP is deployed and what it governs in each case.

  • ✓Lists Twinly + HELP Network deployments
  • ✓Structured so new entries are easy to add
  • ◑Explicit "keep current / may go stale" flagNo visible freshness/last-reviewed note prompting updates when a new product integrates RSP.
Event Token /rsp/event-token
Met

Plain-language subsystem summary + link to existing whitepaper.

  • ✓ERC-721 on Base summary
  • ✓Links to existing whitepaper (not re-written)
  • ✓Plain-language explanation for non-technical visitor
For developers /rsp/for-developers
Gap

Real @rsp/core + @rsp/react API docs, install, integration quickstart.

  • ✕API reference reflects actual package APIs (verified vs source)Non-negotiable. @rsp/core (8 modules) and @rsp/react (3 hooks / 4 components) are not present in this repo, so documented signatures are not verified against source.
  • ◑Install uses file: dependency conventionShows npm install; spec calls for the file: monorepo convention.
  • ✕Integration quickstart (add grant · check permission · handle revocation)No end-to-end quickstart using real package APIs found.
Governance /rsp/governance
Met

Who maintains RSP, how it changes, versioning approach.

  • ✓Maintainer + change process documented#versioning section.
  • ✓Explicit version numberRSP v1.6.
  • ✓Written with external-adopter possibility in mind
FAQ /rsp/faq
Gap

Plain-language Q&A, cross-linked to the actual privacy policy.

  • ✓Covers cross-site data, revocation, leaving a product
  • ✓Clarifies RSP-vs-privacy-policy distinction
  • ✕Cross-linked to the site's actual privacy policyExplains the relationship in prose but does not link to a real privacy-policy URL (awaiting the canonical /privacy link).
Non-negotiables (sitewide)
  • ✓No content overstates what RSP guaranteesManual review — honesty standard held across pages.
  • ✓Written for a general audience first
  • ✕Developer docs reflect actual package APIs (not invented)See /rsp/for-developers — packages not vendored, so APIs are unverified.
  • ◑Cross-reference rather than duplicateWhitepaper is linked ✓; privacy policy is not yet linked ✗.