Cyan Eclipse Insurepack

Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio

What it does

• Novel mechanism (SPEC §2.1, verbatim) — a live underwriter-facing evidence API fed by bench verdicts, incident records, and control receipts — premium-relevant changes emit change receipts to the insured. (In v0.1.1 the API shape is rehearsed locally over fixtures only: no live API is built, no underwriter is served, and no insurer system is touched.)
• Load-bearing disclosure (SPEC §11.1, verbatim): the evidence pack is insured-side disclosure tooling; underwriting reliance is the insurer's process, not Insurepack's claim. Insurepack is evidence assembly only. It does not underwrite, is not an insurer, broker, MGA, or underwriting tool, does not price or bind coverage, does not adjust or pay claims, and does not act for any carrier.
• Bench path: v0.1.0 bench (wave4/bench-insurepack.md, DEFECT-1..3) + v0.1.1 delta re-bench (wave4/rebench-insurepack.md: DEFECT-1..3 all CLOSED, Condition 1 amended to Condition 1′ by the bench, builder suite 28/28 reproduced, no new defect).
• Amended Condition 1′ (verbatim, named by the bench): a single-pack VERIFY_PASS attests the pack, its own transition, and the internal integrity of the presented stream; it must NOT be relied on as proof of completeness of transitions earlier than the pack's immediate predecessor (a fully re-signed, re-linked rewritten stream is indistinguishable there); full-history reliance requires per-pack chain verification (which the export transcript now performs) or an external anchor.
• Change receipts are issued for premium-relevant CHANGES only (verdict/insured-tool-set/control/incident-summary/named-field changes), never for re-assembly, verification, export, or same-state refresh — the change-receipt stream cannot be flooded into meaningless noise by re-running assembly. Absence of evidence is shown as absence: an input class with no registered fixture records is named in gaps[] (INPUT_ABSENT), never fabricated or silently omitted. Herald (signing pattern), Meter (metering grammar), and Docket (pack grammar) are consumed by reference only.

Tools

Problems it addresses

• Cyber-insurance evidence gets assembled once, at application or renewal, from whatever screenshots and spreadsheets are at hand — then it goes stale while the insured's actual posture changes underneath it
• I need the pack to be a signed, recomputable index over artifacts that already exist — bench verdicts, incident records, control receipts — kept current by change receipts that name the field, the prior value, and the new value whenever a premium-relevant fact changes
• I need the disclosure boundary load-bearing: the pack is insured-side disclosure tooling; underwriting reliance is the insurer's process — and absence of evidence shown as absence, never fabricated or silently omitted

Not tested

• Underwriting, pricing, binding, claims, or any insurer-side reliance — Insurepack is evidence assembly only (evidence assembly only; no underwriting): it does not underwrite, is not an insurer, broker, MGA, or underwriting tool, does not price or bind coverage, does not adjust or pay claims, and does not act for any carrier; underwriting reliance is the insurer's process, not Insurepack's claim (SPEC §11.1)
• Any live phase — serving real insureds, real incident records, real policies, a live underwriter-facing API, or any insurer/carrier/regulator integration is SPEC §10 counsel-gated and UNBUILT; there is no dormant live path in v0.1.1
• Full-history completeness from a single pack — per amended Condition 1′, a single-pack VERIFY_PASS must NOT be relied on as proof of completeness of transitions earlier than the pack's immediate predecessor; full-history reliance requires per-pack chain verification (which the export transcript performs) or an external anchor
• External anchoring / multi-party reliance — the pure local file store caps any verdict at PASS-CONDITIONAL (local/simulator); an external anchor is required before live or multi-party reliance
• Production key custody — signing is an HMAC fixture stand-in for Herald RS256 (fixture keys in keys/, gitignored, mode 600); a live phase would need real Herald signing and a re-bench