Skip to content

README: document the live and sandbox deployment model - #6

Open
samlown wants to merge 4 commits into
mainfrom
sandbox-deployment
Open

README: document the live and sandbox deployment model#6
samlown wants to merge 4 commits into
mainfrom
sandbox-deployment

Conversation

@samlown

@samlown samlown commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Documents the two-instance model agreed for sandbox usage: lookup.gobl.org (live) and lookup.sandbox.gobl.org (sandbox) run the same service with independent identities, CouchDB databases, and VERIFIERS lists — sandbox strictness is purely which providers are accepted (e.g. a dummy KYB service), not a code path.

Also rewrites How verification works to the confirmed supplier-initiated flow: register → registry countersigns (no verifier) → supplier delivers the registered envelope to the provider's inbox → provider initiates by email against the party's published address → KYB → provider returns the countersigned envelope to the registry as an ordinary renewal → auto-verify names the provider → delivery → supplier publishes two operative countersignatures with independent lifetimes. The registry-run web flow (OTP, picker, session hand-off) is dropped; the open pieces are the provider service itself (first target: a sandbox dummy-KYB provider) and publishing the accepted-provider list.

No code changes needed here: the service was already fully configuration-driven, and the registry side of the flow (accepted list + auto-verify) is implemented. Includes the commits from #5 (README tidy) since both touch the same section — merging #5 first leaves this PR clean.

Companion PRs: invopop/gobl#924 (sandbox trust list + WithSandbox, plus the §5.3 delivery choreography) and invopop/deploy-production-apps#27 (sandbox deployment).

🤖 Generated with Claude Code

samlown and others added 4 commits August 7, 2026 22:59
Verifier examples use the neutral verify.example.com placeholder
instead of naming a specific provider bridge, the architecture
section no longer points at internal Invopop services, and the
configuration/operations sections describe container platforms
generically rather than "the cluster".

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two independent instances of the same service — lookup.gobl.org and
lookup.sandbox.gobl.org — each with its own identity, CouchDB
database, and accepted verification providers. Sandbox strictness
is purely a configuration difference (relaxed providers in
VERIFIERS); the code path is identical, and the gobl/net trust
lists keep the environments disjoint.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Rewrites the verification flow to the confirmed design: after
registration the supplier delivers its registered envelope directly
to the chosen provider's inbox, the provider initiates by email to
the party's published address, runs KYB, and returns the
countersigned envelope to the registry as an ordinary renewal —
auto-verify names the provider and the supplier publishes an
envelope carrying two operative countersignatures with independent
lifetimes. The registry-run web flow (OTP, provider picker, session
hand-off) is dropped; the open pieces are the provider side itself
and publishing the accepted-provider list.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant