Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:05:04 UTC

A.22:1 - Problem frame

Use this pattern when a practitioner needs to select U.Structure as the EntityOfConcern: an organization among constituents and obtaining relations, selected to expose a relation class, applied constraint, invariant, variation class, preserved arrangement, or lost arrangement that changes the next engineering or reasoning action.

Recover the organization selected for the named use:

  1. identify every constituent independently through the content that defines its kind and identity;
  2. recover the relation occurrences among those constituents that obtain under their predicates;
  3. state the constraints applied to those constituents and relations, plus the named selection-use frame that says what question or action this organization serves;
  4. name the resulting selected organization and the admissible action or stop that follows.

When the account asserts dated selection Work, establish its independent grounds under §4.1. Those facts explain the performed selection and remain outside U.Structure identity. If the judgment must persist, identify a separate C.2.1 result episteme whose claim content designates the selected structure.

The four values above can be stated in ordinary prose or recovered from an existing description. The following optional aid also keeps use limits and any separately needed claims visible:

StructureQuestionCard@Project:
  named selection use:
  independently identified constituents:
  obtaining relation occurrences selected:
  constraints applied:
  selected structure:
  preserved structure:
  lost, hidden, or excluded structure:
  admissible action:
  stop or non-admissible overread: stop or return condition
  grounded non-admissible overread, optional:
  selecting system, method, and dated work, only when dated Work is asserted:
  selection-result episteme, when a durable result is needed:
  claim scope or effective reference scheme of that claim, if current:
  reliance relation, if a neighboring reliance claim is being made:

StructureQuestionCard@Project is a project-side triage aid for this selected-structure use. It is not a new structure kind. Fill the reliance row only when extraction, coarsening, source-description, base-dependence, grounding, evidence, lens, simulation, representation, or action reliance is being claimed; otherwise leave it unused and keep the move on selected structure.

The @Project suffix is a local retrieval cue. If the account separately asserts a composite project U.Work, identify that Work and how the current selection, decision or description concerns it. The suffix supplies neither identity nor that relation; the same applies to ArchitectureStructureKindTriage@Project.

Stop when the selected organization and next use are clear. Develop a neighboring description, view, publication, extraction, comparison or other claim only when the receiving task needs it.

What goes wrong if A.22 is missed: the practitioner reasons from the visible diagram, source publication, source-use record, lens output, generated representation, project record, or architecture description instead of asking which organization is selected and what loss or reliance boundary matters for action.

What A.22 buys in practice: a practitioner can name selected structure, state preserved and lost structure, name source-basis or lens reliance only when it is being claimed, add a StructureUseReturnCondition when loss matters, and apply the FPF definition or test for any non-structure claim being made.

Not this pattern when the question under repair is grounded architecture adequacy, architecture structural-view adequacy, or mathematical-lens use. Use C.30, C.30.ASV, or C.29 respectively. For any other claim, use the pattern that defines or tests that claim and keep A.22 only to the selected-structure portion.

For unresolved wording: when the wording still may name a structure, a structure description, an architecture description, a view, a publication form, or another claim, use C.30.P or C.30.STRAT first as triggered. Apply A.22 only after the selected-structure claim or structure-view portion is recoverable.