The module layer is stable. | Keep layer as a source label until the sentence reveals a module or interface relation, scale or comparison, publication or view, state, dynamics, or temporal claim. Use only the matching pattern: for example A.6.M, C.16.P, C.29, C.2.P, A.19.SPR, A.3.3, C.27.TA, or C.27. |
The expert routes the token. | In mixture-of-experts prose, first test submodel or subholon, specialized transformation, path selection, architecture-to-flow relation, candidate selection, ordinary wording, or non-use. Only an unresolved claim-bearing use of role opens E.10.ROLE; any system-role kind, classification, assignment, performer, Work, responsibility, or authority claim must be established independently under its direct pattern. |
The cache proves the architecture scales. | Split three questions: what cache names, whether an evidence or assurance relation exists, and what measurable scale or lens-use claim is being made. Use A.6.M, A.6.F, E.18, state or temporal patterns, C.16.P, C.29, A.10, B.3, or G.6 only for the branch that is actually present. |
The LCA upper layer guarantees safety. | First decide whether layer names a control relation. If so, C.30.LCA records the relation, participant meanings, rate band, and relevant locality or model-use boundary. Safety, evidence, assurance, dynamics, temporal, and gate claims remain separate. |
The architecture description places service logic in the application layer. | Recover the description’s declared viewpoint or model-kind convention and what application layer means there. It may be a useful grouping in the description. State separately any claim that the described system itself has an obtaining layer, dependency, module, control, or flow relation; neither the diagram position nor architecture-description conformance establishes that world-side claim. |
Our operating model has strategic, coordination, and execution levels. | If these are only headings or work areas, keep them as local labels. Before claiming levels in an organization or practice, say what the three areas are, how they are ordered or mapped, when that ordering applies, and whether it is asserted, proposed, assumed, or only illustrated. Slide order, a curriculum, or a first-then flow establishes none of this. |
This gate selects the winning architecture. | A neural-network gate or router uses A.6.F or E.18; an internal-constraint result uses A.20; a project gate decision uses A.21; a selector-facing set-result declaration uses G.5, while a local choice among already available options uses C.11. The label alone decides none of these. |