EM-ORG-02 · Subject model · W1
Legal Identity and Registration
The legal subject, registry records, branches and legal succession. A registry record has its own identity and a verifiable basis.
Partially published; research continues
Claude: complete-frozen-study-and-single-audit-remediated; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- LegalEntity
- Registration
- Branch
- LegalStanding
- SuccessionRelation
Deep research questions
- Which attributes distinguish an independent entity from a branch?
- How are LEI, tax and registration numbers linked without false identity?
- Which changes continue an identity, and which create a legal successor?
Verifiable invariants
- A number is unique within its scheme and jurisdiction
- Registration status does not substitute for the subject's status
- Succession does not overwrite the parties of old contracts
End-to-end acceptance scenario
One subject with three registrations, a branch without separate legal personality, and a merger must give correct answers as of a historical date.
Negative case
A new extract from a different registry creates a second company.
Approaches to compare
- W3C ORG: collectives, roles, membership and posts
- GLEIF: registered identity and consolidation relationships
- Comparison of corporate governance, the actual org structure and the HR/ERP representation
Candidates in the live catalogue
- WM-ORG-001 · Organization · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ORG-010 · Legal Entity Registration · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ORG-011 · Business Establishment / Branch · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.