MECHASSURE-IEB / Version 0.1Open Standard · Free Verifier
MECHASSURE.org
Machine Evidence · Coverage Handoff · Assurance Standard
MECHASSURE-IEB / Profile 0.1 / Public Draft

Free insurer verification profiles for AI evidence bundles.

MECHASSURE is the free insurer verification arm for Legal OREO evidence bundles — an open profile that lets insurers inspect whether an AI-assisted legal or institutional decision preserved the evidence needed for underwriting, coverage review, claims defense, exclusions analysis, and loss-control review.

Legal OREO
structures the proof.
BAINK
seals the bundle.
MECHASSURE
verifies whether the bundle is insurable.
Read the standard →Browse schemasDownload templates
Scope notice
  • — MECHASSURE does not sell insurance.
  • — MECHASSURE does not provide legal advice.
  • — MECHASSURE does not certify that an AI system is safe.
§ 1

What MECHASSURE verifies

MECHASSURE answers a single question: Can an insurer rely on this bundle as preserved evidence of AI-assisted reasoning, decision control, source grounding, human review, and exception handling?

  1. 01
    Bundle integrity

    Are all files present, hashed, and unchanged?

  2. 02
    Source sufficiency

    Are material claims tied to source documents?

  3. 03
    Authority traceability

    Are legal and policy rules cited and versioned?

  4. 04
    Defeater awareness

    Are objections, exclusions, exceptions, and adverse facts preserved?

  5. 05
    Human review

    Was attorney, claims, compliance, or risk review recorded?

  6. 06
    Temporal safety

    Does the bundle state what law, policy, model, and data version applied when?

  7. 07
    Coverage relevance

    Does the bundle map facts to policy terms, exclusions, conditions, and duties?

  8. 08
    Claims defensibility

    Could the insurer later reconstruct what happened?

  9. 09
    Loss-control usefulness

    Does the bundle help prevent repeat loss or identify weak controls?

  10. 10
    Reinsurance portability

    Can the evidence be shared without vendor lock-in?

§ 2

Standard family

MECHASSURE sits at the insurer-facing end of a four-layer evidence stack. Each layer is independent, open, and inspectable. The MECHASSURE profile only adds the insurer-specific files; the upstream evidence comes from Legal OREO and is sealed by a BAINK-compatible bundle.

Figure 1 — Standard familyRead top-down
  1. LP
    LegalProof.dev
    Proof graph
    Reasoning · claims · authorities · defeaters
  2. OR
    Legal OREO
    Legal evidence structure
    Opinion · Rule · Evidence · Objection · Seal
  3. BK
    BAINK.dev
    Bundle infrastructure
    Manifest · source hashes · verifier · registry
  4. MA
    MECHASSURE.org
    Insurer verification profile
    Coverage-readiness · exclusions · claims defensibility
§ 3

OREOS → insurer interpretation

Legal OREO structures legal work product. MECHASSURE re-reads the same five fields in insurance terms — no new evidence is required, only an insurer-facing lens.

Legal OREOMECHASSURE insurer reading
OpinionCovered / excluded / reserved / unresolved position
RulePolicy term · statute · regulation · underwriting guideline
EvidenceDocuments · facts · logs · source spans · exhibits
ObjectionExclusion · exception · adverse fact · limitation · pending issue
SealHash · signature · receipt · verifier report
§ 4

What MECHASSURE stands for

The wordmark is a brand; the expansion describes the function.

  • Machine
  • Evidence
  • Coverage
  • Handoff
  • ASSURE — Assurance Standard for Underwriting, Review, and Exceptions
“Machine Evidence Coverage Handoff Assurance — for insurers.”
§ 5

Profile excerpt

A minimal mechassure-ieb-0.1 bundle declaration. The full schema and validator are published under /schemas.

mechassure-bundle.json (excerpt)
001{
002 "bundle_id": "mechassure_legal_oreo_2026_001",
003 "profile": "mechassure-ieb-0.1",
004 "base_profile": "legal-oreo-lr-0.1",
005 "standard_family": [
006 "BAINK Evidence Standard",
007 "Legal OREO Standard",
008 "MECHASSURE Insurer Evidence Bundle Profile"
009 ],
010 "matter_type": "ai_assisted_legal_review",
011 "insurance_context": {
012 "line_of_business": "professional_liability",
013 "review_stage": "underwriting",
014 "coverage_position": "not_determined"
015 },
016 "artifacts": [
017 { "path": "legal-oreo-bundle.json", "type": "legal_oreo_bundle", "required": true },
018 { "path": "insurance/coverage_map.json", "type": "coverage_map", "required": true },
019 { "path": "insurance/exclusions_map.json", "type": "exclusions_map", "required": true },
020 { "path": "insurance/risk_controls.json", "type": "risk_control_map", "required": true },
021 { "path": "reports/mechassure_report.json", "type": "insurer_verification_report" }
022 ],
023 "bundle_hash": "sha256:..."
024}
§ 6

Verifier output (preview)

The verifier returns a short, deterministic report. It never opines on the legal conclusion or the coverage decision.

mechassure_report.json · summary
  • pass
    Bundle integrity
    Manifest, hashes, event chain, receipt
  • pass
    Legal OREO compatibility
    Opinion · Rule · Evidence · Objection · Seal present
  • pass
    Insurance review files
    Coverage · risk-control · exclusions maps present
  • warn
    Defeater resolution
    One defeater remains substantively unresolved
  • warn
    Adequacy review
    Insurer must independently evaluate legal adequacy
  • info
    Final status
    MECHASSURE-READY · COVERAGE NOT DETERMINED · RECORD VERIFIED

For institutional adopters

Implement the open profile.

Schemas, templates, and the verifier are public-domain. Read the standard, pick the audience profile that matches your workflow, and inspect a sample report.

For insurersFor reinsurersFor legal teams