How OBINexus turned UK human rights legislation into a 625-address mathematical lattice — every right enumerable, bounded, and computable. Open source, with a polar-priority schedule for disability rights."
tags: opensource, law, architecture, accessibility
cover_image:
canonical_url:
series: OBINexus Constitutional Computing
"Breathing without Living is Suffering / When System Fails, Build Your Own."
Repo: github.com/obinexusmk2/upower_framework
I recorded the voice note for this at about 3:49 AM on the 27th of April, 2026. I'd been thinking about it for a while. The short version: I'm a care leaver. Under the Care Act 2014, I should have had an independent property in the community by 18. The right existed. The path to enforce it didn't. So I built the framework I needed the system to have.
This is that framework.
TL;DR
Most rights frameworks are flat lists of documents. U-POWER treats every legal entitlement as a computable power relation with a deterministic address inside a 625-element lattice (5⁴ = 625). Each address resolves to a UK statutory anchor, a duty-bearer, an enforcement route, a remedy, and a review mechanism — all without cross-references between articles.
If you've ever shipped a system where a missing pointer in one module nukes the whole graph, you already understand why this matters. UK rights legislation has the same failure mode. U-POWER fixes it the way good systems engineers fix anything: with addressability, isolation, and a priority scheduler.
The Problem
UK human rights, equality, social, economic, and environmental statutes form an implicit graph. The Human Rights Act 1998 references the ECHR. The Care Act 2014 leans on the Children Act 1989. The Equality Act 2010 backstops the Disability Discrimination Act 1995. When a duty fails, you have to traverse the graph to find the next remedy — and if a node is silently broken (statutory ambiguity, repealed clause, conflicting case law), the right is practically unenforceable even though it's legally present.
This is not a metaphor. This is the daily lived reality of disabled people, care leavers, and anyone trying to enforce a right they technically have.
The framing I keep coming back to: it's not primarily a broken system. It's a law system that needs data for human accountability and error margin. Corruption, scandals, injustice — those are the symptoms of a rights graph that was never made addressable. You can't audit what you can't address.
The U-POWER Principle
U-POWER — Umbrella, Papa, Oscar, Whiskey, Echo, Romeo — is a constitutional computing framework that expresses every legal entitlement as a power relation. The framework is grounded in three Igbo pillars:
- OHA — Public (rights are public claims)
- IWU — Law (the enforcement mechanism)
- IJI — Order (the governing constraint)
Rights are not what's printed in a statute. Rights are the power to act within a system that recognises you as an addressable entity.
The Math
The address space is derived from a sensory power relation:
5 senses × 5 senses × 5 senses × 5 senses = 5⁴ = 625
The four multiplications represent:
- Rights you can act on
- Rights you can measure
- Rights you can enforce
- Rights you can review
625 is the local maximum for a baseline rights-bearer. Every entitlement you hold is reachable inside this space.
Disability Variant (Half-Dimension Rights)
Where a sensory dimension is impaired, the formula shifts:
Disability Rights = (A + B)^(A × B) where A = 4, B = 5 → 9^625
Astronomically large but computable. To put a number on the worst case: 9^625 ≈ 1.93 × 10⁵⁹⁶ addresses. That's the disability rights envelope. It's not a typo, and it's not a flex — it's the structural admission that when a sensory dimension is impaired, the rights surface area you have to enforce is vastly larger than the rights surface area someone else takes for granted.
This is intentional. Disability rights receive polar priority — they're processed first in any rights resolution queue, mirroring the MMUKO OS Polar Priority Scheduler:
PENDING → LOADED → FILTER → FLASH → RUNNING → DONE
If you're disabled and you can't reach the right, it isn't equitable. Polar priority is the correction.
Article Address Format
Every article in the 625-space has a unique address:
D{1-5}.{DIM}.{SUB}.{1-5}
| Field | Meaning | Values |
|---|---|---|
D{n} |
Domain (sense) | D1 Existence, D2 Communication, D3 Autonomy, D4 Sustenance, D5 Environment |
{DIM} |
Legislative dimension | CR (Civil), ER (Equality), SR (Social), ECR (Economic), ENV (Environmental) |
{SUB} |
Sub-right category | AC (Access), EN (Enforcement), RM (Remedy), ND (Non-Discrimination), PA (Participation) |
{n} |
Implementation layer | 1 Primary Duty, 2 Procedural, 3 Enforcement, 4 Redress, 5 Review |
Example resolutions
D1.CR.AC.1
→ Existence / Civil Rights / Access / Primary Duty
→ Human Rights Act 1998 Art. 2 (Right to Life)
D3.ER.RM.3
→ Autonomy / Equality / Remedy / Enforcement Mechanism
→ Equality Act 2010 s.20 (reasonable adjustments)
D2.SR.ND.4
→ Communication / Social / Non-Discrimination / Redress
→ Care Act 2014 s.23 (care leavers)
If you've worked with IPv4, this will feel familiar. The address is the route.
The Five Domains
| Domain | Sense | Core Right | Article Range |
|---|---|---|---|
| D1 Existence | Sight / Physical Presence | Right to exist, be seen, occupy space, housing | 1–125 |
| D2 Communication | Hearing / Expression | Right to speak, be heard, access information | 126–250 |
| D3 Autonomy | Touch / Agency | Right to self-determination, consent, bodily integrity | 251–375 |
| D4 Sustenance | Taste / Nutrition | Right to food, water, economic participation | 376–500 |
| D5 Environment | Smell / Sensing | Right to safe environment, community | 501–625 |
Each domain × dimension cell holds a 5×5 sub-grid of (Sub-Right × Implementation Layer) — 25 articles per cell, 125 articles per domain, 625 total.
The No-Cross-Reference Principle
This is the part that matters most to engineers.
Each of the 625 articles is self-contained. No article may depend on another for its interpretation or enforcement.
Every article encodes, in a single computable unit:
- The right
- The duty-bearer
- The enforcement route
- The remedy
- The review mechanism
You can think of it as a flat key-value store of rights, where lookup is O(1) and there is no transitive dependency to traverse. This is the structural guarantee that prevents rights from being nullified by inter-article conflicts — the failure mode that breaks current UK legislative architecture in practice.
Polar Priority Schedule
| Tier | Category | Formula | Anchor |
|---|---|---|---|
| P1 | Disability Rights (Half-Dim) | (A+B)^(A×B) = 9^625 |
Equality Act 2010 s.20, Care Act 2014 s.18 |
| P2 | Civil Rights (Standard) | A^(A×B) = 5^625 |
Human Rights Act 1998 — full ECHR |
| P3 | Social Rights | 5^4 = 625 |
Care Act 2014, Children Act 1989 |
| P4 | Economic Rights | 5^4 = 625 |
Welfare Reform Act 2012, NMW Act 1998 |
| P5 | Environmental Rights | 5^4 = 625 |
Environment Act 2021, HSWA 1974 |
Disability gets polar priority not as a courtesy but as a structural correction: when one sensory dimension is impaired, the address space expands rather than contracts, and those addresses are scheduled first.
UK Legislation Coverage
The 625-article space anchors to roughly 30 primary UK statutes and instruments, including:
- Human Rights Act 1998 (incorporating ECHR Articles 2–14)
- Equality Act 2010 (ss.4, 13, 15, 19, 20, 26, 27, 149)
- Care Act 2014, Children Act 1989, Children (Leaving Care) Act 2000
- Housing Act 1996, Homelessness Reduction Act 2017
- Welfare Reform Act 2012, Employment Rights Act 1996, NMW Act 1998
- Environment Act 2021, Health and Safety at Work Act 1974, Clean Air Act 1993
- Mental Health Act 1983 (as amended 2007), Mental Capacity Act 2005, Autism Act 2009
Every article ID resolves to a specific section of a specific statute. The mapping is exhaustive and reproducible.
Why Treat Rights as Code
If you can address a right, you can:
- Verify it — does this person hold this article? Yes/no, deterministic.
- Enforce it — the address carries its own enforcement route. No graph walk required.
- Audit it — every duty-bearer can be queried for compliance against the 625-article space.
- Schedule it — the Polar Priority Scheduler tells you what to process first.
-
Compose it — within the OBINexus stack, the U-POWER spec sits alongside the OBI U AI Constitutional Runtime (FILTER/FLASH state machine), the NSIGII Protocol (Suffering Formula
Σ = (N − R) × K), and the IWU Equity Act 2026 (decentralised ledger for financial liquidation).
This is what "constitutional computing" means in the OBINexus sense: the conversion of abstract legal entitlement into a formal system that can be loaded, verified, and enforced by machine.
The Stack
U-POWER is the rights specification layer. It plugs into the broader OBINexus toolchain:
LaTeX spec + Markdown repos + compliance scripts
│
▼
riftlang.exe → .so.a → rift.exe → gosilang
│
▼
nlink → polybuild
│
▼
OBI U AI Constitutional Runtime (FILTER / FLASH)
Rights are loaded as articles, filtered through the runtime, and either flashed to enforcement or held pending. The address is the contract.
Get Involved
The full 625-article mapping, the LaTeX specification, the compliance scripts, and the constitutional governance docs live in the repo:
github.com/obinexusmk2/upower_framework
Pull requests welcome on:
- Additional jurisdiction mappings (the current spec is UK-anchored; the 625-space is jurisdiction-agnostic)
- Compliance script coverage
- Address-resolution tooling
- Test fixtures for edge cases (especially around the half-dimension disability variant)
If you've been told a right exists but can't enforce it, you've already seen the bug. U-POWER is the patch.
Closing — Every Path Has a Solution
The reason I built this — and the reason I'll keep building it — is simple. For every shape you go: left, middle, right, back, forward, turn, upside down, inside out — there is a solution to the problem. That's why human rights matter. The 625-article space is the structural guarantee that the solution is always addressable, even when the system in front of you pretends otherwise.
Your right to the power is not a metaphor. It is a specification.
OBINexus Computing — Nnamdi Michael Okpala
obinexus.org · github.com/obinexusmk2
Top comments (0)