Emit

Produce governance evidence another party can read.

Reading evidence rather than producing it? → READ

For the systems and organisations that produce the record: AI-governance and GRC platforms, monitoring and control engines, identity and telemetry systems, and companies emitting first-party evidence about themselves.

§ 01 · The question a record answers

What happened, under what authority, with what evidence?

A governance evidence record states what a system was permitted to do, what it did, under what control, and whether the control held. The company's systems emit the underlying signals. A conformant engine produces the record against one open schema, so that an insurer, a lender or an acquirer can read it without adopting the system that produced it. The format is on the Evidence page; the schema is on the Schema page.

The record is the company's. Portability is a schema property: evidence generated against the schema moves with the company across engines, insurers and capital events without re-basing. No vendor, and not Arkaya, holds it captive.

§ 02 · What Arkaya does here

One open schema, and the assessment of what implements it.

Arkaya is custodian of the schema and, until the Foundation handover set out in the Charter, its founding assessor. Assessment on this side is of the implementation against the schema, not of the organisation's governance.

The open schema and its published specifications.
The published conformance tests, which any party can run.
Conformance assessment of an engine implementation against the schema. Conformance attaches to the implementation, never to any organisation's governance.
Portability testing: does the record keep its meaning outside the environment that produced it?
Authority-continuity testing: does the record preserve what was authorised at the moment the consequential act occurred?
Emission triage: what belongs in a record, what travels as a committed reference, and what is product content that never enters a record.

Arkaya produces no evidence record, connects no system and issues no score.

There are no systems to connect.
There are three parties writing to one contract, and the only thing passing between them is a file.

§ 03 · Advice to a company on its own record

Advice for the company alone.

A company can ask Arkaya how its record will read to the parties that price it, and which records would make a control checkable. That advice is given to the company. Where Arkaya has designed evidence or advised on it, it does not read that evidence for anyone else. Where Arkaya has only translated a platform's records into the open format, it may later read them for an insurer, after telling the insurer and having the translation checked independently.

A Dynamic Risk Maturity Assessment and event-readiness work, calibrated to the obligations the company's next capital moment will test, sit on this side. If an insurer, lender or acquirer later reads that evidence, Arkaya does not carry out the reading. Detailed scope held under NDA. Improving the controls themselves is operational work; Arkaya does not sell it.

§ 04 · How it starts

Two steps, each one evidenced.

For a company emitting evidence about itself:

First engagement

The board authors the Protocol and ranks the domains material to enterprise value.

First evidence record

A conformant engine produces a signed record against obligation, in the eight-field format.

For a platform or engine, the starting point is conformance assessment of the implementation against the schema, as set out above.

What happens next is the reader's: the desk read at inception and the renewal re-read are on the READ page.

§ 05 · What this is not

Not an integrator. Nothing is connected; a record is produced and a file travels.

Not an improvement adviser. The record shows the state of the controls; changing them is the company's own operational work.

Not a certification of anyone's governance. Conformance attaches to an implementation; no rating, level or score is issued to an organisation.

Not pay-to-include. There is no fee for inclusion in the schema, no priority path and no commercial tier. The Charter says so, and the Schema page carries it.

The emitter produces the evidence.
Arkaya does not.

Of the three roles on the READ page, the Subject sits on this side. Its systems emit the underlying signals; a conformant engine produces the record. Supervisor and Pricer are readers.

Discuss an evidence review →

Or request the Emitter Brief by email: