C.30.STRAT:0 - Use this when

Use this pattern when a source uses a compact architecture or stratification label and that word alone does not tell you what technical claim is being made.

Typical labels are layer, level, tier, stack, ladder, rung, structural uses of vertical or horizontal, and architecture-operation words such as block, expert, cache, router, and gate.

What goes wrong if missed. A useful local label starts acting as ontology. A layer is assumed to be a holon level, control layer, publication layer, scale window, or module boundary without deciding which. A stack becomes architecture by name; a block becomes a module; an expert becomes a system-role kind or performer; a cache becomes a state or memory relation; a router becomes a decision policy; a gate becomes a gate decision. Word shape establishes none of these.

What this buys. The reader can keep the source word while making its actual meaning and safe use explicit. Once the object, relation, or claim is clear, use the pattern that defines, constrains, or tests it.

First useful move. Copy the sentence and ask: “What does this label name here, what may I infer from it, and what must I do next?” If it is ordinary wording, keep it and stop. If the answer is already clear, use the applicable pattern directly. Otherwise write one line: label -> recovered meaning; allowed use; next pattern or blocker; stop or return condition. Do not fill an author-facing E.10.ARCH routing row during ordinary project work. Include a blocked overread only when it passes F.19’s plausible-reader test.

Not this pattern when. Do not detour through C.30.STRAT when the object, relation, or claim is already clear. Do not use it merely because a familiar word appears. Ordinary source prose with no FPF claim remains ordinary prose or a quotation.