Skip to content
gluon

Conflicting expiry dates

The ERP and the legal library disagreed about when a contract ends. The answer said so, and cited both.

We built this example on the product as it is, with invented names and figures. It is not a customer story.

Two people at a meeting table going through printed documents.

Results

2 sources
disagreed, and the answer named both instead of picking one.
1 conflict
surfaced to the buyer and kept in the record.
Every change
re-tested against golden questions, so the answer keeps catching it.

Systems disagree

A buyer asks which supplier contracts need attention this quarter. The ERP says contract C-1 ends on 14 November 2026; the legal library says 31 March 2027. An assistant that reads one of them gives a clean answer with the wrong deadline, and nobody sees the conflict.

Authority decides

Every source has a trust level and every value keeps the source it came from. The Authority Graph lets the authoritative record prevail and shows the conflict instead of smoothing it over. Drift tests on every change that answers keep catching it.

  1. The signed contract outranks the copy.

    Which source prevails is part of the model, not a guess of the assistant.

    Legal contract libraryAuthoritative · signed contract
    ↳ conflicts with
    ERP contract registerExpiry 14-11-2026 · shown as a conflict
    ↳ outranks
    Team chat threadConversational · evidence only
  2. An answer that names the conflict.

    The buyer sees the date that applies and the one that disagrees.

    Decision

    Contract C-1 ends on 31-03-2027 according to the signed contract. The ERP register says 14-11-2026: check with the contract owner.

    Source
    Legal contract library · C-1
    Conflict
    ERP contract register · expiryDate
    Permission
    Buyer · procurement · confirmed
    Audit log
    17-10-2026 09:12 · 2d7c…91fa

Where Gluon acts