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:00:10 UTC

C.32 - Architecture Candidate Synthesis

Type: Architectural pattern Status: Stable Normativity: Normative unless marked informative

C.32:1 - Problem frame

Use this pattern when a practitioner has a C.30-grounded architecture question for one described holon and needs to synthesize several candidate architecture configurations across selected structures before comparison, archive or front-policy work, selected-set result declaration, publication, or decision. Keep any obtaining C.30 ArchitectureRelation occurrences, the selected U.Structure values they relate to the holon, and any candidate, required, desired, or expected structures named only in an ArchitectureClaim distinct throughout the synthesis.

Primary working reader: an architect or architecture-responsible practitioner preparing alternatives for one described holon before comparison, selection, selected-set result declaration, publication, local choice, or project decision.

Typical entry phrases:

"The functional structure is clear, but module allocation and placement change the trade-off."
"One platform proposal improves reuse and worsens evidence or control burden."
"A search or workshop produced options; which selected structures and architecture characteristics do they change?"
"We need a candidate palette with structurally different architecture configurations before choosing one."
"The architecture of the team or tool that changes the target holon no longer fits the target architecture."

First-minute use slice. A regulated product-family team has a C.30-grounded architecture question for one field-device-family holon. The question names its current obtaining ArchitectureRelation occurrences and their selected structures separately from candidate or expected structures stated only in the current ArchitectureClaim.

The work question is synthesis: how should required functions, constructive modules, field placement, control responsibility, and certification evidence be coordinated so maintainability, substitutability, latency, and evidence reuse stay acceptable?

Follow one field replacement through removal, fitting and acceptance. Keeping a common module can save the field team a replacement procedure if the common qualification covers the installed interfaces. Splitting the family can simplify each interface while requiring two sets of spares and evidence. Keeping the existing split and securing qualified local approval can suffice for an exceptional site. These are different configurations because they change what must fit, who can accept the replacement or what the field team must stock.

The team can describe these candidates before any field unit has been changed. To decide which to carry forward, establish which sites each can serve and compare the work left to the field team.

The primary EntityOfConcern is the candidate architecture palette for one C.30-grounded synthesis question. Its inputs are the described holon, any obtaining ArchitectureRelation occurrences and their selected U.Structure participants, and any candidate, required, desired, or expected structures stated only in an ArchitectureClaim.

The described holon may be a system, product family, organization-as-system, discipline, AI-agent setup, built asset, episteme, Work occurrence, or another admitted holon kind. Do not admit a source label as a holon.

For example, practice, culture, tradition, style, Method, or role may refer to a Method, Method relation structure, relation among local system-role kinds, classification, assignment, Work structure, episteme, source-local meaning, or C.36 cultural-evolution relation. Recover the object and claim through its subject pattern; route unresolved claim-bearing role wording through E.10.ROLE.

ClaimScope and a bounded model-use structure qualify the named use; neither becomes the holon. Architecture pressure may concern Method-family structures, relations among local kinds, classifications, or assignments. Keep each as a selected structure or separate input for the named architecture use, not as a holon kind or function bearer by label. C.32 is not software-system architecture by default; software-system sources are one source family and one domain example.

What goes wrong if C.32 is missed: the team optimizes one visible structure, such as modules, placement, team responsibility, control relation, or evidence package, and then treats that local improvement as architecture synthesis. The competing structures, architecture characteristics, losses, and alternatives disappear before they can be compared.

What C.32 buys in practice: a practitioner can build a small set of candidate architecture configurations, each grounded in selected structure changes, architecture characteristics, known losses, and patterns for the next questions.

Ordinary working move: name the selected structures and architecture characteristics that make the question consequential, then construct the structurally different configurations needed by the comparison, with expected gains, relevant preservation or loss, and next receiving use. A supported account that already settles the question can finish without constructing another option.

A completed comparative palette makes at least two structurally different configurations recoverable, with their selected-structure changes, relevant characteristics, expected gains, known losses and next use. A single configuration can be the starting point for that construction; it is not yet the comparative palette. Preserve a source-return condition when omitted detail can change the receiving use.

Use C.32 only for candidate palette construction. Do not use it to ground the architecture claim, recover one structure, build characteristic criteria rows, design eval programs, handle architecture-influence correspondence, run archive or front-policy work, declare a selected-set result, publish it to an audience, choose locally, or decide the project architecture.

Use C.32.MWA instead when several structures of Methods, Work, subjects and their descriptions, capabilities and providers, and cultural change do not line up one-for-one and the needed result is one usable practice architecture. Keep C.32 for a palette of candidate configurations for one grounded architecture question.

For control alternatives whose observations, decisions and interventions must work together under information, time, resource and authority constraints, use C.32.LCA to construct and compare that connection. Bring its explained alternatives into the wider palette when other selected structures also change. C.30.LCA addresses the separate question of which control relations a description represents and what use that description or view supports.

Common exits by claim kind:

  • C.30 grounds the described holon, any obtaining ArchitectureRelation, its selected U.Structure, and any separate ArchitectureClaim; C.30.ASV, A.6.F, and A.6.M recover structural views, function wording, and module-interface relations.
  • C.32.HCS, C.32.ACS, C.32.ACE, C.25, C.31, C.31.ASAP, and C.16 govern starter heads, project criteria rows, eval programs, Q-Bundles, modularity or scale-preference claims, and measurement.
  • C.32.MLAO, C.32.CONWAY, C.32.FAIL, and C.29 govern residual-reducing frames, architecture-influence and transformed-architecture correspondence, candidate repair, and mathematical-lens use.
  • Use A.19.CPM for comparison, A.19.SelectorMechanism for set-returning selection, C.18 and C.19 for archive, front, and current-pool treatment, G.5 for selected-set result declaration, C.11 for local choice, and C.32.PAD for a project architecture decision. For audience availability, use E.24.PUB for the publication occurrence, form, carrier and bounded use, with E.17 when a source-backed face and return are needed.
  • C.30.AD, E.17, E.24.PUB, A.10, and B.3 govern architecture-description, publication-face, publication-occurrence, evidence, and assurance claims, respectively.

The first useful output is the small candidate palette. An adequate ordinary account can carry it; CandidateArchitecturePalette@Project is an optional working record. Its name introduces no new U.* kind, and the record does not establish selection, publication, evidence, assurance or decision authority.

For a first pass, identify:

  • the described holon, synthesis question and intended palette use;
  • relevant actual and proposed structures and what they contribute;
  • the architecture characteristics under pressure;
  • the configurations; and
  • the sufficient stop.

Add ClaimScope or a bounded model-use structure only when it changes synthesis; add optional references only when they change the next use:

