Solutions · Data Resolution
Your data, cross-examined.
Every value in the estate gets the questions an auditor would ask. Conflicts, stale facts, breach and fraud signals, gaps: surfaced with their evidence and held for a person to decide.
A duplicate is held for a person, never deleted by a hunch
01 · Resolve
One supplier, spelled four ways.
Estates disagree with themselves. The layer matches values across documents, checks them against your system of record, and resolves mentions into entities, at record scale.
Meridian BioTech
4 mentions · matched on registration number, address, contract reference
Each match shows its evidence. A duplicate is held for a person, never deleted by a hunch.
Cross-document checks run on the same mechanism: an invoice against its purchase order and delivery note, a certificate against the register that issued it, a claim against the policy it cites.
02 · Conflicts
Conflicts named, never smoothed.
Two sources, two values, one field. The layer records both, quotes both, and holds the field in conflict until a person resolves it.
It never averages and never picks the newer file by default. The signed agreement says one thing; a later thread says another. Both entries stay on the record with their sources, and the resolution, once made, is recorded too: who chose, which value, on what grounds.
“aggregate liability is capped at £2,000,000
“we agreed the cap comes down to £1m for the renewal
Neither value is discarded. The field carries the conflict flag until a person resolves it, and the resolution goes on the record.
03 · Currency
Current, or flagged.
A value that was true in March is not a fact in September. Ageing rules you write decide when a value needs re-evidencing, and the record says so out loud.
Certificates age against their expiry, figures against the period they describe, details against the last document that confirmed them. When a legal or regulatory change lands, the affected records are re-checked against it and flagged where they no longer hold.
The same pass carries the harder signals: values that match a known breach disclosure, payment patterns that look wrong, activity that deserves a second look. Signals for your reviewers, never verdicts.
04 · Gaps
The gaps report.
What the estate does not contain is a finding too. Missing areas come back named, each with the reason it was looked for.
An expiring certificate with no renewal on file. A supplier invoiced all year with no executed agreement anywhere in the estate. The report says what is missing, where it should have been, and which rule noticed.
Each gap names the rule that looked for it, so the report is a work list, not an accusation.
05 · Held
Held for a person.
Cross-examination produces findings, not actions. Every finding waits, with its evidence, for someone with the authority to decide.
Surfaced, never smoothed
A conflict is a finding, not a nuisance. The layer records both sides with their quotes and refuses to pick one for you. Averaging two values that disagree is how estates lie to themselves.
Nothing deleted by a hunch
Duplicates, stale values and failed rows are held with their reasons attached. Deletion follows your instruction, and the deletion is itself recorded.
Signals, not verdicts
A fraud pattern or a breach match is a referral to your reviewers, never an automatic action. The record shows exactly why the flag fired; a person decides what it means.
Ask the record what is held and why: Sokros Copilot →
Bring the two systems that disagree.
One field both systems claim to own, cross-examined in front of you: the conflict named, the quotes attached, the finding held.
A 30-minute briefing: one estate slice scoped, its conflicts and gaps shown before anything integrates.