E.10:9.6 - Worked micro‑examples (short, cross‑domain)

Factory. ✗ “The process failed; the service restarted itself.” ✓ The compact strings PLC_17#ObserverRole:PipelineOps, CAB_Chair#ApproverRole:ChangeControl, and OpsBot#DeployerRole:CD_Pipeline_v7 remain quoted source cues only. Start with E.10.ROLE; they are neither system-role-kind designations nor assignment occurrences. PLC_17, ChangeControlBoardSystem, and OpsBot are independently admitted systems. Use ObserverSystemRole, ApproverSystemRole, and DeployerSystemRole only where those classifications matter. For each precise dated Work occurrence, recover the exact actual performer through A.13 and let A.15.1 independently admit the occurrence. Add F.6 only when the example or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves the Work intact. Omit only assignment identifiers that the receiving example does not use. Source suffixes and interpretation epistemes remain separate. The exact dated Work occurrences remain separate from covering assignments and F.6 attributions, and all three remain separate from the log episteme, approval speech-act content, and fulfillment claim. Assignment and F.6 references appear only in an expressly consumed attribution branch. Cloud. ✗ “The process owner approved; the API service deployed.” ✓ The source strings ProductLead#AuthorizerRole:Rollout_2025 and sCG‑Spec_ci_bot#DeployerRole:CD_Pipeline_v7 remain quoted cues. Recover ProductLeadershipSystem and sCGSpecCIBot independently; use AuthorizerSystemRole and DeployerSystemRole only for exact local classification claims. For RolloutApprovalWork-F123 and DeployWork-F123, recover each exact actual performer through A.13 and let A.15.1 independently admit each dated Work occurrence. Add F.6 only when this account or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves the Work intact. Omit only assignment identifiers that the receiving account does not use. Keep source titles, source or scheme cues, approval content, deployment results, and telemetry separate, and identify each through the rule for that value or relation. RESTAccessMethod : U.Method names the exact API access method; RESTAccessDescription is U.MethodDescription only if its claim content substantively describes that method as its exact EntityOfConcern, and it is an access Spec only after the named specification-use gate. Any selected description edition is reached through a separate governed U.EpistemeRef, while file or carrier version remains separate. FeatureAccessPromiseContent states the acceptance condition; telemetry measurements provide evidence for the evaluation that the deployment fulfilled that promise content.

Research. ✗ “Dataset X proves the theory; the process is reproducible.” ✓ DatasetX supports claim C only under the applicable evidence rule, with model-fit scope, polarity, time and provenance stated. Use A.10 to recover its exact source and independently established support/use relations; use B.3, G.6, F.10 or another subject pattern only for the result that pattern defines; replication is recorded through evidence-use, source-use, status-use, or reproducibility-status relations under their respective patterns; procedure wording first recovers one exact U.Method; a separately identified claim-bearing episteme is U.MethodDescription only when that method is its exact EntityOfConcern and its claims pass A.3.2, while re-runs are exact Work occurrences only on the A.15.1 basis.

Semioarchitecture. ✗ “projection has one meaning in routing and bridge prose.” ✓ A.16 keeps projection as a move name for route-bounded partialization; F.9.1 keeps projection as a bridge stance label. If one durable reusable replacement name is really needed, recover the value and use that need a name, record the applicable F.8 decision, and then use F.18 plus F.17 when public publication is current; otherwise retain the source expression or local phrase explicitly rather than flattening both interpretations into one umbrella rewrite.

Editorial note. This section inherits section 7 MG-DA (anchored head nouns; enumeration rule gate; U.Characteristic and CharacteristicSpace only when one named Characteristic has that enumeration as its declared CSLC scale; collision checks) and section 8 LEX.Morph (suffix, prefix, and casing). It deliberately omits their details to avoid duplication. The only admitted uses of plane in the Core are CHR:ReferencePlane and the derived operators CL^plane and Phi_plane; policy flags do not introduce new planes. To distinguish pre-operational and operational states within ReferencePlane=world, use WorldRegime in {prep | live} (formerly PlaneRegime).