CandidateArchitecturePalette@Project:
  projectWorkOccurrenceRef?: U.EntityRef constrained to U.Work
  architectureSynthesisProjectUseRelationRef?: U.RelationRef resolving to the synthesis-use or work-use relation
  architectureQuestionCardRef?: C.30 ArchitectureQuestionCard@Project ref when that card is the intake
  describedHolonRef:
  architectureClaimRef?: C.30 ArchitectureClaimRef when a durable actual, candidate, required, desired, or expected claim is current
  currentArchitectureRelationRefs[]?: obtaining C.30 ArchitectureRelation refs only
  currentSelectedStructureRefs[]?: the U.Structure participants of those obtaining relations
  synthesisQuestion:
  intendedPaletteUse:
  claimScopeRef?: U.ClaimScope
  boundedModelUseStructureRef?: A.1.1 BoundedModelUseStructure, only when its organization changes synthesis
  architectureSynthesisFrameRef?:
  selectedStructureContributionRows:
    - structureKindRef:
      selectedStructureRef?:
      contributionToSynthesis:
      constraintOrAffordance:
      relationFunctionClaimRef?:
      sourceReturnCondition?:
  architectureCharacteristicCriteriaSetRef?:
  architectureCharacteristicCriteriaRowRefs?:
  qBundleRefs?:
  characteristicImprovementCycleRef?:
  architectureIdealityPressureRef?:
  scaleAmenabilityPolicyRef?:
  functionBearerFeasibilityRef?:
  candidateArchitectureConfigurations:
    - candidateId:
      candidateName:
      selectedStructureChanges:
        - structureKindRef:
          selectedStructureRef?:
          changeMade:
          relationFunctionClaimRef?:
      affectedArchitectureCharacteristicRefs:
      affectedCriteriaRowRefs?:
      architectureCharacteristicEvalResultRefs?:
      qBundleRefs?:
      expectedArchitectureGain:
      knownArchitectureLoss:
      constraintFit:
      preservedStructure:
      lostOrHiddenStructure:
      sourceCueRefs?:
      sourceSideReferent?:
      sourceReturnCondition?:
      nextUse:
  tradeoffFrontOrArchiveRef?:
  evolutionWindowRef?:
  architectureInfluenceCorrespondenceRef?: C.32.CONWAY frame or pair-row ref
  paletteStopCondition:

Across C.32, @Project is a compatibility and retrieval cue, not a project kind or relation assertion. CandidateArchitecturePalette@Project, ArchitectureSynthesisFrame@Project, and ArchitectureCharacteristicImprovementLoop@Project establish no composite project work, context, authority, viewpoint, or parthood by name.

When one of these records is local to one project, identify the composite U.Work and the direct relation by which synthesis framing, palette construction, or improvement feedback concerns that work. Otherwise no project-work relation is implied.

A cited ArchitectureQuestionCard@Project transfers neither project locality nor architecture truth: each affirmative currentArchitectureRelationRef must already resolve to one obtaining C.30 occurrence, while candidate, required, desired, or expected structure remains claim content until the C.30 predicate is independently satisfied.

C.32:2 - Problem

Architecture synthesis is the constructive middle of architecture work. A practitioner may already know the described holon, architecture question and intended use, some obtaining architecture relations and selected structures, and some concerns, but still need to configure those structures together into alternatives for later comparison or decision.

The typical synthesis problem is multi-structure. State each required function or functioning claim through the predicate and bearer recovered with A.6.F. Candidate module, placement, control, transformation-flow, information, evidence, Method, Work, local-kind, classification, or assignment structures may constrain or help explain a candidate, but a kind or assignment establishes no functioning, participation, capability, function bearing, or Work.

A control relation can improve supervision while increasing timing or responsibility burden; an information structure can improve maintenance access when exposed through a digital-twin view while still hiding source-return loss; a team structure can improve flow while failing to match module or deployment structure.

Every positive responsibility claim still needs its direct domain predicate, actual participants, applicability, and occurrence identity, or the A.6.RCD missing governor.

A functional description contributes only part of the synthesis. Recover the function or functioning claim and possible bearer, using A.6.F when that meaning remains unresolved. Module, Method, resource, placement, control, Work, evidence and assignment conditions can constrain its feasibility.

If no bearer can satisfy the function under the applicable constraints, mark the candidate infeasible: repair or reject it before treating it as a feasible option for choice. It can remain an explicit countercase for comparison or diagnosis. Missing feasibility evidence instead leaves the claim unresolved. Neighboring structures constrain the candidate; their labels do not establish function bearing.

The typical synthesis problem is also multi-characteristic. Architecture characteristics such as cohesion, coupling, substitutability, evidence reuse, work repeatability, latency, locality, control separation, source-return cost, and composite quality families often compete. Functional demands describe what the holon is to do; architecture characteristics describe whether the selected structures make those demands maintainable, controllable, evolvable, replaceable, inspectable, and otherwise acceptable in the current context.

One recurring candidate-generation heuristic is idealization: ask whether an existing bearer or resource can carry an additional required function under the selected-structure constraints, whether a support bearer can disappear, or whether a more general scale-amenable bearer can replace several special bearers. Admit that heuristic only as a candidate. The candidate must name the functions transferred to a bearer, the bearer removed or generalized, the architecture characteristics improved and worsened, and any BLP scale window or waiver when scale advantage is claimed.

Use C.32 to make the constructive translation explicit. Build a small palette whose candidates answer: which selected structures are configured together, which architecture characteristics improve or worsen, which constraints remain admissible, what source detail must remain recoverable, and which pattern supplies the next claim or test.

C.32:3 - Forces

ForceTension
Decision pressureTeams want one answer before the alternatives are explicit.
Candidate pluralitySeveral plausible variants may be useful for different reasons.
Source richnessSource cues can suggest candidate work without establishing the architecture claim.
Compression riskA short palette can hide source distinctions needed later.
Neighboring claim patternsCandidate construction supplies content for front use, selected-set declaration, publication, choice, evidence, assurance or decision; each receiving claim needs its own grounds when made.

C.32:4 - Solution

Use an adequate existing candidate account directly. To start from one current or proposed configuration, trace a required result or constraint through the selected structures: which bearer and relation supply it, and where does the arrangement fail, impose a material burden or leave feasibility unknown? Use the applicable change in the table below to construct a variant, then follow its changed inputs and connections through to the receiving result. C.32.MWA.PP supplies this tracing and construction for performance and provision; C.32.LCA supplies it for control, and C.32.CONWAY:4.1.1 for a constraining production or organization arrangement. Keep the incumbent when it is adequate, including as a comparison candidate.

