One business record.
Purpose · business owner · lifecycle · review decisions
db-017 ↘Invoice assistantsn-204 ↗01 / AGENT RECONCILIATION
Different records.
One agent.
Your platforms report identities.
CatProof connects them to an accountable agent.
THE ARCHITECTURE
Evidence flows in.
Decisions stay yours.
CatProof keeps source observations separate from the business record. A confirmed link connects them.
Databricks
db-017ServiceNow
sn-204Your other sourcesConfigured scope only
READ-ONLY CONNECTORS · METADATA IN · NO AGENT INVOCATION
01AVAILABLE
Source observations
Keep the source ID, connection, reported name, technical owner, provenance and last-seen evidence. New identities start with separate agent records; refreshes update the source observations.
Source identity ≠ business identity02IN DEVELOPMENT
Possible matches
The proposed queue compares normalized names across separate connections. It shows supporting clues and owner conflicts. Stale or unavailable evidence is excluded. Manual linking works without this optional queue.
Suggestion ≠ confirmed identity03AVAILABLE
Human review + explicit link
Compare source IDs, purpose and ownership. Choose the destination agent and confirm moving one source identity. Differently named records can be reviewed and linked manually.
No automatic merge · no owner copied from a matchEvery link has context.
Link and unlink events stay recorded. Both original business records and their history are preserved. The existing link workflow supports undo.
Next source refresh → update observations.Keep confirmed links, business ownership and prior decisions.
WHAT CATPROOF STORES
Three pieces. Clear boundaries.
What the source reported.
Original identifiers, reported metadata, scope and freshness. A maker account stays a source owner.
Which agent it belongs to.
Each imported source observation has one canonical binding. An explicit link changes that binding; it does not combine or delete source records.
What your team decided.
The accountable business owner, purpose, lifecycle and review history. Source refreshes do not replace these decisions.
WHEN THINGS CHANGE
Refresh the evidence.
Keep the decisions.
| Source event | CatProof behavior |
|---|---|
| Name or source owner changes | Update the observation. Retain its identity link and the canonical business owner. Conflicting details remain reviewable. |
| Read fails or evidence is incomplete | Retain previous evidence and expose its stale or unavailable state. A failed read is not an empty inventory. |
| A record is absent from a scan | Mark it not observed or stale according to the connector’s guarantees. Absence does not prove deletion; the business record is retained. |
| A link needs correction | Review and relink or split the source identity. Preserve the business records and record the change in history. |
Invoice helper
db-017Source owner: maker account
Invoice assistant
sn-204Source owner: platform team
Same job. Different IDs.
Check the evidence before linking. Names alone aren’t proof.
Open the example evidence
In this fictional example, your team has confirmed that both source records describe the same invoice workflow. A source owner is a technical role; the business owner is a separate decision.
CATPROOF / LINK CONFIRMED
One invoice assistant.
Business owner: Finance team
db-017 + sn-204Both source records stay put. Owner and history stay here.
Illustration only. This changes no real records and makes no provider calls.
START WITH YOUR SOURCES
Read. Review. Link.
Repeat without the mess.
Read the sources.
Scoped identities. Original IDs. Last-seen evidence.
You call the match.
Review both records. Confirm which identity belongs where.
Keep the decisions.
Source refreshes preserve your business owner and history.
Today: deliberate identity linking. A dedicated match-review queue is in development. No automatic merging or direct ITSM/CMDB write-back.