E.17.0 - Viewpoint and View Recognition for Multi-View Describing
Status: Stable
At a glance. Use E.17.0 to decide whether one identified engineering account is a view under the existing viewpoint you are testing. Test the viewpoint’s rules even when the account’s label, layout, generation history, bundle position or publication suggests it is a view.
Use this when. A description, model slice, query result, diagram, or other claim-bearing episteme is being called a functional, safety, maintenance, architecture, or other view, and the next reading, comparison, construction, or publication depends on whether that claim is warranted.
What goes wrong if missed. A viewpointRef, familiar face name, generated table, or readable diagram is accepted as a view without testing the viewpoint’s concerns and rules. The opposite failure is to rebuild a viewpoint convention, bundle, evaluation package, and publication dossier before an ordinary reuse can proceed.
What this buys. One stable test works for directly authored and derived epistemes. Identify the candidate E, resolve the viewpoint edition P, and test P’s fixed conformance predicate. Both epistemes retain their identities.
First action. Recover candidate E through C.2.1, resolve an existing U.ViewpointRef to P, and read the target, concern-coverage, semantic-form, completeness, consistency, and admitted-omission rules fixed by P. Do not author a new viewpoint or bundle merely to perform this test.
First useful result. State one readable judgment: either episteme E conforms to viewpoint edition P, in which case the same E is a U.View, or E does not conform to P, naming the failed fixed rule without inventing a negative relation occurrence. Keep the identities of E and P recoverable. If missing identity or interpretation prevents the fixed predicate from being evaluated, report the unresolved condition rather than manufacturing a negative result.
Ordinary stop. If the next work needs only view recognition, stop after that judgment. Add an occurrence designator, explicit result ValueKind, evaluation package, source-viewing relation, correspondence model, collection or structure, publication occurrence, form, or carrier only when a named receiving use depends on it.
Tech-name:
MultiViewDescribingPlain-name: recognizing viewpoints and views in multi-view describing
MultiViewDescribing names this pattern’s method. It is not a public U-kind, a family record, or an extra entity beside the epistemes and relations recovered below.
Builds on: C.2.1 for episteme identity; C.13 for collections; A.22 for selected structures; A.6.5 for relation-signature participant SlotSpecs; A.6.3 for an optional source-to-view construction relation; C.2.1:6 for description and specification use, with E.10.D2 for naming; E.24.PUB for publication; A.6.3.RT/A.6.3.RT.OE for expression construction and C.29 for mathematical representation.
Used by: E.17 publication, E.17.1 viewpoint bundles, E.17.2 TEVB, E.18 transformation-flow descriptions, and domain patterns that compare several views.
E.17.0:1 - Problem frame
An engineer may have several claim-bearing epistemes about one system, method, structure, work occurrence, or another identified entity. A functional description, safety description, maintenance description, and allocation description may serve different concerns. One episteme may also be constructed from another by a query or projection, rendered in several forms, published several times, or compared with another view.
Those uses involve different objects and relations:
- the EntityOfConcern of each episteme;
- the episteme itself, identified under C.2.1;
- a
U.Viewpointepisteme carrying fixed concerns and conformance rules; - an obtaining
EpistemeViewpointConformanceRelationoccurrence; - dependent
U.Viewmembership of the same episteme individual; - an optional A.6.3 viewing relation recording how one episteme was constructed from another;
- an optional viewpoint selected for one current describing use when it changes what that use reads or checks or may conclude;
- exact correspondence relations and epistemes that assert or describe them;
- publication occurrences, forms, carriers, and representations.
Use the list to choose the distinctions your task needs. Ordinary positive recognition needs items 1 through 5; a negative test stops without an obtaining conformance occurrence or U.View membership. Construction, selection, correspondence, and publication stay outside unless the receiving use calls for them.
E.17.0:2 - Problem
How can an engineer recognize and use views under explicit viewpoints while preserving exact episteme identity and direct relation semantics, without treating a selected viewpoint, a query result, a diagram, a family label, or a publication as what makes an episteme a view?
A common error is using the wrong object to justify the next action. For example, an engineer may accept a table as a view because it was generated, accept a published diagram because it is readable, or treat a viewpointRef as proof of conformance. Calling a package of documents a multi-view model without recovering a cross-view relation makes the same mistake.
E.17.0:3 - Forces
| Force | Tension |
|---|---|
| Lightweight use vs inspectable assurance | Most uses need one readable conformance judgment; contested use needs exact participants, predicate, occurrence identity, evaluation, and warrant. |
| Stable kind membership vs changing use | An episteme can remain a view after a reading, project, publication, or selected-use episode ends. |
| Direct authoring vs derivation | Some views are authored directly; others are constructed through a query or projection. Construction history must not define view membership. |
| Self-contained viewpoint vs reusable convention structure | One P can carry the complete fixed test; separate C/Q/S is useful only when convention components and their organization vary independently and change a named reuse, comparison, or maintenance action. |
| Several views vs one invented container | Multi-view work needs organization and correspondence, but a package, graph, or shared heading does not establish either. |
| Readable domain language vs ontological precision | Practitioners need functional view and safety view; load-bearing use still needs exact epistemes and direct relations. |
| Correspondence vs consistency repair | A correspondence can obtain while later evaluation finds an inconsistency or while repair work is still pending. |
| View vs publication | A view can be unpublished, and one view can be published repeatedly through different forms and carriers. |
E.17.0:4 - Solution
Recognition test. Identify the candidate episteme. Resolve the existing viewpoint episteme. Test their fixed conformance predicate. If it obtains, recognize the same episteme as a view; if it fails, name the failed rule and stop or repair. Add construction, selection, correspondence, evaluation, or publication only for the current use.
See §§4.1–4.11 for the object distinctions, obtaining rules and stopping conditions behind this reminder.
E.17.0:4.1 - Identify the candidate episteme before calling it a view
Recover candidate E : U.Episteme through C.2.1:
- claim content;
- EntityOfConcern
T; - effective
ReferenceScheme.
These three discriminators identify E. A layout, file, query run, viewpointRef, selected project context, publication form, or carrier does not add another episteme identity discriminator.
Recover a diagram element or graph node under the chosen representation and its correspondence, adding C.29 when a mathematical lens is used. Recover a publication form or carrier under E.24.PUB. Do not promote it to an episteme or view by appearance.
E.17.0:4.2 - Resolve one exact viewpoint episteme
U.Viewpoint is a same-individual dependent durable kind under U.Episteme. One viewpoint P is the same individual as a C.2.1 episteme.
P has one C.2.1 EntityOfConcern. In the ordinary self-contained branch it is the exact independently admitted durable or local target kind whose membership criterion P uses. For a local kind, recover which candidates it can classify, what intended members must satisfy, what separates relevant non-members, and when a changed declaration still describes the same kind. A practice or source boundary helps find and compare that membership rule; it does not decide kind identity.
Only when separately versioned convention components and their organization change a named reuse, comparison, or maintenance action is P instead about the selected S_viewpoint : U.Structure. Neither branch introduces a new public kind or organization record.
Existing-P route. Resolve one current U.ViewpointRef to P and inspect P’s fixed target criterion, admitted kinds, concern coverage, semantic-form, completeness, consistency, and omission rules. Do not reconstruct P’s constituent collection or authoring history merely to use the already admitted edition.
E.17.0:4.3 - Run the ordinary E/P route contiguously
- Identify the candidate episteme E under C.2.1.
- Resolve the existing viewpoint edition P and its fixed rules.
- Apply the five-condition test in §4.4 to fixed
<E,P>. - State exactly one readable result: positive, negative with the failed fixed rule, or unresolved with the missing identity or interpretation.
- Stop unless a named receiving use triggers exact occurrence designation, warrant, new-viewpoint authoring, evaluation, selection, construction history, multi-view organization, or publication detail.
E.17.0:4.4 - Test the direct conformance relation and state the result
EpistemeViewpointConformanceRelation is a direct species of U.Relation. Plainly: the episteme conforms to this exact viewpoint.
Its only two participants are independently identified before the test:
- candidate episteme
E : U.Episteme; - viewpoint episteme
P : U.Viewpoint.
EpistemeViewpointConformanceRelation(E,P) obtains exactly when:
- E is one independently identified episteme and P is one independently admitted viewpoint episteme;
T := EntityOfConcern(E)is recovered only from E’s C.2.1 constitution;- T satisfies P’s fixed
EntityOfConcernKindCriterionthrough the cited public durable-kind membership rule or the direct identity and membership rule of one exact independently admitted local kind; an exact C.3.2KindSignatureedition and one exactU.ContextSliceare separate test inputs only when P’s local membership test needs them; - E has at least one independently admitted episteme kind referenced by P’s admitted-kind claims, excluding
U.Viewand every kind whose membership depends on this same conformance; and - E’s fixed claim content, interpreted under its effective reference scheme, satisfies P’s fixed concern-coverage, semantic-form and consistency rules, including each completeness rule and each admitted omission or loss condition named by P.
T is recovered from E, not guessed from a use qualifier, topic, P, label, reference spelling, or evaluator input, and it is not a hidden third participant. Changing T changes E.
Changing P’s target criterion, admitted target kind or cited membership rule, any exact KindSignature edition or U.ContextSlice named as a separate test input, admitted-kind claims, or conformance rules changes P.
State the result immediately after the five tests:
- positive: all five conditions hold, so the pair-determined positive relation occurrence obtains and the same E is a
U.Viewrelative to P; - negative: at least one evaluable fixed condition fails; name that condition, do not mint a negative relation occurrence, and do not claim
U.Viewmembership through P; - unresolved: missing or ambiguous E identity, P identity, kind criterion, local sense, or interpretation prevents evaluation; name that missing condition and claim neither positive nor negative conformance.
Ordinary stopping rule. Stop with that readable result when the next work needs neither an exact occurrence designator nor warrant. Add an occurrence designator, assertion episteme, evaluation episteme or local result value, evidence path, work record, or decision-use episteme only for the named receiving need. A readable assertion is distinct from occurrence identity.
For fixed E and P, one positive occurrence is participant-determined by <E,P>. Discovering, warranting, or using the judgment may involve a classifier, evaluation work, assertion, evidence path, result value, operational state, publication, audience, current use, or newly selected slice; none adds a participant or identity discriminator to the conformance occurrence.
If conformance could change while E and P remain fixed because another current object changed, route that condition to a separately identified adequacy or evaluation claim or reopen the relation architecture.
Conformance covers E’s semantic content relative to P’s fixed convention claims. Truth about T, decision fitness, stakeholder satisfaction, evidence-backed adequacy, publication usefulness, and operational usefulness remain separate evaluations. Evaluation never makes the direct predicate obtain or produces another occurrence for the same fixed pair.
E.17.0:4.4.1 - Exact declaration and public designation of conformance
EpistemeViewpointConformanceRelationSignature is a separate RelationSignature episteme about the direct kind and declares exactly:
| SlotSpec | ValueKind | RefKind |
|---|---|---|
CandidateEpistemeSlot | U.Episteme | U.EpistemeRef |
ViewpointEpistemeSlot | U.Viewpoint | U.ViewpointRef |
The declaration, SlotSpecs, references, and relation-participant designations alone do not establish that the relation obtains. Its positive occurrence is identified by the E/P pair under the fixed predicate. P remains the ordinary episteme about its C.2.1 EntityOfConcern; P is not this signature.
The F.18 NameCard for the direct conformance kind identifies its naming settlement and current F.17 public row:
| Field | Exact value or rule |
|---|---|
NameCardId | NameCard.EpistemeViewpointConformanceRelation.FPFPublic; card identity only |
GovernedValueRef | exact direct kind EpistemeViewpointConformanceRelation, not a source line, card, signature, token, phrase, occurrence, or reference |
GovernedValueKindRef | U.Kind; this is the kind of the governed value, not another value reference |
SubjectPatternLocator | E.17.0, locating the exact defining and occurrence-identity claims; F.18 separately constrains naming, A.6.5 declares SlotSpecs, and E.24.UK admits the dependent kinds |
ReferenceScheme | exact by-value FPFCoreReferenceScheme |
ClaimContent | NameCard.EpistemeViewpointConformanceRelation.FPFPublic.ClaimGraph, constituted by all identity-bearing naming-settlement claims in this table |
LocalSenseCellRef | SenseCell.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02 |
LocalSenseBasisRelationRef | LocalSenseBasisRelation.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02 |
TechLabel | EpistemeViewpointConformanceRelation |
PlainLabel | the episteme conforms to this exact viewpoint |
CandidateSet | selected label, EpistemeConformsToViewpointRelation, ViewpointConformanceRelation, ViewConformanceRelation, EpistemeViewpointGovernanceRelation, ViewpointGovernanceRelation, ViewMembershipRelation, viewpoint-to-description relation |
RejectedCandidates | shorter conformance names hide a participant or assume view membership; governance collapses selection with semantic conformance; membership names the derived classification; the description placeholder narrows arbitrary episteme and omits the predicate. None is an alias. |
SelectionRationale | the selected Tech label names both participant kinds and the obtaining predicate without presupposing that E is already a U.View |
BridgeRefs | none; this naming settlement makes no semantic-correspondence or substitution claim |
PublicRowStatus | current |
UnifiedTermRowRef | UTS.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02 |
LineageEntries | the selected name replaces viewpoint-to-description relation without admitting that placeholder as a synonym or second public designation |
RefreshCondition | reopen only when either participant kind, the conformance predicate, direct occurrence identity, exact scheme/cell/basis/row reference, or repeated reader evidence changes; not for spelling preference, one reaction, layout, repackaging, or unchanged semantics |
The card, label, candidate list, and former placeholder are naming evidence only. None is relation admission, occurrence identity, or proof of obtaining.
E.17.0:4.5 - Recognize the same episteme individual as U.View
An episteme is a U.View exactly when EpistemeViewpointConformanceRelation(E,P) obtains for at least one viewpoint P. This is same-individual dependent-kind membership of E under U.Episteme, not a second view individual, wrapper, form, carrier, result value, or identity discriminator.
One unchanged E may conform to zero, one, or several viewpoint editions through different pair-determined occurrences while remaining one episteme.
Direct authoring and A.6.3 construction—including identity viewing—are separate histories: either may be present or absent, and neither grants membership. Selection, transformation, bundling, naming, rendering, publication, audience, or current use also grants none.
Membership survives the end of reading, selection, use, evaluation, bundle membership, or publication.
P_old and P_new are different C.2.1 epistemes when they differ in fixed claims, effective scheme, or exact EntityOfConcern—the target kind in the self-contained branch or selected S in the structured branch; an obtaining EpistemeEditionRelation relates them but transfers no conformance. A current use may select P_new while unchanged E still conforms to P_old; adequacy and conformance for <E,P_new> are judged separately.
If E’s claim content, EntityOfConcern, or effective scheme changes, C.2.1 identifies another episteme and its membership is judged anew.
E.17.0:4.6 - Author or revise a reusable viewpoint only when existing P cannot serve
New-viewpoint authoring has two branches. Use one self-contained viewpoint episteme P by default. Open the convention-structure branch only when separately versioned convention components and their organization change reuse, comparison, maintenance, or another named action independently of P’s fixed conformance claims.
Two viewpoint-authoring tasks.
| Smallest useful authoring task | Self-contained P | C/Q/S/A.22 branch | Action-changing result |
|---|---|---|---|
| A maintenance lead needs a viewpoint for short pump-status descriptions: the candidate must concern an admitted Pump, state operating state and observation time, cite the source reading, and may omit maintenance history. | One P about the admitted Pump kind carries those fixed concerns, allowed episteme kinds, completeness rule, admitted omission, and use frame. The lead can issue U.ViewpointRef(P) and immediately test candidate E. | Splitting the same four rules into constituent epistemes, C, Q, selected relations, and S adds objects and selection work but changes no reuse, comparison, maintenance, or conformance action. | No independently varying fact or receiving action exists; use self-contained P and do not create C, Q, S, or A.22 selection. |
| Several viewpoint editions reuse separately versioned measurement, reference-plane, and safety-terminology convention epistemes. A base-edition change must identify every dependent P requiring comparison or maintenance. | Copying those conventions into each P hides shared edition dependence and makes change-impact comparison manual. | Exact constituent editions, obtaining dependency relations, Q, and selected S make the shared organization and affected-P query recoverable. | The independently varying base edition changes the maintenance and comparison action; this is a valid convention-structure trigger. |
The first row sets the ordinary architecture. The second demonstrates the narrower case in which structure pays for itself. Formality, assurance, or the wish to make a diagram does not trigger the second branch.
E.17.0:4.6.1 - Author the smallest self-contained viewpoint episteme
Identify the independently admitted target kind K_target that the candidate epistemes’ EntitiesOfConcern must satisfy. For a local kind, recover its candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule. Use a practice or source boundary only to find or compare that membership rule. Use an exact C.3.2 KindSignature edition and U.ContextSlice only as separate inputs when the membership test needs them.
Constitute P under C.2.1 as <ClaimGraph(P), K_target, ReferenceScheme(P)>; the target kind is P’s EntityOfConcern because P states how epistemes about members of that kind are to be read. P’s fixed ClaimGraph:
- states the target-kind criterion and cites its direct authority;
- names stakeholder or audience referents only when they change the concerns, and states the concerns;
- names the independently admitted episteme kinds allowed for candidate E;
- states fixed concern-coverage, semantic-form, completeness, consistency, omission, and conformance rules without circular use of
U.View; and - states the describing-use frame and fixed applicability qualifiers needed to interpret those rules.
The same episteme P is admitted as U.Viewpoint when those five claim-content conditions hold under its effective scheme. No parent U.Signature, C.13 collection, Q, selected S, A.22 work, organization record, or evaluation result is required. Changed P claim content, target-kind EntityOfConcern, or effective scheme identifies another P edition; packaging, publication, evaluation, representation, or current-use selection does not.
E.17.0:4.6.2 - Add a viewpoint-convention structure only when it changes action
Use the structured branch only when at least two convention components remain independently identified or versioned and their obtaining dependencies or organization change a named reuse, comparison, maintenance, or joint-interpretation action. Mere decomposition, citation, co-membership, a graph, or future possibility is insufficient.
Construct C_viewpoint under C.13 from the exact constituent episteme editions. The collection may be heterogeneous: its invariant is exact constituent identity, not uniform declaration power. Give each constituent the least-powerful independently admitted kind that carries its claims.
| Constituent | Admit it when | Exact subject and practical job | Do not collapse it with |
|---|---|---|---|
E_target | A target-kind criterion is current. | One C.2.1 episteme whose EntityOfConcern is the admitted target kind and whose claims cite the direct identity and membership rule. For a local target, those claims state which candidates it can classify, what intended members must satisfy, what separates relevant non-members, and when a changed declaration still describes the same kind. A practice or source boundary only helps find or compare that membership rule. An exact C.3.2 KindSignature edition and U.ContextSlice remain separate test inputs when the receiving membership judgment needs them. Use another U.Signature only when the criterion is itself a reused declaration with vocabulary, laws, and applicability. | a raw kind reference, target mention as membership proof, a local KindSignature or ContextSlice substituted for the target kind, or a wrapper Signature around a local declaration |
E_stakeholder.system[i] | The concern names one stakeholder system. | One C.2.1 episteme whose EntityOfConcern is the independently admitted U.System. | system mention, stakeholder-family typing, a current system-role assignment, or the episteme substituted for the System |
E_stakeholder.systemRoleKind[i] | The concern addresses Systems classified under one exact local system-role kind. | One C.2.1 episteme whose EntityOfConcern is that local U.Kind; its claims state which admitted Systems are candidates, what work-facing condition intended members must satisfy, what separates relevant non-members, and when a changed declaration still describes the same kind. A practice or source boundary only helps find or compare that membership rule. They may cite the current KindSignature edition and U.ContextSlice as separate classification-test inputs when the receiving use needs them. A reusable reference field ends in ...SystemRoleKindRef and is typed by U.KindRef. Classification judgments and actual assignments remain separate. | bare role spelling, KindSignature, classification judgment, holder reference, assignment occurrence, or responsibility |
E_stakeholder.systemRoleAssignment[i] | One exact obtaining assignment occurrence changes the concern. | One C.2.1 episteme whose EntityOfConcern is that occurrence under a directly declared species of U.SystemRoleAssignment. A reusable reference field ends in ...SystemRoleAssignmentRef and is typed by U.RelationRef constrained to U.SystemRoleAssignment. | local kind, holder System, assertion or description of the assignment, assignment spelling, or responsibility |
E_stakeholder.collection[i] | Several exact Systems jointly form the concern referent. | One C.2.1 episteme whose EntityOfConcern is the independently identified C.13 collection-as-whole. | list adjacency, one System, local system-role kind or assignment, the member plurality, or a description substituted for the collection whole |
E_stakeholder.localKind[i] | The concern quantifies over one exact local kind. | One C.2.1 episteme whose EntityOfConcern is the independently admitted local kind. Its claims state which candidates it can classify, what intended members must satisfy, what separates relevant non-members, and when a changed declaration still describes the same kind. A practice or source boundary only helps find or compare that membership rule. An exact C.3.2 KindSignature edition and U.ContextSlice remain separate inputs only when a classification judgment is current. If the concern later relates this kind to another exact local kind, ask the C.3.3 relation question separately. | a wrapper Signature, raw class spelling, KindSignature or ContextSlice substituted for the kind, silent public-kind promotion, or a local extension treated as universal |
E_concern[i] | One question or concern claim is needed. | Ordinarily one C.2.1 episteme about one independently identified entity. It states what a conforming episteme must address. Promote it to U.Signature only when the concern predicate itself is a reused declaration with vocabulary, laws, and applicability. | a public U.Concern, unresolved EntityOfConcern, one-use question inflated into a Signature, or a concern label |
E_admittedKind[i] | One independently admitted episteme kind may enter conformance. | One C.2.1 episteme that cites the exact kind and the rule that admits its members; an exact local KindSignature may itself be the constituent. | a raw label or reference, admission by citation, a local wrapper, circular U.View admission, or the reference substituted for the membership rule |
E_rule[i] | A construction, interpretation, coverage, semantic-form, completeness, consistency, or omission constraint is current. | Ordinarily one C.2.1 episteme stating the constraint about its EntityOfConcern. Use U.Signature only for reusable declaration content with vocabulary, laws, and applicability; use U.MethodDescription only when the claims describe one independently admitted method as a way of doing. | every rule coerced to Signature, procedural appearance as method-description admission, missing exact subject, or one-use constraint inflated with declaration fields |
D_method[i] | A method-based convention is current. | One A.3.2 U.MethodDescription whose EntityOfConcern M_method[i] independently passes A.3.1. The description supplies the convention; the raw method stays outside C_viewpoint. | method mention as membership, raw method as constituent, several descriptions inferred to form one workflow, or description as performed work |
Preserve every exact edition. A concern question, kind citation, or one-use rule acquires none of SubjectKind, RangedValueKind, Vocabulary, Laws, or Applicability merely to fit a common table. Conversely, a constituent that independently is a reusable relation declaration, kind declaration, or method description keeps that stronger admitted kind. Collection position grants no convention job and no stronger membership.
For this branch:
- identify the least-powerful constituents above;
- construct
C_viewpointfrom those editions under C.13; - recover each selected direct relation occurrence using the pattern that defines its obtaining test and occurrence identity;
- identify ordinary constraint episteme
Q_orgaboutC_viewpointand the admissible describing-use frame; - have an exact system use the applicable A.22 selection method over C, selected obtaining occurrences, applied Q constraints, and the use frame, yielding exact
S_viewpoint; and - constitute P under C.2.1 with
EntityOfConcern(P)=S_viewpointand the same five fixed claim-content conditions from §4.6.1.
In this branch, changed P claim content, S, or effective scheme identifies another P edition. S is not U.Viewpoint; P is the claim-bearing individual. No viewpoint record, wrapper, organization object, context entity, bundle position, package ID, publication grouping, or parent U.Signature grants membership.
When the action-changing trigger disappears, use or author self-contained P rather than preserving C/Q/S as ceremonial structure.
E.17.0:4.6.3 - Keep explicit evaluation values optional
The fixed E17ViewpointSemanticsSlice@FPFEdition selects the exact FPF and E.17.0 declaration editions, effective ReferenceScheme, and Γ_time. In that slice the admission predicates defined here permit exactly two optional C.3.2 local ValueKinds, each carried by its own C.2.1 KindSignature episteme:
| Local ValueKind | Exact extension | Admit an explicit value only when |
|---|---|---|
KS.ViewpointConformanceValue.E17, carrying KindSignature(ViewpointConformanceValue@E17) | the two values designated conforms and doesNotConform | separately performed conformance-evaluation work emits the value and a named A.21 gate or C.11 comparison/selection decision consumes it |
KS.ViewpointOrganizationSatisfactionValue.E17, carrying KindSignature(ViewpointOrganizationSatisfactionValue@E17) | the two values designated satisfiesOrganization and doesNotSatisfyOrganization | separately performed candidate-structure evaluation emits the value and a named C.11 comparison or selection decision consumes it |
The four values remain distinct from their designators. Each KindSignature declaration states its admitted value domain and exact-equality predicate with a fixed interpretation under C.2.3. That predicate determines membership. The kinds have no SubkindOf, and definedness fails closed. Incomplete evidence or interpretation leaves the optional evaluation unsupported or undefined; it supplies neither a negative result nor a third unknown member.
Omit both local values from P, direct relation obtaining, and—when the structured branch is active—Q_org and structure identity unless the named consumer needs one. Without such a consumer, state the direct conformance judgment or the structured branch’s Q_org constraint judgment.
E.17.0:4.6.4 - In the structured branch, state Q_org and select S without hidden organization
Q_org is one ordinary C.2.1 constraint episteme with EntityOfConcern(Q_org)=C_viewpoint. Its ClaimGraph carries the applied semantic constraints under its effective reference scheme and the named admissible describing-use frame. Q is not C, a selected relation occurrence, S, P, a result value, Signature, MethodDescription, organization record, actor, or method.
When the structured branch is triggered, Q carries these eight organization constraints by value:
- One target criterion. Select exactly one
E_targetby its claim content and cited target-kind membership rule; a raw kind label, viewpoint name, or collection position proves neither selection nor membership. - Concerns depend on the target. Every
E_concern[i]depends onE_target. When stakeholder attribution changes the concern, cite one exact stakeholder referent recovered as an independently identified System, local system-role kind, obtaining system-role assignment, collection-as-whole, or another exact local kind whose members are the concern referents. A responsibility claim remains a separately defined direct relation and never follows from the kind or assignment. - Coverage depends on the concerns and claim families it evaluates. Each coverage constraint depends on the concern constituents and claim families it evaluates; a heading, graph edge, unresolved family label, or coverage result is neither the dependency nor proof of coverage.
- Semantic form depends on the admitted kind. Each semantic-form constraint depends on the independently admitted-kind constituent to which it applies; notation, form, or a raw kind reference grants no admission or dependence.
- Method conventions depend on the method descriptions they use. Each method-based convention depends on one
D_method[i]whose EntityOfConcern is an independently admitted A.3.1 method. The raw method remains outside C, and description, method, dependence, and performed work remain distinct. - Completeness, consistency, and omission name their subjects. Each such constraint depends on the concern or claim components it constrains and names any admitted omission condition by value; a bare status or whole-P label is insufficient.
- Resolution does not establish a relation. Resolve every designation and reference under the effective scheme, while keeping spelling equality, lookup, graph adjacency, compatible schemes, token presence, and reference resolution from counting as direct-relation obtaining.
- No circular view admission. No admitted-kind constituent may depend on
U.Viewmembership or the same conformance judgment being established. Every mutually dependent group needs one named joint-interpretation method or fixed-point criterion.
Replay mutually dependent groups through stratified or witnessed joint/fixed-point semantics. Without that witness, the candidate fails the A.22 selection criterion for the named use. A graph, strongly connected component, iteration syntax, or fixed-point diagram is at most a C.29 representation of already judged occurrences and semantics; it is not the witness, criterion, or selected structure.
An identified System uses the applicable A.22 structure-selection method over C, the obtaining occurrences r_1,...,r_n, the applied Q constraints, and the admissible-use frame. The symbols r_1,...,r_n are local notation, not an O object or collection kind. The selection yields S under A.22; C remains the C.13 collection, and each r retains the predicate and occurrence identity defined by its relation pattern.
Identity and change stay local:
- Q changes only with its claim content, C as its EntityOfConcern, or effective reference scheme; another graph, form, carrier, representation, or publication leaves the same Q edition unchanged.
- Replacing a selected obtaining occurrence changes the organization used to identify S. Replacing only its assertion, occurrence description, D, J, result, production or use relation, provenance, or graph leaves that occurrence unchanged, although use-specific admissibility may need reevaluation.
- S changes when C, any selected obtaining occurrence, the applied semantic constraint set, or the admissible-use frame changes. Replacing only Q while those discriminators remain semantically unchanged leaves S unchanged.
- In the structured branch, P changes only with its fixed claim content, S as its EntityOfConcern, or effective reference scheme. In the self-contained branch, the target kind replaces S as that discriminator. P is neither its EntityOfConcern, a reference, a bundle position, a publication object, nor an evaluation result.
Resolve P’s target criterion, admitted kinds, coverage, semantic-form, completeness, consistency, and omission rules through exact constituent claims and selected obtaining occurrences cited by P. Do not leave them as untyped fields, mandatory Signature constituents, or graph edges treated as occurrences.
In the structured branch the selected public individual is episteme P about S. These nearby alternatives remain rejected:
- S is not
U.Viewpoint: consumers require the claim-bearing edition P, whileEntityOfConcern(P)=S. - An episteme about one method is a neighboring
U.MethodDescriptiononly when M and that description independently pass A.3.1 and A.3.2; it is not the viewpoint genus. A method-description constituent does not retarget P from S to M. - No viewpoint record, wrapper, organization object, context entity, or non-entity value is needed; P, S, C, and selected relation occurrences already exhaust the identity-bearing objects.
- A catalogue or local family-declaration position, catalogue edition, package ID, or publication grouping does not constitute P or grant membership.
- P requires no parent
U.Signature, is not a public C.3 local kind, and is notEpistemeViewpointConformanceRelationSignature. A reusable kind declaration, a local-kind classification judgment, and a direct-relation declaration are different jobs with different subjects.
U.Viewpoint is therefore the same P under the complete positive predicate above.
E.17.0:4.6.5 - Author progressively and stop at the needed assurance
Use as much of the authoring path as the new viewpoint needs. For self-contained P, identify target kind, constitute P with the five fixed claim-content conditions in §4.6.1, apply the positive viewpoint-membership predicate, and mint or reuse U.ViewpointRef. For the structured branch only:
- identify every constituent edition and state each proposed dependent-to-base claim readably;
- resolve both endpoint designations, apply the direct obtaining criterion, and construct C from those editions under C.13;
- add D only for a named A.22 selection-use claim, and J or evaluation only when that receiving use needs the additional assurance;
- apply the Q constraints and have an identified System use the applicable A.22 selection method over C and the selected obtaining occurrences, producing S; and
- identify ordinary episteme P about S, apply the positive viewpoint-membership predicate, and only then mint or reuse
U.ViewpointRef.
Citation, collection membership, graph adjacency, and displayed edges never close step 2. Selection identifies an existing selected object; it does not construct another constituent episteme. Viewpoint authoring requires neither five fixed stages, one composite method, empirical/formal evaluation, nor J.
Identify every cited method under A.3.1 and use B.1.5 only when an order-sensitive method whole independently obtains. Stop as soon as the named receiving use is served; add no assurance artifact merely because a longer path exists.
E.17.0:4.7 - Keep viewpoint-convention dependence direct
Use ViewpointConventionDependencyRelation(E_dependent,E_base) only when interpreting or replaying the fixed claims of dependent constituent episteme E_dependent depends on an exact criterion, law, public name, or method claim carried by base constituent episteme E_base, and replacing that base edition or making the content used by the dependent episteme unavailable can change the interpretation or replay. It is the A.6.6 base-dependence case specialized to viewpoint-convention constituents.
Citation, co-membership, reference resolution, compatible schemes, or a graph edge alone does not establish this predicate. For fixed endpoint editions, one positive occurrence r is participant-determined by <E_dependent,E_base>. Scope, time, status, evaluator, evidence, result, use, selection, representation, and publication are neither participants nor occurrence-identity discriminators.
ViewpointConventionDependencyRelationSignature is a separate RelationSignature episteme about the direct relation kind. It declares exactly:
| SlotSpec | ValueKind | RefKind |
|---|---|---|
DependentConstituentSlot | U.Episteme | U.EpistemeRef |
BaseConstituentSlot | U.Episteme | U.EpistemeRef |
The SlotSpecs declare reusable participant meanings and polarity. Their declaration does not make the relation obtain or identify an occurrence.
The current A.6.6 vocabulary resolution chain is viewpointConventionDependsOn -> current vocabulary entry -> ViewpointConventionDependencyRelationSignature -> its EntityOfConcern, ViewpointConventionDependencyRelation. The NameToken, its separate NameCard, vocabulary entry, signature episteme, direct kind, and occurrence remain distinct; spelling or citation proves none of them equivalent and makes no occurrence obtain.
E.17.0:4.7.1 - Local designation of the direct relation kind
Within this pattern, ViewpointConventionDependencyRelation designates semantic dependence of one exact viewpoint-convention constituent episteme on one exact base constituent episteme, dependent first. Replacing the base edition or losing its exact used content can change interpretation or replay. The Plain designation is “this viewpoint-convention constituent depends on that exact base constituent.” The signature above retains the participant meanings and polarity.
E.17.0:4.7.2 - Add only the neighboring object the receiving use needs
The compact positive statement may stop at “this exact constituent depends on that exact base constituent.” Add the following objects only under their positive trigger; do not flatten them into one witnessed-base record or add their fields to the two-participant relation.
| Object | Positive trigger and exact identity | Boundary |
|---|---|---|
A_dependency | a separately reviewable readable assertion is needed: one C.2.1 assertion episteme whose EntityOfConcern is E_dependent and whose claims state the direct predicate for E_base | authoring does not make r obtain; A is neither r, an occurrence description, nor a third participant |
O_dependency | an already recoverable r needs a separate description: one C.2.1 description episteme whose EntityOfConcern is r and whose claims may state endpoints and participant-determined identity | the description is not r, and endpoint mention without independently recoverable r is insufficient |
D_dependencyUse | one named A.22 structure-selection judgment needs a reviewable claim that r is admissible: one C.2.1 episteme identified through obtaining EpistemeConstitutionRelation(G_dependencyUse,r,S_decl), where G is its claim content in the NonemptyClaimContent range, r is its EntityOfConcern, and S_decl is its effective ReferenceScheme | D is not G, r, S_decl, an assertion, occurrence description, U.Signature, RelationSignature, selected structure, actor, or third dependency-relation participant; the participant triple does not constitute itself, and obtaining r does not entail use-specific admissibility |
J_dependency | that named selection judgment needs inspectable inferential support | J is non-constitutive justification content, distinct from G; it carries the inferential account for the obtaining and selection-admissibility claims. Claim truth and r’s occurrence identity remain governed by their direct rules |
| empirical or formal evaluation package | a named receiving use needs a tested result or formal conclusion | its actors, work, methods, bases, results, evidence, production, and use relations remain separate from r and D |
| later selection work and C.11 result | accountable selection or project choice is separately current | an identified System performs Work using the selected method; no generic acceptance relation follows |
D_dependencyUse is therefore the C.2.1 episteme identified through obtaining EpistemeConstitutionRelation(G_dependencyUse,r,S_decl). The ordered triple names the ClaimGraph, EntityOfConcern, and effective ReferenceScheme participants; it is not a self-constituting card or record and does not make the relation obtain.
When the structured branch is active, G_dependencyUse designates r and the receiving A.22 use: C_viewpoint, the Q_org constraints applied, and the named admissible-use frame. It carries two separate claim values:
c_dependencyObtains: the direct predicate obtains, independently of use and evidence;c_dependencyAdmissibleForSelection: r is admissible among candidate organizing occurrences for that named use frame.
Both are claim values in G, not C.2.1 epistemes, occurrences, or decision results. Changing the use frame can change the second claim while r remains unchanged.
Add U.ClaimScope or a time qualification to G only when it changes the represented claim; neither becomes a participant. Cite the exact current A.6.6 vocabulary entry and exact RelationSignature as declarations, not as r or proof of r. D is reidentified only when <G_dependencyUse,r,S_decl> identifies a different claim graph, relation occurrence or effective reference scheme; a changed claim value changes D only through changed constitutive G.
When J is present, keep separate conclusion nodes for the two claims and at least these distinct premises when the justification relies on them:
E_baseunderS_basecarries the criterion, law, public name, or method claim used to interpret or replayE_dependent;- an identified System in the interpretation or replay Work, enacting an admitted method, resolves and applies that base content to
E_dependentunderS_dep; and - replacing base edition
E_baseor making the base content used byE_dependentunavailable can change interpretation or replay of fixedE_dependent.
Designation, citation, graph location, co-membership, scheme compatibility, version difference alone, or a failed lookup supplies none of those premises. If the interpretation is method-dependent, cite the exact U.MethodDescription, but identify the acting system, admitted method, and work occurrence separately.
E.17.0:4.7.3 - Keep empirical and formal evaluation local
When empirical interpretation or replay testing is current, identify separately:
H_dependencyEvaluator : U.Systemunder A.1 as performer;RA_dependencyEvaluator : DependencyEvaluationWorkAssignment <: U.SystemRoleAssignmentunder A.2.1, withH_dependencyEvaluatorinHolderSystemSlot, declaration-local assigned-kind domainDependencyEvaluatorSystemRoleKindDomain, andDependencyEvaluatorSystemRoleas RA’s assigned-kind value admitted by that domain; the value, assignment, holder System, and Work remain distinct, and neither the value nor assignment acts;M_dependencyTest : U.Methodunder A.3.1 and, when needed,D_dependencyTest : U.MethodDescriptionunder A.3.2; D describes M but is neither method, work, RelationSignature, nor OperationAlgebra, and a separate A.6.1 operation declaration is cited only when typed application is current;W_dependencyTest : U.Work: A.13 first recovers H as the actual performer through the already named obtaining RA; A.15.1 independently admits W as enacting M. Add F.6 only when the receiving claim needs precise attribution of W through that same RA. An attribution failure alone leaves independently admitted W intact; if the finding invalidates a consumed performer or Work-admission premise, recheck that premise and its dependent conclusions;B_dependencyEmpirical, a C.2.1 episteme identifying the model, calibration, assumptions, and interpretation basis; and- result episteme
T_dependency = <G_dependencyTestResult,E_dependent,S_test>, whose ClaimGraph designatesE_base, predicate, method, conditions, basis, and positive or negative result.
Establish actual participation of E_dependent, E_base, each parameter, and B_dependencyEmpirical during W only through the exact relations that define those participation positions or A.6.1 operation-application bindings. A MethodDescription or compatible SlotSpec establishes no participation. Open a local A.15.PROD claim only when the receiving use needs to say W first constituted T or later completed its declared production; inception, completion, episteme identity, and dependency obtaining remain distinct.
When formal interpretation is current, constitute formal-evidence episteme E_dependencyProof = <G_dependencyProof,E_dependent,S_proof> and B_dependencyFormal identifying the theory, axiom set, proof semantics, and interpretation basis. Its ClaimGraph designates E_base, proof obligation, formal method, basis, and result. Preserve entailment, refutation, malformed input, timeout, and checker failure as different outcomes; neither a refutation nor a checker failure fabricates positive r. The proof episteme is distinct from r and its participants.
If reusable target claims are needed, constitute them separately under C.2.1:
C_dependencyObtainshasc_dependencyObtainsas its principal claim and concerns the exact endpoint pair and predicate;C_dependencyDoesNotObtaincarries a distinct negative principal claim and is not a state of the positive episteme; andC_dependencyAdmissibleForSelectionconcerns r under the named use frame and remains distinct from both obtaining claims.
Co-representation in one ClaimGraph does not merge these epistemes. T carries its empirical conclusion locally; E_dependencyProof carries its formal conclusion locally. If a target-claim episteme separately represents one conclusion, recover its correspondence to that conclusion; add C.29 when mathematical inference or transfer matters. That correspondence does not establish the conclusion’s truth, its use, or r. Mint no duplicate evidence-bearing relation and no new A.10 ontology.
Keep these three cases distinct:
- r obtains while support for
c_dependencyObtainsis unknown; a selecting system may decline reliance without deleting or reidentifying r; - a negative empirical or formal result may support
C_dependencyDoesNotObtainwithout presupposing r, fabricating D, or becoming a positive occurrence; and - T may support the claim that r obtains without supporting use-specific admissibility; a later decision method may consume empirical and formal result epistemes in separate declared premise slots and produce a separate C.11 result.
For historical reliance on a claim or result, recover its obtaining premise, decision-use, reference-use, or operation-argument relation for the named bounded use. Use A.10 when the source-to-use account is implicit or must remain replayable.
Recover the Work and its enacted Method only when the current claim concerns that dated Work or the expressly selected empirical evaluation branch above requires them. Retain that branch’s A.13 performer basis, independent A.15.1 Work admission, and F.6 when precise assignment-bound attribution is consumed.
Storage, inspection, citation, attachment, production, graph membership, or adjacency alone does not establish that use. Keep empirical and formal algebras distinct; keep provenance and assurance with A.10, G.6, and B.3. Retain a missing-governor blocker instead of inventing a generic evidence, use, or acceptance relation.
E.17.0:4.7.4 - Schemes, scope, transformation, and change
Recover S_dep from E_dependent, S_base from E_base, and S_decl from D. They are three uses of existing ReferenceScheme, outside r and its RelationSignature. G may designate exact endpoints, claim values, and declared names through those schemes; designation is neither occurrence obtaining, truth, nor historical participation.
Keep claim-scope widen, narrow, and refit under A.2.6 when no local-sense translation is needed. Use translate only when scope membership must be expressed between exact local senses: require an obtaining F.9 Bridge between their exact SchemeSenseCell values, the separate affirmative claim for that translation’s direction, rule, and tolerance, and the current A.10 or B.3 reliance branch. Scheme difference, same spelling, token reuse, or translation intent triggers no Bridge.
Use A.6.3.RT when the dependency use depends on a changed representation language or reasoning medium. Recover exact source and receiving epistemes and their construction, preservation, loss, and admissible use when that reliance-facing use requires them.
When the receiving use depends on the transition occurrence, apply RepresentationTransitionRelation@Context. Recover the six participants separately. They are the independently selected BoundedModelUseStructure : U.Structure, the preserved EntityOfConcern, source episteme X, receiving episteme Y, an episteme describing the effective interpretation rules of X, and one describing those of Y. Establish the actual representation-transformation Work as required by A.6.3.RT:4.1.b. The six participants determine the occurrence’s identity. The Work is part of the test that the occurrence took place. @Context is the retrieval label for that A.1.1 use. Apply A.6.3.RT’s conditions for preservation, loss or recoverability. Add a description of the transition only when the receiving use needs it.
Add C.29 only for a current mathematical lens. Use F.9 separately when the claim needs a Bridge between distinct local senses. If interpretation or the proposed dependency use lacks a required basis, name that gap and block only that use; the absence of a six-participant transition occurrence or Bridge by itself blocks neither the direct dependency judgment nor a supported exact construction.
Changing only J, an assertion or occurrence description, evaluation result, basis, provenance, production, later-use relation, or representation leaves r unchanged while its endpoint pair is fixed. It also leaves D unchanged while <G_dependencyUse,r,S_decl> is fixed. Unknown support does not make an obtaining r non-obtaining, and support for a negative claim creates no positive r. A changed representation transition invalidates judgments that depended on that transition, but changes r only when an endpoint episteme or the direct predicate also changes.
Progressive stopping rule. Add only what the receiving use requires: readable dependency assertion; reusable RelationSignature when declaration reuse matters; D only for a named A.22 selection-use claim; J only for inspectable inference; evaluation work and exact participation only when evaluation is current; local A.15.PROD only for a needed result-inception or completion claim; provenance, assurance, representation transition, mathematical lens, scope translation, and Bridge only at their own triggers. Adding one of these objects does not by itself prove that an underlying relation obtains.
E.17.0:4.8 - Keep selection for one describing use separate
For one current describing use, always name the use. Add one singular viewpointRef : U.ViewpointRef only when selecting P changes what the use reads or checks or what a relying use may conclude; otherwise omit the reference. When present, resolve it under the effective reference scheme to P. ViewpointId is P’s designator; designator, reference, episteme, and describing use remain different objects.
When the viewpoint matters, select P only for that describing use. The selection does not establish conformance or U.View membership, give E a new C.2.1 identity, reidentify E, or create a universal selection relation, legacy context tuple, bounded-context object, or generic model-use identity field. Another use may select another P while E remains unchanged. A use needing several viewpoints first identifies the C.13 collection and its exact membership; it does not overload viewpointRef with a collection value.
The architecture therefore keeps exactly two positive dependent-kind rules—P as U.Viewpoint by its fixed self-contained content about an exact target kind or, conditionally, by fixed content about selected S; and E as U.View by obtaining conformance—and two direct relation kinds: viewpoint-convention dependence and E/P conformance.
D remains optional for a named A.22 use; the two local explicit-result ValueKinds remain optional for named evaluation consumers. Families carry exact U.ViewpointRef values only when a named use needs viewpoint selection. C.2.1 identity, MethodDescription, A.6.3 construction, E.24.PUB publication, C.29 mathematical representation, and unrelated interfaces retain their separate identities and rules.
E.17.0:4.9 - Add viewing construction only when its history matters
A.6.3 defines a viewing relation from a source episteme to a separately identified receiving episteme. It preserves the same EntityOfConcern. Claim content and the effective reference scheme may be preserved or changed only within A.6.3’s declared construction law. If the EntityOfConcern changes, the move requires A.6.4 rather than counting as viewing construction.
Keep these claims independent:
- constitution: C.2.1 identifies the receiving episteme;
- construction: A.6.3 states an obtaining source-to-receiving viewing relation when one exists;
- membership: E.17.0 states whether the receiving episteme conforms to the identified viewpoint;
- work: A system may perform query, authoring, or rendering work;
- production: use A.15.PROD only when a local work/change/entity-identity-inception or completion claim about the receiving episteme is current.
Do not infer one claim from the label generated view.
E.17.0:4.10 - Recover multi-view organization and correspondence only as needed
Several conforming views do not automatically form one new entity. For ordinary comparison, exact view epistemes, exact viewpoint epistemes, and their conformance occurrences can remain a plurality.
When the work depends on the collection as a whole, construct it under C.13. When it depends on an organization among those views, recover the exact direct relation occurrences and select one U.Structure under A.22. A package, table, graph, or shared EntityOfConcern is not that structure by appearance.
When cross-view correspondence matters:
- name the participant epistemes or represented entities;
- state the direct correspondence, consistency, realization, trace, or change-impact relation that is claimed;
- apply the concrete pattern that defines and tests that relation, including its obtaining and occurrence-identity rules;
- identify a C.2.1 assertion or description episteme only when the correspondence claim itself must be reviewed or used;
- recover the correspondence by which a graph, matrix, or diagram represents those objects and relations; use A.6.3.RT/A.6.3.RT.OE for its construction and C.29 when a mathematical lens is required.
Plain correspondence model may describe such a claim-bearing episteme after its EntityOfConcern and direct relations are recoverable. It is not a universal U.CorrespondenceModel kind, a substitute for the relations, or proof that they obtain. If no pattern defines and tests the needed direct relation, report the missing definition or test for that relation, or use A.6.RCD; do not close the case with linked, mapped, or consistent.
Temporary inconsistency is represented by exact evaluation claims and, when current, repair work. It does not silently weaken the conformance predicate or erase an obtaining correspondence relation.
E.17.0:4.11 - Keep publication and conceptual form outside view identity
E.24.PUB keeps three direct relation occurrences distinct:
PublicationExpressionRelation(selectedEdition,expression,boundedUseDeclaration)states that X conveys the required claims of E for U;PublicationExpressionBearingRelation(presentationCarrier,expression)states that an actual state or realization of independently identified C yields that same X; andEpistemePublicationRelation(selectedEdition,audienceDeclaration,boundedUseDeclaration,expression,presentationCarrier)makes E available through X and C to the declared audience for U while expression, bearing and audience access obtain.
Expression has the three named participants, bearing the two named participants, and publication the five named participants. Each occurrence retains its own maximal continuous obtaining or availability interval. Changing a participant identifies another occurrence; an availability gap followed by restoration creates a later publication occurrence. None of those changes reidentifies an otherwise unchanged C.2.1 episteme.
When reusable form F matters, establish X/F conformance. E.24.PUB retains form-mediated expression and bearing with the same-X witness, and broader availability over permitted expressions or carriers. A changed exact publication need not interrupt that broader availability.
Rendering, upload, or carrier manipulation is U.Work only when an exact system performs it. A.6.3.RT and A.6.3.RT.OE govern construction and correspondence of expressions; C.29 supplies the additional mathematical-lens conditions. A form, carrier, representation, rendering, or publication occurrence grants no U.Viewpoint or U.View membership and makes no world-side relation obtain.
In this pattern’s Plain wording, published view means an already recognized view episteme participating as the selected edition in an exact publication occurrence. It is not another durable kind. One unchanged view may participate in several publications through different audiences, uses, expressions, carriers, and availability intervals.
E.17.0:5 - Worked cases
E.17.0:5.1 - Directly authored architecture view
Architecture episteme E concerns system T. Maintainability viewpoint episteme P concerns its selected viewpoint-convention structure and states the target-kind, concern, admitted-kind, coverage, and semantic-form rules. E satisfies those fixed rules, so EpistemeViewpointConformanceRelation(E,P) obtains and the same E is a U.View. No source episteme or A.6.3 viewing is required.
E.17.0:5.2 - Query output that is not yet a view
A query over source episteme X constructs episteme Y, and A.6.3 records the source-to-Y viewing relation. Y omits a concern component that viewpoint P requires. The construction relation obtains, but conformance does not; Y is not a U.View under P. A later repair may create Y2 with different claim content and a new C.2.1 identity.
E.17.0:5.3 - One episteme, two viewpoints, one selected use
Unchanged episteme E conforms to safety viewpoint P1 and maintenance viewpoint P2. Two participant-determined conformance occurrences obtain, while the named current review use selects only P1 through one viewpointRef. E remains one U.View; the selection neither creates the P1 conformance nor removes the P2 conformance.
E.17.0:5.4 - Viewpoint revision and library repackaging
Adding a reference to unchanged viewpoint episteme P to another E.17.1 local family declaration, or carrying it in another catalogue edition, changes only the catalogue declaration and provenance; it does not change P. Revising P’s conformance rules creates another episteme P_new; conformance of E to P_old does not imply conformance to P_new. An EpistemeEditionRelation may relate the P editions, but it is not a conformance occurrence.
E.17.0:5.5 - Two publications of one view
View episteme E conforms to P. A web publication uses expression X1 following reusable form F1, borne by carrier K1; a printed publication uses X2, F2 and K2. Expression, bearing and selected form conformance obtain for each. Two exact publications make the same E available under their own audience, bounded-use and maximal availability intervals. E remains one view episteme. Broader availability of E can continue when an alternative expression or carrier replaces one of these exact publications.
E.17.0:5.6 - Cross-view correspondence
A functional view names transformation F and a structural view names module M. A project claim says M realizes F. The shared system EntityOfConcern and aligned diagram positions do not establish realization. Identify F and M, apply the direct realization-relation pattern, then identify an assertion episteme about that occurrence if review needs it. A traceability matrix may represent the assertion and occurrence through an explicit correspondence; C.29 applies when that use requires a mathematical lens. Its cell is not the realization relation.
E.17.0:5.7 - Procedural view is not a method description
A TEVB procedural view E concerns holon H and carries claims about methods, order, state, concurrency, and recovery through their exact relations to H. E may conform to procedural viewpoint P and therefore be a U.View, but it is not a U.MethodDescription because its EntityOfConcern is H rather than one admitted method. A method-description view retargets to the method and uses a viewpoint whose target-kind criterion admits methods.
E.17.0:6 - Consequences
| Gain | Cost or boundary |
|---|---|
| Directly authored and derived views share one stable membership rule. | A contested view claim requires inspection of one exact viewpoint edition and its fixed rules. |
| One episteme can serve several viewpoints without duplicated view individuals. | Current-use selection must be kept separate from conformance. |
| Viewpoint catalogues package references without redefining viewpoint identity. | A self-contained new P must state its complete fixed test; the C/Q/S branch is justified only when separately versioned convention organization changes a named reuse, comparison, or maintenance action. |
| Multi-view structures and correspondences become inspectable. | A package or graph cannot substitute for collection, structure, or direct-relation recovery. |
| Publication and rendering can evolve independently of view identity. | Publication users must name the exact occurrence, form, and carrier when those distinctions affect work. |
Reopen the pattern when either conformance participant kind changes, the fixed predicate changes, or a proposed condition makes occurrence identity depend on an object other than E and P. Reopen the affected use when its candidate episteme, viewpoint edition, selected describing use, direct correspondence, or publication occurrence changes.
E.17.0:7 - Rationale, lineage, and current FPF basis
ISO 42010 supplies vocabulary lineage. The remaining rows explain FPF design choices using its construction, representation, relation, evaluation and work rules. They supply no external state-of-the-art evidence for those choices.
| Source or practice line | Adopted move | Rejected overread | Practical effect |
|---|---|---|---|
Architecture-description viewpoint practice, including ISO/IEC/IEEE 42010:2022, used as established practice lineage rather than current architecting SoTA | Separate concern-bearing viewpoint, view, described entity, correspondence, and publication. | A standards vocabulary does not supply FPF identity, obtaining, or work methods. | Readers can recover familiar distinctions while using FPF direct relations and dependent-kind criteria. |
FPF design rationale: C.2.1 identifies source and receiving epistemes; use A.6.3 for any source-to-receiving construction, A.15.1 for performed query or projection work, A.6.3.RT/A.6.3.RT.OE for expression construction and correspondence, and C.29 for a mathematical lens. | Treat a query or projection as one possible construction route between separately identified epistemes. | Query execution, a query definition, or a projected form does not grant U.View membership or prove claim preservation. | Directly authored and query-produced candidates use the same independent E/P conformance test; construction history is opened only when consumed. |
FPF design rationale: direct-relation patterns define and test correspondence predicates; A.6.3.RT/A.6.3.RT.OE govern expression construction and correspondence, C.29 adds mathematical-lens conditions, F.9 defines an exact Bridge between distinct F.17 cells when its predicate obtains, evaluation patterns test consistency, and A.15.1 identifies repair work. | Keep correspondence, consistency evaluation, and performed repair distinct. | A trace link, graph edge, correspondence episteme, or repair result does not make the subject relation obtain. | Inconsistency and repair can be stated and acted on without collapsing world-side relation, epistemic judgment, representation, and work. |
| FPF design rationale: FPF constructive-relation and episteme architecture | Identify E and P independently; identify selected S and convention-dependency occurrences only in the action-changing structured branch; derive U.View membership from obtaining E/P conformance. | Do not materialize a universal family record, mandatory convention structure, context slot bundle, or correspondence-model kind. | Ordinary authoring can stop at self-contained P, while work on shared conventions can be replayed when that maintenance is undertaken. |
E.17.0:8 - Relations and contribution boundaries
- C.2.1 identifies episteme, claim-content, EntityOfConcern, scheme, and edition identity for P, E, D, and any optional assertion, description, result, basis, or target-claim episteme. E.17.0 adds dependent
U.ViewpointandU.Viewmembership to those same individuals. - Use C.13 to construct
C_viewpointonly in the action-changing structured-viewpoint branch, and any separately needed collection of selected viewpoints or views. - A.6.6 defines the reusable
viewpointConventionDependsOnvocabulary entry; A.6.5 declares the four SlotSpecs inside the two RelationSignature declarations. E.17.0 defines direct dependency and conformance obtaining tests and positive occurrence identity. - C.3.2 admits the two optional local explicit-result ValueKinds and any exact local target or stakeholder KindSignature; their values do not determine direct judgments.
- Use A.22 to select
S_viewpointonly when separately versioned convention organization changes a named action, and to select any separately current multi-view structure. E.17.0 supplies Q and candidate relation occurrences for that branch. - A.6.3 defines optional source-to-receiving viewing construction, including identity viewing; it does not define view membership.
- E.10.D2 defines description epistemes and specification use. A describing use is always named; it selects a viewpoint only when that choice changes reading, checking, or a permitted conclusion. Selection does not establish conformance.
- F.18 governs the two relation-kind designations. F.9 applies when a separately needed semantic relation between distinct F.17
SchemeSenseCellvalues is at issue. - E.17.1 defines exact catalogue epistemes and local family declarations whose members are exact
U.ViewpointRefvalues. E.17.2 supplies the four-position project-local engineering viewpoint authoring template and, only after local materialization, its four exact bindings. A declaration, template position, or reference grants no viewpoint or view membership. - E.24.UK admits dependent
U.ViewpointandU.Viewonce for public use; E.17.0 supplies their stable positive membership predicates. - E.24.PUB defines exact expression and bearing, selected form conformance, form-mediated availability and publication recurrence. A.6.3.RT and A.6.3.RT.OE govern expression construction; C.29 governs a mathematical lens. Their use retains the independent predicate for any represented subject relation.
- A.1, A.2, A.2.1, A.3.1, A.3.2, A.15.1, and F.6 distinguish performer Systems, local system-role kinds, exact assignments, Methods, MethodDescriptions, Work, and attribution. Responsibility remains under its direct predicate. Use A.15.PROD only for a separately needed local inception or completion claim.
- A.10, G.6, and B.3 retain provenance and assurance. Use A.6.RCD when no pattern defines a needed cross-view or use relation.
E.17.0:9 - Conformance checklist
- Candidate E has recoverable C.2.1 claim content, EntityOfConcern, and effective reference scheme.
U.ViewpointRefresolves to one viewpoint episteme P; designator, reference, P, P’s exact target-kind or structured EntityOfConcern, and any catalogue position remain distinct.- Self-contained P has the exact admitted target kind or exact local-kind subject as EntityOfConcern and carries the complete fixed conformance test in its ClaimGraph. Only the action-changing structured branch uses an A.22-selected
S_viewpointover least-powerful exact constituent editions and obtaining relations, with Q carrying the eight organization constraints. - Every dependency occurrence has only the identified dependent and base epistemes as participants; assertion, description, D, J, evaluation, work, scope, time, scheme, representation, publication, and use remain conditional neighbors.
EpistemeViewpointConformanceRelationhas exactly E and P as participants, the fixed five-condition semantic predicate, and pair-determined positive-occurrence identity.U.Viewmembership follows only from an obtaining conformance relation, never from authoring, identity viewing, query, selection, packaging, form, carrier, rendering, or publication.- The current describing use is named. A singular viewpoint reference selects P only when that choice changes reading, checking, or a permitted conclusion; omission otherwise changes neither episteme identity nor conformance. Multi-selection uses a C.13 collection with exact membership.
- Optional local result values, evaluation, evidence, occurrence designation, decision-use D, and J exist only for a named receiving work or decision need; unsupported evaluation is not a third or negative value.
- For every multi-view collection, selected structure, or cross-view relation, apply the pattern that defines its identity or obtaining test; a table, graph, matrix, or shared subject proves none.
- Exact expression, carrier bearing, optional form conformance, five-participant publication availability and recurrence, rendering work, and mathematical representation under C.29 remain distinct from E, P, view membership, and every represented world-side relation.
- Ordinary use stops at a readable direct judgment unless a named consumer needs more structure; authoring stops at the shortest progressive path that produces P and its reference.