Self-Location Registry
The GitHub repository defines and operates the first public registry node for the AI Foundations Self-Location Standard.
Self-Location Registry
The Self-Location Standard defines how a person, project, organization, system, paper, AI agent, dataset, hypothesis, or other entity publishes an accurate, source-supported Self-Location Record.
The Registry repository defines how a record enters a federated index.
The full Self-Location Record does not become the property of the Registry repository.
The registry receives a structured summary, checks the source and stated authority, records the submission decision, and creates a searchable entry that points back to the canonical record.
Full Self-Location Record → canonical source
AI Foundations | Self-Location Standard
The Registry repository does not replace or rewrite that standard. It implements the operational layer required to receive, validate, register, and index records created under it.
The Registry repository is:
- an intake point for public Index Manifests,
- an authority and source validation protocol,
- a record of registry decisions,
- a public index of accepted entries,
- an initial registry node,
- and a reference implementation for future federated registry nodes.
The Registry repository is not:
- the canonical home of every full Self-Location Record,
- the owner or author of submitted records,
- a universal authority over people or entities,
- proof that every claim in a submitted record is true,
- an endorsement of every indexed entity,
- a merger of the records it resolves,
- or the only registry node that may exist.
Submission Protocol
Create record → publish canonical record → complete Index Manifest → submit manifest → validate source and authority → record decision → register accepted manifest → create index entry
Create the Full Record
Create a Self-Location Record using the Self-Location Standard.
Publish the Canonical Record
The full record must be available at a stable canonical location controlled by the appropriate person, entity, organization, or responsible authority.
Complete the Index Manifest
The Index Manifest is the compact submission summary used by the registry.
Submit the Manifest
Submit through the repository's Index Manifest Submission issue form.
Registry Validation
The registry checks schema completeness, canonical source availability, source consistency, stated authority, public indexing permission, version consistency, visibility consistency, retrieval key relevance, relationship evidence, and whether the entry would merge, reassign, or misrepresent another record.
Registry Decision
The Registry repository records one decision: pending, needs-revision, accepted, rejected, withdrawn, or superseded.
Registration
An accepted manifest is stored under records/<record-id>.yaml.
Index Entry
A searchable entry is added to INDEX.md. The entry points to the canonical record, accepted manifest, and any public relationship pointers. The index entry is a route. It is not the canonical record itself.
Core Registry Boundary
The GitHub repository is a public registry node.
The GitHub repository accepts only information that the submitter is authorized to make public. A public manifest may point to a restricted canonical record, but restricted fields must not be copied into the GitHub repository. Fully private records require a permissioned registry node and are not submitted through the public Registry repository.