Construct each alternative far enough to explain how it could deliver the same required result. Identify what changes hands, who or what performs the changed operation, and which other work depends on its output. Two drawings of the same connections can support different inquiries while describing one arrangement. A different assignment, interface or order of work counts as an architectural alternative when it changes an operative connection. When assessing an architect’s work, identify which connections the brief already specified and which ones the architect constructed and justified. Selecting from supplied designs can answer a selection assignment.

The palette retains the configurations needed by the receiving question. ArchitectureSynthesisFrame@Project can expose their connections and CandidateArchitecturePalette@Project can retain the result. Selection, publication and decision remain separately governed uses.

Work in seven steps:

  1. Anchor the palette to one described holon or holon family, synthesis question, and intended next use. Name any current C.30 architecture relations and selected structures that can change that question.

  2. Explain the contributions of the smallest useful set of selected structures. Start with the recoverable functional demand and candidate bearer, using A.6.F for unresolved function meaning, and constructive module/manufacture or placement/deployment structures when they shape the question. Add control, flow, Method, Work, local-kind or classification, assignment, information, evidence or scale structures only when they change it. Send unresolved claim-bearing role wording through E.10.ROLE.

    For each candidate treated as feasible, name a bearer able to satisfy each required function under the declared constraints; retain unknown or failed feasibility explicitly for diagnosis or repair.

  3. State the characteristics and any Q-Bundle slots that define the trade-off, reusing existing criteria rows when available. Use C.32.ACS when a criteria-row construction is needed. Keep functional demand, characteristic, criterion, evaluation result and decision distinct.

  4. Generate candidate architecture configurations. A candidate claim may propose, for example, changed decomposition, allocation, A.6.F function bearing, bearer count, placement, interface grammar, a control or transformation-flow relation, Method use, future assignment conditions, an independently established responsibility relation, evidence scope, information structure, or a bounded exception.

    Modal candidate wording creates no assignment occurrence and proves no Work occurred. Use a WorkPlan, policy, commitment, permission, decision, or other truthful prospective object when one applies. For actual precise Work, recover each actual performer System through A.13 and let A.15.1 independently admit the dated Work and enacted Method; add an assignment occurrence, its declared species, and F.6 only when the candidate account or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment.

    F.6 identifies neither assignment nor performer, missing or failed F.6 attribution alone leaves the Work intact while its independent A.13/A.15.1 grounds still hold, and an assignment never carries responsibility by itself.

  5. For each candidate, state its selected-structure changes, expected gains, known losses, constraint fit and preserved or hidden structure. Identify material unknowns rather than inventing a gain or loss. Add a source-return condition when omitted distinctions affect the next use.

    Identify the event the recipient needs. The work can finish, be accepted and become available to its user at different times. Follow each alternative to that event. A later distribution batch can deliver two accepted versions at the same time. Keep the operating conditions common to the alternatives, including shared resources and any binding acceptance criterion. A gain on one operation can trade against a loss on another. Compare the candidates under each operating condition that the evidence still allows. When the same choice holds throughout, carry it forward with that range of use. If the choice reverses, locate the condition that distinguishes the alternatives. A preference among the candidates examined extends to all eligible configurations only when the comparison covers them or an applicable bound rules the others out.

  6. When a front, archive, search result, or pool-treatment policy is being used, cite C.18, C.19, or NQD and OEE support as generation or retention support only. Keep the C.32 candidate content separate from archive work, front membership, pool treatment, selected-set result declaration, publication, and local choice.

  7. Stop when the palette supplies the candidate content needed by the receiving question, such as comparison, archive use, selected-set declaration, publication, choice or repair. That content need not perform the receiving operation in advance.

Together these contributions explain how the proposed relations make a configuration possible and what they constrain. Ordinary prose or rows can carry that account. Cite a defining rule through relationFunctionClaimRef only when the interpretation or receiving use depends on its identity; a pattern citation normally suffices to locate the rule. Name an evolution window when the expected use or comparison assumptions depend on that range of change.

Architecture-characteristic improvement loop. A completed palette can finish the current question. Reopen synthesis when changed characteristic pressure or feedback warrants another configuration. The practitioner uses characteristic pressure or criteria from C.32.ACS, C.31, C.25, C.16, C.16.P, C.31.ASAP or a local Q-Bundle to construct selected-structure changes, stating which characteristics should improve and which protected conditions may worsen.

ArchitectureCharacteristicImprovementLoop@Project is a local feedback record for reopening C.32 synthesis when characteristic pressure changes.

Keep each receiving claim with its subject pattern:

Improvement-question framing and repeated-improvement method stay with E.22 or E.23.

Use A.19.CPM for comparison, A.19.SelectorMechanism for set-returning selection, G.5 for selected-set result declaration, C.11 for local choice, and C.32.PAD for a project architecture decision. For publication, use E.24.PUB for occurrence and audience availability, with E.17 when a source-backed face and return are needed.

For this loop, bring only the changed characteristic pressure into C.32 and return the next candidate palette. Open another synthesis question only when an evaluation result, front relation, retained alternative, rejected candidate or source-return trigger changes what must be configured.

An evaluation result that cohesion improved, evidence reuse decayed, coupling changed, latency worsened or exceptions grew does not choose an architecture. To use it as feedback, recover the bearer, characteristic or criterion, scale or qualitative reading frame, affected structures and the inference it supports. A parity frame is needed when that inference relies on parity.

ArchitectureCharacteristicImprovementLoop@Project:
  projectWorkOccurrenceRef?: U.EntityRef constrained to U.Work
  architectureSynthesisProjectUseRelationRef?: U.RelationRef resolving to the synthesis-feedback or work-use relation
  describedHolonRef:
  currentArchitectureCharacteristicPressureRefs:
  architectureCharacteristicCriteriaSetRef?:
  architectureCharacteristicCriteriaRowRefs?:
  synthesisQuestion:
  candidatePaletteRef:
  architectureCharacteristicEvalResultRefs?:
  changedSelectedStructureRefs:
  improvementClaimPatternLocator: C.32.ACS | C.32.ACE | C.31 | C.25 | C.16 | C.16.P | C.31.ASAP | other pattern for the next question
  nextSynthesisQuestion?:
  sourceReturnCondition?:
