docs(backlog): add phase 10 (OpenZaak hardening) and phase 11 (behandelportal)

WP-55..60 harden the OpenZaak integration for production (secrets/TLS, idempotent provisioning, least-privilege scopes, real notifications, confidentialiteit config, write-divergence resilience). WP-61..66 stand up a staff-facing behandelportal per ADR-0002, wired to the same backend via BFF-lite decision DTOs. Both phases are independent tracks; WP-60's Decisions block is deliberately left open for a planner-agent kickoff. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-30 11:59:11 +02:00
parent 66f8125ccd
commit f21c3c7ca2
13 changed files with 840 additions and 0 deletions
@@ -0,0 +1,69 @@
+# WP-66 — Wire the decision into OpenZaak
+
+Status: todo
+Phase: 11 — Behandelportal
+
+## Why
+
+WP-65's decision currently only updates local state (`LocalZaakSource`). For the
+behandelportal to actually function against a real register, the recorded decision needs
+to also write a besluit/status transition to ZGW — extending the write capability that
+already partially exists (`CreateStatusRequest`, `CreateRolRequest` in
+`OpenZaakZaakSource.cs`) rather than building a new ZGW client from scratch.
+
+## Read first
+
+- `backend/src/BigRegister.Api/Zgw/OpenZaakZaakSource.cs` (existing write records)
+- ZGW's Besluiten API (referenced in `openzaak-integration.md` if covered, or the ZGW
+  standard docs) for besluit creation
+- [WP-50](WP-50-openzaak-create-zaak.md) (the first ZGW write slice, for the pattern to
+  follow)
+
+## Decisions (pre-made, don't relitigate)
+
+- Extend `IZaakSource`/`OpenZaakZaakSource` with a besluit/status-transition write,
+  following the same pattern WP-50 established for create-zaak (a records + mapper
+  addition, not a new abstraction).
+- Gated by `Zgw:Enabled` like every other ZGW write — the behandelportal keeps working
+  against `LocalZaakSource` when it's off.
+- Best done after Phase 10's WP-60 (write-divergence resilience) lands, since this is
+  exactly the second write pair that resilience work should already cover — but not
+  strictly blocked on it if Phase 10 is still in progress (call out the residual risk
+  explicitly if shipped first).
+
+## Files
+
+`Zgw/OpenZaakZaakSource.cs` (besluit/status write), `Data/IZaakSource.cs` (new write
+method), tests.
+
+## Steps
+
+1. Add the besluit/status-transition write to `OpenZaakZaakSource`, mirroring WP-50's
+   create-zaak pattern.
+2. Wire WP-65's decision command to call it when `Zgw:Enabled=true`.
+3. Integration test against the WP-54 harness (extend `OpenZaakIntegrationTests`).
+
+## Acceptance criteria
+
+- [ ] A recorded decision writes a real besluit/status transition to OpenZaak when
+      `Zgw:Enabled=true`.
+- [ ] Behandelportal still works unchanged against `LocalZaakSource` when
+      `Zgw:Enabled=false`.
+- [ ] `OpenZaakIntegrationTests` covers the new write.
+
+## Verification
+
+`cd backend && dotnet test --filter Category=Integration` against the (ideally
+Phase-10-hardened) OpenZaak harness; manual smoke with `Zgw:Enabled=true`.
+
+## Out of scope
+
+Any further behandelportal screens beyond beoordeling.
+
+## Risks
+
+If Phase 10's WP-60 (write-divergence resilience) hasn't landed yet, this introduces a
+second unprotected write pair — call this out explicitly if the two phases aren't
+sequenced together in practice.
+
+Depends on: WP-65. Benefits from (but doesn't strictly require) WP-60.