
Oct 12, 2026
IN /
SANAD
1 min read
SANAD: every Shariah invariant enforced four times
Types, service layer, database and an adversarial test suite each enforce the same rules — no sale before the gates, a total that never increases, no rate.

IOTA Labs Team
Digital Engineering Practice
Types, service layer, database and an adversarial test suite each enforce the same rules — no sale before the gates, a total that never increases, no rate.
A single layer of enforcement is a single point of failure, so SANAD enforces each invariant four times. Transitions that would sell before the gates are not callable in the type system, the service layer evaluates the gates, the database checks the sale timestamp, and an adversarial test passes only when the forbidden attempt fails.
The same pattern covers the obligation total that can never increase, one document per contract leg, no duplicate financing of an invoice, late charges that are never income, and the absence of any rate construct in the Murabaha engine.

Oct 12, 2026
IN /
SANAD
1 min read
SANAD: every Shariah invariant enforced four times
Types, service layer, database and an adversarial test suite each enforce the same rules — no sale before the gates, a total that never increases, no rate.

IOTA Labs Team
Digital Engineering Practice
Types, service layer, database and an adversarial test suite each enforce the same rules — no sale before the gates, a total that never increases, no rate.
A single layer of enforcement is a single point of failure, so SANAD enforces each invariant four times. Transitions that would sell before the gates are not callable in the type system, the service layer evaluates the gates, the database checks the sale timestamp, and an adversarial test passes only when the forbidden attempt fails.
The same pattern covers the obligation total that can never increase, one document per contract leg, no duplicate financing of an invoice, late charges that are never income, and the absence of any rate construct in the Murabaha engine.

Oct 12, 2026
IN /
SANAD
1 min read
SANAD: every Shariah invariant enforced four times
Types, service layer, database and an adversarial test suite each enforce the same rules — no sale before the gates, a total that never increases, no rate.

IOTA Labs Team
Digital Engineering Practice
Types, service layer, database and an adversarial test suite each enforce the same rules — no sale before the gates, a total that never increases, no rate.
A single layer of enforcement is a single point of failure, so SANAD enforces each invariant four times. Transitions that would sell before the gates are not callable in the type system, the service layer evaluates the gates, the database checks the sale timestamp, and an adversarial test passes only when the forbidden attempt fails.
The same pattern covers the obligation total that can never increase, one document per contract leg, no duplicate financing of an invoice, late charges that are never income, and the absence of any rate construct in the Murabaha engine.

Oct 12, 2026
IN /
SANAD
1 min read
SANAD: every Shariah invariant enforced four times
Types, service layer, database and an adversarial test suite each enforce the same rules — no sale before the gates, a total that never increases, no rate.

IOTA Labs Team
Digital Engineering Practice
Types, service layer, database and an adversarial test suite each enforce the same rules — no sale before the gates, a total that never increases, no rate.
A single layer of enforcement is a single point of failure, so SANAD enforces each invariant four times. Transitions that would sell before the gates are not callable in the type system, the service layer evaluates the gates, the database checks the sale timestamp, and an adversarial test passes only when the forbidden attempt fails.
The same pattern covers the obligation total that can never increase, one document per contract leg, no duplicate financing of an invoice, late charges that are never income, and the absence of any rate construct in the Murabaha engine.
(iota — 11)
Product updates
More updates
More updates
More updates
Notes on AI systems, architecture decisions,
and lessons from real deployments.
No hype. Just systems
Clarity beats automation
Decisions over demos
Designed for messy reality
Systems that hold under pressure

(iota — 15)
OUR PRINCIPLES
Book a
free call
We design AI systems that improve real work —
not just demonstrate technology.
We design AI systems that improve
real work — not just demonstrate technology.
We’ll review your
workflows, identify
where AI can create
impact, and outline
a clear path forward.
We’ll review your workflows, identify AI opportunities, and outline a clear path forward.
We’ll review your workflows, identify where AI can create impact, and outline
a clear path forward.
No preparation needed — we’ll guide the conversation
and focus on what matters.
No preparation needed — we’ll guide the conversation and focus on what matters.
7 AI products
100%
deployable on-prem, air-gapped





