Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 18:05:19 UTC

E.10.MOVE:5 - Archetypal Grounding - Worked Slices

E.10.MOVE:5.1 - Bounded mantra move

Source sentence: “The next mantra move is to compare the two patterns.”

For the post-qualification demonstrative case, recover one E.11.PUA practice-continuation description inside a named post-qualification demonstrative slice. The description states its proposed use, expected result and kind, direct PatternID and name, current condition, and continuation disposition. That PatternID locates the applicable pattern. If the pattern choice is unresolved, the description may point to a separate nested selection question.

Selected fields of an optional note; include BlockedOverread only for an observed or independently grounded misreading:

WordingUseDispositionValue: boundedDemonstratedContinuation
SubjectPatternLocator: E.11.PUA
RecoveredGovernedValueRef: PatternUsePracticeContinuationDescription@SeminarArchitectureUse
RecoveredGovernedValueKindRef: PatternUsePracticeContinuationDescription@Context
RetainedPlainWording: mantra move, only in the bounded CGUS-demonstrative context
BlockedOverread: this bounded source phrase does not license a `U.Move`, performed Work, or universal sequence in the demonstrated receiving use
RemainingReaderUse: inspect the shown candidate, Solution, expected result, and condition
QualificationWindow: the current E.11.PUA continuation description and the named A.22.CGUS demonstrative slice
CurrentnessBasis: the enclosing structure qualifies under A.22.CGUS, the slice shows this E.11.PUA description, and E.10.MOVE admits the bounded Plain wording
ReopenCondition: the enclosing structure or slice boundary changes, the E.11.PUA description changes, or readers use the phrase as Work, recommendation, or universal sequence

E.10.MOVE:5.2 - Expected evaluation-result change

Source sentence: “The repair should create an upward evaluation movement.”

If the claim predicts a later evaluation result, restore the evaluation pattern, coordinate, scale, current result, one expected scale value, range, or closed direction, candidate proposal basis, and protected tradeoffs. Write the result as ExpectedEvaluationResultChange@Context. If those positions are unavailable, keep a provisional prediction description or use E.22 and E.23 to obtain the missing prediction basis.

E.10.MOVE:5.3 - Next FPF use

Source sentence: “The next FPF move is to check architecture.”

If this is a project-local recommendation, restore PatternUseRecommendation@Context under E.11.PUR and cite the exact architecture pattern being recommended. With this sentence alone, the architecture, check question, and expected result remain unspecified. Return the blocker: “Specify which architecture is to be checked, which question the check must answer, and which result is required.” Once those are known, the recommendation may say “next useful pattern use” and name the operation on that architecture and its expected result.

E.10.MOVE:5.4 - TameFlow MOVE

Source sentence: “The MOVE is full-kitted and ready.”

Preserve MOVE as imported source wording. Restore the target WorkPlan or PlanItem, full-kit criterion, A.15.5 work-entry readiness result, and any actual gate decision under their direct patterns. Do not claim target Work occurred unless a dated A.15.1 occurrence is current.

E.10.MOVE:5.5 - Workflow diagram

Source sentence: “This workflow is the next move after problem framing.”

If the diagram describes a transformation-flow structure or method description, use A.3.4.P, E.18, or A.3.2. If the sentence recommends the next pattern use, use E.11.PUR. If it demonstrates one continuation through a wider CGUS, use A.22.CGUS. Split the sentence when more than one claim is current.

For example, if the surrounding text identifies an admitted MethodDescription for heat-treating a shaft, the descriptive clause becomes: “This diagram describes the method for heat-treating the shaft.” State any recommended next pattern use separately, with its object and expected result; return a blocker while those remain unspecified.

E.10.MOVE:5.6 - Evidence path

Source sentence: “Follow the evidence path to approval.”

Use A.10 to recover the selected claim, exact sources, independently established evidence or provenance relations, currentness and bounded reliance. Identify separately the decision meant by approval: A.21 governs an applicable gate result; any authorization or commitment uses the pattern governing that exact relation.

E.10.MOVE:5.7 - Manufacturing operation

Source sentence: “The next move is to heat-treat the shaft.”

If this names the reusable way of changing the shaft, recover the U.Method and its description under A.3.1 and A.3.2. If it places a heat-treatment operation in intended work, recover the WorkPlan or PlanItem under A.15.2. If heat treatment has occurred, recover the dated A.15.1 Work occurrence, affected shaft, method enactment, and result. If the question is whether that intended work can start, recover A.15.5 work-entry readiness. If the receiving context does not select among them, return the blocker: “Specify whether this describes the heat-treatment method, plans the work, reports completed heat treatment, or asks whether the planned work can start.”

E.10.MOVE:5.8 - Clinical readiness

Source sentence: “The patient is ready for discharge.”

When ready hides a patient-state claim, use A.19.SPR to recover the patient as bearer, the clinical state frame or subject pattern, the current value or classification, its evidence and qualification window, and the practical discharge use. A discharge recommendation, accountable decision, work-entry condition, and completed discharge remain different claims under their direct clinical and FPF patterns.

E.10.MOVE:5.9 - Reopen when a local mantra is not CGUS

Initial sentence: “The next mantra move is: name the thing.”

An initial repair classified the phrase as boundedDemonstratedContinuation. Inspection then shows that the enclosing text is A.6.P’s local RPR mantra: a short rendering of the A.6.P Solution. It has no qualifying wider ConstraintGovernedUnfoldingStructure@Context, no post-qualification slice of an independently qualified CGUS, and no E.11.PUA practice-continuation description with the required proposed use, expected result, pattern, condition, and disposition.

That evidence overturns the initial disposition. Remove the demonstrated-continuation claim, retain the local RPR mantra as Plain didactic wording, use the A.6.P Solution and its direct relation-recovery guidance, and write: “Apply the first clause of the local RPR mantra: name the thing; then recover the relation or comparison.” The A.6.P locator and Solution establish neither a U.Method nor a U.MethodDescription. Establish a separate U.Method, a qualifying U.MethodDescription episteme, and any Method-use relation only if A.3.1 and A.3.2 independently admit them and the receiving claim depends on those identities. Reopen the demonstrative-slice question only if a later qualified structure and slice actually show a complete E.11.PUA practice-continuation description.

E.10.MOVE:5.10 - Trajectory under changing constraints

Constructed wording for repair: Our architecture follows a trajectory under changing constraints.

Read the sentence through F.19 first. If it means only that the team expects to revise the architecture as constraints change, state that proposed action directly. When an FPF inference relies on the trajectory claim, recover the exact architecture or system subject, the changing constraints and reference window, whether the sentence concerns actual changes to the architecture, editions of its description, a proposed evolution policy, or a modelled sequence, and the direct architecture, transformation, or model owner. For a C.29 curve or ordered rendering, name its correspondence to the architecture and the losses allowed by that use; establish transformation and evidence claims under their direct owners.

Overlap example: The development trajectory improved. Start with E.10.DEV to recover the developed subject and the basis of improved. Open this branch only when a separately relied-on ordered path, model, plan, or representation remains. Stop when the recovered direct claim answers the question.