C.32.P2S:4.2 - Architecture Unfolding Structure Use

Use ArchitectureUnfoldingStructureUse@Project when a named constraint-governed unfolding structure is being used as architecture-relevant structure inside problem-to-structure architecturing. This dependent architecture-use relation record is defined here; use it with the relevant C.30 or C.32 pattern. Record any architecture decision, description, ADR projection, or realization Work through its direct pattern when that claim is current.

ArchitectureUnfoldingStructureUse@Project:
  kind: dependent architecture-use relation record under C.32.P2S, C.30, and adjacent architecture patterns
  projectWorkOccurrenceRef: U.EntityRef constrained to the exact composite U.Work that is an explicit participant in this use relation
  architectureQuestionCardRef?: U.EpistemeRef resolving to one exact C.30 ArchitectureQuestionCard@Project
  architectureBearingHolonRef: U.EntityRef resolving to the exact described holon
  architectureRelationRefs[]?: exact obtaining C.30 ArchitectureRelation refs
  architectureClaimRefs[]?: exact C.30 ArchitectureClaimRefs for affirmative, negative, unresolved, candidate, required, desired, or expected content
  unfoldingStructureRef:
  architectureStructureUseKind:
    transformationFlow |
    methodWork |
    control |
    narrativePublication |
    evidenceAssurance |
    referenceCurrentnessRefresh |
    otherDeclared
  architectureViewpointRef?:
  affectedSelectedStructures[]:
  architectureCharacteristicRefs[]:
  acceptedLosses[]:
  methodOrWorkLinkageRefs[]?:
  architectureDecisionRef?:
  architectureDescriptionRefs[]?:
  architectureUseReturnCondition:
  repairOrSupersessionCondition:

For ArchitectureUnfoldingStructureUse@Project, the suffix remains a compatibility and retrieval cue until an exact use is asserted. Every asserted occurrence includes projectWorkOccurrenceRef as the exact composite U.Work participant; without that Work, keep only the retrieval cue and do not assert the use relation. architectureQuestionCardRef may cite the exact C.30 triage episteme, while architectureBearingHolonRef names its independently identified subject. architectureRelationRefs[] contain only independently obtaining C.30 occurrences; modal architecture content stays in architectureClaimRefs[]. unfoldingStructureRef names the admitted CGUS or local block being used. affectedSelectedStructures[], architectureCharacteristicRefs[], and acceptedLosses[] state why the unfolding structure matters for architecture rather than for a generic route. Method and work refs point to the A.15 family only as realization or feedback linkage. For decisions, descriptions, ADR-like projections, measurements, evals, evidence, gates, publication, and performed work, use the exact subject predicates and treat their patterns only as locators.

Stop conditions:

• stop at C.22.2 when the signal is not yet a reviewable problem-side record;
• stop at C.30 or C.30.ASV when the current need is only architecture claim or structural-view adequacy;
• stop at C.32 when the next useful artifact is a candidate palette rather than a whole P2S carry-through record;
• stop at C.32.PAD when the project architecture decision is current;
• stop at A.3.1 for Method identity or A.3.2 for MethodDescription membership, or at the A.15 family when the current question is method-work alignment, work planning, readiness, or performed work;
• stop at C.16, C.25, C.29, C.32.ACE, E.23, or G.11 when the current claim is measurement, quality-bundle, mathematical-lens, eval, improvement, or G.11 currentness refresh;
• reconsider P2S only when a later subject assertion establishes architecture pressure that changes candidate structures, expected structures, actual structures, selected structures, or the stronger-structure inspection condition.