Golden Rules¶

Non-negotiable principles that govern every decision on the KRG Digital Real Estate & Municipality Platform. When in doubt, refer to these rules.

The 10 Golden Rules¶

1. Property Data is Sacred¶

Every property record ownership, parcel boundary, transaction history is treated as a legal document. Data integrity is absolute. No record is modified without an immutable audit trail entry. No record is deleted, ever. History is append-only.

2. We Are a Tenant, Not the Landlord¶

We consume shared government infrastructure (Sulaymaniyah DC, KRG-Road, Payment Gateway, KRDPASS, EJBCA). We do not build, manage, or duplicate that infrastructure. Our responsibility starts at our Kubernetes namespaces and ends at the KRG-Road Security Server boundary.

3. GIS is a First-Class Citizen¶

Every property has a spatial representation. Every query can be spatial. The map is not a nice-to-have visualization it is a core data layer. PostGIS, GeoServer, and pg_tileserv are as important as PostgreSQL and Redis.

4. One Property, One Truth¶

There is exactly one authoritative record for each parcel and each property in the system. No copies. No spreadsheets. No parallel registries. When another system needs property data, it queries our API it does not maintain its own copy.

5. Paper and Digital Must Coexist (Until They Don't)¶

The legal framework may not be ready on day one. The system must operate in parallel with paper processes during transition. Every digital workflow has a paper fallback. The goal is to eliminate paper entirely but not by pretending it doesn't exist today.

6. Open Standards, Open Source, No Lock-In¶

Every technology choice is open-source or open-standard. PostgreSQL, not Oracle. Keycloak, not Auth0. GeoServer, not ArcGIS Server. OGC WMS/WFS, not proprietary map APIs. When we hand over the system, the KRG pays zero license fees to operate it.

7. Build for the Citizen, Not the Bureaucracy¶

The system is designed around the citizen's property journey not around internal ministry processes. One application per transaction. One visit (or zero visits) per service. Every internal routing, approval, and inter-department coordination happens behind the scenes.

8. Measure Everything, Guess Nothing¶

• Every transaction has timestamps (submitted, processed, completed)
• Every OCR result has a confidence score
• Every ML valuation has accuracy metrics
• Every service center has throughput and satisfaction data
• Every decision about expanding, scaling, or changing the system is data-driven

9. Security is Not Optional¶

Property records are among the most sensitive data any government holds. Zero-trust architecture. Encryption everywhere. RBAC enforced at every layer. Quarterly penetration testing. Immutable audit trail. Every access logged. There is no "we'll add security later."

10. Handover is the Goal¶

We are building this to hand it over. Every architectural decision, every documentation page, every training session is designed so that the KRG operates this platform independently after Month 42. If the vendor disappears tomorrow, the documentation and code must be sufficient for a competent team to take over.