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:00:10 UTC

C.32.MLAO:5 - Worked Residual Cases

Grounded working caseResidual-bearing locusResidual-reducing candidatesStop condition
Regulated product family where shared platform reduces engineering work but grows certification exceptionsProduct-variant scope against family evidence scope; module-interface and evidence-scope structuresAdd reusable evidence scope; narrow interface grammar; keep bounded exception for one variantStop before assurance, G.5 selected-set result declaration, publication availability, or decision unless those claims are current.
Clinical triage arrangement where local intake speed increases downstream escalation missesIntake scope against hospital escalation scope; proposed triage Systems, procedure or Method structure, escalation relation, and optional kind or assignment requirements kept distinctPropose a mediator System or relation, split triage scope by patient class, and state any assignment requirement as plan or decision content. Retarget responsibility only through an admitted direct predicate or record the exact missing governor. Only after performance occurs, recover every precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only when precise assignment-bound attribution is current, and add a Work-to-change relation only when that predicate independently obtains.Stop before ethical mediation or staffing decision unless D.3, D.4, or the receiving staffing-decision pattern is current.
AI-agent review setup where local agent quality improves while policy violations increaseAgent task scope against policy-control scope; control and evidence-refresh structuresAdd supervisor relation; narrow model-interface admissibility; change evidence refresh cadenceStop before safety, gate, release, or causal claims unless their subject patterns are current.
ML inference workflow where the searched functional graph improves quality and exceeds edge-device resource limitsFunctional graph against deployment and resource scopes; module-interface, placement, and resource structuresSplit the function, change deployment placement, add a resource bearer, or reject the candidate for this evolution windowStop before release, benchmark, G.5 result declaration, or publication claims unless the definition and test for each current claim are applied.
Method family where template reuse accelerates authoring and creates review residueAuthoring scope against review scope; method-structure and authored-section structuresSplit method variants; add review-evidence scope; accept bounded local method residueStop before method governance, MVPK publication-face governance, or project decision unless the pattern for the next question is current.
Built-asset maintenance program where digital-twin abstraction hides lower-scope source lossAsset-family scope against maintenance activity scope; reference-designation, information, and maintenance-Method or plan structuresAdd source-return scope; split the information view; retarget maintenance responsibility only through its admitted direct predicate or record the exact missing governor. Introduce actual maintenance Work only through its basis: A.13 first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution.Stop before built-asset architecture-description, publication-face, or A.10 evidence-use claims unless their subject patterns are current.