Synthesis positionTypical selected structureWhat it contributesFirst pattern for the next question
Functional demandFunctionalStructureA.6.F-recovered functional demands, dependencies, constraints, and candidate bearer pressure.C.30.ASV, A.6.F, C.30.TFS-REL when flow relation is current.
Constructive bearerModuleInterfaceStructure, material, manufacturing, or component relation.Candidate modules, interface grammar, substitutability, variation slots, and fabrication burden.A.6.M, C.31, C.30.ASV.
Placement and localityPlacementDeploymentStructure or MaterialSpatialStructure.Location, latency, access, environment, maintenance, and source-return burden.C.30.ASV, domain pattern when current.
Control and flowControlStructure and TransformationFlowStructure.Feedback, supervisor relation, rate, flow relation, crossing, and transformation relation.C.32.LCA for constructing and comparing control arrangements; C.30.LCA for control-description or view adequacy; E.18, C.30.TFS-REL, C.27 when timing is current.
Method, Work, local-kind or assignment, information, and evidenceMethod and Work structures; relations among local system-role kinds, classifications, or assignment structures; direct allocation or responsibility relations; information and evidence structures.Prospective enactment burden, independently established responsibility, data custody, evidence reuse, assurance pressure, and source return.E.10.ROLE for unresolved wording; A.2 and A.2.1 for recovered kind, classification, or assignment; A.15 for actual Work, with F.6 only when precise assignment-bound attribution is expressly consumed; the admitted direct domain predicate or missing governor for responsibility; A.10, B.3, C.25, and C.31 when those claims are current.

Candidate architecture changes are local C.32 entries for candidate configurations. They are not FPF work occurrences, method steps, or receiving-pattern claims. A change is admissible only when the selected structure being changed is named.

Architecture-change kindConstructive useMinimum repair against overread
configurationSynthesisCoordinate several selected structures into one candidate architecture configuration.State the selected-structure contribution rows and architecture characteristics before claiming improvement.
functionalAllocationChangeChange the candidate A.6.F bearer or the module, Method, Work, local kind, separate System-classification judgment, assignment, control, or other structures that constrain its functioning.Keep the functional predicate and bearer distinct from every neighboring structure; unresolved “role” wording goes through E.10.ROLE.
functionBearerFeasibilityRepairRepair a candidate whose functional structure names a required function that no admitted bearer can bear under module, placement, resource, control, or evidence constraints.Add or change an A.6.F bearer, split the function, change placement or resource access, change the direct control or responsibility relation, or reject the candidate. If a lower demand would make the candidate feasible, take the proposed change to the authority that owns the commitment. Compare against the demand in force until that authority changes it.
functionBearerConsolidationTransfer a required function onto an existing bearer under the selected-structure constraints, remove a support bearer, or propose one more general bearer for several functions.State the functions transferred, the bearer removed or generalized, the affected architecture characteristics, the lost options, and the BLP scale window or waiver when scale advantage is claimed.
structuralSubstitutionReplace one selected structure with another candidate structure.State what is preserved and what is lost.
relationRetargetingChange an affected relation endpoint, direct responsibility relation, system-role assignment, dependency relation, admissible-use boundary, or source-return relation.Name the relation kind and its predicate before using the change in a candidate; if a needed responsibility predicate is absent, record the missing governor.
architectureInfluenceCorrespondenceSynthesisCoordinate candidate structures when an independently typed architecture or other source constrains transformed-side architecture content for a changed referent.Use C.32.CONWAY:4.1.1 to recover the operative constraint and construct applicable changes; name the changed referent and any independently grounded A.3.4 transformation separately; name each typed influence source by kind and its direct relation when an influence occurrence is asserted, otherwise keep the pressure synthesis-local with its missing-governor, unresolved-grounding, or false-predicate disposition; for each actual architecture side keep the C.30 holon, obtaining ArchitectureRelation, and selected U.Structure visible, and keep modal content in ArchitectureClaim; then prepare influence-source-side, transformed-side, joint, or bounded-mismatch candidates with affected architecture characteristics, expected gain, known loss, any needed source-return condition, and the pattern for the next question.
decompositionOrAllocationChangePropose reallocation of a module, future assignment condition, Work boundary, evidence relation, data custody, control relation, or variation slot across structures; retarget responsibility only through its direct domain predicate.State the proposed boundary, participant conditions, prospective object, and migration burden. Do not create an assignment or Work occurrence from candidate wording; return the missing governor when the needed responsibility relation has no current predicate.
placementOrDeploymentChangeChange locality, deployment, material placement, installation, or maintenance access.Name the affected structure and the latency, access, source-return, or environment burden.
flowOrControlVariantChange transformation flow, control depth, rate band, feedback boundary, or mediator relation.State the timing, control, observability, or accountability burden created by the change.
interfaceGrammarChangeNarrow, split, widen, or stabilize an interaction boundary.Apply A.6.M when module-interface relation repair is current.
declaredScopeOrHolonLevelChangeSplit, merge, add, or remove a declared holon-level reference, declared scope, evidence scope, work-method scope, or aggregation scope.Name the affected reference, use C.30.STRAT when the wording is only a stratification term, and use B.2 only when whole reidentification is current.
boundedExceptionKeep a residual because removing it costs more than it buys now.State the exception, reopen trigger, and next subject pattern if later source use or decision use expands.

Didactic mini-slices. Use these as examples of the kind of work C.32 expects, not as domain-specific templates.

SituationFirst C.32 stepCandidate repair
A sterilization function is placed in a shared field module, but the field placement has no power and no certified evidence relation for that heat cycle.Keep the functional demand separate from the module and placement structures.Add a local certified bearer, split the function into pre-field and field steps, change placement, or reject the shared-module candidate.
An ML functional graph includes retrieval, planning, and action, but no module-interface relation or direct domain predicate carries evidence-refresh responsibility or admissible-use control.Treat the graph as functional structure and recover module-interface, evidence, control, admitted-System, and responsibility relations separately.Add a retrieval service and an admitted evidence-refresh responsibility relation with actual participants, add a supervisor relation, narrow model-interface behavior, return the missing governor, or reject the candidate.
A Method family says the review function is automated, but A.6.F identifies no bearer and no direct responsibility predicate identifies who is responsible for exceptions.Recover the Method structure and A.6.F function bearer first. Keep any admitted Systems, local kinds, separate System-classification judgments, assignments, actual Work and separately needed F.6 attribution, responsibility relation, and evidence structure separate.Propose an assignment condition only in truthful plan or candidate content; cite a direct exception-responsibility relation or missing governor; split the Method step, change evidence scope, or keep the automation as source cue. Use a full Work chain only after performance.

When one independently typed architecture-side or other source constrains transformed-side architecture content for a changed referent, use C.32.CONWAY before using Conway, mirroring, or inverse-Conway language in candidate synthesis. Use :4.1.1 there to obtain an unexplained constraint and candidate change from available work, test and approval material.

The practitioner names:

  • the changed referent and any actual A.3.4 transformation separately;
  • each influence source by kind and its direct relation only when that occurrence is asserted; and
  • for each actual architecture side, the C.30 described holon, obtaining ArchitectureRelation, and selected U.Structure.

Modal architecture content stays in an ArchitectureClaim.

