AI governance

Governance that stays current, tied to what actually runs

For each AI system and each vendor, one page answers what it is, who owns it, how it was assessed, who approved it, under what conditions, until when, and what has changed since.

  • One record for each AI system and vendor
  • Decided by a named administrator
  • Approvals last three years at most
  • No automatic decisions
MERIDVAR consoleIllustrative

Approval Approved

Decided by an administrator who did not make the request.

Requested by
Operator, Customer Operations
Decided by
Administrator, Security
Basis
Classification, both reviews, vendor approval and inventory snapshot, pinned at the time of the request
Conditions
Block the delete tool on the linked MCP server
Ends
Twelve months from the decision

If anything in the basis has changed since the request, the approval is refused.

The model

Six separate records, kept separate on purpose

A completed assessment is not an approval. A classification is not a field on an assessment. Keeping them apart is what makes each one auditable.

  1. 01

    AI system

    The inventory record: name, owners, purpose, vendor, models, and linked agents and MCP servers. Observed in traffic or declared by a person.

  2. 02

    Assessment

    Answers to a versioned questionnaire. Every answer is kept with who gave it and when, together with the hash of the exact question answered.

  3. 03

    Risk classification

    A level, the rules version, the facts read and the reason for each factor. Only an administrator can override it, and only with a reason.

  4. 04

    Privacy review

    A reviewer’s decision, findings and conditions, and the organisation’s own DPIA position. It is not a DPIA.

  5. 05

    Security review

    Six areas rated, from access to tool and MCP access. Exceptions always carry an expiry date. It is not a certification.

  6. 06

    Approval

    An administrator’s decision on a request, with a reason, conditions and an end date no more than three years ahead.

Separation of duties

The approver is never the requester

An operator or an administrator makes the request. A different administrator decides. The two are compared on a stable operator ID, so renaming an account does not get round the rule.

  • A request needs its prerequisites. A current classification, every required review decided without objection, and an approved vendor where one is required. A refused request lists every missing piece.
  • The basis is pinned. The classification, the source assessment, the reviews, the vendor approval and a snapshot of the inventory fields that matter.
  • Approval checks the basis again. If anything has changed since the request, approval is refused.
  • The server enforces roles. Hiding a control in the console is not the check.
ReviewsIllustrative

Support reply assistant

Each review records the reviewer’s decision, with findings, conditions and the next review date.

Privacy review2 findings, 1 conditionNo objection
Security reviewTool and MCP access: gapNo objection
Vendor approvalHolds until its end dateApproved

A privacy review is not a DPIA. A security review is not a certification. The console says so on the page.

Governance status

One status for each system and vendor, and no score

The status is derived by a fixed order of precedence, and the parts it was derived from are always shown beside it. Missing information stays missing.

StatusMeaning
Not assessedNo baseline assessment has been completed. Never shown as low risk.
Classification requiredThe system is not classified, or its classification is out of date.
Ready for approvalEverything required is in place, and nobody has requested approval.
Pending approvalA request is waiting for a decision.
ApprovedA granted approval holds.
Review requiredA granted approval is in question, or a required review is missing or out of date.
Approval expiredA granted approval has passed its end date.
Evidence mismatchA stored decision does not match the evidence record that made it. Shown above everything else.
MERIDVAR consoleIllustrative

Governance status Review required

The vendor’s classification changed after approval. Nothing is revoked automatically.

#1041classification.recordedhash match, signature valid
#1057review.privacy.decidedhash match, signature valid
#1063approval.grantedhash match, signature valid
#1188vendor.classification.changedhash match

The audit package can be downloaded: every record about this system, as stored.

Nothing is approved or revoked automatically

MERIDVAR cannot reliably tell whether a change is material. It says that an approval needs review, and it says why. A person then decides whether to renew or revoke it. Every earlier decision stays readable.

An approval reads “review required” when

  • the classification has changed or is out of date
  • a newer review exists, or a review objects or is out of date
  • the vendor approval no longer holds
  • an inventory field in the pinned snapshot has changed
  • the system has been retired

Where it fits

The AI record that your wider programme can rely on

Beside your GRC platform

MERIDVAR is the AI-specific system of record. It supplies inventory, decisions and evidence to the enterprise risk programme you already run.

A faithful record

MERIDVAR records the decisions people make and the facts they state, with who and when, in a log in which any later edit is detectable.

People stay accountable

Every approval is a named person’s decision. Legal and regulatory determinations remain with the organisation and its counsel.

See MERIDVAR refuse a request on your own network

A working session with the founder, on a host you control.

What happens next

  1. You send the formYour request goes straight to the founder.
  2. We reply by emailWe agree a time and what you want to see.
  3. We run a working sessionWe install the appliance with you, route a test request through it and read the evidence it leaves.