Resolution engine + evidence boundary
data/build-011-engine-v1.jsonSignals, source authority, conflict behavior, inherited schema gate and non-claims.
BUILD 011
Entity / Ownership Resolution X-Ray
Similarity is not identity. Resolution requires a valid entity model, source-linked support and conflict evidence, attribute minimization, and an accountable human decision record.
QUESTIONWhen do two records refer to the same thing?
STRUCTURED PUBLIC BUILD ARCHIVE
Research, creation, decisions, audits and plans are publicly structured without claiming that every release gate is complete.
This page exists so the durable record does not depend on conversation history. Research, decisions, generated artifacts, audits, limitations, media metadata, plans and canonical source paths are retained here as part of the build itself. A listed repository path proves that an implementation record was retained; it does not independently support a real-world factual claim.
5 of 5 listed retained paths have a public reader link on this archive page. Unlinked paths remain named for traceability but are not represented as publicly inspectable evidence.
What informed the build
NIST SP 800-63A-4
Grounds contextual resolution, evidence validation and authoritative or credible sources.
NIST identity-resolution implementation resource
Grounds minimum-necessary attributes and additional evidence for conflicts.
What exists because we built it
011-A Entity / Ownership Resolution X-Ray
Compare records, toggle evidence and conflicts, validate the model, record review and export locally.
011-B Same Name Is Not Same Entity
Three interactive resolution states with visible human authority.
Entity Resolution Engine v1
Reusable merge-candidate, human-review and keep-separate assessment.
Why it works this way
Build 010 is concretely inherited
The resolver directly calls assessIdeaSkeleton and blocks the strongest result when the entity model is invalid.
Authoritative conflicts dominate similarity
A hard conflict can keep records separate despite matching names or relationships.
The score never executes a merge
A named human records rationale, aliases, sources and rollback.
Minimization is a gate
Unnecessary identifying attributes prevent the strongest assessment.
How the work was checked
Machine-readable archive
data/build-011-archive-v1.jsonRoutes, lineage, privacy and consumers.
Privacy/support
data/build-011-privacy-support-v1.jsonClient-local state and minimization boundary.
Freshness/performance
data/build-011-freshness-performance-v1.jsonOffline operation and record-freshness rule.
Browser fixtures
tests/build011.spec.tsMerge, conflict, review, reset, export, lifecycle, 320px and B-state coverage.
What this build intentionally leaves forward
Release path
Complete static gates, Chromium/WebKit matrix, media, preview and exact-head certification.
Future consumers
021, 026, 027, 041, 046, 056, 060, 062, 082, 084, 085, 088 and 099 consume cap:011.
Take the social artifact with you
B-LINKEDIN / CANONICAL FILM
720×900 · 4:5 MP4 · 24 fps · silent-first
CURRENT VERIFIED MEDIA / 30-second film · 345.1 KB
FINAL PROPOSITION / SAME NAME IS NOT THE SAME ENTITY.
SHA-256 923834fb6921b91378124d7c436544526f9d881c28c4dc7e8d89afb118d9629aReproducible from data/linkedin-film-specs-v1.json with scripts/render-linkedin-films.py. The website—not a chat attachment—is the canonical media source.
The repository files that preserve the implementation record
apps/web/app/100-builds/011/a/EntityResolutionLab.tsxapps/web/app/100-builds/011/b/IdentityField.tsxpackages/release/src/decision-engines.tsdata/build-011-engine-v1.jsondata/build-011-archive-v1.jsondocs/builds/011/SPEC.mddocs/builds/011/ARCHIVE.mdtests/build011.spec.tsThese paths preserve the implementation record. Only items with an explicit public reader link are publicly inspectable here. A file path, working interface or internal engine is not independent support for a real-world claim; synthetic propositions and design reasoning remain labeled within the retained record.