Without an admitted and satisfied direct influence predicate, the pressure stays synthesis-local in the C.32.CONWAY frame with its missing-governor, unresolved-grounding, or false-predicate disposition and no pair row.

Candidate work then names influence-source-side, transformed-side, joint, or bounded-mismatch changes, architecture characteristics under pressure, expected gains, known losses, and any source-return conditions needed by the use.

Keep the candidate palette as the C.32 result. C.32.CONWAY carries the architecture-influence correspondence frame or one reusable pair-row episteme.

Influence alone supplies no acting System, local system-role kind, System-classification judgment, assignment, Work, changed-referent identity, or transformation participation. Transformation, acting and Work attribution, exact influence, transformation-flow, and module-interface claims belong to A.3.4, A.12, A.2.1, A.15.1, F.6, the direct influence pattern, E.18, C.30.TFS-REL, or A.6.M when current.

Establish preservation and correspondence under their applicable subject rules, using C.34 for adequacy questions. Use C.29 when mathematical representation choice, transfer or reliance is unresolved.

A richer dossier is optional. Open it when source views, relation notes, measurements, C.29 lens outputs, evidence or failure repairs affect the next architecture use. Ordinary use needs one recoverable account per configuration; a row is one convenient form.

Downstream use. The C.32 result is architecture-specific candidate content. Use G.5 to declare a selected-set result, C.11 for a fixed local choice, and C.32.PAD for a project architecture decision. Use C.18 or C.19 for archive, front, pool-treatment, or generation policy when that claim is current. Use C.30.AD for architecture-description work. For publication, use E.24.PUB for occurrence and audience availability, with E.17 when a source-backed face and return are needed.

Stop condition. Stop when the palette supplies the selected structures, proposed changes, gains, losses, constraint fit and relevant limits needed for the next use. Retain source return where it protects that use.

Lowering and return. A single visible configuration can be the starting point for synthesis; use :4 to construct another configuration only when the question needs it. Recover a missing architecture claim through C.30 or candidate content through its available source or description. Repair an unqualified feasibility, gain or loss under C.32.FAIL, retaining the supported content and identifying what remains unknown.

When an adequate palette or retained configuration answers the synthesis question, stop; continue to comparison, selection, publication, choice, decision, evidence or assurance only for the receiving question that remains.

Reopen C.32 when a criteria row, eval result, retained alternative, front relation, source-return trigger or source-currentness change alters the structures under pressure or acceptable loss.

C.32:5 - Archetypal Grounding

Grounded working caseSynthesis questionC.32 candidate workStop condition
Regulated product family with growing field exceptionsHow should functions, module interfaces, placement, and evidence scope be configured so substitutability and certification burden stay acceptable?Prepare candidates that narrow interface grammar, split the family by evidence scope, change placement responsibility, or keep a bounded exception with source return.Stop at palette unless G.5 selected-set result declaration, publication availability, assurance, or architecture decision is current.
Built-asset digital-twin handover where a method-defined digital-twin view hides source lossWhich selected structures do the digital-twin dimensions describe, and which source-return obligations must survive maintenance use?Prepare candidates that split information view, add source-return scope, retarget maintenance responsibility, or change module and placement structure.Stop before built-asset architecture-description, MVPK publication-face, or A.10 evidence-relation claims unless C.30.AD.BA, E.17, E.24.PUB, or evidence patterns are current.
Emergency-department triage arrangement whose local desk is fast but hospital-wide escalation is brittleHow should admitted Systems, local system-role kinds or classifications, future assignment conditions, procedure and Method structure, control, direct responsibility, evidence, and any actual Work and separately needed F.6 attribution be configured so speed does not erase escalation adequacy?Prepare candidates that retarget responsibility only through an admitted direct predicate, state a possible mediator assignment as plan or candidate content rather than an occurrence, split triage scope by patient class, or adjust evidence capture; use the missing governor when needed.Stop before ethical mediation, evidence, staffing decision, assignment occurrence, or performed Work unless those claims are current.
AI-agent review setup where local autonomy conflicts with policy scopeHow should control, module-interface, evidence-refresh, and work-method structures be configured so autonomy and policy conformance stay jointly acceptable?Prepare candidates that add supervisor relation, narrow model interface behavior, change evidence refresh cadence, or alter work-method responsibility.Stop before safety, release, gate, or causal claims unless their subject patterns are current.
Method family whose shared template shortens drafting and lengthens reviewWhich arrangement gets an acceptable document to its reader earlier?Compare drafting and review of each document with use of the template. Another candidate separates reusable checks on the common material from checks that need the completed document. Establish which checks can travel with the template.Use the qualifying conditions and the reviewer’s availability to decide what can already be recommended. See §5.1.

C.32:5.1 - Choose an arrangement for an accepted document

A team must deliver a document after an independent review. Under one design the author drafts for 50 minutes and the reviewer needs 20 minutes. A shared template changes those times to 35 and 30 minutes. Both designs preserve the same review of the finished document. For this comparison assume those durations, a common start, an immediately available author, review after drafting and no rework. The reviewer has time to finish once available, is authorized to accept the document and accepts it when the review ends. In this agreement, delivery occurs when the accepted document becomes available to the reader. Acceptance gives the reader immediate access.

If the reviewer is ready for either handover, the template delivers at minute 65 and the existing arrangement at minute 70. If the reviewer first becomes available at minute 60, both drafts wait. The existing arrangement delivers at minute 80 and the template at minute 90. The template saves five minutes of combined effort in both comparisons. The earliest acceptable delivery changes with the appointment. Even an inexact appointment can settle the choice. Availability by minute 39 puts the template ahead throughout that range.

A third design could qualify common material once and review its use in each finished document. To compare it, identify the common checks, the authority that accepts their reuse and the local checks each document still needs. A new heading in the template leaves this work in place unless a check or its input actually changes.

These times are consequences of the stated designs. Suppose instead that accepted documents are delivered together at minute 100. Both designs then meet the same delivery time under either appointment. If the recipient chooses the lower effort at equal delivery, the template can be selected without first resolving the appointment. To establish how long a particular release took, use its actual start and the event promised to the recipient. Use the delivery terms to identify the event and its evidence. A portal access record can establish when the document became available under this agreement. If delivery is complete when a named recipient receives the document, establish when it reached them. If the agreement also requires their acknowledgement to complete delivery, use the time of that act. A receipt at minute 100 followed by a required acknowledgement at minute 120 completes delivery at minute 120. To establish what passed review, use the applicable criterion and the review result for that document. A comparison across releases also depends on what they had to deliver, reviewer availability and any rework. A shorter observed release can raise a question about the design without identifying what caused the difference.

