chore: Restructure specs to proper OpenSpec format

openspec/changes/dso-omgevingsloket/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: conduction
+created: 2026-03-20

openspec/changes/dso-omgevingsloket/design.md

@@ -0,0 +1,6 @@
+# Design: dso-omgevingsloket
+
+## Architecture Overview
+
+See specs/dso-omgevingsloket/spec.md for detailed requirements and scenarios.
+Design details to be elaborated during implementation planning.

openspec/changes/dso-omgevingsloket/proposal.md

@@ -0,0 +1,13 @@
+# Proposal: dso-omgevingsloket
+
+## Summary
+Implement a DSO (Digitaal Stelsel Omgevingswet) adapter for OpenConnector to receive verzoeken from the Omgevingsloket and map activiteiten to zaaktypes in OpenRegister.
+
+## Motivation
+Municipalities must receive and process permit applications (verzoeken) from the national Omgevingsloket. OpenConnector needs a DSO adapter to bridge the DSO-LV API with the local case management system.
+
+## Scope
+- DSO-LV inbound endpoint (STAM) for receiving verzoeken
+- Activiteiten-to-zaaktype mapping configuration
+- DSO-SWF (Samenwerkfunctionaliteit) integration
+- Verzoek validation and transformation

openspec/changes/dso-omgevingsloket/tasks.md

@@ -0,0 +1,6 @@
+# Tasks: dso-omgevingsloket
+
+## Task 1: Implementation planning
+- **Spec ref**: specs/dso-omgevingsloket/spec.md
+- **Status**: todo
+- **Acceptance criteria**: Requirements from spec are decomposed into implementable tasks

openspec/changes/ibabs-notubiz-connector/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: conduction
+created: 2026-03-20

openspec/changes/ibabs-notubiz-connector/design.md

@@ -0,0 +1,6 @@
+# Design: ibabs-notubiz-connector
+
+## Architecture Overview
+
+See specs/ibabs-notubiz-connector/spec.md for detailed requirements and scenarios.
+Design details to be elaborated during implementation planning.

openspec/changes/ibabs-notubiz-connector/proposal.md

@@ -0,0 +1,13 @@
+# Proposal: ibabs-notubiz-connector
+
+## Summary
+Implement connectors for iBabs and NotuBiz raadsinformatiesystemen (council information systems) to synchronize meeting agendas, decisions, and documents with OpenRegister.
+
+## Motivation
+Dutch municipalities use iBabs or NotuBiz for council meeting management. Synchronizing this data with OpenRegister enables cross-referencing council decisions with cases and documents.
+
+## Scope
+- iBabs API integration (meetings, agendas, documents)
+- NotuBiz API integration (meetings, decisions, attachments)
+- Parafering (approval) workflow support
+- Bidirectional synchronization of meeting data

openspec/changes/ibabs-notubiz-connector/tasks.md

@@ -0,0 +1,6 @@
+# Tasks: ibabs-notubiz-connector
+
+## Task 1: Implementation planning
+- **Spec ref**: specs/ibabs-notubiz-connector/spec.md
+- **Status**: todo
+- **Acceptance criteria**: Requirements from spec are decomposed into implementable tasks

openspec/specs/prometheus-metrics/spec.md

@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: reviewed
 ---
 
 # Prometheus Metrics Endpoint

openspec/specs/stuf-adapter/spec.md

@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: reviewed
 ---
 
 # StUF Adapter