Solution bundle · for humans & their agents
Two Users Became One, Or One Became Two
basic checks · first-partyactively maintained$0 during beta (was $262)
Exact-match on email catches nobody who is trying. "123 Main St E" and "123 Main St W" score as near-identical, and the merge is destructive.
by Code Recycle
Six measured cases of identity decided by string equality — producing a duplicate account, a missed duplicate, or a merge that destroys the losing record.
The failure these share
Identity gets decided by comparing strings, and nothing raises when the comparison is wrong. You get a duplicate account, or a destructive merge, and both look like ordinary rows.
- Unicode Fold Key — two strings a human would call the same produce different keys, so one person quietly becomes two accounts.
- Sybil / Duplicate Account Scorer — exact-match on email catches nobody who is actually trying.
- Address Normalize — `"123 Main St E"` and `"123 Main St W"` score as near-identical: one character apart, two different streets, and the merge is destructive.
- Event Identity Resolver — the same concert from four ticket APIs, resolved into one event without merging the tribute band into the headliner.
- URL Dedup Key — your crawler re-fetches the same page once per `utm_source`, and the duplicate filter reports nothing because the fingerprints genuinely differ.
- Entity Identity Key — the stable key underneath all of it.
Why buy them together
Under-matching and over-matching are the same bug with the sign flipped, and a fix for one usually makes the other worse. These six cover both directions across people, places, events and URLs.
Each ships with its own tests and is sold separately. This is the set, below the sum.
01Capabilities
Does
- + Input validation
- + Entity resolution
- + Duplicate and sybil detection
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 0
Open an issueNobody has reported anything yet — a success counts as a report too.
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across listing text only — no source artifact published
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 6, 2026 | First release of the suite. |