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.

Head-to-head task replay.

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 exact 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 deliberately 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 exact 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 exact P under C.2.1 as <ClaimGraph(P), K_target, ReferenceScheme(P)>; the target kind is P’s truthful exact EntityOfConcern because P states how epistemes about members of that kind are to be read. P’s fixed ClaimGraph:

states the exact target-kind criterion and cites its direct authority;
names exact stakeholder or audience referents only when they change the concerns, and states the exact 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, exact 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 actual 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 exact 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 exact EntityOfConcern is the independently admitted exact `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 exact 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 exact 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 exact 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 exact 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 exact 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 exact EntityOfConcern. Use `U.Signature` only for genuinely 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 actually current.	One A.3.2 `U.MethodDescription` whose exact 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 exact constituents above;
construct exact C_viewpoint from 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_org about exact C_viewpoint and 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_viewpoint and the same five fixed claim-content conditions from §4.6.1.

In this branch, changed P claim content, exact S, or effective scheme identifies another P edition. S itself 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 U.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 exact 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 exact 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 exact values remain distinct from their designators. Both kinds use F4 formality, deterministic exact-equality membership, no SubkindOf, and fail-closed definedness. 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 actually needs one. Without such a consumer, state the direct conformance judgment or the structured branch’s Q_org constraint judgment. KindMembershipJudgment and ConcernCoverageJudgment remain withdrawn and do not return as kinds or result fields.

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 exact 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_target by its exact 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 exact E_concern[i] depends on E_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 exact concerns and claim families. Each coverage constraint depends on the exact concern constituents and exact 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 exact independently admitted-kind constituent to which it applies; notation, form, or a raw kind reference grants no admission or dependence.
Method conventions depend on exact method descriptions. Each method-based convention depends on one exact D_method[i] whose exact 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 exact 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.View membership 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 exact system uses the applicable A.22 structure-selection method over exact C, exact 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 exact 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, exact C 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, exact S EntityOfConcern, or effective reference scheme. In the self-contained branch, exact target-kind EntityOfConcern 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 exact episteme P about S. These nearby alternatives remain rejected:

S itself is not U.Viewpoint: consumers require the exact claim-bearing edition P, while EntityOfConcern(P)=S.
An episteme about one method is a neighboring U.MethodDescription only when exact 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 not EpistemeViewpointConformanceRelationSignature. 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: no new root identity, wrapper identity, method requirement, selection-dependent membership, or generic-episteme shortcut.

E.17.0:4.6.5 - Author progressively and stop at the needed assurance

Authoring is a progressive path, not a mandatory workflow. For self-contained P, identify exact 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 exact constituent edition and state each proposed dependent-to-base claim readably;
resolve both endpoint designations, apply the direct obtaining criterion, and construct exact 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 exact Q constraints and have an exact system use the applicable A.22 selection method over C and the selected obtaining occurrences, producing exact 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.