Pre-award
The mission never becomes a testable requirement before selection.
Institutional authority assurance
MIZAN ميزان
The record of whoauthorised themachine.
Institutional authority assurance for public-sector AI agents - maintaining the evidence, authority, accountability and expiry behind permission to operate.
01InstitutionMandate
02PeopleAccountability
03AI systemOperation
Mandate
Accountability
Operation
MMIZANAuthority recordAuthority recorded
Scroll transition
From machine telemetry to an institutional record.
Machine
Runtime signals are observed.
People
Responsibility remains named.
Institution
Mandate and conditions hold the case.
Record
Authorisation can be reconstructed.
The problem
Enterprises can deploy AI. They must still reconstruct authority.
MIZAN establishes a continuous control record across approval, operation, change and review, giving enterprise stakeholders a shared view of permission and accountability.
Approval
Approval may be recorded without a reconstructable argument.
In-life
Changes to evidence, models or operating conditions may invalidate the basis of acceptance.
Institutional outcome
Leadership needs a clear record of accountability, control effectiveness and decision outcomes.
Enterprise product suite
One connected system for institutional AI assurance.
MIZAN connects authority with institutional capability, qualified people, trusted knowledge and controlled research across the enterprise.
MIZANGoverns authority - the central institutional assurance platform.
QudraBuilds capability
Mu'tamadCertifies people
IsnadAttests knowledge
MisbarControlled research
Qudra builds institutional capability: mandate, readiness and ownership. It can stand alone and also supplies reusable capability context into MIZAN.
Where MIZAN sits
The layer between law and runtime control.
Agent-control systems watch behaviour in operation. MIZAN maintains the institutional permission around the use case.
Institutional authorisation
MIZAN holds the authority envelope: mandate instrument, named holder, conditions, expiry and capability gate.
Runtime governance watches the system.
MIZAN watches the permission.
MIZAN watches the permission.
The authorisation record
An assurance case, not a checklist.
A MIZAN record links public purpose, mandate, use case, evidence, capability, conditions, acceptance, expiry and change events into a named institutional case.
Authority EnvelopeNamed permission, conditions and expiry around one AI use case.
Public PurposeWhat outcome justifies the use case.
MandateThe instrument that permits action.
AI Use CaseThe bounded machine-mediated function.
Named OwnerThe visible person responsible for acceptance.
EvidenceMaterial claims trace to named artefacts.
CapabilityLive, expiring institutional condition.
ConditionsBlocking issues remain visible.
ExpiryReview, re-authorise, condition or withdraw.
Permission that expires
Permission that expires - not a policy that sits on a shelf.
Capability is live. Evidence ages. Material change can trigger review. A blocking issue must not disappear inside an average.
Authorised
A named decision holder accepts a bounded AI use case against a mandate, evidence set, conditions and review date.
From claim to evidence
Every material claim traces to named evidence.
MIZAN connects every material claim to its evidence source, accountable owner, specialist review and validity period.
Build the record
MIZAN makes computationally mediated authority visible, testable, reconstructable and accountable.
Build the record behind the decision.