PAT-0310
Orphaned Structure
A structural condition where a node, region, object, state, or declaration exists without linkage to the governing graph or integration pathway.
Primary Lenses
Absence Lens
Detects structurally required elements that are missing from the observed structure.
Lens Application
As a primary lens, the Absence Lens is a strong inspection mechanism for orphaned structure because it focuses attention on missing structural requirements around present nodes, regions, objects, states, or declarations. It helps identify where an element exists but lacks the expected connection into its governing graph or pathway.
Inspect For
- Present elements with no parent, owner, or governing reference
- Nodes or regions excluded from traversal or integration paths
- Declarations without consuming, binding, or resolving structures
- States or objects not reachable from expected graph entry points
Avoid
Treat missing linkage as inspection evidence requiring context, not as a standalone determination that the structure is orphaned.
Secondary Lenses
Propagation Lens
Traces how structural declarations, effects, or state changes propagate across boundaries or stages.
Lens Application
As a secondary lens, the Propagation Lens supports inspection of Orphaned Structure by tracing whether a structural element participates in expected downstream effects, transitions, or boundary crossings. It may reveal elements that remain locally present but do not propagate into governing graphs, consumers, workflows, or later stages.
Inspect For
- Declarations with no downstream consumers
- State changes that stop at a boundary
- Objects absent from expected integration paths
- Regions skipped by propagation rules
Avoid
Treat propagation gaps as supporting inspection signals, not as confirmation that the structure is orphaned.
Primary Issue Matches
Supporting Issue Matches
Merge Step Leaves Unresolved Differences
A merge, reconciliation, or consolidation step combines outputs or reviews but leaves important differences unresolved.
Relationship Map Has Missing Links
A map of related Issues, rules, patterns, cases, fields, tools, or workflow steps is missing links needed to navigate or reason over the structure.
Review Queue Becomes Bottleneck
A review queue, approval path, or validation stage accumulates too much work and begins blocking the workflow.
Task Progress Is Lost Midway
The AI loses track of completed work, prior decisions, current position, or remaining steps before the task is finished.
Workflow Stage Has Too Few Checks
A workflow stage lacks enough checks, gates, criteria, or review conditions to safely support the work it controls.
Workflow Step Has No Decision Owner
A workflow step requires a decision, approval, judgment, or routing choice, but no owner is declared for making it.
Workflow Step Lacks Required Conditions
A workflow step can run, route, approve, reject, or continue without the required conditions being declared or checked.
Workflow Waits on Step That Waits Back
A workflow step waits for another step that also waits on the first step, creating a blocking loop.