C.32:6 - Bias-Annotation

Scope: Limited to constructing a small candidate architecture palette for one C.30-grounded architecture question about one described holon or holon family. C.32 is not a universal architecting Method, a software-architecture default, a comparison or selection rule, a publication route, or a decision procedure.

LensLikely driftRepair
GovA candidate, front member, generated option, or workshop consensus is treated as selected, authorized, accepted, published, or current.Stop at the palette and use the pattern for the next claim; candidate wording creates none of those relations.
ArchOne visible structure, source diagram, functional graph, or organizational arrangement is treated as the architecture.Ground the holon and architecture question, then coordinate only the selected structures and characteristics that change the candidate.
Onto-EpistA description artifact, claim, model, role-shaped label, or proposed structure is treated as an obtaining architecture relation or world-side structure.Keep the holon, obtaining relations, selected structures, modal claim content, source artifact, and candidate change distinct; use each direct subject pattern.
PragThe palette becomes a dossier or exhaustive search although two to five useful alternatives would support the next use.Keep the smallest useful set of selected-structure contribution rows, keep one row per candidate, and add richer evidence only when it changes the next architecture use.
DidFormal records or software examples obscure the constructive move for another field.Lead with the ordinary move—structures changed, gain, loss, constraint fit, source return, next use—and use unlike grounded cases; keep the richer record optional.

C.32:7 - Conformance Checklist

IDRequirementPurpose
CC-C32-1The use names one synthesis question, described holon, intended palette use, and the current architecture relations and selected structures that change the question; ClaimScope or a bounded model-use structure is added only when action-changing.Keeps the palette local without a generic context premise.
CC-C32-2The selected-structure contribution rows name the smallest useful set of selected structures and subject patterns and state what each contributes.Prevents one-structure optimization from masquerading as synthesis.
CC-C32-3Architecture characteristics and any quality bundles are named before candidate comparison.Keeps functional demand distinct from architecture trade-offs.
CC-C32-4Each candidate configuration names selected structure changes, expected gain, known loss, and constraint fit.Makes the candidate actionable.
CC-C32-5Compressed, generated or view-derived candidates carry a source-return condition when omitted distinctions change their receiving use.Keeps dependent source-use or decision claims tied to recoverable grounds.
CC-C32-6Archive, front, pool-treatment, G.5 result declaration, publication availability, local choice, and decision uses have named patterns for the next questions.Keeps synthesis separate from downstream receiving claims.
CC-C32-7Each configuration explains how its selected structures work together toward the required result and which dependencies constrain it.Makes the synthesis usable beyond a list of parts.
CC-C32-8If an independently typed source constrains transformed-side architecture content for a changed referent, C.32.CONWAY is opened before Conway, mirroring, or inverse-Conway language is used as guidance; the source kind, its obtaining direct relation or precise provisional disposition, and both C.30 architecture sides or modal claims are named without inferring acting, Work, or transformation facts.Keeps influence-source and transformed-side content distinct while making correspondence synthesis constructive.

C.32:8 - Common Anti-Patterns and How to Avoid Them

C.32:8.1 - Architecture trade-off failures

Anti-patternRepair
Local structure win hides other-scope loss. A module split, control placement, evidence scope, or direct responsibility-relation change helps one concern while worsening another architecture characteristic.Rebuild the selected-structure contribution rows and record the gained and lost characteristics before comparison; do not infer responsibility from a team label or assignment.
Function and architecture characteristic collapse. The candidate is argued from user-visible function while evolvability, coupling, cohesion, latency, evidence burden, or another architecture characteristic remains unnamed.Recover the function through A.6.F or the structural-view pattern, then name the architecture characteristic separately.
Function without feasible bearer. A functional architecture, workflow, Method step, or searched graph asks for a function but A.6.F identifies no bearer that satisfies the functional predicate under the relevant module, resource, placement, control, evidence, local-kind, classification, or assignment constraints.Repair or reject it before treating it as feasible; retain its failure explicitly when useful for diagnosis or comparison.
Missing structural alternatives. The receiving question requires alternatives, but only one configuration is visible or the alternatives differ only in description.Use :4 to construct structurally different candidates from the limiting relation. If a supported incumbent already answers the question, retain it; if a needed alternative remains unknown, name the unresolved construction rather than a completed comparison.
Description artifact stands in for candidate content. A diagram, ADR, view, dashboard, benchmark output, or digital-twin view is the visible work product, but the selected structures and architecture-characteristic trade-off are still missing.Recover the candidate content from the visible work product under its description, benchmark, publication or source-use rules. Use C.29 only for an unresolved mathematical representation choice, transfer or reliance question.
Front member treated as durable optimum. A front member, local winner, or benchmark leader is used as if the evolution window will stay fixed.Record evolution window, source-return condition, and retained alternatives under the C.18 or C.19 predicates; use G.5 only to declare a selected-set result from those alternatives. If the result is published, use E.17 for a source-backed face and source return and E.24.PUB for the publication occurrence and audience availability.
Software-source overfit. A software architecture source supplies a useful architecture-change idea, but the described holon is not a software system.Translate only the change over selected structures and characteristics; do not import the software ontology.
Architecture-influence source omitted. The candidate architecture for a changed referent cannot be built, tested, deployed, certified, or evolved under the current architecture, Work, communication, method, tool, deployment, evidence, selected-structure, or other source, but that source’s kind and influence status are hidden.Use C.32.CONWAY:4.1.1 to recover the operative constraint and an applicable change; recover the source kind and either its obtaining direct relation or the precise provisional disposition, keep the acting System, any local system-role kind or assignment, Work, changed referent, and any actual transformation distinct, and prepare the applicable source-side, transformed-side, joint or bounded-mismatch alternatives, preserving the requirement each must meet.
Method-defined dimensions lose their semantics. A BIM, digital-twin, or view-method dimension already carries method-defined structure, constraint, cost, schedule, use-phase, or maintenance semantics, but the synthesis text keeps only the dimension name or dimension count.Preserve the method semantics and map them to selected structures, constraints, characteristics, and source-return conditions.
Ideality shortcut. Fewer bearers, fewer modules, or one universal module is only a candidate direction until functions, architecture characteristics, scale window, safety, admissibility, and losses are named.Keep it as one candidate and expose those missing tests before comparison.

C.32:8.2 - More repair cues

Repair cueSymptomFirst repair
BenchmarkWinnerAsArchitectureA comparison result is treated as architecture selection.Treat the result as comparison input or as source material for an A.10 evidence relation when that claim is current; admit a C.32 candidate only after selected structure, architecture-change kind, gain, loss, and pattern for the next question are recovered.
ShortlistByNameA set is called shortlist before the result fields required by G.5 exist.Keep it as a local palette or open G.5.
SourceCompressionNoReturnA candidate hides source distinctions needed by its receiving use.Restore those distinctions, add a source-return condition or narrow that use.

