Synthetic Solmara data. No real residents, addresses, or government records.

Solmara Lab Registry Stack demo

Developer workspace

Run the country, inspect every boundary

This is the complete technical surface behind the guided homepage: a clean-checkout journey, published metadata, source configuration, credential boundaries, and runnable requests.

Engineer door

Clone to green smoke, then go off script

Five commands to a running country

just setup
just up-generated
just smoke
just portal-live-e2e
just down

Reference and tooling

Pinned release artifacts

Registry Stack v0.22.0 d9a278a55fa3cd275e391cdf2d94dae342c65edc

Evidence ghcr.io/registrystack/evidence@sha256:175cb81e12125bbb17425bdc2df34b109b0da95b3b1df2d6cb2bfa3223f2c577

Mint ghcr.io/registrystack/mint@sha256:a4aaf418493ce2d14994082b93fb1ccb32b1351d71b3850a694045ad00174e54

Credentials stay server-side

Mint issues short-lived credentials to the programme and each authority service. The visitor center never publishes them. Curl examples use shell placeholders for your local credentials, nonce, and synthetic subject identifier.

Copy-as-curl

Read the deterministic publication

Published metadata is public. The deterministic publisher is not an Evidence authority.

curl -sS 'https://metadata.solmara.registrystack.org/metadata/catalog.json'
Ask CRA Evidence for one minimized value

Purpose is a JSON member. Supply the scoped token, nonce, and UIN from your local shell.

curl -sS -X POST 'https://cra-evidence.solmara.registrystack.org/v1/evidence' \
  -H 'Authorization: Bearer $CRA_EVIDENCE_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"requestNonce":"$REQUEST_NONCE","requirement":"https://id.registrystack.org/solmara/requirement/cra-child-benefit/v1","purpose":"https://id.registrystack.org/solmara/purpose/child-benefit-review","subjects":[{"role":"subject","selector":{"profile":"solmara-uin-v1","values":{"uin":"$SOLMARA_UIN"}}}]}'
Ask NIA Evidence independently

CRA and NIA are distinct Evidence services with distinct issuers and audiences.

curl -sS -X POST 'https://nia-evidence.solmara.registrystack.org/v1/evidence' \
  -H 'Authorization: Bearer $NIA_EVIDENCE_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"requestNonce":"$REQUEST_NONCE","requirement":"https://id.registrystack.org/solmara/requirement/nia-child-benefit/v1","purpose":"https://id.registrystack.org/solmara/purpose/child-benefit-review","subjects":[{"role":"subject","selector":{"profile":"solmara-uin-v1","values":{"uin":"$SOLMARA_UIN"}}}]}'
Run the child-benefit programme collection

The programme sends its governed purpose in the JSON body and collects separately signed authority results.

curl -sS -X POST 'https://child-benefit.solmara.registrystack.org/v1/evaluations' \
  -H 'x-api-key: $CHILD_BENEFIT_PROGRAMME_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"purpose":"https://id.registrystack.org/solmara/purpose/child-benefit-review","target":{"type":"Person","identifiers":[{"scheme":"solmara_uin","value":"$SOLMARA_UIN"}]},"claims":["birth-is-registered","population-record-active","child-age-under-5","household-below-poverty-threshold","not-already-enrolled"],"disclosure":"predicate","format":"application/json"}'
Skeptic path: an unapproved JSON purpose

The same requirement under a pension purpose is refused with the current not_authorized problem code.

curl -sS -X POST 'https://cra-evidence.solmara.registrystack.org/v1/evidence' \
  -H 'Authorization: Bearer $CRA_EVIDENCE_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"requestNonce":"$REQUEST_NONCE","requirement":"https://id.registrystack.org/solmara/requirement/cra-child-benefit/v1","purpose":"https://id.registrystack.org/solmara/purpose/pension-payment-review","subjects":[{"role":"subject","selector":{"profile":"solmara-uin-v1","values":{"uin":"$SOLMARA_UIN"}}}]}'