Foundation
Why a structurally-separated foundation governs the rules. The for-profit operating entity runs the infrastructure under contract — the design's central commitment.
The foundation governs the rules. Iqrar operates the infrastructure under contract.
That sentence is the brand-discipline summary of Iqrar's structural separation. The same words appear on iqrar.io and on iqrar.foundation. They describe a real legal and operational pattern, not a marketing claim.
The structural problem
A regulator-trusted infrastructure venture has an inherent conflict if the same legal entity:
- Authors and signs the rules agents must follow.
- Operates the infrastructure that distributes those rules.
- Operates the infrastructure that ingests the resulting telemetry.
- Earns revenue from the regulated firms whose telemetry it ingests.
A single private vendor cannot durably hold all four. Companies will not adopt regulator-only platforms because doing so concedes data to a competitor's investor base; regulators will not endorse vendor-only platforms because doing so concedes regulatory authority to a vendor.
Iqrar's resolution is the foundation pattern — already proven in Linux Foundation, Apache Software Foundation, ICANN, OpenSSF — applied to AI agent governance.
How the separation works
| Function | Who holds it |
|---|---|
| Rule-authoring authority | Regulators (DFSA, ESMA, FCA, ...) — public bodies, signers in the registry. |
| Registry-update governance | Iqrar Foundation — board of regulators, regulated-firm representatives, technical stewards. Multi-sig threshold required to publish a new registry. |
| Infrastructure operation | Operating entities — including the for-profit Iqrar — under contract with the foundation. |
| Telemetry ingestion routing | Operating entities — but events are encrypted at the SDK boundary, per recipient, before they enter the worker. |
| Public commitment ledger | Sigstore Rekor — operated by the Linux Foundation's open-source supply-chain security project. Iqrar Foundation does not control it. |
The for-profit Iqrar is one of multiple possible operating entities. The foundation's bylaws permit additional operators under the same contract. If Iqrar the operator ceased to exist, the foundation's registry would remain valid and another operator could take over by signing a new infrastructure contract — agents would not need to redeploy.
What the foundation publishes
| Document | Status (May 2026) |
|---|---|
| Foundation governance white paper | v0.1 — in formation |
| Bylaws (registry-update protocol, signer roster, rotation procedure) | Forthcoming |
| Audit methodology | Forthcoming |
| Quarterly transparency report | First report Q4 2026 |
The honesty about which documents exist and which are forthcoming is itself a credibility move. The foundation reports what is real.
Board composition (intended, in formation)
A three-pillar board with structurally separated voting rights:
| Seat | Description |
|---|---|
| Regulator seats | DFSA-anchored seat for the founding jurisdiction. Subsequent regulator seats added by board approval. |
| Regulated-firm seats | Senior compliance representatives from active customers. Two-year rotating terms. |
| Technical-steward seats | Independent open-source / cryptography contributors. No commercial alignment with operating entities. |
The full bylaws will name initial signers before Provisional B is filed.
Why this matters for the patent
The structural separation is patent claim §5.2 — the foundation-countersignature requirement on every registry update. It is what makes the §8.1 "authority-signed runtime directive propagation" claim defensible against a "single vendor with optional countersignature" prior-art read.
When the foundation operates as a 3-of-5 multisig with a regulator on the board, the structural separation moves from nominal to genuinely operational. That shift is the work of Item B in the engineering plan.
See also
- iqrar.foundation — the foundation's institutional surface — iqrar.foundation
- Concepts overview — how the foundation's signing keys flow through every other layer —
- Audit-challenge protocol — what the foundation's signature lets a regulator verify —