Library / Method Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 03:55:20 UTC

ME.17:7 - Conformance Checklist

  • A C.20 Discipline result is used, or a smaller C.36 practice and population boundary is named with the Discipline claim unresolved.
  • The subject branch is honest: admitted Method plus independently grounded enactment, or candidate/observed practice plus honestly named candidate accounts, source claims, cards, templates, description epistemes, and Work facts without Method, U.MethodDescription, or enactment inflation.
  • One value, participant meanings, applicability condition, obtaining predicate, positive case, and discriminating negative or failed case are explicit.
  • A.6.RCD returns the lightest truthful disposition; A.6.REL occurrence identity is opened only when later use must distinguish occurrences.
  • The world-side claim, claim episteme, evidence and reliance, and named-interval observations remain separate.
  • Cards, descriptions with their recorded kind and status, publications, Systems, teaching/tutoring/event Work, rules, fields, forums, assignments, permissions, authority, and other direct relations are separately identified as subjects.
  • A.22 is used only for one selected structure and C.30 only for a current architecture question.
  • When the intended action requires authorization, its assignment, permission, or authority predicate, participants, permitted action, scope, positive basis, and protected conditions are explicit; a factual account creates no intervention.
  • The supported current account or continuation can finish without a fixed hypothesis count or new intervention. Credible action-changing rivals and relevant uncertainty remain; a selected inquiry has an attainable contribution worth its whole burden, including design effort, and feasible participants, access, resources, and window.
  • C.27 is used only for a temporal adequacy claim, A.3.3 only for a transition law, C.28 only for causal reliance, A.15.7 only during ongoing Work, and C.11 only after a chooser and OptionSet exist.
  • A claim of tested change or later retention uses the actual Work and interval observations it asserts, without automatically reidentifying one occurrence across intervals. Missing later evidence withholds only the dependent claim.
  • Practitioner or constructed-Method consequences, non-use, burden, adaptation, and rejection remain separate from the cultural predicate.
  • An unresolved explanation remains unknown where relevant without erasing an independently supported continuation, narrower claim, or stop.
  • Separate cases, populations, organizational Systems, histories, predicates, and effects are not joined.
  • Any return to ME.15 or ME.10 names one particular contradicted maintained claim or edition. ME.8 receives a needed MethodDescription or candidate-Method-account correction, preserving its status; other source claims return to their own episteme or a local stop. Population spread alone triggers no return.