Replaying the gateway's calls against a live Objecten + Objecttypen pair turned
up two blockers CI would only have found after the fact:
- Objecten rejects an objecttype it has not been configured with, and it
identifies one by uuid — assigned at seed time by a one-shot that runs after
Objecten's static setup_configuration. Pin the uuid on both sides instead.
- Objecten notifies on every write and notifications_api_common *raises* when
that config is absent, so every POST 500'd after rolling the object back.
Objecten → NRC has no broker, worker, kanaal or abonnement yet, so disable
notifications rather than wire a client that drops every message; S-19b turns
them on for real.
With both in place the full exchange verifies end to end: lookup → version →
search → create → update (still one object), and a record carrying a bsn is
rejected by the schema. ADR-0028 records both.
ADR-0028 records why the register record lives in Objecten rather than as zaak
eigenschappen, why the ACL owns the hop, and how two non-atomic writes are made
to converge instead. Also retires the PRD §15 out-of-scope line the slice
supersedes.
not