Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:05:04 UTC

A.16:4 - Solution

A.16 defines admissible move names, guards, identity decisions, and next-use docking.

Here move means a typed transition in the publication of selected episteme content. Observation can supply a precursor cue for early preservation under A.16.1; B.4.1 begins when route publication becomes worth making explicit. A.16 starts when a cue is deliberately noticed, stabilized, route-published, projected, formalized, operationalized, reopened, respecified, or retired.

A.16:4.1 - Canonical move table

This is the canonical move table. Later examples apply it; they do not define another move family.

MoveUse it whenPublication resultKeep explicit
noticea low- or unstable-articulation cue is worth preservingpreservation-worthiness becomes explicit; a first typed preservation may beginwhy the cue is worth preserving and which witnesses remain
stabilizethe noticed cue needs a steadier local shape before route or endpoint choicePreArticulationCuePack or an equivalent early form may become admissiblecue nucleus, anchors, contrasts, witnesses, and preservation rationale
routea stabilized cue has several plausible downstream directions or one route must be selectedRoutedCueSet or another route-bearing publication makes plurality and any selection explicitlive routes, selected route if any, selection reason, and reopen condition
projectionone aspect of an explicit route must be foregrounded without claiming endpoint admissiona typed route-bounded partial publication on an existing MVPK facewhat is foregrounded, what is omitted or lost, and how reopen remains possible
formalizearticulation or closure can increase under a named later rulea more explicit symbolic, slot, or normal-form publicationthe rule used, changed facets, and any new evidence-generating Work boundary
operationalizeselected content is ready to face a method, Work, gate, or other operational questionthe episteme or project record is docked to the pattern that defines or tests that usethe downstream contribution, its guard, and any world-facing Work boundary
reopenthe inquiry or intended use remains appropriate, but closure was over-committedthe publication expresses the reopened alternatives and reduced closure claimreopened rivals, retained witnesses, and which prior endpoint-use or current-use claim no longer holds
sketchBackoffan endpoint-bound or operational form over-commits the available groundsan exploratory cue-bearing form becomes admissible againretained anchors and witnesses, withdrawn closure, and the next safe question
respecifythe inquiry or intended use remains appropriate, but its framing, facet reading, or route specification is wronga revised framing or route specification replaces the earlier onereplaced commitments, what remains supported, and any episteme-identity change
retirea cue, route-bearing publication, episteme, or branch is no longer current for the named use because its grounds failed, a successor took over, or a current-use decision endedretirement or withdrawal is explicitreason, retired object, preserved history, and supported successor information or an unresolved successor question when the receiving use needs it

The table names moves, not the resulting objects. PreArticulationCuePack and RoutedCueSet are publication forms defined elsewhere. U.AbductivePrompt is the question account defined by B.5.2.0; its publication form is selected separately. A claim-bearing episteme remains U.Episteme; E.24.PUB separately defines a bounded publication occurrence.

projection means route-bounded partialization. Publish its result in a typed publication form. An expression must satisfy that form’s content requirements as well as the presentation rules of any selected MVPK face; a face label or an untyped placeholder supplies no such conformance. respecify changes framing, route specification, or a facet-profile reading. A revision can also reopen closure; state both changes when both occur, using A.16.2:4.1. Precision repair remains with A.6.P or C.16.Q; recovery of an ambiguous action-oriented claim or question remains with A.6.A.

Do not use A.16 to decide measurement admissibility, Bridge substitution, endpoint ontology, or another subject claim. Name the applicable pattern and test directly; A.16 coordinates only the publication move that makes that question current.

A.16:4.2 - Guard discipline

State the guard through the language-state readings or route condition on which the move depends. Obtain any required AE reading from C.2.4, CD reading from C.2.5, and representation-factor reading from C.2.7. State required source, evidence, access or action conditions separately under C.2.6. A guard can use both readings and direct relation claims, cited separately or through one published profile; a relation account is not a CharacteristicSpace slot. Add witnesses, scope, and GammaTime selectors when needed. “The idea matured” is not a guard.

A summarized chain may omit repeated unchanged fields, but it must leave every move identity, endpoint-rule change, loss, and status change that affects interpretation reconstructible. A later higher-closure publication does not retroactively strengthen an earlier cue; later retreat does not erase the earlier publication.

A.16:4.3 - Decide identity before describing movement

Do not use “move between publication forms” as a shortcut across these three cases:

  1. First typed preservation. A precursor cue, trace, contrast, or witness may have no source episteme or source publication form. Name the precursor and the first typed preservation form. C.2.1 governs the identity of the first claim-bearing episteme when one is admitted.
  2. Same episteme edition, another form. When EntityOfConcern, ClaimGraph content, and effective reference scheme remain the same, one episteme edition may be issued in another form or on another carrier. Name the episteme and source and target forms only when they matter. E.24.PUB governs each claimed availability occurrence; neither form nor occurrence creates a successor episteme.
  3. Content-changing successor. When a C.2.1 discriminator changes, identify a separate target episteme. Name the source and target epistemes, the changed discriminator, what content is preserved, changed, and lost, and the lineage relation only when its predicate obtains. A repeated label, form, carrier, or move name proves no continuity. Use A.16.0 only if the multi-step or branching history is load-bearing.

