C.37 - Select and Use Representations for One Action
Type: Method pattern Status: Stable Normativity: Normative unless marked informative
C.37:1 - Problem frame
Plain name. Selecting and using representations for one action.
Use this when. One person, team, organization, or other consuming System must take one action or make one decision, and several diagrams, tables, models, records, plans, descriptions, views, notations, or other results may each support only part of that use.
This is the one-use selection branch of representation work. Decide how the receiver may use independently governed candidate results for that action. C.37 does not decide what those results are, whether their subject-side claims obtain, whether an episteme is a view, whether a graph is mathematically admitted, whether evidence may be relied on, or whether the receiving action is authorized. Those answers remain with the patterns that govern those claims.
Primary working reader. A practitioner who has more than one plausible way of seeing or carrying information into an action and needs a selection without building a universal representation taxonomy.
First useful move. Name the receiving System and action or decision in one sentence. For each candidate, name the result it already has, the claim this use would rely on, what the candidate exposes and withholds, and the result that permits, declines, or leaves that use unresolved. Stop after one row if one row is enough.
First useful result. One complete use-bounded representation-selection account: one or more candidate claims with their material loss, basis and receiving action supported, declined or unresolved. It can be the immediate working answer; the row form and persistent record are not required when no later use needs them. Its use boundary is <receiving System, action or decision>.
If retained as a standalone claim-bearing object, it has ordinary C.2.1 identity, an EntityOfConcern and effective reference scheme; the use boundary does not replace episteme identity.
What goes wrong if missed. A readable diagram is treated as a conforming view; provenance is treated as approval; an evidence classification is treated as permission; several adjacent results are treated as one coherent structure; or a choice made for one action silently travels into another action with different loss, evidence, and decision conditions.
What this buys. The practitioner can say which candidate is selected, declined, or unresolved for one use; which claim is being carried; what remains hidden or transformed; what result supports the use; and what change requires return or reconsideration.
Not this pattern when. Use the pattern governing the candidate and stop when it already returns the complete one-result/one-use selection and limits. Use E.17.0 for view conformance, C.29 for a mathematical-lens use, A.6.3.RT for changing representation while preserving content, A.22 for selected structure, C.13 for a construction or collection question, E.24.PUB for publication, and C.2.P.DR for declarative-representation overread. Use C.37 only when the receiving action still needs the cross-kind selection account after those results are available.
C.37:2 - Problem
Representations are useful because they foreground different things. A workflow diagram may expose order while hiding effort. A work plan may expose intended timing while saying nothing about actual performance. A work record may expose an observed breakdown while saying nothing about whether a proposed change will repair it. A graph may support traversal or calculation while omitting distinctions needed by a receiving decision.
The practical question is therefore not “which representation is best?” It is “which candidate result may this receiver use for this action, for which claim, under which limits, and what result makes that use available?”
Five recurrent shortcuts substitute other facts for the grounds the use requires:
- Object shortcut. A label such as diagram, view, model, graph, or record substitutes for the direct result that identifies the candidate and its subject-side claim.
- Classification shortcut. An A.2.4 intended first evidence-use classification is treated as evidence sufficiency or permission.
- Provenance shortcut. A source path, current carrier, or authentic publication is treated as a positive
RelianceDispositionor receiving result. - Decision shortcut. A selected row is treated as the choice, authorization, permission, or gate result without the direct receiving pattern.
- Composition shortcut. Several rows are treated as a collection, structure, integrated view, world model, or graph merely because one receiver reads them together.
C.37:3 - Forces
| Force | Tension |
|---|---|
| Useful foregrounding vs visible loss | A representation helps by emphasizing some distinctions, but the same emphasis can hide uncertainty, conditions, or alternative readings. |
| Cross-kind comparison vs direct authority | Candidate results may be diagrams, plans, records, views, or mathematical objects, while each keeps a different identity and obtaining rule. |
| Cheap orientation vs bounded reliance | Reversible inspection may need only a direct result and limit; consequential use may require an A.10 path and disposition. |
| Co-use vs invented whole | Several candidates may be needed for one action without forming a collection, structure, composite view, or unified world account. |
| Stable source vs changing action | The same candidate can be selected for one action and declined for another because the relied-on claim and tolerated loss differ. |
| Clear decision support vs borrowed authority | The account must help a decision without becoming the choice, gate, permission, authorization, assurance, or domain result. |
C.37:4 - Solution
Use one action spine:
- name the receiving System and action or decision;
- recover each candidate and its direct subject result;
- separate the direct subject result, optional first-use classification, bounded reliance, receiving conditions and result when needed, and auxiliary facts;
- state what the candidate exposes or preserves and what it withholds, loses, transforms, or leaves uncertain;
- mark the row
select,decline, orunresolvedfor the named use and give its return trigger; - co-record only rows that support the same receiver and action or decision.
Local mantra. One receiver, one action. Recover each candidate under its direct pattern. Name the claim, reliance, loss, receiving conditions, disposition, and return. Put rows together only for that action.
The mantra is a recall aid, not a decision rule. The receiving pattern still emits the choice, gate, permission, authorization, or domain result.
C.37:4.1 - Fix the receiving use before inspecting candidates
Write one sentence:
<receiving System> must <take this action or make this decision>.
Every row in the account uses that same receiver and action. A diagram used to select a proposed Method edition and the same diagram used later to tailor that Method have different use accounts. Reuse unaffected candidate and source results; reconsider the claims, losses and conditions that change with the action. Adjacent actions, one project, one carrier or one meeting do not merge their use boundaries.
If one direct pattern already returns the complete representation–operation choice and limits for this use, take that direct exit. Do not add C.37 merely to rename its result.
C.37:4.2 - Recover each row through five separate layers
Open only the layers required by the attempted use.
| Layer | What must be recoverable | What it does not establish |
|---|---|---|
| Direct subject result | The candidate’s independently governed kind or result, its subject, and any representation, conformance, correspondence, transition, structure, collection, mathematical, plan, Work, or domain relation on which the selected claim depends. | Intended evidence use, reliance, receiving decision, permission, gate passage, or authorization. |
| Optional A.2.4 first-use classification | When the candidate episteme is being used as evidence or as a status carrier, the episteme, target claim or status, polarity or value, intended use, and any scope or window that changes that use. | Provenance, sufficiency, RelianceDisposition, assurance, permission, or receiving action. |
| Bounded reliance and a needed A.10 account | The relied-on claim, source, actual use relation and support needed for that use. When the source-to-use account remains implicit or must be replayable, use A.10’s path and RelianceDisposition. Retain currentness, a live challenge, a locally plausible unsupported use, and a reopen or stop condition when they affect this reliance. | Claim truth, selector outcome, gate result, approval, permission, assurance, or Work authorization. |
| Receiving conditions and result | The entry conditions imposed by the rule governing this contribution, including any required gate, permission or authorization. Obtain the choice, acceptance, task or domain result when that result is itself required by the receiving work. Qualified inputs may be used to construct it. | Candidate identity or evidence merely by mentioning the row. |
| Auxiliary facts | Lens, publication, form, carrier, repair, provenance, source, or rendering facts needed to interpret or recover the row. | Any missing positive subject result, reliance, or receiving result. |
If a condition required for the candidate’s stated use is negative, missing or unresolved, decline that use or mark it unresolved and name the missing fact or direct result. Preserve independently supported premises.
Use ready qualified inputs in the receiving comparison or construction; an unfinished choice or task result does not by itself create a missing input-admission result. Any action that depends on that later result still waits for its grounds.
C.37:4.3 - State exposure, loss, and the row disposition
For each candidate, state only distinctions that change the receiving action:
- what it exposes, foregrounds, or preserves;
- what it withholds, omits, loses, transforms, or leaves uncertain;
- the claim for which it is selected or declined;
- the direct result and reliance basis that bound that claim, including an A.10 disposition when that account is needed;
- the condition that sends the reader back to the source or reopens selection.
Use exactly these ordinary row dispositions:
| Disposition | Use |
|---|---|
select | The required subject identity and relations are established, the reliance basis supports the bounded claim, and the conditions imposed on its use by the receiving rule hold. Use the claim in the receiving operation; obtain its eventual result there. An A.10 degrade disposition narrows the selected claim. |
decline | A required result is negative, the applicable receiving rule excludes the stated contribution, or the candidate’s loss makes the attempted use inadmissible. State the retained weaker use, if any. |
unresolved | A required identity, relation, currentness fact, reliance path, disposition, or receiving result is missing or ambiguous. Name what would reopen the row. |
Selection is use-bounded. It does not make the candidate true, complete, current, published, conforming, relied on, assured, or authorized outside the claim and action stated in the row.
C.37:4.4 - Use the smallest complete account
Use this shape when the result must be retained:
Use-bounded representation-selection account:
Receiving System and action or decision:
Receiving rule, required entry conditions, and result when needed:
Candidate rows:
- Candidate and direct subject result:
Claim used:
Intended first evidence use, if at issue:
A.10 path, direct use relation, and RelianceDisposition, if at issue:
Exposed or preserved:
Withheld, lost, transformed, or uncertain:
Disposition: select | decline | unresolved
Return or reconsideration trigger:
Action supported, declined, or blocked under the combined limits:
C.37 may use a single row when it still adds a needed layer separation. If the pattern governing the candidate already supplies the same complete one-result/one-use answer, use that result instead.
This is a logical claim group, not a universal record kind, U.Representation, RepresentationOf relation, taxonomy, manifest, view family, collection, or structure. Do not give it another schema merely because several domains use the same questions.
C.37:4.5 - Realize the result once
First determine whether a later receiving use needs the selection basis retained. An immediate sufficient selection can finish with its grounds, material loss and receiving conditions, without a new record.
When retention is needed:
- If an owning domain result already carries the same receiving use, embed the complete needed claim group and action boundary there.
- Otherwise retain that basis as one ordinary C.2.1 episteme.
- Create no embedded and standalone duplicate for the same use.
A later reader who must reconstruct the selection receives its complete basis; a bare verdict or locator is insufficient for that use.
Retention preserves the needed separation: direct subject result, optional A.2.4 classification, reliance basis and any required A.10 account, receiving conditions and result when needed, exposure and loss, disposition and return. An immediate answer preserves the same substantive limits without instantiating every form field. A cross-use ensemble may later relate accounts under its own direct pattern; C.37 does not perform that organization.
C.37:4.6 - Keep co-use local to one action
Co-use means only that the same receiver relies on two or more completed rows for one action or decision. Each row keeps its own direct result, premise, reliance boundary, loss, and return trigger. One positive row cannot repair another row’s missing subject result or reliance path.
Co-use does not establish:
- one collection or selected structure;
- one multi-view family or mutual conformance;
- one integrated model or coherent world account;
- one constructional whole or composition relation;
- one shared representation language, graph, or correspondence;
- one assurance result or authorization.
For an additional claim, open C.13, A.22, E.17.0, C.29, a domain integration pattern, or another governing pattern only when the receiving action depends on that claim.
Use C.37.MM when the decision requires an inference across models or a successor must recover their governing conventions and the methods by which their results were obtained. A straightforward use of several sources can end here.
C.37:4.7 - Recognition, reliance, assurance, and action remain separate
Recognition asks what the candidate is and which direct result or relation obtains. A.2.4 may add its first evidence-use or status-use classification. Relied-on claims need the source, support and use conditions that warrant them; A.10 develops the source-to-use account when it remains implicit or must be replayable.
Use B.3 only when the question concerns a named assurance claim; consequence or reuse alone does not require an assurance package. The receiving pattern owns the action result.
Use an already adequate source-to-use account. A new A.10 path or disposition is unnecessary when the claim and its warranted use are already explicit and no further replayable account is needed. A source gap, stale consumed premise or unsupported use still blocks the conclusion that depends on it; narrow the use, obtain the required support, or stop. Reuse an applicable A.10 disposition when one already supplies this boundary.
C.37:4.8 - Direct exits and boundary cases
| Case | C.37 disposition |
|---|---|
| One direct domain Method already selects one representation–operation configuration for the same one use and returns its limits, as in rhythmic-representation choice. | Use that Method and result; do not invoke C.37 for a duplicate account. |
A candidate is called a view but EpistemeViewpointConformanceRelation(E,P) fails or cannot be evaluated. | Decline it for the view-dependent use or mark that row unresolved. C.37 cannot grant U.View membership. Another independently positive direct basis may support a different row and claim. |
| A candidate is a mathematical graph or other mathematical object. | Identify the object and the subject relations on which the claim depends. Use an adequate domain result; use C.29 when a separate mathematical representation, transfer, or reliance question remains. C.37 neither admits the object nor makes the mapping obtain. |
| A candidate is an ordinary non-graph diagram. | Identify its episteme and subject. Require the conformance, representation, correspondence or domain grounds needed for the selected claim. Preserve its evidence and reliance basis; use A.10 for a still-implicit or required replayable source-to-use account. Publication, carrier, provenance or C.2.P.DR repair supplies no missing subject or action ground. |
| Several project, process, or case viewpoints concern one Work. | Co-record them only when each can change the same action about that independently identified Work. A viewpoint for another action starts another account. |
C.37:5 - Archetypal Grounding
C.37:5.1 - Qualified premises for a bounded-trial decision
MethodEngineer-ME1 must select or decline MethodChange-MC7 as the proposed Method edition for one bounded trial in planned Work item WP4. This one decision is the receiving use for all three rows.
In this constructed case, the options are to prepare and run the MC7 trial or retain the current Method edition. WP4 provides a one-hour trial slot. The stipulated setup estimate for MC7 is four additional hours, while the applicable total setup-and-trial ceiling is three hours. Retaining the current edition is feasible within that ceiling. These case facts are additional planning inputs; WorkRecord-W19 does not establish the setup estimate or predict the benefit of MC7.
C.11 result CR7 is choose now: ME1 selects retaining the current edition and declines MC7 for this WP4 use because 4 + 1 hours exceeds the three-hour ceiling. The selected comparison criterion is compliance with that total budget; the earlier rework record supplies motivation, not permission to exceed it. Reopen CR7 if the setup estimate, budget, options or trial conditions materially change. The decision makes no claim that the planned trial occurred.
| Candidate | Direct result, reliance, and receiving result | Exposed and withheld | Disposition and return |
|---|---|---|---|
Workflow diagram in MethodDescription-MD5, edition 5 | A.3.2 identifies the episteme as a MethodDescription about Method-M2. A.2.4 may classify its intended evidence use. A.10 path P-MD5 carries the premise “edition 5 states the proposed MC7 action order,” its source/currentness window, direct decision-use relation, and RelianceDisposition=pass. Receiving result: CR7, defined above. | Exposes proposed sequence and handoff; withholds actual effort, achieved result, and future performer availability. | select for proposed-way claims only; return if the edition, intended Method, path, or reliance window changes. |
WorkPlan-WP4 trial item | A.15.2 identifies the schedule-of-intent episteme and its planned performer, interval, and capability conditions. A.2.4 may classify the intended use. A.10 path P-WP4 carries the premise “WP4 currently provides the named trial slot and conditions,” source/currentness, direct decision-use relation, and RelianceDisposition=pass. Receiving result: CR7, defined above. | Exposes a bounded trial slot and intended conditions; withholds actual occurrence, performance, and result. | select for the stated trial-slot availability and intended conditions only; return if the plan, performer, interval, capability condition, path, or disposition changes. |
WorkRecord-W19 about actual Work-W19 | A.13 establishes the performers’ assignment bases; A.15.1 admits the dated Work independently. C.2.1 identifies the record episteme. A.2.4 may classify its intended use. A.10 path P-W19 carries the premise “WorkRecord-W19 reports the stated rework and effort under the named earlier conditions,” its provenance and decision-use relation, and RelianceDisposition=degrade to that comparability-limited premise. Receiving result: CR7, defined above. | Exposes observed breakdown and effort under the earlier edition and conditions; withholds proof that MC7 fixes the breakdown or that the trial planned in WP4 will reproduce those observations. | select only for the narrowed comparability-qualified premise; return if the observed conditions, path, currentness, disposition, or relevance to MC7 changes. |
The completed account retains two pass premises and the comparability-limited degrade premise as inputs to CR7. Declining MC7 for WP4 does not make those representations unusable as decision premises; it states the result obtained using them and the additional budget facts.
None of the three rows proves that MC7 improves the Method. If the same diagram is later used for a tailoring choice or WorkRecord-W19 for a learning decision, establish that different use account, reusing unaffected premises and reconsidering changed dependencies.
C.37:5.2 - Failed diagram use
A release team receives a polished architecture diagram and wants to authorize deployment. E.24.PUB establishes that the diagram edition is available through a current carrier. C.2.P.DR repairs one route-shaped arrow that had been read as operational authority. Neither result establishes view conformance, a representation correspondence, runtime structure, evidence reliance, or deployment permission.
Until the needed direct subject result, reliance basis, and permission or gate result are available, the row is unresolved. Use A.10 when the source-to-use account remains implicit or must be replayable. Visual polish and provenance cannot upgrade it.
If the direct release gate or permission pattern instead returns a negative result because its required basis is absent, the row is decline; classification, publication, provenance, and repair facts cannot override that direct result.
C.37:5.3 - One decision now and a later reader’s need
In section 5.1, the engineer completes the current comparison using the three independently qualified inputs and the stated budget facts. The direct receiving result and material limits are already clear: the description supplies proposed order, the plan supplies intent rather than performed Work, and the earlier record supplies only its comparability-limited observation. If no later use needs another account of this comparison, the answer is complete without a standalone C.37 record. The rules for those claims still govern required source and receiving-result evidence.
Now suppose a later trial reviewer must reconstruct why those inputs were usable for WP4. That use needs the claims, source and reliance boundaries, losses, dispositions and receiving result—not merely “MC7 declined.” Retain the complete basis in the existing same-use decision account if it can carry it, otherwise in one identifiable account. A new receiving decision still requires its own use-bounded selection; the retained earlier basis is not authority for the new action.
C.37:6 - Bias-Annotation (informative)
| Lens | Likely drift | Repair |
|---|---|---|
| Ontological | Repeated use of diagrams, tables, and records motivates a universal representation kind or relation. | Keep each candidate under its kind and relation; C.37 governs only the one-use selection move. |
| Epistemic | Selected means true, sufficient, or assured. | State the claim and its support and limits, reuse or obtain an A.10 disposition when that account is needed, and ground any B.3 assurance claim separately at issue. |
| Decision | The account is mistaken for the receiving choice, permission, authorization, or gate result. | Name the receiving rule and obtain its result for the claim or action that requires it; use qualified inputs to construct that result. |
| Structural | Co-used rows appear to form one integrated whole. | Treat co-use as a shared action key only; open collection, structure, construction, or coherence claims separately. |
| Didactic | A large form replaces the recognizable action. | Start with one receiver, one action, and one row; add a field only when it changes selection or return. |
C.37:7 - Conformance Checklist
| Check | Passing condition |
|---|---|
CC-C37.1 One receiving use | Every row names the same receiving System and action or decision. Another action has a distinct use account; unaffected grounds can be reused. |
CC-C37.2 Direct exit tested | The account is absent when one direct pattern already supplies the complete one-result/one-use selection and limits. |
CC-C37.3 Direct subject result | Each row identifies the candidate, subject, rule governing the subject claim, and every positive relation required by the selected claim. |
CC-C37.4 A.2.4 bounded | First evidence-use or status-use classification is optional and never substitutes for provenance, reliance, or action authority. |
CC-C37.5 Reliance bounded | A relied-on claim has the source, support and actual use conditions it needs. Use A.10 when the source-to-use account remains implicit or must be replayable; then preserve its path, use relation and current RelianceDisposition, with the currentness, challenge, unsupported-use boundary and return conditions material to that reliance. |
CC-C37.6 Receiving result separate | The choice, gate, permission, authorization, acceptance, or domain pattern supplies the action result. |
CC-C37.7 Exposure and loss | Each selected or declined claim states what is exposed or preserved and what is withheld, lost, transformed, or uncertain. |
CC-C37.8 Row disposition | Each row is select, decline, or unresolved; degrade narrows the selected claim rather than creating another row vocabulary. |
CC-C37.9 Return visible | Every row names the source or governing pattern and the condition that reopens selection. |
CC-C37.10 Co-use bounded | Joint use means only reliance by the same receiver for the same action; no collection, structure, view family, graph, or integrated world account is inferred. |
CC-C37.11 Use-needed retention | An immediate sufficient selection can finish without another record. When a later use needs the complete basis, it is recoverable once in an owning same-use result or one ordinary C.2.1 episteme, never both. |
CC-C37.12 Assurance progressive | B.3 is used only when the question concerns a named assurance claim; reversible inspection carries no mandatory assurance burden. |
CC-C37.13 No universal ontology | No U.Representation, universal RepresentationOf, fixed representation taxonomy, master mediation route, or public account kind is introduced. |
C.37:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| Best representation overall | A candidate is ranked without a receiver, action, claim, or tolerated loss. | Start a one-use account and compare only claims that can change that action. |
| Evidence-use classification as warrant | A.2.4 is treated as a positive reliance or authorization result. | Establish the support and conditions needed for the actual use. Use A.10 for a still-implicit or required replayable account and keep the receiving action result separate. |
| Provenance as decision | A current source or authentic carrier is treated as a positive choice or permission result. | Use provenance for the claim it supports; obtain the direct choice, gate, permission or domain result when the receiving work requires it. |
| Publication as representation authority | A published diagram is accepted because it is available and readable. | Recover the direct subject result, any conformance or correspondence, and the relied-on claim; E.24.PUB supplies availability only. |
| Co-use as composition | Several rows become a collection, structure, integrated view, or graph by adjacency. | Keep independent rows; open C.13, A.22, E.17.0, C.29, or a domain integration pattern only for an additional named claim. |
| Duplicate account | A completed immediate choice is made to create an unused record, or an owning result and standalone episteme repeat the same claims. | Retain the complete basis only for a use that needs it; embed once in the same-use owner when available, otherwise use one identifiable account. |
| Cross-use carryover | A row selected for one decision is silently reused for tailoring, learning, maintenance, or another action. | Establish the new use account. Reuse unaffected direct results and reassess the claim, loss, path, disposition or receiving result that the changed action affects. |
| Diagram-first ontology | What exists or what happened is inferred from a graph, table, card, or route shape without the direct subject result. | Recover the object and relation first; then state the representation use or none. |
C.37:9 - Consequences
The gain is a small, repeatable bridge from heterogeneous results to one practical action. A practitioner sees why each candidate may be used, what it cannot support, and where the decision must return when sources, conditions, or reliance change. Domain results remain authoritative and can embed the claim group without duplicating it.
The cost is that some attractive candidates remain declined or unresolved because publication, provenance, classification, or visual form cannot supply a missing required result. That cost is preferable to an account that looks integrated while borrowing warrant across incompatible layers.
C.37:10 - Rationale
The receiving use is the smallest stable boundary shared across domains. Representation kinds, correspondence relations, view predicates, plan claims, Work records, mathematical objects, and decision results do not converge on one ontology, but practitioners repeatedly need the same action sequence over them: recover the direct result, state the relied-on claim and loss, establish its warranted use and required entry conditions, and select, decline, or stop. Selected inputs contribute to the receiving operation; obtain its action result through the receiving Method.
Co-use is chosen instead of composition because the rows need not form a new whole. The same receiver may use them together while every candidate and relation retains its own identity, predicate, and return condition.
C.37:11 - SoTA-Echoing (informative)
| Source line and status | Adopted move | Rejected overread |
|---|---|---|
| Dutilh Novaes, Formal Languages in Logic (2012), and Krämer, “Why notational iconicity is a form of operational iconicity” (2017), conceptual and diagrammatic-reasoning lineage already used by C.2.1 | Representation and notation can change what users can inspect, compare, calculate, or infer; each row therefore states exposure, loss, and bounded use. | Reasoning affordance does not identify the represented subject, make a direct relation obtain, or authorize the receiving action. |
| W3C PROV-O Recommendation, 2013, stable provenance lineage used by A.10 and C.2.1 | Preserve source, entity, activity, and derivation distinctions when they are material to bounded reliance. | Provenance alone is not truth, currentness, permission, assurance, decision, or evidence of actual use. |
| Decision Theory, Stanford Encyclopedia of Philosophy, stable baseline used by C.11 | Fix the chooser, option or action question, comparison basis, and explicit receiving result rather than ending with an informed-looking inventory. | C.37 does not replace C.11 or turn every representation-selection question into one universal decision calculus. |
Reopen this source use when newer representation, provenance, view, or decision practice supplies a lower-effort way to keep the same direct-result and receiving-action boundaries, or when interoperability requires a common standalone account kind that cannot preserve them through ordinary C.2.1 identity and direct references.
C.37:12 - Relations
C.37.MP relates several completed use-bounded selections when a cross-use Method-representation profile is needed. C.37.CF constructs a comparison of changed content and changed form for a stated reader and use. Neither profile nor comparison retroactively merges the one-action boundaries here.
- Builds on:
C.2.1for any standalone account episteme and for the identity of claim-bearing candidate results. - Coordinates with: the pattern governing each candidate’s subject result;
A.2.4for optional first evidence-use or status-use classification;A.10for evidence-provenance and bounded reliance; and the choice, gate, permission, authorization, acceptance, or domain pattern for the receiving result. - Coordinates with:
E.17.0for view conformance,C.29for mathematical-lens use,E.24.PUBfor publication,A.6.3.RTfor representation transitions,A.22for selected structure,C.13for construction and collection boundaries, andC.2.P.DRfor declarative-representation overread repair. - Used by: domain patterns only when differently governed candidate results must support one receiving action and the direct one-result/one-use path is not already complete.