Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:25:14 UTC

C.30.AD:4.2 - View membership, viewpoint, and structure-kind binding

An architecture description episteme is not a U.View because it is put in a multi-view set, authored under a viewpoint label, constructed by A.6.3, returned by a query, selected, bundled, diagrammed, rendered, or published. First identify the candidate episteme by its C.2.1 identity. Then identify one exact viewpoint episteme and test the fixed five-part E.17.0 predicate. Only a separately obtaining EpistemeViewpointConformanceRelation(candidateEpisteme, exactViewpoint) admits that same episteme as U.View.

When a receiving use needs one multi-view description set, recover an exact collection of independently identified description epistemes under C.13; set membership is ordinary collection membership. A shared file, bundle, heading, graph, publication, or query result neither identifies that collection nor grants U.View membership. The collection keeps no second episteme identity for its members.

C.30.AD can record use of already recoverable architecture structural views inside one description set without minting a local relation kind:

ArchitectureDescriptionViewUseClaim content:
  architectureDescriptionSetRef:
  usedArchitectureStructuralViewRef:
  usePurpose:
    orientation | comparison | implementationGuidance |
    assuranceInput | sourceUse | strongerUseReturn | declaredOther
  correspondenceClaimOrRelationRefs?: FinSet(U.EpistemeRef | U.RelationRef)
  sourceToUsePathRefs?: FinSet(U.RelationRef)
  sourceReturnCondition?
  admissibleUse:
  nonAdmissibleUse:
C.2.1 constitution:
  entityOfConcernRef: exactly one architectureDescriptionSetRef
  effectiveReferenceScheme: U.ReferenceScheme, byValue

ArchitectureDescriptionViewUseClaim is a C.2.1 episteme about one description set. The block separates what the claim says from the objects that identify it; it does not add slots to the episteme. The claim cannot make anything a U.View or make a view, set, viewpoint, or structure obtain. Each referenced view must already satisfy E.17.0. Use C.30.ASV to check viewpoint conformance and selected structure, A.22 for structure itself, and C.30 for an obtaining architecture relation or grounded architecture claim. Use C.30.AD only for description identity and use, cross-view correspondence, source use or return, freshness, specification or publication use, and the remaining architecture move. Common architecture-description views:

View useRequired FPF application
Function or functionality viewA.6.F for function or functionality wording and C.30.ASV for the structural view.
Transformation-flow viewE.18 for the selected transformation-flow structure, path, crossing, or valuation; E.18.2 for its graph-shaped mathematical description; C.30.TFS-REL when either is used by architecture.
Control or LCA viewC.30.LCA when a control structure view is being used.
Module or interface viewA.6.M, signature or interface patterns, and C.30.ASV when module-interface structure is being used.
Mathematical-lens viewC.29 for lens-use result and preserved and lost structure; C.30.AD only for the architecture-description use of the lens result.
Boundary, interface, or Markov-blanket viewA.1, A.6.RSIR, A.6.P, A.6.0, A.6.5, A.6.M, A.6.F, C.26, C.26.3, and C.29 according to the recovered claim; A.6.B only when the recovered object is L, A, D, or E statement classification inside a boundary package. C.30.AD records only exact description identity, description-set use, cross-view correspondence, source-to-use path when a source is used, an applicable stronger-use return condition, freshness, representation, or publication use.
Evidence or assurance reuse viewUse A.10, B.3, or the relevant evidence or assurance pattern for the non-architecture claim.
Architecture residual viewUse C.30.ILC for a cross-scope or interlevel architecture residual. C.30.AD records only the view episteme, its conformance, description-set use, correspondence to other views, and allowed use; add a source-use relation only when a source is actually used.
Multilevel-learning or frustration mathematical-lens viewC.29 when the view contains a recoverable level mapping or scale mapping and preserved structure and lost structure; C.30.AD records only the architecture-description use of that lens result.
Residual-reducing candidate or optimization viewUse C.32.MLAO for the residual-reducing multilevel candidate frame, C.32 for the candidate architecture palette, A.19.CPM or A.19.SelectorMechanism for comparison or selector-policy use, C.18 and C.19 for archive, front, or current-pool treatment, G.5 for selected-set result declaration, and C.11 for final local choice. Record with C.30.AD only the exact description identity, description-set use, cross-view correspondence, source-to-use path when used, applicable source-return condition, freshness, representation, publication use, or specification use.