| Start from a compulsory document or view list | Start from the receiving decisions and decision-changing claims; add a description only when its use changes Work or reliance. |
| Treat one repository as one model | Recover each claim-bearing episteme, source edition, subject, scheme, and use independently of storage co-location. |
| Treat same names as same subjects | Resolve actual identity, kind, part, configuration, interval, and designation separately. |
| Count links as traceability | For each material link, name its participants, relation, relying decision, and failure consequence. |
| Call every publication face a view | Apply E.17.0 only when U.View membership matters; otherwise name the publication form and bounded use plainly. |
| Let a simulation stand for the plant | State the modeled subject, assumptions, validity boundary, and evidence needed for the physical claim under SYSE.10. |
| Freeze one baseline as lifecycle truth | Keep configuration and effectivity under SYSE.13; refresh affected claims and relations when the world or source changes. |
| Demand one shared ontology | Use a shared scheme only where its benefits exceed lost specialist distinctions; otherwise maintain explicit correspondences and unresolved differences. |
| Create a digital twin by label | Name the selected subject, description/model set, automation, observations, current use, evidence, and maintenance Work; drop the label if it changes nothing. |
| Accept generated correspondence by confidence score | Treat it as a candidate episteme; inspect sources, subjects, relation, exceptions, and decision consequence. |
| Let specialists exchange files without a receiving use | Use SYSE.9 to state the requested professional contribution, receiving decision, acceptance condition, and result to return. |
| Make the pattern or account act | Name the Agent, Method, and performed Work; epistemes describe, support, or constrain through use relations. |