Aspect Scoped Identity Projection¶
Represent one underlying entity under a defined aspect or role as a linked derived bearer, so properties, rights, obligations, identifiers, and lifecycle rules attach only where they belong.
Summary¶
Aspect-Scoped Identity Projection creates a governed identity for an entity-under-aspect: a person-as-student, work-as-expression, organization-as-licensee, object-as-cataloged-item, or account-as-admin-principal. It should be used when the aspect carries local properties, rights, obligations, identifiers, or lifecycle conditions that must not collapse into the whole entity.
When This Archetype Applies¶
Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.
Diagnostic problem
A system needs to attach properties, responsibilities, statuses, identifiers, or histories to one role/aspect of an entity, but the available model either collapses everything into the whole entity or splits the aspect so completely that its connection to the underlying bearer is lost.
Applicability expression2 distinct conditions
groundedpartly groundedopen
2 conditions, all required.
2Required in every casenumbered 1–2
These hold no matter which pattern applies.
Multiple scoped identities · grounded
The same underlying entity participates in multiple roles, capacities, phases, accounts, records, or expressions that have different properties or obligations.
A system needs to attach properties, responsibilities, statuses, identifiers, or histories to one role/aspect of an entity, but the available model either collapses everything into the whole entity or splits the aspect so completely that its connection to the underlying bearer is lost. The narrower requirement in this condition set is: The same underlying entity participates in multiple roles, capacities, phases, accounts, records, or expressions that have different properties or obligations.
primeAspectual Individual— Treating a single underlying entity, under a fixed role or aspect, as a distinct derived bearer of properties with its own narrower existence conditions.
Independent aspect lifecycle · grounded
The aspect has its own start, end, succession, suspension, or validity conditions.
This is a load-bearing situation condition in the diagnostic expression. The condition is: The aspect has its own start, end, succession, suspension, or validity conditions. If it does not hold, this particular condition set is incomplete.
primeAspectual Individual— Treating a single underlying entity, under a fixed role or aspect, as a distinct derived bearer of properties with its own narrower existence conditions.
Other requirements and context (3)
Why these sit outside the expression
Goal — a goal states an intended outcome or evaluation criterion, not a pre-existing situation that independently summons the archetype.
GoalClaims made about one aspect should not automatically apply to the whole entity or to other aspects.
A system needs to attach properties, responsibilities, statuses, identifiers, or histories to one role/aspect of an entity, but the available model either collapses everything into the whole entity or splits the aspect so completely that its connection to the underlying bearer is lost. In this archetype, the relevant goal is: Claims made about one aspect should not automatically apply to the whole entity or to other aspects. It supplies a criterion for evaluating what the intervention should accomplish or preserve.
GoalDifferent systems need to refer to the aspect without losing the link to the underlying entity.
A system needs to attach properties, responsibilities, statuses, identifiers, or histories to one role/aspect of an entity, but the available model either collapses everything into the whole entity or splits the aspect so completely that its connection to the underlying bearer is lost. In this archetype, the relevant goal is: Different systems need to refer to the aspect without losing the link to the underlying entity. It supplies a criterion for evaluating what the intervention should accomplish or preserve.
GoalA role-specific record must survive changes in some underlying properties but not others.
A system needs to attach properties, responsibilities, statuses, identifiers, or histories to one role/aspect of an entity, but the available model either collapses everything into the whole entity or splits the aspect so completely that its connection to the underlying bearer is lost. In this archetype, the relevant goal is: A role-specific record must survive changes in some underlying properties but not others. It supplies a criterion for evaluating what the intervention should accomplish or preserve.
Coverage
2 of 2 conditions grounded.
Core move¶
The intervention is not merely labeling or filtering. It creates a linked derived bearer with an explicit selector, scope boundary, persistence criteria, property inheritance map, lifecycle state, and reference rule. The underlying entity remains visible, but facts do not spill automatically across every aspect.
Pre-draft disposition result¶
The disposition check supported a full draft. Existing accepted archetypes own neighboring pieces—classification, context anchoring, source-of-truth records, identifier binding, role formation, and access-control mechanisms—but none owns the full aspectual-individuation pattern. Queue-local outputs such as Identity-Bounded Change and Durable Identifier Binding remain important neighbors: they govern diachronic continuity and handles, while this archetype governs the projected bearer that exists under an aspect.
Use with caution¶
For human subjects, this pattern can improve purpose limitation and contextual accuracy, but it can also create hidden profiling infrastructure. Sensitive uses require visible scope, clear authority, contestability, minimization, and fairness review.
Common Mechanisms¶
9 catalogued mechanisms: 8 documented across 4 implementation forms; 1 awaits an authored page and reviewed form classification.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Record, Log & Register · 2 mechanisms
- Aspect Lifecycle Register — Tracks each aspect's state through time — proposed, active, suspended, superseded, retired — with the persistence rules that decide every transition and the evidence that triggered it.
- Legal Capacity or Status Record — Establishes a person or organization acting in a specific legal capacity as a formal, authority-backed record naming the capacity and the evidence that created it.
Representation, Specification & Plan · 2 mechanisms
- Role-Scoped Record Type — Defines a distinct stored record type for an entity under a role, with its own key and its own rules for reconciling clashes with the underlying entity.
- Work / Expression / Manifestation / Item Model — Splits a creative artifact into a four-level ladder — work, expression, manifestation, item — so each abstraction level bears only the properties that belong to it.
Rule, Policy & Commitment · 2 mechanisms
- Role-Based Access Profile — Grants an account the permissions of a named role, scoped and purpose-limited so what one capacity may do never leaks into another.
- Scoped Namespace Suffix — Makes an aspect independently addressable by attaching a scope qualifier to the underlying entity's name, keeping the link to the base visible inside the identifier itself.
Structure, Architecture & Configuration · 2 mechanisms
- Database View or Entity Projection — Exposes an entity under one aspect as a derived record assembled at read time from the underlying source, showing only the columns and rows that aspect is entitled to.
- Typed Identity-Relation Edge — Represents the bond between an underlying entity and one of its aspects as a single typed, first-class edge that can carry its own precedence and conflict rules.
Not Yet Form-Classified · 1 mechanism
- Context-Sensitive Classification — Redesigns categories so membership, risk, ability, need, or treatment depends on specified conditions rather than on presumed inherent essence.
Compression statement¶
When a single entity must be reasoned about differently under different roles, capacities, expressions, phases, or contexts, project an aspect-scoped identity: a derived record linked to the underlying bearer, governed by its own scope boundary, persistence criteria, inherited-property map, identifier rule, lifecycle state, and remerge/supersession policy.
Canonical formula: underlying_entity + aspect_selector + persistence_criteria -> aspectual_individual linked_to underlying_entity
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (8)
- Abstract Work: A content identity that persists across its concrete carriers, with an explicit criterion for which instance-variations preserve the work and which fork a new one.
- Aspectual Individual: Treating a single underlying entity, under a fixed role or aspect, as a distinct derived bearer of properties with its own narrower existence conditions.
- Boundary: Defines system limits.
- Context: Surrounding state that selects which content a fixed focal signal carries.
- Criteria of Individuation: The rules a system fixes for what makes something one entity — when parts compose a single whole, when two presentations are the same entity, and which kind supplies a thing's persistence — together constituting its inventory of countable individuals.
- Identity-Providing Kind: A category whose membership fixes what it takes for an instance to remain the same instance over time, supplying persistence criteria rather than a temporary description.
- Persistent Identifier: A designed token committed to keep resolving to its entity across changes in the entity's location, representation, custodian, or version, via a separately maintained resolver.
- Role: A bundle of expected behaviours attached to a social position.
Also references 19 related abstractions
- Access Control: Restrict system access.
- Accountability: Responsibility for actions.
- Authority: The recognized, legitimate right to issue binding decisions within a defined scope, distinct from raw coercive force or mere persuasive influence.
- Category: Describe a system by its arrows and their composition, not by what its objects are.
- Classification: Sorting entities into discrete categories by explicit rules, turning unbounded variation into a finite, reusable map for downstream reasoning and action.
- Data Integrity: Accuracy and consistency preserved.
- Equivalence Relation: Groups elements into equivalence classes.
- Identity Test: The rule that decides, in a given system, when two presentations refer to the same entity.
- Identity-Preserving Modification: An entity undergoes an event that changes some of its properties while an identity-condition licenses calling the after-state a continuation of the same entity rather than its replacement.
- Indirection: Introduces intermediary references.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Role-Scoped Identity Record · governance variant · recognized
Represents the same underlying entity as a distinct role-bearing record with local properties, obligations, and lifecycle state.
- Distinct from parent: The parent covers any aspect; this variant emphasizes formal role and capacity.
- Use when: Role-specific duties, permissions, or facts must not spill over to the whole entity; The role can start, end, suspend, or transfer independently.
- Typical domains: organizations, access control, legal records
- Common mechanisms: role scoped record type, role based access profile, typed identity relation edge
Abstract-Work Expression Projection · domain variant · recognized
Separates an abstract work from expressions, manifestations, copies, or performances as linked aspectual bearers.
- Distinct from parent: The parent is general identity projection; this variant uses work-expression-item style distinctions.
- Use when: Different levels of a cultural or intellectual object have different properties; Cataloging or rights decisions depend on which level is being referenced.
- Typical domains: libraries, archives, musicology, publishing
- Common mechanisms: work expression manifestation item model, typed identity relation edge
Phase-Scoped Identity Projection · temporal variant · candidate
Treats an entity under a phase or status as a derived bearer while preserving underlying continuity.
- Distinct from parent: The parent is not necessarily temporal; this variant is state/phase-driven.
- Use when: Phase-specific facts or obligations matter; A phase has its own entry/exit conditions.
- Typical domains: case management, product lifecycle, clinical episodes
- Common mechanisms: aspect lifecycle register, typed identity relation edge
Near names: Qua-Object Modeling, Capacity-Specific Identity, Context-Bound Persona Record.
Editorial Notes¶
Problem Classification¶
Classification: Representation, Classification & Model Misfit → Ontology, Identity, State & Part–Whole Modeling
Problem kernel: an entity aspect is either collapsed or detached
Rationale: Properties and histories belonging to one role or aspect cannot remain distinct while still being linked to the underlying bearer.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system needs to attach properties, responsibilities, statuses, identifiers, or histories to one role/aspect of an entity, but the available model either collapses everything into the whole entity or splits the aspect so completely that its connection to the underlying bearer is lost. That is a ontology identity state and part whole modeling problem because The representation lacks explicit entities, aspects, states, proposition modes, or unity rules needed to say what exists and what the model is about.
Review outcome: Independent reviewer agreement; high confidence.