C.30.ASV:4.1 - Architecture structural view record
StructuralAspectDescription describes one selected structural aspect under A.22. It is not an ArchitectureStructureKindRef or U.View by itself. ArchitectureStructuralView names the same architecture-description episteme only after exact E.17.0 conformance obtains.
ArchitectureStructuralView ::= ArchitectureDescription & U.View & {
viewEpistemeRef: U.EpistemeRef,
claimGraph: exactly one C.2.1 ClaimGraph,
entityOfConcernRef: selectedStructureRef,
effectiveReferenceScheme: U.ReferenceScheme, byValue,
selectedStructureRef: U.StructureRef,
relatedStructureRefs?: FinSet(U.StructureRef),
structureKindRef: ArchitectureStructureKindRef,
viewpointRef: U.ViewpointRef,
viewpointConformanceRelationRef: EpistemeViewpointConformanceRelationRef,
concernRefs?: FinSet(U.EntityRef),
describedHolonRef?: U.HolonRef,
architectureRelationOccurrenceRefs?: FinSet(ArchitectureRelationRef),
architectureClaimRefs?: FinSet(U.EpistemeRef constrained to ArchitectureClaim),
claimScope?: U.ClaimScope, byValue,
modelUseStructureRef?: U.StructureRef,
empiricalGroundingRelationRefs?: FinSet(EpistemeEmpiricalGroundingRelationRef),
recordPatternLocator,
selectedRelationKindRefs?,
selectedConstraintRefs?,
selectedInvariantRefs?,
selectedOperationDescriptionRefs?,
selectedDynamicsDescriptionRefs?,
viewConstruction:
directDescription | projection | query | extraction |
coarsening | correspondenceSlice | sourceReturnSlice,
structuralAspectDescriptionRef?: U.EpistemeRef,
hiddenOrLostStructure,
structureKnowledgeState?:
declared | observed | inferred | generated | simulated |
extracted | hypothesized | unknownRegionPresent,
correspondenceClaimOrRelationRefs?: FinSet(U.EpistemeRef | U.RelationRef),
sourceToUsePathRefs?: FinSet(U.RelationRef),
workRelianceRelationRefs?: FinSet(U.RelationRef),
sourceReturnCondition?,
representationRefs?: FinSet(U.EntityRef),
publicationOccurrenceRefs?: FinSet(EpistemePublicationRelationRef),
publicationFormRefs?: FinSet(U.EntityRef),
carrierRefs?: FinSet(U.EntityRef constrained to U.PresentationCarrier),
admissibleUse,
nonAdmissibleUse
}
recordPatternLocator identifies the pattern whose record form is being used. It is a locator, not a substitute for any rule needed by a current claim.
The selected U.Structure is the one EntityOfConcern. Before that field can be filled, A.22 identifies the structure from exact constituents, selected independently obtaining relation occurrences, applied constraint claims, and one exact receiving-use frame. A description, query, diagram, family declaration, file, representation, or publication creates none of those discriminators. relatedStructureRefs may name structures needed to interpret correspondence, allocation, or crossing, but they do not create a union-valued EntityOfConcern. When another selected structure becomes primary, identify another description episteme under C.2.1. Assert edition continuity only when its historical-continuation predicate obtains, and apply A.6.4 separately when retargeting is claimed; do not overwrite identity through a view field.
The direct conformance occurrence has exactly two participants: viewEpistemeRef as candidate E and viewpointRef as exact P. Its fixed E.17.0 predicate requires: (1) independently identified E and admitted P; (2) exact EntityOfConcern(E) recovered; (3) P’s fixed EntityOfConcern-kind criterion succeeds for that exact object; (4) E has an independently admitted episteme kind accepted by P without circular U.View use; and (5) E’s fixed claim content under its effective scheme satisfies P’s concern-coverage, semantic-form, completeness, and admitted-omission rules. The occurrence is participant-determined by <E,P>.
An architecture claim can carry positive, negative, unresolved, required, desired, expected, or candidate content. architectureRelationOccurrenceRefs is affirmative only for independently obtaining direct ArchitectureRelation occurrences. describedHolonRef and participant traces keep the subject recoverable; neither an optional claim nor a diagram derives the subject-side occurrence.
ClaimScope, concern, model-use structure, and empirical grounding remain optional neighboring qualifiers or relations. modelUseStructureRef appears only when an independently selected DDD-style bounded-model-use structure changes interpretation or selection for this use. None enters base episteme or selected-structure identity.
viewConstruction records provenance only. Direct authoring, A.6.3 construction, projection, query, extraction, selection, bundle inclusion, diagramming, rendering, publication, evaluation, or current use neither satisfies the conformance predicate nor creates selected structure. Representation, publication occurrence, form, and carrier likewise retain their own identities.
structureKnowledgeState? states how the selected structure is known when partial knowledge matters: declared, observed, inferred, generated, simulated, extracted, hypothesized, or with an unknown region present. Unknown or inferred structure may guide inspection or source return; it cannot by itself supply architecture truth, assurance, gate, release, causal proof, or architecture decision.