ADR-0027: Bronhouder onboarding toolkit¶
- Status: proposed
- Date: 2026-08-24, updated on 2026-11-02
- Satisfies: D-06, GO ยง6: impact on bronhouders
- Deliberation: reference architecture v0.6.2, gap 6 "bronhouder onboarding toolkit" (archived and unpublished)
- Implemented in: partially. These parts of the demo are reusable starting points: the Helm chart, the source metadata contract (ADR-0016), the source gateway (ADR-0033), and the contract seed scripts.
Context and problem statement¶
GBO has one API and one connectivity stack. Even so, the connection of a bronhouder involves PKI, FSC components, a source gateway, policies, and metadata. Smaller bronhouders, for example municipalities, can lack the capacity for this work.
Proposed decision¶
GBO packages the source-side stack as a deployable toolkit. The toolkit has these parts:
- FSC Inway and Manager.
- The source gateway (
bron-sidecar). - Contract seeds.
- Policy templates per route.
- A reference onboarding process: certificate, FSC registration, metadata publication, contract, and activation.
Some sources cannot host their own GraphQL endpoint. For these sources, GBO offers a GBO translation layer (GBO-vertaallaag) as a shared service.
Open points¶
These points are open:
- Who operates the shared instances of the translation layer?
- The policy templates are guidance. Each bronhouder owns and publishes its own policy (ADR-0021).
- How does a source get its BSNk decryption keys as an onboarding step (BSNK-09, #467)?
- Who builds the registration and onboarding facility (Q-74)?
- The support model and the conformance testing for onboarded sources.