C.32:9 - Consequences

Positive consequenceCost or trade-off
Candidate architecture configurations are visible before local choice or decision.Losses and constraint fits must be named earlier.
Architecture-characteristic improvement can reopen synthesis when needed.A warranted next iteration identifies changed pressure, affected structures and usable feedback; a sufficient palette can finish the current question.
Multi-structure synthesis is reviewable.The practitioner must keep functional, module, placement, control, Work, evidence, and other selected structures distinct when they matter.
Architecture characteristics and quality bundles are recorded as comparison inputs for the receiving pattern.The palette may need characteristic repair through C.25, C.31, C.16, or later comparison, local-choice, selection, or selected-set result-declaration work through A.19.CPM, C.11, A.19.SelectorMechanism, or G.5, respectively, when those claims are being made.
Holonic architecture breadth is preserved.Examples and candidates must name the described holon and selected structures instead of using domain defaults as unstated selected structures.
Source cues can inform architecture work without importing source-domain ontology.Source-side expressions require recovery of referent, selected structure, architecture-change kind, and source-return condition.
Downstream G.5 result declaration and architecture-decision work stay cleaner.The team must open the pattern for the next question when it wants to declare a selected-set result, publish it to an audience, make a local choice, or decide the project architecture.
Evolutionary and search practices are usable without hidden single-winner optimization.The palette may need retained alternatives even when one candidate looks convenient.

C.32:10 - Rationale

Architecture practice needs a method between a grounded architecture question and an architecture decision. Use C.30 to ground the question over selected structures of a described holon. Use C.30.ASV, A.6.F, A.6.M, C.30.LCA, C.30.TFS-REL, C.25, and C.31 to recover the structures and characteristics. Later, use C.18 or C.19 for front, archive, or pool treatment, G.5 for selected-set result declaration, E.17 and E.24.PUB for their distinct publication jobs, C.11 for local choice, and the applicable decision pattern for a project decision.

Use C.32 for the constructive middle: building a small set of candidate architecture configurations whose selected structures, allocations, characteristic trade-offs, known losses, source-return conditions, and patterns for the next questions are explicit.

The same middle repeats during improvement. A later criteria-row change, scale-row change, C.16 reading, C.25 or C.31 pressure change, C.31.ASAP scale-preference change, or C.18 or C.19 front, archive, or retained-alternative relation can reopen C.32 when it changes the architecture-characteristic pressure, the selected structures under stress, or the acceptable loss profile. The practitioner then synthesizes another candidate palette; the trigger does not decide the architecture.

The work is to make architecture content available for a later front, comparison, selected-set result declaration, publication, or decision.

C.32:11 - SoTA-Echoing

These rows show how source practice contributes to C.32. The opening of each second-column entry classifies the source use; the opening of each transfer states its disposition. The blocked-overread column gives the use limit, and the source-currentness boundary below gives the reopen rule. Software-system sources are comparison inputs, examples, or lineage only; they do not narrow C.32 to IT architecture.

