E.10:9 - Ontology recovery rows for overloaded words (LEX L-rules; normative)
What this section does. LEX L-rules standardise how we recover kind and use in Core and local uses when overloaded everyday words hide FPF concepts. What this section does not do. It does not restate naming (see § 7 MG-DA) or morphology, casing, and suffix rules (see § 8 LEX.Morph); it depends on them. Guards. Tokens are classified by
LEX.TokenClass ∈ {KernelToken, ContextToken, DiscriminatorToken}(§ 7.1). Only CHR:ReferencePlane may use the bare word plane. E.10.D2 keeps the EntityOfConcern, an episteme that describes it, and specification use of that episteme distinct; specification use needs a granting gate named by value. Publication faces, publication forms,PublicationUnits, carriers, and renderings stay separate.An enumeration becomes a CHR construction only when it names a
U.Characteristicwith one declared CSLC scale. Without that declaration, recover the exact construction instead of defaulting to a non-measurable attribute: it may be source wording, a field or other representation element under its direct pattern, an example set, unresolved alternatives, a status or state-frame value set, a local kind or classifier, or another value whose kind and definition are already known. It becomes an A.6.5SlotSpeconly inside one exact reusableRelationSignature.
E.10:9.1 - Hard bans and ontology recovery rows (single table; normative)
Use this table as a recovery guide. “Ban” means the listed phrase is not accepted as an unexplained Tech term in Core prose, identifiers, or diagrams. It may remain as ordinary, quoted, or source-local wording when its use is clear; otherwise name the recovered value or relation. EntityOfConcern and Description-episteme boundaries, specification-use gates, and token gates prevent object, description, specification-use, publication-position, and TokenClass leaks (cf. § 8.1).
| L‑rule | Ambiguous or low-precision word (Ban) | Canonical FPF target(s) | EntityOfConcern and Description-episteme boundary and specification-use gate | TokenClass gate | Notes |
|---|---|---|---|---|---|
| L-PROC | process, practice, procedure, workflow, activity, a process-like function step, or method-structure wording | First decide what the sentence is about. Use A.3.4.P for a change situation and U.Method for one way of doing. Name composition, substitution, iteration, fallback, selection, family membership, or another method-side relation under the rule that defines it. Only when a named use depends on how several such relations are organized should the practitioner use A.22’s criterion to select a structure, locally called MethodRelationStructure. Use U.MethodDescription only for an episteme whose EntityOfConcern is one admitted Method and that makes at least one substantive claim about that method as a way of doing. Keep a planning cue or schedule representation as such until A.15.2 admits a U.WorkPlan; use U.Work only for dated performance, and a separate episteme for its record. After E.10.ROLE, recover a local system-role kind and classification, an obtaining U.SystemRoleAssignment, or an A.2.7 relation only when work-facing wording states it. Other branches include an A.1.1 BoundedModelUseStructure when model-use organization changes the answer, an exact source, practice, scope, situation, discipline or cultural-evolution use, U.Transformation, TransformationFlowStructure, and notation under its direct representation rule. | Method, direct method-side relation, optional A.22-selected method relation structure, one-method Description episteme, other subject-description episteme, planning cue or WorkPlan, Work occurrence or Work record, system-role kind and classification, assignment, relation among system-role kinds, model-use structure, source or practice boundary, discipline or source label, Transformation or transformation-flow structure, or selected lens | KernelToken for admitted kinds; ContextToken for admitted local-use designations, occurrences, and records; lens or register when representation is current | A phrase such as “industrial process as line role” first uses E.10.ROLE; it creates neither a system nor a ...SystemRole kind. Chemistry enters U.Transformation, U.Dynamics, or Method only after the claim is recovered. Practice is not a root kind, and procedural, planning, or document form establishes neither U.Method, U.MethodDescription, nor U.WorkPlan. |
| L-FUNC | function, functional, functionality, effect | Apply A.6.F first when kind or relation is hidden. Possible recovered values include a qualified holder-ability claim under A.2.2, U.PromiseContent, U.Method, one dated Work occurrence admitted under U.Work, mathematical function or operator under C.29, and functional-architecture or architecture-to-TransformationFlowStructure relation under C.30, C.30.ASV, or C.30.TFS-REL. | EntityOfConcern is the holder System for an ability claim; otherwise recover PromiseContent, Method, Work occurrence, mathematical object, architecture relation, or transformation-flow relation; any record about Work remains a separate Description episteme | KernelToken or ContextToken according to the recovered value and use | Never use function as a Core kind name or as default architecture meaning. |
| L-SERV | service or access-like wording used for provision, a team, software process, deployed component, endpoint, application, host, cluster, access point, offering, ticket, case, Method, or Work | Apply this row only when relied-on FPF wording hides the concrete subject, participant, predicate, kind, permission, Work occurrence, or next question. Bare service has no default system reading: ordinary wording may name service-provision Work, a Method, PromiseContent, participation, or another direct claim, while software wording may be metonymic for a process, deployed component, endpoint, application, host, or cluster. Apply E.10 and A.6.P:4.11a to recover the hidden choice. Quoted, historical, illustrative, or harmless prose remains outside. | Carry the original wording and relied-on use into A.6.P:4.11a. The recovered object and relation establish what the claim is about; the applicable pattern supplies any EntityOfConcern/Description-episteme boundary or specification-use gate. Use A.1.SCR only after A.6.P has named a bearer claim and the decision depends on systemhood; E.10 supplies neither classification nor a new kind. | Keep the source token’s register and class until the claim is recovered; no TokenClass choice admits a kind. | Ask what stopped, what is provided, how it is provided, or which bearer must be restarted. Do not normalize service to server/system, Method, Work, PromiseContent, permission, or fulfilment. If the concrete subject, relation, or dependent use still cannot be named, stop the relied-on use. Record missing-governor[...] only after participants, needed predicate sentence, and dependent use are named but no current pattern supplies that predicate. |
| L-SLA | SLA or service level agreement used for an SLO, accountable undertaking, published terms, or a document | Unpack acceptance thresholds into U.PromiseContent.acceptanceSpec; accountable obligations or penalties into U.Commitment; the packaged SLA through A.6.C into its separate promise, utterance or publication, commitment, Work or consequence, and evidence claims; and published terms into a speech act plus clause episteme. Keep Work, measurement, evidence, and acceptance verdicts separate. | EntityOfConcern side for PromiseContent, Commitment, and any actual Work; episteme side for clauses, specifications, measurements, evidence, records, and verdicts | KernelToken, ContextToken, or DiscriminatorToken according to the recovered value and use | Treat SLA as polysemic shorthand, never one kind or Work record. |
| L-SCHED | schedule, plan, or calendar as execution | Keep a schedule, planned window, or calendar as source wording, a planning cue, or a representation until one exact episteme passes A.15.2’s present-EntityOfConcern, horizon, PlanItem, and substantive-coordination predicate; only then use U.WorkPlan. For actual performance, identify one Work individual independently under A.15.1; telemetry, actuals assertions, and run records remain separate epistemes about obtaining facts. | Source or representation until the gate; Description episteme for an admitted WorkPlan and for records versus world-side Work occurrence | ContextToken only after the local-use designation or record is admitted | Never infer U.WorkPlan from an intent window or schedule label, attach actuals to a plan, treat telemetry as Work, or store actual relations as occurrence fields. |
| L-ACT | activity, action, task, or step as type | Recover the object before choosing the value: one dated U.Work occurrence; a separate work-record episteme when only a record is current; U.Method for an independently recovered reusable way of doing; assert submethod membership only when the composition question requires and establishes it; a representation element under its direct pattern or claim-content constituent when the step appears only in code, diagram, recipe, or procedure; U.MethodDescription only when the claim-bearing episteme has one U.Method as EntityOfConcern and passes A.3.2; or a planning cue or PlanItem inside an admitted U.WorkPlan. If only order, fallback, substitution, or dispatch is current, name that direct method-side relation; use an A.22-selected MethodRelationStructure only when the receiving use depends on how several such relations are organized. | Work occurrence, record episteme, Method, direct method-side relation, representation or claim-content constituent, MethodDescription, planning content, or optional selected method relation structure | ContextToken for an admitted local-use designation, occurrence, or record; otherwise the token class of the recovered value | Recover assignment, satisfaction, performance, actuation or approval under the predicate asserted. An assignment of a value, satisfaction of a constraint and an assignment to a system role have different participants and governing rules; the verb does not select one of them. |
| L‑AGENT | agent, actor, or doer (bare) | Recover the acting entity and admit it as U.System only when A.1 passes. Ordinary actor wording may stay ordinary when no precise agency or Work claim is consumed. For a precise Agent claim, apply A.13: exact local agential system-role kind and criterion, classification, obtaining assignment, any scope, working situation and window required by the use, and adequate core evidence; add a characteristic profile only for a consumed Grade, autonomy or profile result, criterion-dependent characteristic, or assurance use. For performed Work, A.15.1 then independently admits the dated occurrence from its actual performer basis, Method, time, and containment. Only afterward does F.6 establish any precise assignment-bound attribution through the same obtaining assignment. A compact attribution rewrite keeps the combined basis recoverable and may omit only an unused assignment identifier after attribution is established. | Acting entity or admitted System; optional A.13 local-kind/classification/assignment claim; independently admitted Work; separate F.6 relation when precise assignment-bound attribution is current; separate assertion or description episteme when current | KernelToken or ContextToken according to the recovered value and use | A title, source or scheme cue, capability, evidence item, declaration place, assignment, or actor-like label establishes none of systemhood, classification, agency, profile, Work, or attribution. |
| L‑OWNER | owner of X | Recover what ownership wording says in this claim. Keep owner when an actual architectural, organizational, policy, source-maintenance, responsibility, authority, or commitment relation is current. If the claim is instead a work-facing system classification or assignment, start with E.10.ROLE and use A.2 or A.2.1. | Exact ownership or responsibility relation, exact local system-role kind, exact direct assignment species, ordinary wording, or blocker | ContextToken only when an admitted local-use designation is current | No global owner property; no lexical replacement of a precise architectural owner; no assignment inferred from a title. |
| L-CAP | capability for assignment, recipe, run, or promise | A.2.2 states a holder’s ability within declared conditions and bounds. Keep an exact system-role kind, direct U.SystemRoleAssignment species, U.Method, dated U.Work, Work record, and U.PromiseContent separate under their patterns. | EntityOfConcern is the holder System for an ability claim; method, system-role kind, assignment and Work occurrence retain their own identities; one-method Description episteme only after membership; separate run-record episteme | KernelToken or ContextToken according to the recovered value and use | A system-role kind or assignment establishes no capability; a recipe form or record establishes neither MethodDescription membership nor Work. |
| L-DYN | process of diffusion, growth, or learning | Recover the claim first. Use U.Dynamics only when one episteme passes A.3.3: its EntityOfConcern is the changing subject and its claims state the state space and transition law. Use A.3.4.P for an unresolved change situation or E.10.LRN for unresolved learning wording. | Dynamics episteme separate from its changing EntityOfConcern, Method and Work | KernelToken or ContextToken according to the recovered value and use | The law may include exogenous inputs, constraints and disturbances; Dynamics is not restricted to uncaused change. |
| L‑EVID | “paper or dataset proves or ensures” | Recover the evidence-use, source-use, status-use, assurance-use, gate-use, or publication-use relation under B.3, F.10, G.6, E.17, C.28, or the rule that defines the recovered use relation. Reuse adequate direct source and use grounds. Use A.10 when their source-to-use account needs recovery or replay. Use U.SystemRoleAssignment only for a separate exact assignment that currently obtains, whose holder is an admitted system and whose assigned participant is one exact local system-role kind. | Episteme with exact claim target and direct use relation; any system-role assignment remains separate | ContextToken or DiscriminatorToken according to the recovered value and use | Evidence use is a relation over an episteme and a claim or use; the episteme is not a system-role holder. |
| L‑CTX | context wording whose action-changing content is hidden | Apply E.10.D1; recover the subject-defined value or relation that changes the action—for example, a scheme, scope, model-use boundary, situation, design-time or run-time referent, architecture, environment, domain subject, or local-practice use. | Apply the pattern for the recovered subject and name its EntityOfConcern and any claim-bearing episteme; introduce no generic Context participant or card. | Keep the recovered subject’s token class; the spelling context selects none. | Keep quoted and ordinary uses, and established uses already defined by a pattern. Rewrite only the use that hides the next action or stop. |
| L-BRIDGE | sameness, equivalence, alignment, or mapping inferred from a shared label | Identify the two exact local senses first. If the F.9 predicate is being asserted, address each sense as an exact F.17 SchemeSenseCell and apply F.9 only when the direct Bridge relation obtains; state the bounded-use claim separately; when relying on it, preserve the A.10 evidence-provenance path for that same use, use its local RelianceDisposition for ordinary evidence reliance, and B.3 when an actual named assurance claim is current. | The Bridge relates those two cells. A card, row, label, score, or publication is a separate episteme or representation and makes no relation obtain. | Keep each source expression under its effective scheme. | A shared label creates neither a Bridge nor substitution, merge, admission, authorization, or performed use. |
Recovery example. For “The process ensures quality,” first recover what process names and which quality condition is claimed. If it names a Method, recover the quality claim and its grounds under
C.16.Q,C.25or the direct subject rule; useB.3only for a selected assurance claim. Leave an unsupported guarantee unresolved. Identify a separateU.MethodDescriptiononly when the receiving claim needs it and A.3.2 membership holds.
E.10:9.2 - Diagnostic examples, not substitutions
Use these rows only after the compact cue surface selects the named lexical problem. Accept a repaired sentence when its object, head kind, relation or claim, use, and scope are preserved, the applicable § 7 or § 8 rule passes, and the changed sentence passes the local F.19 reread. If an example would change the kind in the current sentence, split the claim or leave a blocker; do not copy it as a ready-made rewrite.
| Trigger symptom | Recovered ontology example |
|---|---|
| “the process owner approves” | Start with E.10.ROLE for the title-like wording. If owner names an architectural or responsibility relation, keep that relation instead of forcing a system-role reading. State ApproverSystemRole separately only when the classification matters. If approval is precise performed Work, recover ApprovalSystem through A.13 and let A.15.1 independently admit the dated Work. Add F.6 only when the sentence or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer. A missing or failed attribution alone leaves independently admitted Work intact; recheck any A.13 or A.15.1 premise invalidated by the same finding under A.15.1:4.1. Keep the approval speech act, authority, and decision separate. |
| “the document enforces policy” | Policy_vN states the policy used by the applicable gate, constraint, commitment, or evidence relation. When enforcement Work is current, name its actual performer, admit the dated Work through A.13 and A.15.1, and add F.6 only for a precise assignment-bound attribution. Add PolicyEnforcementSystemRole only when that classification changes the claim. |
| “our service runs nightly jobs” | Apply L-SERV and A.6.P:4.11a first. If the sentence means dated service-provision Work performed by a scheduler system, recover that actual performer through A.13 and let A.15.1 independently admit the Work. Add F.6 only when the sentence or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer. A missing or failed attribution alone leaves independently admitted Work intact; recheck any A.13 or A.15.1 premise invalidated by the same finding under A.15.1:4.1. Add SchedulerSystemRole only when that classification matters. Promise content remains separate. |
| “the API is the service” | Apply L-SERV and A.6.P:4.11a. A reusable way of access may be API_Access_Method : U.Method; a claim-bearing interface specification is an episteme and becomes U.MethodDescription only under A.3.2; an addressable endpoint is a separate bearer; use A.1.SCR for it only when the claim depends on systemhood. Any API publication form/carrier remains separate, and promise content states the promised result and acceptance criteria. The source wording chooses none of these by itself. |
| “capability assigned to team Y” | Split the claims. TeamY may be an admitted System that has Capability C within envelope E. If the wording also means a work-facing classification, name its local system-role kind; if it means an assignment, name the occurrence with TeamY as holder and its declared U.SystemRoleAssignment species. Capability, classification, and assignment do not establish one another. |
| “process health green” | Apply A.19.SPR: name the bearer, state frame, value green, criteria or evidence, admissible use, and change condition; the color alone does not establish health or acceptance. |
| “function of component A fails” | Apply A.6.F. If the recovered claim is behavior performed as Work, use A.13 to recover the system that performed the Work and let A.15.1 independently admit the dated Work. Add F.6 only when the sentence or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer. A missing or failed attribution alone leaves independently admitted Work intact; recheck any A.13 or A.15.1 premise invalidated by the same finding under A.15.1:4.1. Add ServiceOperatorSystemRole only when that classification matters. The evaluation result separately records failed acceptance on the cited observations. |
| “context is unclear here” | Apply E.10.D1 and name what changes the interpretation or next action: the exact source and edition, effective scheme, claim scope, model-use structure, working situation, frame, referent, or local practice. If two local senses are compared, identify them; assert an F.9 Bridge only when its direct relation between exact cells obtains. |
E.10:9.3 - Acceptance tests (LEX‑AC)
A text passes LEX if all answers are Green:
-
Action-changing use recovered. Each use of context that changes interpretation or action names the exact source, scheme, scope, model-use structure, situation, frame, referent, or practice that matters. Ordinary, quoted, and already defined uses remain available.
-
Distinguish the EntityOfConcern, the Description episteme, and its specification use. EntityOfConcern, Description-episteme, specification-use, publication relation, and run-record uses are not conflated (cf. § 8.1 gates).
-
Promise, ability, and performance split.
PromiseContent(promise clause),Capability(ability),Work(performance) are not conflated. -
Agentive predicates and metonymy. A doubtful agentive or causal predicate—including a negated one—calls for the whole-span
F.19check. Retain ordinary, unambiguous metonymy; otherwise state the capable participant or the exact non-agentive relation. Add a denial only for a grounded plausible misreading whose correction matters. -
Scheduling hygiene. No actuals belong in a
U.WorkPlan. A performed occurrence is admitted as datedU.Workfrom its independent A.13/A.15.1 basis. A complete A.13/A.15.1/F.6 basis is required only when the receiving use additionally claims precise assignment-bound attribution; a missing F.6 link alone does not revoke independently admitted Work; recheck any admission premise invalidated by the same finding under A.15.1:4.1.Other direct facts, including affected referent, bindings, and resource use, remain separate. A short attribution sentence may omit only an assignment identifier unused by its receiving claim; the underlying occurrence and attribution remain recoverable. An assertion, description, log, or record about the Work is a separate episteme, not the occurrence.
-
Cross-local relation. When the text relates two different local senses, it identifies the exact F.17 cells and cites an F.9 Bridge only if that direct relation obtains under the applicable F.9 relation profile. When a receiving use is current, a separate C.2.1 claim says what action is proposed, its use direction, correspondence rule, tolerated loss, and polarity. That claim does not show that the action occurred.
For reliance on the bounded-use claim, preserve the A.10 evidence-provenance path for that same use. Ordinary evidence reliance requires the applicable local RelianceDisposition; an actual named assurance claim requires its B.3 result for the same bounded assurance use. Apply A.6.9 (RPR-XCTX) when published wording such as “same”, “equivalent”, “align”, or “map” still hides the relation.
-
MG-DA ok. New or refactored tokens pass § 7 MG-DA (anchored head noun; collision check; an enumeration names its closed value set, classified kind, and classification rule; use
U.CharacteristicandCharacteristicSpaceonly when the enumeration is the declared CSLC scale of that exact Characteristic). -
Morphology ok. Suffix, compound, prefix, and casing respect § 8 LEX.Morph (for example, concrete
…SystemRolekind designations,MethodDescription,Work, and reserved prefixes); bare...Roleis not a default Tech form. -
Banned tokens absent or recovered. No process, practice, function, task, or activity in Kernel senses unless the sentence applies the selected recovery pattern (
A.3.4.P,A.6.F, work patterns, method patterns,C.36.P, or another relevant pattern) and names the recovered value by value; no tooling or file suffixes in Kernel tokens. -
State gating present (when needed). Readiness of an assignment to a system role is expressed through
SystemRoleAssignmentStateRelationplus a separateSystemRoleAssignmentStateAssertionwhen an assertion is needed, not through vague “approved” or “ready” wording.
E.10:9.4 - Coordination map (how LEX plugs into the rest of FPF)
-
With E.10.D1 — Recovering What “Context” Means in Use. E10-CTX-1: When context changes the statement or next action, recover what supplies the boundary—for example, a value, relation, scope, scheme, situation, or use defined by the relevant pattern. E10-CTX-2: For source-local meaning, state the exact source, expression, effective scheme, and local sense. Create F.17 cells when stable addresses are needed; use F.9 only for an obtaining direct Bridge between two exact cells, and keep every proposed use and reliance claim separate.
-
With E.10.D2 (EntityOfConcern and Description-episteme boundary and specification use and refinement discipline). Distinguish the EntityOfConcern from its Description episteme, then say whether that episteme has specification use. E10-EOC-DESC-SPEC-1..3 apply: the EntityOfConcern is named directly; Description suffixes name Description-episteme use; Spec suffixes name specification use on a Description episteme; a work assertion or description is a separate
U.Epistemeabout one Work individual and is not the occurrence; a state assertion is a separately governed claim about a state and is not that state; an evaluation-result episteme is neither the evaluated object nor an occurrence. Upgrade a Description episteme to specification use only when checkable acceptance or another specification-granting gate named by value exists. -
With E.10.ROLE, A.2, A.2.1, and A.15 (system-role-kind, assignment, Method, and Work alignment). Bare role has no default Tech reading. A local system-role kind classifies independently admitted systems; classification, assignment, and Work remain separate.
U.Methodis a way of doing;U.MethodDescriptionis a claim-bearing episteme about one admitted method that passes A.3.2. A performed occurrence is datedU.Work: A.15.1 admits it first from its actual performer basis, Method, time, and containing System; F.6 follows only for precise assignment-bound attribution. A compact attribution account keeps the Work basis and all performers named or recoverable and may omit only an assignment identifier unused by the receiving claim after attribution is established. Assertions, descriptions, logs, and records about the occurrence are separate epistemes. -
With F‑cluster (Unification) and UTS (F.17). Recover each source-local cell under its effective scheme. A comparison row may cite direct Bridges, losses, contrasts, and separately warranted use claims; the row creates none of them. UTS is the human-readable term publication.
Acts and tokens. Identify the class of the token. For a mint, rename or use, check the conditions of the act against the policy for that class (§7.5).
E.10:9.5 - Conformance checklist (LEX‑CC)
- LEX‑CC‑1 (Triggered use, not spelling ban). A listed word opens repair only when its FPF-governed use hides a kind, relation, claim, or action; quoted, ordinary, and already precise uses remain available.
- LEX‑CC‑2 (Context wording). After
E.10.D1, each action-changing use of context names what supplies the relevant boundary, interpretation, or situation and makes the next action or stop clear. - LEX‑CC‑3 (EntityOfConcern and Description-episteme boundary and specification-use morphology). Usage passes § 8 gates (suffix, prefix, and casing), EntityOfConcern and Description-episteme boundary checks, and specification-use checks.
- LEX-CC-4 (Cross-local relation). Recover the exact relation being asserted between local senses. Cite an F.9 Bridge only when its direct predicate obtains between identified cells; any proposed use and reliance remain separate. Shared spelling establishes none of them.
- LEX‑CC‑5 (MG-DA). New tokens pass MG-DA tests, including full‑text collision and Reserved‑Names checks.
- LEX‑CC‑6 (Service, acceptance, and evidence). Service or access wording establishes neither Work nor acceptance. An acceptance claim names the selected criterion episteme, any evaluation or acceptance Work that applied it, the returned value or result episteme, and the acceptance predicate with its participants under the applicable acceptance pattern; delivery Work, evidence, or a positive display proves none by itself. Evidence use is a relation over an Episteme, target claim or use, the scope, polarity, temporal conditions and provenance required by the evidence use.
- LEX‑CC‑7 (USM compatibility). Apply the token-class policy to the individual use or proposed range of uses (§7.5).
- LEX-CC-8 (Naming discipline). If overload cleanup yields one local replacement phrase, the text records the repaired phrase and applicable local repair pattern. If cleanup yields one durable reusable name, the text first records the applicable F.8 decision for the already identified value, then completes an F.18 NameCard; public, Core-facing, durable, or cross-local publication also supplies the F.17 term row. Intuition-first labels, partial NameCards, and naming acts that substitute for value or kind admission are non-conformant.
E.10:9.6 - Worked micro‑examples (short, cross‑domain)
Factory.
✗ “The process failed; the service restarted itself.”
✓ The compact strings PLC_17#ObserverRole:PipelineOps, CAB_Chair#ApproverRole:ChangeControl, and OpsBot#DeployerRole:CD_Pipeline_v7 remain quoted source cues only. Start with E.10.ROLE; they are neither system-role-kind designations nor assignment occurrences.
PLC_17, ChangeControlBoardSystem, and OpsBot are independently admitted systems. Use ObserverSystemRole, ApproverSystemRole, and DeployerSystemRole only where those classifications matter. For each precise dated Work occurrence, recover the actual performer through A.13 and let A.15.1 independently admit the occurrence. Add F.6 only when the example or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer. A missing or failed attribution alone leaves independently admitted Work intact; recheck any A.13 or A.15.1 premise invalidated by the same finding under A.15.1:4.1. Omit only assignment identifiers that the receiving example does not use. Source suffixes and interpretation epistemes remain separate.
Keep the log episteme, approval speech-act content, and fulfillment claim separate from those Work occurrences, assignments, and attributions.
Cloud.
✗ “The process owner approved; the API service deployed.”
✓ The source strings ProductLead#AuthorizerRole:Rollout_2025 and sCG‑Spec_ci_bot#DeployerRole:CD_Pipeline_v7 remain quoted cues. Recover ProductLeadershipSystem and sCGSpecCIBot independently; use AuthorizerSystemRole and DeployerSystemRole only for exact local classification claims.
For RolloutApprovalWork-F123 and DeployWork-F123, recover each actual performer through A.13 and let A.15.1 independently admit each dated Work occurrence. Add F.6 only when this account or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer. A missing or failed attribution alone leaves independently admitted Work intact; recheck any A.13 or A.15.1 premise invalidated by the same finding under A.15.1:4.1. Omit only assignment identifiers that the receiving account does not use. Keep source titles, source or scheme cues, approval content, deployment results, and telemetry separate, and identify each through the rule for that value or relation.
RESTAccessMethod : U.Method names the exact API access method; RESTAccessDescription is U.MethodDescription only if its claim content substantively describes that method as its EntityOfConcern, and it is an access Spec only after the named specification-use gate. Any selected description edition is reached through a separate governed U.EpistemeRef, while file or carrier version remains separate. FeatureAccessPromiseContent states the acceptance condition; telemetry measurements provide evidence for the evaluation that the deployment fulfilled that promise content.
Research.
✗ “Dataset X proves the theory; the process is reproducible.”
✓ DatasetX supports claim C only under the applicable evidence rule, with the model-fit scope, polarity, provenance and temporal conditions needed for that inference. Preserve its exact source and independently established support/use relations. Use A.10 when the source-to-use account needs explicit recovery or replay; use B.3, G.6, F.10 or another subject pattern only for the result that pattern defines;
replication is recorded through evidence-use, source-use, status-use, or reproducibility-status relations under their respective patterns;
procedure wording first recovers one exact U.Method; a separately identified claim-bearing episteme is U.MethodDescription only when that method is its EntityOfConcern and its claims pass A.3.2, while re-runs are exact Work occurrences only on the A.15.1 basis.
Semioarchitecture.
✗ “projection has one meaning in routing and bridge prose.”
✓ A.16 keeps projection as a move name for route-bounded partialization; F.9.1 keeps projection as a bridge stance label. If one durable reusable replacement name is needed, recover the value and use that need a name, record the applicable F.8 decision, and then use F.18 plus F.17 when public publication is current; otherwise retain the source expression or local phrase rather than flattening both interpretations into one umbrella rewrite.
Related lexical rules.
Apply section 7 MG-DA (anchored head nouns; enumeration rule gate; U.Characteristic and CharacteristicSpace only when one named Characteristic has that enumeration as its declared CSLC scale; collision checks) and section 8 LEX.Morph (suffix, prefix, and casing). The only admitted uses of plane in the Core are CHR:ReferencePlane and the derived operators CL^plane and Phi_plane; policy flags do not introduce new planes. To distinguish pre-operational and operational states within ReferencePlane=world, use WorldRegime in {prep | live}.
E.10:9.7 - Guarded-head cross-reference (normative lexical caution)
When one wording head already carries several FPF-governed local interpretations, lexical cleanup should prefer a guarded-head note over silent flattening. The note may record that the head remains risky, name the cited texts or patterns that define or constrain the local interpretations, and point readers to the local canonical interpretation in each cited text.
If cleanup reveals that no admissible existing token can carry the needed meaning, use the local repair pattern for one-off wording. If the change needs one durable reusable name, first recover the value and its kind and record the applicable F.8 decision, then use F.18 for the NameCard and F.17 when public, Core-facing, durable, or cross-local publication is current. Do not invent an ad hoc synonym or let naming settle an unresolved object.
This cross-reference is lexical only. It does not create a new repair-side definition site, does not establish global or cross-local equivalence, and does not overrule cited local definitions. It keeps overloaded heads from being normalized into one false global interpretation.
projection is the main current example: A.16 keeps it as a move name for route-bounded partialization, while F.9.1 keeps it as a bridge stance label. E.10 therefore uses deconfliction notes and explicit naming of the cited text that governs each local interpretation, not one umbrella rewrite that erases the distinction.
Bare claim-bearing role is another guarded head and has no default Tech reading. Use E.10.ROLE to recover the current object or relation; use SystemRole only inside a concrete local system-role-kind designation after that kind is independently admitted.
E.10:9.8 - control, management, regulation, governance, steering
These words locate a possible ambiguity; they are not prohibited words or interchangeable names. Read the complete claim and recover its subject and use. A field name, a group of people, a governing act, an observation and an arrangement that influences what happens can require different explanations despite sharing the same word.
Apply C.43:4.1.4 when the control meaning remains unresolved. It recovers what is influenced, the maintained condition or intended change, the information and means, and the connection to actual action. Operations management can realize this control construction without changing its disciplinary name. Retain its organizational conditions; do not infer a machine-like actuator, an automatic feedback loop or a fixed cadence from the word control.
Use the recovered subject directly: C.30.LCA for a control-structure claim, C.32.LCA for constructing its architecture, C.11 for the needed local choice, and the applicable authority, commitment, measurement or evidence rule for those relations. A.6.P helps when a direct relation still cannot be stated. Use F.18 only when a reusable name must be settled after its meaning is known. A translation retains the source meaning, including the difference between checking and influencing; a lexical match alone establishes no equivalence.
Do not force a control interpretation onto a field title or an already clear sentence. Repair only the ambiguity that changes understanding or use, then return to the work.
E.10:9.9 - Thinking terms and the whole being considered
When a thinking term identifies the subject of a holonic question, name the whole and the relation that the reasoning needs. System thinking can consider how Systems are constituted and contribute to larger systems. Methodological thinking can consider how reusable Methods are constructed and composed. Reasoning about performed work can consider how actual Work occurrences and their parts form a performance history. Use A.1, A.3.1/B.1.5 and A.15.1 for their different construction rules.
These are qualified applications, not exhaustive definitions of the familiar forms of thinking. An “operational” judgement can also concern capacity, commitments and service under OPS.23. Management and strategic reasoning can connect Systems, Methods, Work and Epistemes. Mathematical thinking can compose claim-bearing knowledge and proof Methods while also constructing mathematical objects and operations. Keep an object of a mathematical claim distinct from the Episteme making that claim.
Translate the intended subject and operation, not just the adjective. Russian «методологическое мышление» concerns methods and their grounds in this use; English “methodical thinking” can instead mean orderly procedure. “Systematic” does not by itself mean FPF’s “system thinking.” For the Work application, “reasoning about performed work” identifies what happened and whose contribution is at issue. Preserve a source’s different use when quoting or explaining it.
Library.Reference:1.2 develops the common construction and its limits. Apply this distinction with F.19 when authoring or repairing a consequential use. The adjective alone supplies neither holon admission nor a part–whole, level or layer relation.
E.10:9.10 - present, represent, representation, representative
Recover what is being shown, described, modelled, instantiated, sampled or acted for, and which relation the current sentence asserts. The shared word can conceal different questions. A presentation can be an act of communicating or its material; a representation can be an expression used to reason about a subject; a representative can be a selected case, a statistical sample or an authorized participant.
When the intended participants and predicate are already clear, keep ordinary wording and use the subject rule. For a remaining ambiguity, E.10.ARCH:3 recovers them. C.2.P supplies source, content and publication distinctions; C.37 supplies representation choice; C.29 supplies mathematical correspondence and returned inference. Kind membership, composition, statistical inference and acting under an assignment retain their own governing rules.
When a sentence relies on a “representative” example or fragment, recover the claim it supports and the basis of that support. A case chosen to illustrate an operation and a sample used for population inference have different grounds. Use C.39.QR when the unresolved question is what the obtained result establishes for the originating assignment; use C.39.WA when that assignment requires the still-missing explanation of a whole subject. Select a useful case by its contribution to the explanation, while preserving the general proposition and its grounds.