Πρόσωπον
Prosopon. Becoming one person
Person resolution across every legal entity.
A person replies, not an autoresponder.
One customer, not three strangers
Merges are stewarded and additive: nothing is overwritten, no keys are discarded. Models the whole cast, Account Holder, Data Subject, Visitor, Organisation, Subsidiary, Tenant Group, which is what makes federation a mechanism rather than an adjective.
The situation today
A group accumulates the same person several times over: once in retail, once in wealth, once in the commercial arm, once overseas. Every entity holds part of the picture, none holds the whole one, and the usual remedy is a data-warehouse programme measured in years.
What Prosopon does about it
Prosopon resolves the Person across every legal entity and keeps the resolution stewarded and additive. Nothing is overwritten, source keys survive, and each merge carries the evidence of how it was formed, which is what makes it defensible rather than merely convenient.
Runs alone as
A single-customer-view with evidence: one golden record per Person across retail, wealth, commercial and overseas entities, without a data-warehouse programme.
Becoming one person, in four parts.
Person, not record
A Person has many manifestations, an account holder here, a data subject there, a visitor before either. The identity model holds all of them under one resolved Person.
Stewarded, additive merges
A merge is a decision with an author and a reason, and it is reversible. Source keys survive, so the systems that fed the record keep working.
Group and tenant model
Organisation, Subsidiary and Tenant Group are first-class, so scope questions, which entity may see this, which consent covers it, have somewhere to attach.
No warehouse programme
Resolution runs against the systems you have. This is a single customer view you can stand up in a phase, not a three-year data project.
Reference set shown: UK. EU and EEA equivalents on request.
What changes once it is running.
A single view without the programme
Resolution runs against the systems you have. No migration, no warehouse, no three-year dependency.
Merges you can defend
Every merge has an author, a reason and a reversal path, so a wrong join is a correction rather than a data-loss incident.
Scope has somewhere to attach
Because Subsidiary and Tenant Group are modelled, questions about which entity may see what have a real answer.
Compounding value
Every other module reads the same Person, so identity work done once is never redone.
Phase one, one number
Duplicate records collapsed
Counted per entity pair, with the evidence of how each merge was formed.
Written to the evidence rail
worked example
- PERSON_RESOLVED3 records to 1, merge stewarded, reversible
Stronger with Agora. Prosopon is the noun the rest of the platform conjugates.
Four weeks. One number for Prosopon.
We map Prosopon against two entities in your group and quantify phase one, duplicate records collapsed, with no integration required to produce the number.
A person replies, not an autoresponder.
Proven in production at a systemic European bank: transmission to regulated subsidiaries with full consent management and audit trail.
- Enquiries
- info@trustnexus.eu
- Partnerships
- Become a provider