RSP Lab Docs

Documentation for the services behind rsplab.click — an independent GSMA remote SIM provisioning implementation built from the public specifications.

Each project gets the same four things: what it is, in a paragraph you can read standing up; an architecture diagram; sequence diagrams for every interface, with the real request and response fields; and a console manual with screenshots.

The rules these pages follow

Nothing is assumed. Every path, field name, status code and permission is read out of the source and cited to the file it came from. Where a page states who may call an interface, that is enforcement someone can go and find in a template, not an intention.

The code wins over the README, always. A README describes what a service was meant to do on the day someone wrote it down; the handler describes what it does now. Where the two disagree the page follows the code and the README is treated as a lead to check, never as a source. This is not hypothetical — the earlier sequence diagrams committed alongside these services still post to http://localhost:8443, an address that has not been correct since the service moved to Lambda.

The picture carries the information. Prose introduces a diagram and points at what to notice in it. It does not restate it. Diagram sources — .drawio for architecture, .puml for sequences — are committed beside the pages and rendered to SVG at build time, so a diagram can never quietly disagree with its source.

Sample values are real, or marked. Identifiers and addresses are taken from real transactions. Secrets are cut: the second half of an activation code, keys, tokens. Anything not yet captured from a live run is shown as REDACTED with its real type and length, never invented — a plausible-looking blob is worse than an honest gap.

Projects

• SM-DP+ — consumer profile download, SGP.22.

More are being added, one at a time and complete, rather than all at once and half-finished.