A.6.3 - Episteme viewing - EntityOfConcern-preserving episteme construction
Status: Stable
Use this when. You need to derive a smaller, reorganized, or differently expressed body of claims from existing claims while keeping the same thing under discussion. In FPF terms, the source and result are independently identifiable epistemes with the same EntityOfConcern. The result may select, reorganize, normalize, translate, or combine claims from the named sources, but it must not add a claim those sources do not support.
First useful result. Write one source-to-result statement. For example:
Under the declared viewing rule, the claims in result Y are licensed by X together with any additional named sources and admitted facts required by that rule. X and Y are about the same named thing. Y keeps [named claims], omits [named claims], and adds no claim unsupported by those premises.
Then name or show the rule that selects, rewrites, or combines the claims. Do not call the construction an A.6.3 viewing unless X and Y can be identified separately and this rule can be inspected.
What this does not decide. A.6.3 says how Y is licensed by named sources about the same thing. It neither proves the claims true nor makes Y a U.View; use E.17.0 for view membership. Use A.15.1 for the work that produced Y, A.15.PROD if first constitution matters, and E.24.PUB for publication, but only when those separate facts matter.
Builds on: A.6.0 direct declaration structure; A.6.2 effect-free episteme morphing; C.2.1 episteme identity; E.17.0 viewpoint conformance and view membership; A.6.3.CR conservative retextualization; A.6.3.RT representation transition; A.6.4 retargeting; C.29 mathematical-lens use; A.13 Work basis; A.15.1 work; A.15.PROD local work/change/entity-identity-inception claims.
Used by: E.17 publication-face construction, E.17.0 multi-view describing, E.18 transformation-flow descriptions, and domain patterns that derive a smaller or differently expressed episteme from one or more source epistemes.
A.6.3:1 - Problem frame
Engineering work often needs a different body of claims about the same thing. Examples include a safety-focused slice of a system description, a normalized technical card, a conservative translation between notations, or a coverage view built from requirements and design epistemes plus stated correspondence claims.
Several neighboring facts can all be true but are not the same fact:
- X and Y are identified as C.2.1 epistemes;
- a declared viewing rule licenses Y’s claims from X and any additional named sources or admitted facts it requires;
- X and Y have the same EntityOfConcern;
- Y makes no stronger claims than the identified sources license;
- Y conforms to a viewpoint and is therefore a
U.View; - a system performed work that first constituted Y;
- Y was later published through a form and carrier.
Ordinary use may need only items 1 through 4. The remaining claims are opened independently.
A.6.3:2 - Problem
How can a project state how X and any additional named sources or admitted facts license Y under a viewing rule while making clear what was preserved, what was lost, and why Y adds no unsupported claim?
Keep that construction separate from the work that produced Y, any publication of Y, and any separate check that Y qualifies as a U.View.
Without this distinction, a query execution is treated as view membership, a generated file is treated as the episteme, a new claim is treated as a formatting change, or an EntityOfConcern change is treated as a same-entity projection.
A.6.3:3 - Forces
| Force | Tension |
|---|---|
| Conservativity vs usefulness | A receiving episteme may reorganize, summarize, or omit claims while adding no unsupported commitment about the EntityOfConcern. |
| Same concern vs changed expression | X and Y share one EntityOfConcern, while claim content or effective reference scheme may differ and therefore identify another episteme. |
| Algebraic composition vs actual work | Viewings should compose and replay as mathematical constructions, while systems and work occurrences remain separate. |
| Direct source vs several-source correspondence | Some constructions use X alone; others depend on relations among several source epistemes. |
| Viewing construction vs stable kind membership | Viewpoint conformance depends on Y and the viewpoint, independently of any source-to-Y viewing claim. |
| Lightweight assertion vs assurance | A readable source-to-receiving statement often suffices; disputed loss or correspondence requires declarations and evidence. |
A.6.3:4 - Solution
Local mantra. Identify X and Y. Hold their EntityOfConcern fixed. State the conservative construction and admitted loss. Add correspondence dependencies when used. Test U.View membership separately under E.17.0 only when the receiving use needs that membership.
A.6.3:4.1 - Identify both epistemes independently
Before declaring a viewing, recover for each of X and Y under C.2.1:
- claim content;
- EntityOfConcern;
- effective interpretation rules, identified under C.2.1:4.1.1 (
ReferenceScheme).
X and Y are separate epistemes whenever one of those identity discriminators differs. A filename, table, diagram, query result, viewpointRef, or publication form is not a substitute for either identity.
If the supposed receiving item has no recoverable claim content or EntityOfConcern, stop: the receiving episteme has not been identified. If the EntityOfConcern differs, use A.6.4 retargeting rather than A.6.3.
A.6.3:4.2 - Declare the viewing construction
A.6.3 viewing is a preserve-mode specialization of A.6.2’s local effect-free arrow class, subject to the viewing construction and laws below. In the selected formal substrate, one viewing arrow is written v : X -> Y and has source episteme X and receiving episteme Y.
The reusable A.6.0 declaration describes the admitted local arrow family, rather than turning one arrow or endpoint pair into a kind:
SubjectKind = local A.6.2 EpMorphism type restricted to preserve-mode viewing arrows
RangedValueKind = admitted ordered-pair range over U.Episteme values satisfying the declared endpoint-kind constraints
ResultKind = omitted; v is the declared subject and Y is its receiving endpoint
Applicability = selected formal substrate, admitted endpoint kinds, viewing-rule conditions, and preserve mode
EpMorphism is a local mathematical type in the selected substrate, not a durable FPF U-kind. The arrow records the declared construction from X to Y. Section 4.6 separately governs an account of its execution.
A viewing declaration states:
- X and Y;
- that
EntityOfConcern(X)=EntityOfConcern(Y); - the claim-content construction from X and any additional named sources to Y;
- how the source and receiving reference schemes are related;
- preserved claim components, admitted omissions or losses, and prohibited strengthening;
- applicability conditions and any fixed configuration needed for replay.
A separate assertion says whether this arrow supports one named receiving use and states any use-specific loss or conditions. If the current use needs an account of a query, rewrite, model, or other method being applied, identify that application and any admitted Work separately; v : X -> Y alone does not assert that they occurred.
A.6.3:4.3 - Apply the same-EntityOfConcern and conservativity laws
For every admitted v : X -> Y:
- Same EntityOfConcern. X and Y designate the same EntityOfConcern. Similar labels, bridge claims, or one shared project do not establish this equality.
- No unsupported strengthening. Every claim in Y is recoverable as a consequence, conservative re-expression, or explicitly admitted aggregation of claims in the identified sources under the declared reference and representation semantics. This includes claims about the EntityOfConcern and any asserted correspondence, evidence or evaluation facts.
- Declared loss. Every omitted concern or claim family that affects receiving use is named, together with the condition under which the loss is admitted.
- Reference discipline. A changed effective reference scheme is explicit. If the change alters available operations or representation semantics, use A.6.3.RT; apply C.29 when the transition uses a declared mathematical lens. Do not call such a change formatting.
- No hidden retargeting. Subsystem-to-system, method-to-work, model-to-modeled-system, or episteme-to-publication changes are not same-EntityOfConcern viewing.
For a lightweight check, take each claim in Y—or each group covered by one rule—and point to the source claims and the selection, rewriting or aggregation rule that licenses it. Mark omitted claim groups. If support cannot be established, leave that claim’s admissibility in the viewing unresolved; if the rule demonstrably introduces an unsupported claim, the proposed construction fails the viewing law. A structural or domain check used as an approximation states what it cannot establish. Add a proof when disagreement, risk or the receiving use requires one.
Truth of source claims is a separate evaluation. Conservativity says what Y is licensed to claim from the sources; it does not establish that those claims are true in the world or adequate for a decision.
A.6.3:4.4 - Keep optional viewpoint selection and view membership separate
For the current use of receiving episteme Y, name the describing use and viewpoint P only when that selection changes what the receiver reads or checks. Keep Y, its EntityOfConcern, the use, and P distinct. Selecting P is outside C.2.1 identity and does not make E.17.0 conformance obtain.
After Y is identified, apply E.17.0 only when the current use needs U.View membership:
EpistemeViewpointConformanceRelation(Y,P) obtains
-> the same episteme Y is a U.View
Directly authored Y can qualify as a view without establishing an A.6.3 source-to-Y construction. Conversely, a valid A.6.3 construction can yield Y that fails P’s concern-coverage or semantic-form rules and therefore is not a view under P.
A.6.3:4.5 - Distinguish direct and correspondence-mediated construction
Direct viewing. Y is constructed from X and fixed configuration only. The declaration names the claim selection or rewriting rule and any loss. No generic correspondence object is required.
Correspondence-mediated viewing. Y depends on several source epistemes or on relations between their claim-bearing contents. Recover each direct correspondence, realization, trace, equivalence, or consistency relation under its governing pattern before using it. Then identify the C.2.1 episteme that states or describes those relations if the construction must cite it.
Plain correspondence model may name that claim-bearing episteme. It is not a public U.CorrespondenceModel kind. A graph edge or table cell may state or support a correspondence claim; its presence does not establish that the relation obtains. Judge the content and any evidence under the relation’s governor and A.10. If a needed relation lacks a governor, return the missing-relation blocker or use A.6.RCD.
The viewing declaration cites the source epistemes and correspondence claims on which Y depends. If Y asserts facts about a correspondence episteme, evidence, or evaluation result, those assertions belong to Y’s claim content and follow C.2.1’s identity rule. The cited objects remain independently identified, and the assertions still require the support specified by the viewing law.
A.6.3:4.6 - Keep mathematical construction, work, production, and publication distinct
Describe querying, rewriting, modeling or rendering in ordinary practitioner terms. When the account claims a dated U.Work occurrence, establish its A.13 basis and A.15.1 admission; identify the system that performed the work and the method it used. The source epistemes, parameters, tools, and receiving entities participate only through their direct relations or A.6.1 operation bindings.
If that work first constitutes episteme Y and the identity-inception claim matters, A.15.PROD governs the local work/change/identity claim. Neither work nor inception establishes conservativity or E.17.0 conformance.
If Y is made available, E.24.PUB separately identifies the publication occurrence, expression, any selected reusable publication form, and independently identified carrier whose state or realization yields that expression. Publication neither creates the A.6.3 construction nor grants U.View membership.
A.6.3:4.7 - Preserve composition and replay
The selected formal substrate supplies the identities, admitted compositions, and arrow equivalence. For fixed source epistemes, rules, reference semantics, correspondence dependencies, and configuration:
- identity viewing preserves the same C.2.1 episteme;
- composing
f : X -> Ywithg : Y -> Zgives the admitted compositecompose(g,f) : X -> Zunder A.6.2 P3; - if a separately declared construction operation is deterministic, replay with the same admitted inputs yields the same receiving C.2.1 identity discriminators;
- random seeds, model editions, external service state, or timing that can change Y are explicit inputs to the work or declaration;
- a normalization repeat claim identifies
n_X : X -> Yand the next arrown_Y : Y -> Z, establishesZ = Yunder C.2.1, and witnessescompose(n_Y,n_X) ≃ n_Xunder the declared arrow equivalence. OneX -> Yarrow is self-composable only when X = Y.
A composition requires the middle episteme to match. A claim that two routes yield the same receiving episteme requires equality of all three C.2.1 identity discriminators; representation equivalence alone does not establish that identity. The repeat claim requires a fixture or proof under A.6.2 P4.
A.6.3:4.8 - Stop at the lightest sufficient statement
For ordinary use, this can be enough:
Safety summary Y is conservatively constructed from plant description X; both concern Plant-7; Y omits maintenance-cost claims and introduces no safety claim not recoverable from X.
Add a reusable declaration, explicit mathematical arrow, correspondence episteme, evaluation result, work occurrence, production claim, or publication objects only when a named receiving work or decision depends on that object.
A.6.3:5 - Worked cases
A.6.3:5.1 - Safety-focused system description
X is a system-description episteme about plant S. Y is a smaller episteme about the same S containing only safety-critical functions, hazards, and mitigations recoverable from X. The viewing declaration names the filter and omitted claim families. A.6.3 construction obtains. Y becomes a U.View only after safety viewpoint P is resolved and EpistemeViewpointConformanceRelation(Y,P) obtains.
A.6.3:5.2 - Directly authored view
Architecture episteme E is authored directly against maintainability viewpoint P and passes E.17.0 conformance. E is a U.View on that basis; no source-to-E viewing claim is needed for this result. A mathematical viewing relation may be established separately, including identity viewing on E. Any claim that the authoring used a source needs its own historical basis; the mathematical arrow does not supply it.
A.6.3:5.3 - Query result that fails conformance
Query Q constructs Y from source X while preserving the same system and making only licensed claims. Y omits one concern required by viewpoint P. A.6.3 construction is valid; E.17.0 conformance fails, so Y is not a view under P.
A.6.3:5.4 - Normalized publication card
X and Y are separately identified epistemes about morphism f. Y reorders claims and normalizes names without changing their interpretation. NormalizeTechCard : X -> Y is a direct viewing. For a repeat claim under the same scheme and normalization rules, identify the next normalization arrow n_Y : Y -> Z; establish Z = Y under C.2.1 and compose(n_Y, NormalizeTechCard) ≃ NormalizeTechCard under the substrate’s declared arrow equivalence, with a fixture or proof.
A later publication occurrence makes Y available through a TechCard form. Y is called U.View only if it conforms to the publication viewpoint; the form and carrier remain separate.
A.6.3:5.5 - Cross-model coverage
Requirements episteme R and design episteme D concern system S. Realization relations connect requirements to design elements. A correspondence assertion episteme states those occurrences.
Receiving episteme Y selects only requirements with an obtaining realization relation. A.6.3 records the correspondence-mediated construction from the sources to Y; the assertion episteme and matrix representation remain separate from the realization occurrences.
A.6.3:5.6 - Retargeting boundary
X concerns pump P-14. A proposed Y concerns the whole cooling skid. Even if every Y claim is derived from X plus neighboring descriptions, A.6.3 does not apply because the EntityOfConcern changed. If declaring a retargeting arrow, use A.6.4. For a claimed receiving use, separately state its invariant, visible loss, use conditions and affirmative or negative proposition; assess that proposition against case facts when a current-case judgement is needed.
A.6.3:6 - Consequences
| Gain | Cost or boundary |
|---|---|
| The source-to-result construction is inspectable without defining view membership. | X and Y must be independently identified before the construction is asserted. |
| Direct authoring and generated epistemes coexist. | A generated result needs a separate E.17.0 test before it can be called a view. |
| Correspondence-mediated constructions can use domain relations. | A graph or trace table must supply the relevant claims and grounds; its presence alone does not establish the relation. |
| Work and publication stay outside the mathematical construction. | Tool execution and availability require their own patterns when current. |
| Composition and any declared deterministic replay can be checked. | Composition needs matching endpoints and admitted laws. Uncontrolled state that can change Y prevents the corresponding repeatability claim for the construction operation; undeclared material loss prevents the corresponding receiving-use claim. |
A.6.3:7 - Rationale and SoTA-Echoing
| Source or practice line | Contribution | Boundary | Practical effect |
|---|---|---|---|
| Lenses, optics and compositional transformation research | Supply identity and composition structures; the selected viewing family adds its stated conservativity and loss conditions. | A mathematical construction does not itself establish that a world-side relation obtains. | Viewing arrows can be composed while operation applications, Work occurrences and world-side relations remain separately governed. |
| Bidirectional transformation and model-synchronization practice | Make cross-model correspondence dependencies explicit and test path agreement. | A record or graph must carry the required correspondence claims and grounds; its presence alone is insufficient. | Coverage and consistency viewing declarations cite their source relations, so broken dependencies can be repaired locally. |
| Model-based view-as-query practice | Treat query and projection as common construction routes. | Query execution does not establish E.17.0 conformance. | Generated and directly authored epistemes meet the same independent E.17.0 membership rule. |
| FPF C.2.1 and E.17.0 architecture | Keep episteme identity, viewing construction, conformance, evaluation, work, production, and publication separate. | — | The next engineering action can rely on the relation it needs. |
A.6.3:8 - Conformance checklist
- X and Y each have recoverable C.2.1 identity.
- X and Y have the same EntityOfConcern; otherwise the route is A.6.4.
- The declaration states the claim construction, reference semantics, applicability, preserved content, and admitted loss.
- Every claim in Y has the support required by the viewing law, including any claim about a correspondence, evidence or evaluation result.
- Every correspondence-mediated dependency resolves to source epistemes and governed direct relations.
U.Viewis asserted only after independent E.17.0 conformance.- A viewpoint selected for a named describing use is not used as membership evidence and does not enter X or Y identity.
- Systems, tools, work, parameters, and production claims are recovered separately when construction work matters.
- Publication occurrence, form, carrier, and rendering remain separate from X, Y, and v.
- Composition and declared loss satisfy their laws; any deterministic replay claim is tested under its stated conditions.
- Ordinary use stops without materializing objects the next work or decision does not need.
A.6.3:9 - Relations
- A.6.0 supplies the direct declaration structure used in A.6.3:4.2.
- A.6.2 supplies the effect-free morphism and composition discipline.
- C.2.1 identifies source and receiving epistemes.
- E.17.0 alone governs
U.Viewpoint, conformance, andU.Viewmembership. - A.6.3.CR governs conservative textual re-expression when wording and organization are the main change.
- A.6.3.RT governs same-EntityOfConcern representation transition with explicit recoverability and loss.
- A.6.4 governs a changed EntityOfConcern.
- C.29 governs a declared mathematical-lens use of the construction or correspondence, including a diagram used for that mathematical claim.
- A.13 supplies the basis for an explicit dated Work claim; A.15.1 and A.15.PROD govern its admission and any local entity-identity-inception or completion claim.
- E.24.PUB governs publication occurrence, form, and carrier.
- Use A.6.RCD when a needed correspondence relation lacks a governed expression.