PD-SP-IDENTITY-REGISTRY-001 · PD-SP-IDENTITY-OPS-001 · 23 SEPTEMBER 2026
One identity. One ID. One operational chain.
This register is the join layer connecting people, companies, analytical structures, institutions and proceedings with P0 actions, the convergence graph, public dossiers, legal distinctions and the evidence still required to close each identity.
Coverage boundary. The 380 IDs cover the current canonical register: 176 people, 100 organisations, 11 structures, 49 institutions and 44 proceedings. Retrospective backfill across emails, attachments, pleadings and authorised records remains open. A name match does not create identity, merge companies, or transfer knowledge, intention, control, benefit or responsibility.
Verified public freshness gap · 19 September 2026. Anonymous GitLab Pages renders a later 7 September registry with 515 aggregate IDs (256 people, 119 organisations, 12 structures, 68 institutions and 60 proceedings). Those aggregate counts prove a deployment freshness difference only. The identities and exact source bytes comprising the 135-ID delta have not been recovered with GitLab object identity, so this GitHub register remains at its source-controlled 380 IDs. Reconciliation control #1535 →
LIVE OPERATIONAL STATE
Which identities are connected—and what must still be closed.
Operational rule. “No public profile” is a publication gap, not a conclusion about relevance or responsibility. “Identity open” means exact legal name, form, jurisdiction or continuity still requires primary evidence. The static totals on this page must always match the canonical JSON; JavaScript only enhances search and filtering.
WORKBENCH
The four queues that should move the matter.
P0-linked identities
Actors, recipients and proceedings used by the twelve immediate preservation and disclosure actions.
Exact legal entity open
Perimeters, brands or variants requiring registry, deed, contract, invoice, signature or jurisdiction evidence.
No public surface
Admitted identities without a dedicated or aggregate route from the registry or graph.
Distinctions that cannot collapse
People versus companies, similar names, distinct vehicles and unresolved legal-form variants.
SEARCH · FILTER · COPY · EXPORT
Operational registry explorer.
Loading registry, actions and graph…
| Immutable ID | Canonical name / aliases | Class | Operational state | Actions | Graph | Public surface |
|---|---|---|---|---|---|---|
| Loading… | ||||||
PD-SP-ID-ACT-0001–0009
Next registry actions.
Immediate priority. Resolve exact legal entities, provide public coverage for P0 identities, audit
not_same_as, propagate IDs to canonical dossiers and rebuild the owner/party perimeter without merging it into the professional register.EVIDENCE-INTELLIGENCE EXTENSION
IDs for documents, events, assets, rights and recovery.
Person and entity IDs remain authoritative. Extensions connect an identity to the native source, document, event, proposition, asset, right, evaluation, custody record and recovery object without exposing private locators.
RESOLUTION RULES
The ID resolves identity; it does not attribute responsibility.
An ID remains attached to the same identity when display name, office, procedural status or corporate relationship changes.
Initials, variants, errors and source literals point to the canonical record without erasing the source wording.
A natural person, legal entity and analytical structure never share an ID or substitute for each other.
A shared company, representation, document, proceeding or perimeter does not transfer knowledge, intention, control or responsibility.
A brand, group or perimeter is not assigned to an exact legal entity by similarity without sufficient evidence.
A documented response may change name, alias, office, route or grade, but should not create a parallel narrative.
Governance for future threads. Before creating a node, attributing an act or adding a recipient, resolve identity against this registry and check ledgers #988 and #995.
SOURCES AND CONTINUOUS CONTROL