Two active vendor relationships require attention due to an active financial dispute and an ambiguous renewal clause.
The portfolio contains two vendor relationships with a term-end history that includes one disputed post-termination charge and one blocked contract analysis. No obligations are currently verified or awaiting signature.
Every figure above is counted from the evidence chain, not written by a model.
| Vendor | Verdict | Notice due | What it means |
|---|---|---|---|
| DataVault Pro | in dispute | 2026-11-30 185 days ago | DataVault Pro billed five hundred forty dollars despite valid notice served on August twenty-sixth two thousand twenty-six, and a dispute has been opened. |
| HostWave Systems | blocked pending review | unverified | HostWave Systems has an ambiguous renewal clause with conflicting written and numeric values, and no deadline could be verified. |
Review the HostWave Systems clause manually to determine the correct notice deadline and resolve the blocked status. Monitor the open dispute with DataVault Pro to ensure the unauthorized charge is refunded.
Every statement in this deck traces to a hash-chained record in the obligations ledger: the clause as it was read, both derivations of each deadline, the gate verdict, the notice delivered, and the invoice document checked against it. Recomputing the chain from its genesis record reproduces every hash.
Narrative written by Gemini from the ledger. Counts, dates and chain verification computed deterministically in code.