Source to inspectSource-use class and why it matters hereTransfer into C.32Blocked overread
Architecture synthesis and quality-attribute optimization: Di Pompeo and Tucci 2023 (https://arxiv.org/abs/2301.07516), ATRAF 2025 (https://arxiv.org/abs/2505.00688), and current FPF C.32.HCS, C.32.ACS, C.32.ACE, C.25, C.31, C.16Research comparison and FPF guidance: quality attributes and architecture characteristics compete, and multi-objective treatment gives the architect a trade-off view instead of one scalar winner.Adapt: make the relevant characteristics and Q-Bundle slots explicit, reusing criteria rows or constructing them through ACS when needed. Use ACE evaluation results as feedback under the rule for the receiving inference.A user function, metric, benchmark, scalarized score, evaluation result, or apparent improvement is not architecture synthesis, comparison, project architecture decision, or improvement-cycle closure.
DSM, multiple-domain matrix, and DSM modularization research, including Jiang and Luo 2026 (https://arxiv.org/abs/2604.28018)Research comparison with DSM lineage: modularization is useful, while LLM-based DSM work also exposes divergence between functional priors and structural objectives.Adapt: use DSM or clustering as one candidate-generation and inspection source; recover selected structures, structural objective, and engineering semantics before treating the result as architecture-synthesis material.A cohesive cluster, graph partition, or generated modularization is not architecture adequacy by itself.
FPF architecture kernel: A.22, C.30, C.30.ASV, C.30.ILC, C.31, C.31.ASAPFPF architecture basis: obtaining architecture relations connect a described holon to selected structures for a named architecture question and use.Adopt: ground the holon, synthesis question and intended use, then use domain and research contributions to construct the relevant structures and alternatives. Recover each proposed change, gain, loss and use condition as the candidate develops.Diagrams, source expressions, software-system templates, and platform proposals remain source cues until the described holon, selected structures, architecture criteria, gain, loss, and pattern for the next question are recovered.
ISO 42010:2022 architecture-description standard (https://www.iso.org/standard/74393.html)The 2022 standard: it distinguishes architecture, description, view, viewpoint, concern, correspondence, and model kind, while leaving architecture itself outside the standard’s subject.Adopt narrowly: treat architecture-description artifacts as source cues or description material until a candidate selected-structure change is recovered.An architecture-description artifact or publication face is not a candidate architecture by itself.
Ford, Parsons, Kua, and Sadalage, Building Evolutionary Architectures, 2nd ed.; overview at https://evolutionaryarchitecture.com/ and O’Reilly page https://www.oreilly.com/library/view/building-evolutionary-architectures/9781492097532/Practitioner comparison: guided incremental change makes affected architecture characteristics and feedback visible.Adapt: add reversible first steps where useful, affected criteria rows, ACE evaluation results, source-return triggers, a next synthesis question, and preserve the source meaning. Represent a source-side fitness-function practice through an appropriate C.32.ACE evaluation program over the criteria used.Evaluation results need a comparison, local-choice, or other preference-use assertion before they affect preference. They can start the next synthesis iteration when characteristic pressure changes and the feedback conditions in Solution 4 hold.
Shaw and Petre, Design Spaces and How Software Designers Use Them (https://arxiv.org/abs/2407.18502); Cortellessa, Diaz-Pace, Di Pompeo, Tucci, Towards Assessing Spread in Sets of Software Architecture Designs (https://arxiv.org/abs/2402.19171)Research comparison: design-space work distinguishes structural alternatives from objective-space scores.Adapt: preserve a candidate palette when one scalar winner would hide structurally different alternatives; distinguish objective-space signals from selected-structure differences.A Pareto front, score, spread indicator, or generated set does not select the architecture and does not replace architecture-space inspection.
MOSA and open-system engineering from C.31.RSA (https://www.cto.mil/sea/mosa/; https://www.cto.mil/wp-content/uploads/2025/03/MOSA-Implementation-Guidebook-27Feb2025-Cleared.pdf); product-line variability and product-platform practice from C.31.RSA and C.31.ASAP (https://www.sei.cmu.edu/library/variability-in-software-product-lines/; https://arxiv.org/abs/2605.21353; https://link.springer.com/article/10.1007/s00163-023-00427-1; https://arxiv.org/abs/2510.11089); information-hiding lineage carried by C.31.RSAStandards, practice comparison and information-hiding lineage: the sources expose interface conformance, substitution, variability, extension, exception, assembly, and hidden-change pressures.Adapt as candidate prompts: change the interface grammar, substitution policy, variation slot, evidence scope, exception boundary, or bearer only when the current architecture question needs it.Before a candidate is preferred, use C.31.RSA for reusable-structure accounting, C.31.ASAP for scale preference, A.6.M for interface grammar, C.16 for measurement, A.19.CPM for comparison, G.5 for selected-set result declaration, and C.11 for local choice, as applicable to the current claim.
TRIZ ideality, Ideal Final Result, technical-system evolution regularities, and current FPF C.19.1 BLPHistorical heuristic lineage plus current FPF discipline: older ideality language suggests useful candidate moves; BLP supplies the current scale-amenability rule.Use as lineage and adapt only as a candidate prompt: transfer a function to an existing bearer, remove support bearers, use available resources, or try a more general bearer; judge the resulting candidate under current FPF rules.An ideal-final-result slogan, fewer modules, or one universal module is not architecture adequacy, scale adequacy, or project architecture decision.
NAS survey line: Elsken, Metzen, and Hutter 2019 (https://www.jmlr.org/papers/v20/18-598.html); multi-objective differentiable NAS 2025 (https://arxiv.org/abs/2402.18213); hardware-aware NAS 2024 (https://arxiv.org/abs/2404.12403); Sutton’s Bitter Lesson (https://www.incompleteideas.net/IncIdeas/BitterLesson.html) and scaling-law practiceML research and practice comparison: functional graph search works under performance, resource, hardware, and transfer constraints.Adapt: treat functional architecture as one selected structure and qualify bearer feasibility under the relevant module, deployment, resource, control, information and evidence conditions. Failed or unresolved feasibility can inform diagnosis and comparison; it does not make an option feasible for choice.A neural cell graph, function graph, benchmark winner, or scale curve is not holonic architecture adequacy unless selected structures and bearers are recovered.
Conway’s law, mirroring, DORA loosely coupled teams (https://dora.dev/capabilities/loosely-coupled-teams/), and Team Topologies key concepts (https://teamtopologies.com/key-concepts)Practitioner comparison with historical lineage: these sources expose co-evolution and coordination pressure between organizational and technical structures without supplying a universal causal law.Adapt: treat team, Work, responsibility, Method, toolchain, deployment, communication, evidence, and selected structures through their kinds; assert a direct influence relation only when its predicate is satisfied. Use inverse Conway only to generate a candidate change to selected influence-source structures.Influence-source change, transformed-side change, joint change, and bounded mismatch remain candidate alternatives or comparison inputs. Architecture influence alone establishes no acting System, Work, or actual transformation.
MAAD 2025 (https://arxiv.org/abs/2507.21382) and LLM-assisted ADD 2025 (https://arxiv.org/abs/2506.22688)Research comparison: generated alternatives are practical, while the studies retain knowledge, trade-off, evaluation, and human-oversight limits.Adapt: use AI outputs to widen candidate space, then recover source-side referent, selected structure, architecture-change kind, gain, loss, source-return condition, and pattern for the next question before palette admission.A generated blueprint, evaluation report, benchmark, or agent consensus is not an authority relation for architecture adequacy, evidence sufficiency, assurance, gate passage, or decision.

Source-currentness boundary. Use each source row only for the C.32 candidate-generation move that the row transfers. Recheck the row before using it again when:

  • a named standard, guide, book edition, survey, or research line changes that move; or
  • a receiving FPF pattern named in the row changes how it handles the source family.

If the project needs comparison, selection, selected-set result declaration, publication, local choice, decision, evidence, or assurance, leave C.32 and open the pattern for the next question.

Rows named as lineage, such as TRIZ ideality, information hiding, or mature DSM lineage, stay lineage until a current source relation is recovered.

C.32:12 - Relations

Uses:

Need or use conditionPattern
A residual starts the candidate work.C.30.ILC
Residual-reducing multilevel framing is being used.C.32.MLAO
Influence-source and transformed-side architecture content must be co-synthesized without inferring acting, Work, or transformation facts.C.32.CONWAY
A defect needs repair before the candidate can serve its intended use.C.32.FAIL
Candidate eval results are needed before later comparison or selection.C.32.ACE
A source, description, view, decision record, eval report, handoff, or realized observation captures only part of selected structure.C.33
Candidate or source structures need preservation adequacy or correspondence adequacy.C.34
Recover the kind and assess the adequacy of a generated or discovered result before candidate palette use.C.35
Mathematical representation choice, transfer or reliance remains unresolved.C.29

Patterns for the next questions:

Question or usePattern
Explicit comparison claimsA.19.CPM
Set-returning selection claimsA.19.SelectorMechanism
Selected-set result declarationG.5
Archive, front, or pool-treatment policyC.18 and C.19
Fixed local choiceC.11
Architecture-description workC.30.AD
A source-backed publication face and source returnE.17
Publication occurrence and audience availabilityE.24.PUB
Project architecture decisionsC.32.PAD
  • P2S docking: C.32.P2S uses C.32 for the candidate-synthesis stages after problem pressure, selected structures, architecture characteristics, and structural uncertainty have been recovered; C.32 continues to define the candidate palette.
  • Routes to: C.32.MWA when one usable practice-architecture answer must be synthesized from several structures that do not line up one-for-one; C.32 retains general candidate-palette construction.
  • Boundary: Use C.32 to construct a candidate architecture palette for one grounded architecture question over selected structures of a described holon. C.35 may support C.32 by recovering a generated or discovered result’s kind and assessing its adequacy for candidate-palette use, but C.35 does not select candidates, publish sets, or decide the project architecture. Evidence, assurance, gate, release, work authorization, Method rules, ethical mediation, and causal claims use their own patterns when those claims are being made.

C.32:End

Referenced in the corpus

170 literal mentions in other sections. Read their context to establish the relation.