The same discipline applies to project records through their own identity patterns. E.24.PUB says that an already identified episteme was made available for a bounded use; it says neither that content changed nor that an endpoint test passed.

A.16:4.4 - Minimum content for a move

Make the following content recoverable in the publication or, where needed, a short move note. Include conditional details only when they change the use:

FieldMinimum content
Current itemprecursor cue or source episteme/project record; source form only when one exists and matters
Identity casefirst typed preservation, same edition in another form, or content-changing successor
Move and guardone move from §4.1 and the changed facet or route condition that justifies it
Targettarget episteme/project record when identified, typed target publication form, and the concrete object or claim that the downstream pattern defines, constrains, or tests; name the ClaimGraph carrying that rule only when its identity or edition changes the use
Preservationwitnesses or anchors retained; for a successor episteme, content preserved, changed, and lost plus any lineage relation
Returnendpoint condition not yet met, omitted or lost content, and reopen or retirement condition

Add an EpistemePublicationRelation occurrence only when bounded availability matters. Add the MVPK face only when rendering matters. Neither replaces the form, episteme, or next pattern.

A.16:4.5 - Work crossing and actual relation changes

Some formalize and operationalize moves only re-express available content. Others require measurement, experiment, installation or use of instrumentation, or execution. Expose the needed action and use the applicable measurement, experiment, gate, or endpoint pattern. If the receiving claim requires a distinct dated U.Work, establish its A.13 basis and independent A.15.1 admission; use F.6 afterward only for precise assignment-bound attribution. A.16 records the pending or separately established crossing; it does not establish that the action occurred or produced a result.

Next-use docking and a Work crossing do not by themselves establish a change in authority, responsibility, permission, or commitment. If one of those relations changes, record it as a separate claim: the relation under its governing pattern; participants in that relation’s own roles, including giving and receiving admitted systems when its predicate requires them; any U.SystemRoleAssignment occurrences through which they participate; its object or action, scope, and effective interval; and the assigning, instituting, revoking, or superseding act when its pattern requires one. A.2, A.2.1, and the applicable deontic or authority pattern establish and test that claim.

Use A.16.0 for such a handoff only when its legitimacy or interpretation depends on upstream move or lineage history. Otherwise the local account of the needed or performed action and the separately established relation are enough.

A.16:4.6 - Keep coordination claims separate

Do not compress several claims into AuthorityState. A reusable language-state coordination readout is only a compact view of independently established facts, not a new U-kind or world-side state. Include only the fields needed by the reader:

ClaimWhat to show
Route plurality or selectionlive routes; selected route if any; selection reason; route-bearing publication
Endpoint admission or use dispositionnamed endpoint test, its result, and the stronger use admitted, narrowed, or blocked
Publication availabilityepisteme, form, bounded use, and EpistemePublicationRelation occurrence when current
Current use or retirementcue, episteme, publication, or branch and the currentness, withdrawal, supersession, or retirement claim that applies
Actual relation changeonly an independently established authority, responsibility, permission, or commitment relation with participants, object or action, scope, interval, and any act required by its governing pattern; otherwise omit the optional claim or report the unresolved change; state that a relation is unchanged only when an applicable negative criterion or complete closure basis supports that claim

Open route plurality is not a lineage fork. A multi-route state keeps several directions live inside one route-bearing publication. A lineage fork has separately identified successor members, their preserved and lost content, and any lineage relations that obtain.

EndpointAdmissionProfile may be reused as a declarative decision profile for next-use docking. Include only inputs required by the proposed use: the relevant C.2.2a position, selected C.2.LS facet readings, any route condition from B.4.1, any prompt-entry conditions from B.5.2.0, and the witness or grounding conditions it consumes. Apply it to judge only whether docking to the later question is admissible: relation-like content toward A.6.P, an open question and rival set toward B.5.2.0, evaluative content toward C.16.Q, ambiguous affordance-like wording toward A.6.A and then the recovered subject, viability or other quality-family content toward C.25 when quality-family decomposition is the question, and executable docking toward A.15. Apply the selected pattern’s own tests. A.6.A may return a sufficient claim, question or missing basis; that recovery establishes no common invitation relation. Tone, style or apparent explicitness supplies no subject result by itself. The admission result creates no authority, responsibility, permission, commitment, publication, gate, or Work state.

A.16:4.7 - One history threshold

Local publication content is sufficient when the move or short chain is reconstructible without extra lineage machinery. Use A.16.0 only when at least one of these is load-bearing:

  • derivation, supersession, fork, merge, or retirement structure;
  • a multi-move history whose compression would hide a change in the applicable pattern or rule;
  • loss notes or reopen conditions spanning more than one move; or
  • an actual responsibility handoff, Bridge entry, or viewpoint entry whose legitimacy or interpretation depends on upstream history.

A.16 defines move admissibility and A.16.0 packages the trajectory account. A graph representation alone does not establish a TransformationFlowStructure. Use E.18 only for an independently selected structure that meets its rules, and E.18.2 for a mathematical description of that structure. Publication faces and bounded audience availability remain under E.17 and E.24.PUB; use C.29 when mathematical-lens adequacy is the current question.