What the Registry Is
The BRSA Registry is the authoritative public record of behavioral and organizational readiness. It is not a database of personal information. It is not a background check system. It is not a credit bureau.
The registry contains one thing: a verified record of presence and standing. Every entry consists of a Registry ID, a readiness state, a status, and a timestamp. That is the entire public record.
Behind that public record is a governed, auditable system of evidence collection, assessment, and scoring operating on the Legacyline platform. That system is internal. The public never sees it. The public only sees the outcome.
What a Registry ID Represents
A BRSA Registry ID is a permanent identifier issued at the moment of registration. It never changes. It is not tied to any personal identifier — not a name, not a Social Security number, not an email address.
A Registry ID represents three things simultaneously: that you entered the system voluntarily, that consent was recorded, and that a governed record of your presence exists. It does not represent a specific readiness level — that is communicated separately through the readiness state field.
How Public Presence Works
Public presence is the principle that your registry record exists and can be verified by anyone who has your Registry ID. You control whether to share your ID.
This design is intentional. Presence in the registry is a tool you control — not a public disclosure you are subjected to.
What Readiness States Mean
Every registry record carries one of three canonical readiness states computed by the FRARI v1.0.0 engine. States reflect evidence — they are never assigned manually.
How Verification Works
Verification is immediate. Enter a Registry ID on the homepage. The system queries the live registry endpoint and returns the public record in real time. No account required. No login. No fee.
The verification endpoint returns exactly four fields — nothing more:
Nothing else is returned. No name. No score. No internal data. The endpoint is public-safe by design and structural constraint — not policy alone.
Privacy & Public Safety Rules
These are structural constraints — not privacy policies. They are enforced at the API level and cannot be overridden by request, relationship, or payment.