feat(rip): add R5.3 (vervroegde) Ingebruikname / Oplevering — the ladder is complete

[sgort]

R5.3 was the last gap in the Flevoland RIP ladder. It had no design when the rest was modelled, so R5.2 and R5.4 were deliberately built to step over it. The sheet arrived dated 3-9-2026, and it lands exactly where those two said it would.

Two commits: the reference sheet (plus a .gitignore entry), then the bundle.

Files	14 (1 BPMN, 7 forms, 6 documents)
Nodes / flows / lanes	15 / 14 / 3
New candidate groups	none — ladder stays at 34

Shape

A single early choice — oplevering, or (vervroegde) ingebruikname — opening two near-mirror paths that never rejoin:

interne schouw → schouw met aannemer en tzh → vaststellen → exit

They differ only in what they're called, which sjabloon they use, and where they leave to. No loop anywhere in the phase: a rejected schouw sends its restpunten back to R5.2 rather than round again here.

Four end events, three returning to R5.2 — deliberately not merged

This is the opposite of the call made in R6.1, and the difference is the point. R6.1's two "Einde proces" markers meant the same completion, so collapsing them lost nothing. Here the three R5.2 returns mean three different things:

• oplevering rejected → restpunten to execute
• vervroegde ingebruikname agreed → part of the areaal goes into use while the work carries on
• ingebruikname rejected → restpunten to be executed by the ON

Same destination, different reasons — and the reason is what the Faseladder has to show. Merged, the phase would report only "back to R5.2".

Also in here

.semgrep/ is gitignored. Semgrep Guardian writes a guardian.yml and lock wherever it's invoked, so copies appeared at the repo root and under examples/organizations/flevoland/. Local tooling state, not project config; the bare directory name catches it at any depth.

Verification

Faseladder contract holds — key RipR53Process, formRefBinding="deployment" on all seven user tasks with no "latest", no businessKey, no municipality variable, no external-task topics, no boardOwner in the bundle, no start event carrying a form.

Both validators pass on every bundle in the ladder. No duplicate form or document ids across all twelve phases.

Already deployed and verified on the local engine: RipR53Process v1, tenant flevoland, 14 of 14 resources matching disk file-for-file, boardOwner=infra-board and ronl:organization=flevoland injected at deploy. All twelve phases now deployed and contract-clean.

Note for the Faseladder side

RBA's skippedPhasesBefore currently surfaces R5.3 as handled outside the tool, and R5.4's precondition resolves its predecessor to R5.2. Both were correct until now; both need revisiting once R5.3 is adoptable. That session is being briefed separately.

🤖 Generated with Claude Code