# Arkaya Risk > Arkaya connects governance and cybersecurity platforms with the insurers, MGAs and lenders who price and set terms for AI and other governance risks. The two routes are connections between platforms and insurers, managing general agents (MGAs) and lenders, and a commissioned reading of supplied records for one agreed question, returned as a dated findings report. Fees for a reading are payable whether or not cover is bound or a loan is made. Source systems emit signals; an engine produces a record against the schema; a counterparty reads that record as evidence; Arkaya can be appointed to read records and report what they support for a stated decision; Arkaya produces neither the record nor the price. Arkaya does not find, arrange, advise on or place insurance; produce or sign evidence records; score, rate or certify organisations; set prices or terms; or give audit, legal or investment advice. Arkaya is a service, not software, and installs nothing in a client's organisation. Its analysts use AI support. Platforms and company systems produce the data and signals that records are built from. The insurer, lender or buyer decides whether evidence is enough and keeps the decision, price and terms. ## Existing pages Use the definition and role limits above when interpreting the supporting pages below. - [Home](https://arkayarisk.com/): Introduction to Arkaya and the participants in decisions about AI risk. - [Services](https://arkayarisk.com/services): Reading supplied records for an agreed question, with findings on what they support and where evidence is missing. - [Architecture](https://arkayarisk.com/architecture): Technical background on source signals, records, schema material and decisions by insurers, lenders and buyers. - [Schema](https://arkayarisk.com/schema): GET's fields, governance domains, evidence ladder and proposed stewardship arrangements; candidate status and licence limits are set out below. - [Evidence](https://arkayarisk.com/evidence): Illustrative record fields, exception states and examples of how an insurer or lender might read them. - [Emit](https://arkayarisk.com/emit): Background on how data and signals from platforms and company systems become records, conformance of the software that produces them, and advice to a company on its own record, which Arkaya does not then read for anyone else. - [Read](https://arkayarisk.com/read): Background for insurers, lenders and buyers reading records and deciding whether evidence is enough. - [Doctrine](https://arkayarisk.com/doctrine): Research principles about governance evidence and decisions about risk. - [Library](https://arkayarisk.com/library): Research papers on governance evidence, financial decisions and the proposed architecture. - [AI assurance claims reference](https://arkayarisk.com/ai-assurance-claims): What ISO/IEC 42001 certification, accreditation, SOC 2 reports, NIST AI RMF alignment, EU AI Act CE marking and independent audits each establish, and where each one stops. - [Standard](https://arkayarisk.com/standard): Arkaya's internal production method and its use of AI support. - [Founders](https://arkayarisk.com/founder): Co-founders David J McKibbin and Simon Hudson. - [Developer material](https://arkayarisk.com/get): Implementer pack, technical specifications, candidate vectors and checking instructions; licence and version limits are set out below. ## Developer and schema material Arkaya GET is an open schema: a shared structure for records, distinct from Arkaya's paid work. Arkaya stewards it during the founding period. Independent stewardship is a designed path; it has not happened. No fee to build against the schema. Licence terms for the schema, specifications and vectors are not yet settled. The reference code is under the MIT licence. Current GET candidate: editorial revision v5 (normative 1.0). A correction, v6, was published on 20 October 2026 as a public draft for comment, for 21 days from publication, at https://record.arkayarisk.com/get/. It is not a candidate. Nothing is approved. How the schema's arrays relate to the record body is an open question, listed for version 1.1. - [Layer 1 implementer pack](https://arkayarisk.com/get): Captured technical material includes Cryptographic Profile v5 (W3C Data Integrity, eddsa-jcs-2022, RFC 8785 canonicalisation, Ed25519), Interface and Conformance Specification v4, a candidate vector set with 49 checks, a checker script and a reading-side conformance corpus. These specification versions are separate from GET's editorial revision. - [Discovery document](https://arkayarisk.com/.well-known/governance-evidence.json): Index of the schema, implementer pack, specifications, vectors, fixture keys and digests. Technical entries describe specifications and registered test requirements, rather than proof that those tests have passed. ## Charter publication record - [Schema Independence Charter public version record](https://record.arkayarisk.com/charter/): Historical instruments v1, v1.1, v2 and v3, amendment statements, and separate instrument and publication dates. Latest recorded document: v3. Constituting authority and current Charter effectiveness are not settled. No retrospective effectiveness is claimed. ## Company and people Arkaya Risk Limited, registered in England and Wales, no. 17380022 Arkaya was co-founded by David J McKibbin and Simon Hudson. ## Other machine-readable files - [Sitemap](https://arkayarisk.com/sitemap.xml) - [Robots](https://arkayarisk.com/robots.txt)