Vendors, as of 2026-10-16

Vendors

The AI vendors behind your systems, from their AVRF records: each capability's class, the questionnaire, the contract terms and the exit test.

Prototype states

One contract waits for your decision: Meridian Language Systems, amendment 2.One contract is flagged: Meridian Language Systems, amendment 2, approved below the authority of the boundary it caps.Nothing here waits for you. The CRO decides on the flagged contract.

Vendor	Capabilities and class	Questionnaire	Contract terms	Exit test
Meridian Language Systems	Customer assistant, class C1	re-issue triggered 2026-10-15 by a material model change	4 of 5 obtained; model-change notice declined	tested 2026-06-18
Corvane	Underwriting triage, class C1	re-issued 2026-10-16 after the new model card, response due 2026-11-06	5 of 5 obtained	not tested no exit capability recorded
Northlight	Document OCR, class C1	renewal due 2026-11-11	4 of 5 obtained; evaluation rights declined	not tested no exit capability recorded

Learn more about vendor records

A class belongs to the capability, not the vendor: one vendor can supply a C1 and a C3 capability, and any doubt means C1. Every answer keeps its outcome (answered, asserted, declined, not applicable) and where its evidence comes from: produced by the institution, asserted by the vendor, or attested by a third party. An assertion is never shown as a finding, and a declined answer is never left blank. Sourcing and negotiation stay in your procurement process; vendor answers arrive as uploads.

Queries

typed entered by a personproduced written by the system

Contract authority nebula-mutual/vendors/query/contract-authority Effective 2026-10-16Author GovernanceOSReason: query run

Query: contracts approved below the authority of the boundaries they cap; typed
Result: 1 of 3: Meridian Language Systems, amendment 2; produced

Vendor assertions nebula-mutual/vendors/query/vendor-assertions Effective 2026-10-16Author GovernanceOSReason: query run

Query: approvals resting only on vendor assertions; typed
Result: 1 approval: Document OCR, G4 of 2025-11-11; produced

typed entered by a personproduced written by the system

Meridian Language Systems nebula-mutual/vendors/meridian Effective 2026-10-16Author Procurement leadReason: vendor record

Capabilities and class: Customer assistant, class C1; typed
Pending capability: Underwriting notes summary, intake int-0011: its class is set when it is triaged; produced
Relationship owner: Procurement lead; typed
Questionnaire: issued 2026-02-02; response 2026-03-04, reviewed by the Procurement lead; re-issue triggered 2026-10-15 by a material model change; typed
Contract terms: Audit rights: obtained
Evaluation rights: obtained
Incident notice: obtained
Model-change notice: declined by the vendor in amendment 2, 2026-08-04
Exit and portability: obtained; typed
Contract: master agreement with amendment 2, approved 2026-08-04 by the Procurement lead; typed
Exit test: 2026-06-18: substitution plan tested, hand-off to people within one business day; typed
Monitoring log, latest: 2026-10-15 09:41 CT: version change seen at the boundary, no notice from the vendor; produced

Corvane nebula-mutual/vendors/corvane Effective 2026-10-16Author Procurement leadReason: vendor record

Capabilities and class: Underwriting triage, class C1; typed
Relationship owner: Procurement lead; typed
Questionnaire: issued 2026-02-20; response 2026-03-10, reviewed by the Procurement lead; re-issued 2026-10-16 after the new model card, response due 2026-11-06; typed
Contract terms: Audit rights: obtained
Evaluation rights: obtained
Incident notice: obtained
Model-change notice: obtained
Exit and portability: obtained; typed
Contract: master agreement, approved 2026-03-12 by the CRO; typed
Exit test: not tested: a plan never tested is not recorded as an exit capability; typed
Monitoring log, latest: 2026-10-15 09:40 CT: new model card received, asserted by vendor; typed

Northlight nebula-mutual/vendors/northlight Effective 2026-10-16Author Procurement leadReason: vendor record

Capabilities and class: Document OCR, class C1; typed
Relationship owner: Procurement lead; typed
Questionnaire: issued 2025-06-02; response 2025-06-27, reviewed by the Procurement lead; renewal due 2026-11-11; typed
Contract terms: Audit rights: obtained
Evaluation rights: declined by the vendor
Incident notice: obtained
Model-change notice: obtained
Exit and portability: obtained; typed
Contract: service agreement, approved 2025-11-04 by the CRO; typed
Exit test: not tested: a plan never tested is not recorded as an exit capability; typed
Monitoring log, latest: no entry since 2025-11-11: there is no boundary, so version changes are not observed; typed

Meridian Language Systems: what the approval rests on

Answer	Outcome	Evidence source
Evaluation on insurance questions	answered	produced: Nebula Mutual's own evaluation run, 2026-06-09, at G2
Training data and prompt retention	answered	attested by third party: the vendor's independent audit report, 2026-01
Incident notice	asserted	asserted by vendor; no evidence attached
Advance notice of model changes	declined	reason given: the vendor will not commit to a notice period

typed entered by a personproduced written by the system

Contract below authority nebula-mutual/vendors/meridian/authority-01 Effective 2026-10-16Author GovernanceOSReason: contract-authority query

Contract: master agreement, amendment 2, approved 2026-08-04 by the Procurement lead; typed
Approver's authority: contracts for capabilities in class C2 and C3, from the delegation record; typed
Caps: the customer assistant, class C1, tier 1: G3 and G4 signed by the CRO; boundary set by the CISO; produced
Term changed: advance notice of model changes, declined by the vendor; typed
Authority needed: the CRO; produced
Since: the vendor changed its model on 2026-10-15 with no notice: chg-0014; produced
Escalated to: the CRO, with a clock of 10 business days from 2026-10-16; produced
Status: open; the finding stays on the record whatever the outcome; produced

Decision

Named: the CRO. A contract that caps a boundary needs authority at or above every control under it.

Only the CRO can ratify or refuse this amendment. The Procurement lead renegotiates if it is refused.

Approval	Rests on	Evidence source
Document OCR, G4 passed 2025-11-11	Northlight's accuracy statement; Northlight declined evaluation rights, so Nebula Mutual has not tested it	asserted by vendor, only

The approval stands. This shows what it rests on, so the CRO and the Validator can decide whether to test it themselves.

Vendors

Queries

Meridian Language Systems: what the approval rests on

Decision

Ratify amendment 2: Meridian Language Systems

Refuse amendment 2: Meridian Language Systems

No vendor records yet