1. ID comes first
If the ID matches exactly, the case moves close to the maximum. If the IDs conflict, the score drops even when the name looks similar.
Labs
This space separates experimental work from the main directory. We will test the zero-cost pipeline here for cross-matching public missing-person reports with public located-person lists.
This page shows possible matches for human review. The percentage is heuristic: an exact ID match carries much more weight than name similarity.
The current formula does not use machine learning. It is a review heuristic: it combines strong and weak signals to suggest human priority.
If the ID matches exactly, the case moves close to the maximum. If the IDs conflict, the score drops even when the name looks similar.
Without an ID, the main weight comes from normalized name similarity: exact, very close, strong, or moderate.
Age and location only adjust the result. An exact or nearby age adds a little; a large difference subtracts. Location adds a small boost and never replaces identity.
How to read the percentages
The percentage does not confirm identity on its own. Review the evidence shown on the card and, when available, verify the ID, age, hospital, and original source.
Loading candidate matches
Initial version
We start without a paid backend: GitHub Actions for source syncs, static JSON files for publishing results, and manual review before confirming any match.
Expected outputs
Public JSON feed with reports of missing people, missing families, rescued people, and related events.
Public read-only API with people located in hospitals and other facilities.
Later this can move to a subdomain like labs.directorioterremotovenezuela.org, but starting with /labs/ is the simplest and cheapest option.