Compliance
Assemble recorded evidence and map controls with their stated limitations.
80 source modules; the private verifier build is excluded. Availability and test evidence are separate. No module is labeled hosted/live without recorded operational evidence.
| Module and job | Delivery | Verification evidence |
|---|---|---|
@zanii/admissibilityTurn a Zanii audit bundle into a court-ready bilingual (Arabic/English) evidence pack for UAE Electronic Transactions Law 46/2021 - verification steps for a judge/expert + offline reproduce commands. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/complianceTurn a Zanii audit bundle into an auditor-ready compliance report - offline verification, action breakdown, anchoring coverage, and control mapping, rendered to Markdown. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/credentialsVerifiable institutional credentials — diplomas, licences, certifications — offline-verifiable in milliseconds with no call to the registrar. Four checks: signature, expiry, revocation (with an explicit freshness window), and a domain-bound issuer root-of-trust. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/decisionsGig/creator algorithmic fairness: decision receipts a worker can audit — completeness (every decision about me, tamper-evident), rule-consistency (the same rulebook decided everyone, via manifest_hash), and committed factors (no post-hoc rationalization). Never claims 'the algorithm is fair'. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/educationIntegrity for AI in learning and assessment: AI-assistance declarations per assignment, provable submission times, assessment-rubric versions, tutor-session summaries and grade-change trails, with students identified by pseudonymous tags. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/electionsChain of custody for election operations, not vote casting: sealed-container and equipment custody with co-signed handoffs, tabulation batches whose totals add up, and a registry of AI-generated political content with disclosure labels. Never handles ballot choices or voter identities. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/ftaFTA filing evidence for Meezan & Books - receipt 'prepared a filing' with the wall enforced (prepares, never files/advises), and the Tax-Agent handoff as its own signed receipt. Zero deps. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/govPublic-sector algorithmic accountability: benefits, visas, fines, licences. A state decision with no governing rulebook cannot be constructed, and appealPack puts a court-ready, bilingual proof of what the algorithm did to you into the citizen's own hands. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/healthMedical audit trails without leaking the pattern: per-episode unlinkable tags (the patient supplies the tag, never the seed), plus who accessed the record, which model recommended what under which protocol, and which named clinician took responsibility. Break-glass is loud, not impossible. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/identity-bridgeConsume enterprise agent identity as an input, don't compete with it. Bind a Microsoft Entra Agent ID or a SPIFFE SVID to a Zanii did:key with a two-way attestation - the external identity's subject and the did:key both sign the same binding, so a Zanii receipt is provably by the agent the enterprise already governs. Token validation is injected (the @zanii/attest discipline): we verify the binding, you plug in the Entra/SPIFFE trust root. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/insuranceMachine-verifiable underwriting for agent liability - risk FACTS from the ledger's own un-inflatable aggregate (never a score), a co-signed policy, and claims that resolve against Merkle-proven receipts instead of disputes. Zanii states facts; insurers price. Ledger silence is unknown, not good. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/kyaKnow Your Agent: screen a counterparty agent against a deny-list / injected sanctions provider before your agent transacts, and receipt the check (kya.screening). Rides @zanii/a2a-directory; the list is injected. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/kybOwner-to-legal-entity binding - the missing link between an owner did:key and who is legally on the hook. Two-way: the company serves .well-known/zanii-owner.json on its own domain AND the owner signs an attestation naming that domain and entity; verification requires both. Zanii verifies domain control, never corporate registration - the claim becomes verifiable and attributable, not officially certified. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/legal-aiAI-assisted legal work, accountable: per-task work receipts with human review, supervising-lawyer sign-off, citation checks against an injected resolver (unresolvable citations are flagged, not trusted), privilege-aware selective disclosure, conflict checks, and court disclosure statements of AI use. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/regulatorA supervisor's toolkit for AI oversight: scoped live feeds of receipts, provably random audit samples (seed committed before the draw), incident-reporting deadline clocks for the EU AI Act, NIS2, DORA and GDPR, and signed supervisory findings and attestations. A labelled regime table (law, guidance or proposal, with sources) adds UAE PDPL, DIFC and CBUAE rows, and feeds can be scoped by jurisdiction binding. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/vcW3C Verifiable Credentials 2.0 bridge - export Zanii credentials and AgentCVs as spec-conformant VCs with genuine eddsa-jcs-2022 DataIntegrityProofs (Zanii already speaks did:key + Ed25519 + JCS, which IS that cryptosuite), and verify any did:key eddsa-jcs-2022 VC from anyone. Bridges the format, not the trust model: revocation freshness and domain binding remain Zanii-side checks. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/jurisdictionSigned bindings of an owner or agent did:key to the regulator, jurisdiction, licence and sector it falls under, so a regulator (DFSA, CBUAE, ADGM-FSRA, SAMA, VARA, SCA, EU market surveillance authorities) can answer 'which agents are mine?'. Self-declared or regulator-attested, closed code registry, checkable offline. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/incident-reportSigned incident evidence into regulator reports with proofs attached: the EU AI Act Art. 73 serious-incident report (Commission draft template) and the OECD common reporting framework (non-binding), in a signed incident.report envelope verifiable offline. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/post-marketEU AI Act Art. 72 post-market monitoring and Art. 12 / 19 / 26(6) log retention evidence: a signed post_market.report per period with receipt counts, retention proofs, incident report hashes and caller metrics, verifiable offline. | Usable source / SDK | not assessed Hosted: unverified |
@zanii/ai-registerA regulator AI-system register built from Ledger and Certify records: one entry per system (agent DIDs, owner, jurisdiction binding, Certify certificate, KYB record, descriptive fields), exported as EU AI Act Annex VIII, UK ATRS and Eurocities Algorithmic Transparency Standard field maps with null-with-reason for anything the inputs do not support, plus a signed zanii.ai_register snapshot and CSV / JSON helpers. | Usable source / SDK | not assessed Hosted: unverified |
Blackbox and Certify
These are separate products. Their hosted gateway availability has not been verified by this deployment. Source packages and integration examples do not establish that a hosted workflow is live.