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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:00:10 UTC

C.35:1 - Problem frame

Use this pattern when a generated, searched, clustered, queried, learned, transformed, simulated, or discovered result may seed or inform architecturing, and the practitioner must decide what that result is and whether it can enter architecture work before or around C.32 candidate admission.

Primary working reader: an architect, architecture researcher, AI-assisted architecture worker, model-based engineer, or reviewer receiving a result from DSM and MDM modularization, MBSE query and view generation, graph grammar, model transformation, NAS, DSE, QD, OEE, and NQD search, LLM-assisted architecture design, code-agent mapping, simulation, benchmark trace, or source discovery.

Typical entry phrases:

"The LLM generated an architecture diagram; can it seed synthesis?"
"The DSM clustering suggests modules; is this a candidate architecture yet?"
"The MBSE query produced a view; which organization is observed, proposed, or still unestablished?"
"NAS found a Pareto point; what architecture claim can use it?"
"A graph grammar transformed the model; what preservation and bearer boundary must be checked?"

Primary working object. The generated or discovered result on which the next architecture use would rely.

First useful move. Identify the result and the organization it concerns, then state its supported next use and any condition or limitation that affects reliance. Distinguish supported, refuted and unestablished claims about existing organization from proposals for a possible organization. Keep a proposal modal; add C.30 claim identity when the receiving use needs independent reidentification.

Keep a representation distinct from its represented object when correspondence or representation operations matter. Use C.30.AD or C.30.ASV for architecture descriptions or views, and C.29 for a remaining mathematical-representation choice, transfer, or reliance question. Publication detail enters only when availability or form changes the use.

Normal first result. A short sentence can suffice; reuse an adequate existing account. When separate lines help, use:

Result: <result relied on>
Organization: <organization concerned; whether the claim about it is established, refuted or unestablished, or presents a proposal>
Next use: <supported use and any unresolved condition>
Limit and return, if needed: <material limitation and how to resolve it>

Stop there when another practitioner can make the intended next move safely. Only when result identity, branch evidence, or a receiving claim must be reidentified independently, extend those four facts into the optional StructuralSynthesisDiscoveryAdequacyNote@Project C.2.1 episteme:

StructuralSynthesisDiscoveryAdequacyNote@Project:
  resultRef:
  organizationConcern:
  nextArchitectureUseAndCondition:
  forbiddenOverreadOrReturn?:
  resultKindAndIdentityRule?:
  admissibleUse?:
  unresolvedConditions?:
  representationRef?:
  representedObjectRef?:
  publicationFormRef?:
  publicationOccurrenceRef?:
  presentationCarrierRef?:
  projectWorkOccurrenceRef?: U.EntityRef constrained to U.Work
  structuralSynthesisAdequacyNoteProjectUseRelationRef?: U.RelationRef under a named architecture-use or work-use predicate when that relation identity is material
  groundedArchitectureQuestionRef?:
  resultBranch?: transformation | discovery | generative-proposal
  generationOrDiscoveryMethodRef?:
  generationOrDiscoveryWorkRef?: U.EntityRef constrained to U.Work
  generationOrDiscoveryWorkAttributionRefs?: refs to obtaining F.6 performedUnderAssignment relations only when the note or receiving use expressly represents attribution
  workToTransformationOrProductionClaimRefs?:
  transformationBranch?:
    exactSourceObjectRefs:
    exactResultObjectRefs:
    transformationTraceRef:
    preservedStructure:
    lostStructure:
    actualTransformationRefs?:
  discoveryBranch?:
    observationOrExtractionBasis:
    observedInferredUnknownStatus:
    coveredRegion:
    unexploredRegion:
    uncertainty:
    validation:
  generativeProposalBranch?:
    constraintRefs:
    proposedOrganizationContent:
    knownOmissions:
    validationNeeds:
    declaredBaselineComparison?:
      exactBaselineObjectRefs:
      preservedStructure:
      lostStructure:
  obtainingConstraintGovernedUnfoldingStructureRef?: A.22.CGUS reference only
  sourceLabelRecoveryRef?:
  obtainingStructureRefs?: A.22 U.Structure references only
  modalArchitectureClaimRef?: C.30 ArchitectureClaimRef or C.2.1 ClaimAddress to its claim
  candidateAdmissionCondition?:
  bearerOrRealizationBoundary?:
  obtainingRealizedHolonStructureRefs?: positive A.22 references only
  measurementOrEvalReturnRefs?:
  bearerFeasibilityQuestionRef?:
  nextClaimOrRuleRef?:
  receivingClaimKind?:

