Access Request
No marketing capture. No mailing list. The schema is the form.
Tier 1+ surfaces — architecture summaries, implementation detail, the diligence room, partner-specific evidence — are gated behind counsel-vetted access. The request is plain text. Compose an email with the fields below; we triage by institution and disclosure tier; counsel routes the response.
How to request
Send an email to access@governedai.ai with the following fields. Plain text is preferred. Attachments accepted only if encrypted.
The eight-field schema below is the entire form. We do not parse free-form requests; missing fields delay triage. Counsel routes only complete requests.
Open mail composer with template →Request schema
Every field is required. The schema is also published as a JSON Schema at /schemas/institutional_access_request.schema.json.
institutional_access_request:
organization: # legal entity name and country of incorporation
role: # requester's role at the organization
jurisdiction: # primary regulatory jurisdiction (e.g. US-SEC, EU-AIAct, UK-FCA)
use_case: # what governed-AI artifact is the request scoped to
requested_tier: # one of: TIER_1_PARTNER | TIER_2_NDA | TIER_3_INTERNAL_ONLY
nda_status: # one of: none | requested | executed | declined
technical_evaluator: # name and contact of the engineer who will evaluate
counsel_contact: # name and contact of retained counsel of record
Field guidance
| Field | What we mean | Why it matters |
|---|---|---|
organization |
Legal entity name and country of incorporation | Counsel-routing depends on jurisdictional fit |
role |
Title and reporting line | Disclosure depth scales to seniority and need |
jurisdiction |
Primary regulatory regime relevant to the request | EU AI Act, SEC, DORA, NIS2, and state regulators each shape what may be shared |
use_case |
The specific governed-AI artifact you are evaluating | We do not accept open-ended discovery requests; the scope is what is shared |
requested_tier |
The disclosure tier you are requesting access to | The tier determines counsel review depth and timeline |
nda_status |
Whether an NDA is in place, requested, or pending counsel | Tier 1+ surfaces require an executed NDA before any disclosure |
technical_evaluator |
The named engineer or evaluator on your side | Diligence rooms are scoped to named evaluators, not organizations |
counsel_contact |
Retained counsel on your side | Counsel-to-counsel routing replaces ad-hoc disclosure conversations |
What happens next
- The request is acknowledged within five business days.
- Counsel verifies the eight fields against retained-counsel-only criteria.
- If the request is in scope, counsel proposes an NDA shape (mutual NDA, scoped NDA, or partner-tier NDA depending on requested_tier).
- Once NDA executes, the diligence room is provisioned for the named technical_evaluator.
- Disclosure occurs only inside the diligence room; no Tier 1+ content is shared by email.
Default to non-disclosure. If a request is ambiguous about scope or jurisdiction, the routing default is to ask the requester to clarify, not to disclose conservatively. The discipline favors a smaller, accurate disclosure over a larger, ambiguous one.