What Phase 6 Means
Phase 6 completes the core technical implementation of the Landblock Registry Template — the reference architecture for a sovereign-controlled, LADM-compliant, federated land registry. The seven layers of the registry are fully operational and validated through end-to-end simulation.
"Complete" here has a specific meaning. It means the architecture is fully specified, implemented, and exercised. It does not mean deployed in production — production deployment requires a real jurisdiction, legal authorization, and an implementation program. What is complete is the technical foundation that makes those steps possible.
The Seven-Layer Registry Architecture
The registry is organized into seven functional layers, each with a distinct responsibility. This separation is not cosmetic — it reflects how real land administration works: legal authority, business rules, workflows, data, spatial processing, security, and communication are genuinely different concerns that need to be independently governed and independently verified.
| Layer | Responsibility | Who governs it |
|---|---|---|
| 0 — Governance & Legal | Constitutional authority, legal framework, tenure policy | The sovereign jurisdiction |
| 1 — Business Capabilities | Property registration, rights management, party administration | Land administration authority |
| 2 — Workflow Engine | State transitions, human approval gates, process orchestration | Configured by jurisdiction |
| 3 — LADM Data Model | ISO 19152 entities: parties, BA units, RRRs, spatial units, sources | International standard |
| 4 — Geospatial Services | OGC-compliant geometry, topology, spatial validation | International standard |
| 5 — Federation & Integration | Cross-registry queries, cryptographic proofs, external APIs | Landblock protocol |
| 6 — Security & Audit | DID authentication, RBAC, tamper-evident audit trail | Security policy of jurisdiction |
| 7 — Channels & Interfaces | REST APIs, user interfaces, notification channels | Implementation |
Layers 0–2 are jurisdiction-specific. Layers 3–4 are governed by international standards (ISO, OGC). Layers 5–7 are governed by the Landblock protocol and implementation choices. This clean separation is what enables sovereign control without technical lock-in.
Standards Compliance
The registry template is built on established international standards:
- ISO 19152 LADM — the international land administration domain model, covering parties, basic administrative units, rights/restrictions/responsibilities, spatial units, and source documents
- OGC Simple Features / ISO 19107 — spatial data and geometry compliance
- W3C Decentralized Identifiers (DIDs) — identity and cryptographic authentication
- VGGT alignment — workflow design reflects the Voluntary Guidelines on the Responsible Governance of Tenure
Standards compliance is not incidental. It is the mechanism by which a jurisdiction can be confident that their registry will be readable, verifiable, and interoperable with other systems — now and in the future.
What This Enables
A government evaluating Landblock can now verify three things that previously required trust in a vendor:
- The complete workflow runs end-to-end, from identity registration through parcel survey, human approval, rights assignment, audit trail generation, and federation proof
- The architecture enforces sovereignty — the jurisdiction's Layer 0 configuration governs the legal framework, approval thresholds, and workflow definitions
- Federation proofs are cryptographically verifiable, not dependent on API availability or bilateral agreement
The Novaterra simulation — a complete end-to-end demonstration using a fictional jurisdiction — is available in the Landblock Core repository. It includes the full simulation report, workflow diagrams, and sample federation proof JSON responses.
What Comes Next
Phase 7 shifts from building the registry to demonstrating it in context — publishing governance documentation, engagement with standards bodies, and structured outreach to jurisdictions evaluating digital land administration infrastructure. A separate post covers the Phase 7 framing in detail.
The absence of a production deployment is not a gap. Production deployment requires a real jurisdiction with legal authority to act. The registry template is the artifact that makes that conversation productive — governments can evaluate a working system, not a promise.