The note retains the result, organization, next use and any material limit or return; its fields are included when the selected branch or receiving use needs them. Its EntityOfConcern is the result designated by resultRef, not the reference value, representation, publication occurrence, form, or carrier used to reach it.

When publication detail is relied on, publicationFormRef, publicationOccurrenceRef, and presentationCarrierRef refer to the form, occurrence, and carrier, respectively; omit every one that the receiving use does not need.

The note’s ClaimGraph states the organization concerned, supported next use, and any material limitation or unresolved condition. A plausible mistaken inference is corrected when that changes reliance. Do not open or fill the dossier merely to prove completeness.

Here @Project is a compatibility and retrieval cue only. It establishes no project entity, composite-work identity, context, authority, viewpoint, or parthood.

When the note is used in one project, projectWorkOccurrenceRef identifies the composite U.Work and structuralSynthesisAdequacyNoteProjectUseRelationRef identifies the relation by which that project Work uses the note. The suffix or either reference alone establishes no project locality. The admission-note episteme, its result, and the composite project Work remain distinct.

When reliance depends on the result’s generation or discovery history, retain the operation and the material source, input, performer and condition facts needed to establish that history and its bearing on the result. For an express claim about a U.Work, generationOrDiscoveryWorkRef names that independently admitted occurrence: its performers have A.13 cores and A.15.1 supplies Work admission.

Include the Method reference when the receiving claim depends on that Method. generationOrDiscoveryWorkAttributionRefs appear only for precise assignment-bound F.6 attribution. Missing or failed F.6 attribution alone leaves independently admitted Work intact; recheck an admission premise questioned by the same finding and any conclusion depending on it. The operation, Work, attribution, admission-note episteme, result, representation and publication objects retain their distinct identities.

actualTransformationRefs cite independently identified A.3.4 bounded changes. A positive link from Work to an actual transformation or produced entity uses the declared predicate governing that link and its supporting facts, including A.15.PROD when its branch is selected. Return missing-governor under A.6.RCD when no predicate governs the link; leave missing case facts unresolved and reject a link contradicted by them.

An entry in obtainingStructureRefs resolves to an A.22 U.Structure with independently identified constituents, obtaining relation occurrences, applied constraints and a named use frame. An incomplete basis for a claim about existing organization leaves that claim unestablished.

A proposal remains modal until its proposed organization obtains; supply modalArchitectureClaimRef when that claim must be independently reidentified. A result, representation, publication item, graph, cluster or description supplies only the structural facts it establishes.

Adoption test. After using C.35, another practitioner can state the four-line minimum or an equivalent sentence: the result, the organization concerned and whether the claim about it is established, refuted or unestablished, or presents a proposal, the supported next use and any unresolved condition, material limitation or required return. That practitioner can also distinguish claim content, an obtaining A.22 structure, its representation, and a publication-side object when those distinctions affect use. Additional identity, branch, Work, bearer, publication, evaluation, or next-claim detail appears only when the receiving use relies on it.

What C.35 buys in practice. The practitioner can keep a useful generated or discovered result without treating it as authority for architecture claims. Architecture use attaches to the result; changing a rendering or file does not silently change the admitted claim, and admitting a carrier does not silently admit claim content.

Ordinary working move. Explain the organization concerned, its actual or proposed status, what remains unestablished, and the use the result supports. Stop when the next move and any material limit or return are clear. Claim an obtaining A.22 structure only when its four identity discriminators resolve. Preserve an unestablished claim about existing organization as unresolved and a proposal as modal. Add claim identity, representation, branch, Method, Work, bearer, publication or evaluation detail when the intended use depends on it; use C.29 for an unresolved mathematical-representation choice, transfer, or reliance question.

Not this pattern when. If the current question is how to search, choose, measure, decide, authorize, publish, govern a reusable generator, govern a cultural-evolution case, or run the work itself, use the pattern that defines or decides that question first, including C.36 for the cultural-evolution relation bundle. Use C.35 only when a generated or discovered result must be admitted or rejected before another architecture claim relies on it.