Organization

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Dimension & namespace

• REFERENCE `world.organizationalUnit` (O2): internal structure is modelled there and resolves back to this organization identity.
• REFERENCE `world.charter` (O4): constitutive rules behind the purpose statements and powers.
• REFERENCE `world.employment` (O3): person-to-organization relations resolve against identities kept here.
• REFERENCE `world.publicRegister` (A12): registry entries anchor to publicly kept registers.
• REFERENCE `world.stewardship` (S1) and `world.accessGrant` (S2): ownership records and access grants over organization data.
• MIX-IN `world.auditTrail` (S4): audit facets on all lifecycle events.
• imports: w3c-org (ALIGN): organizational ontology vocabulary for organization, site and classification.
• imports: iso-17442-lei (REFERENCE): the global legal entity identifier scheme.
• imports: nace (REFERENCE): activity classification code list.
• imports: iso-20275-elf (REFERENCE): entity legal form code list.

Canon, patches & standards

• REFERENCE `world.organizationalUnit` (O2): internal structure is modelled there and resolves back to this organization identity.
• REFERENCE `world.charter` (O4): constitutive rules behind the purpose statements and powers.
• REFERENCE `world.employment` (O3): person-to-organization relations resolve against identities kept here.
• REFERENCE `world.publicRegister` (A12): registry entries anchor to publicly kept registers.
• REFERENCE `world.stewardship` (S1) and `world.accessGrant` (S2): ownership records and access grants over organization data.
• MIX-IN `world.auditTrail` (S4): audit facets on all lifecycle events.
• imports: w3c-org (ALIGN): organizational ontology vocabulary for organization, site and classification.
• imports: iso-17442-lei (REFERENCE): the global legal entity identifier scheme.
• imports: nace (REFERENCE): activity classification code list.
• imports: iso-20275-elf (REFERENCE): entity legal form code list.

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

• `registryExtract`: on-demand disclosure of core registered facts to a requester admitted by the owner or the register.
• `identifierResolution`: resolving an identifier to the canonical organization record with a minimal profile in return.
• `directorySyndication`: a licensed bulk feed of public profile fields for directories and analytics.

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The organization itself, acting through its officers, is the steward of its own record; registers hold their entries as registrar-stewarded copies. All access is granted by the owner under the S1/S2 models of this catalogue.

Objects

• `organization`: the subject itself; key attributes: canonical id, founding date, home jurisdiction, current status.
• `organizationName`: a legal, trading or former name; key attributes: name string, kind, language, validity period.
• `organizationIdentifier`: an identifier issued under a scheme; key attributes: scheme (LEI, national registry), value, issue date.
• `legalForm`: a code drawn from a legal form scheme (ISO 20275 ELF or a national list); key attributes: scheme, code, jurisdiction.
• `registryEntry`: the organization's record in a public or private register; key attributes: register, entry number, entry date, extract reference.
• `activityClassification`: an activity code assignment (NACE or a comparable scheme); key attributes: scheme, code, primary flag.
• `purposeStatement`: a declared mission or object clause; key attributes: text, source (charter or self-declared), declaration date.
• `presencePoint`: a site, address or channel; key attributes: kind (registered office, branch, web), locator, validity period.

Relationships

• `organization` -> knownAs -> `organizationName` (1:n): all names the organization has carried, with validity.
• `organization` -> identifiedBy -> `organizationIdentifier` (1:n): scheme-issued identifiers resolving to this subject.
• `organization` -> hasLegalForm -> `legalForm` (n:1): the legal form under its home jurisdiction.
• `organization` -> recordedIn -> `registryEntry` (1:n): entries in the registers that know this organization.
• `organization` -> classifiedAs -> `activityClassification` (1:n): declared or registered lines of activity.
• `organization` -> successorOf -> `organization` (n:m): lineage through mergers, splits and conversions.

Events

• `organizationFounded`: the organization came into existence as a subject.
• `organizationRegistered`: a register accepted an entry for the organization.
• `nameChanged`: a legal or trading name was adopted or retired.
• `legalFormChanged`: the organization converted to a different legal form.
• `statusChanged`: registered standing moved, for example active to suspended.
• `organizationsMerged`: two or more organizations combined into a successor.
• `organizationDissolved`: the organization ceased to exist as a subject.

Projections

• `publicDirectoryCard`: name, legal form, status, primary activity and public presence; omits identifier history and internal declarations.
• `complianceProfile`: identifiers, registry entries and standing for onboarding checks; omits purpose narrative and presence detail.
• `lineageView`: the succession chain of predecessors and successors; omits all profile content.