RA-E-2026-001 — Synthetic Introductory Example: The Training Claim

The case receives the code RA-E-2026-001. RA refers to Reality Audit. E shows that this is a synthetic example, not an actual case. 2026 is the publication year, and 001 shows that this is the first example in the series.

The case is presented at PL3 as a pedagogical public example: the method is public, but no actual persons, institutions, or source materials from real actors are exposed. The lifecycle status is LS8 after completed demonstration because the example shows the full movement from boundary-setting to closure.

The mandate is to examine one bounded training claim in a fictional workshop community. The claim appears in an internal monthly report: “All participants have been trained in the new safety routine.”

The audit does not decide whether the workshop is safe, whether management is good, or whether anyone acted disloyally. It only tests what this particular claim can bear, what the sources show, what must be corrected, and how the correction can be reviewed.

The example uses only functional roles. No names, actual workplaces, or actual documents are used. This makes it possible to show the party and rights matrix without creating a hidden factual case.

The role “technical lead” is separated from “report author.” “Participant” is separated from “person.” The audit does not evaluate personal traits; it examines how the claim, documentation, and training practice correspond.

The sources are synthetic, but they are recorded as if they had to be reviewable. The purpose is to show how sources receive their own codes and how they should not be counted as independent where they depend on the same origin.

The decisive point is that the meeting minutes, notice, and signature list do not show exactly the same thing. One concerns introduction, another public visibility, another signed receipt. None of them alone equals completed training for everyone.

The large sentence is divided into smaller testable links. This prevents the case from being accepted or rejected as a whole without separating routine, population, training, version, and documentation.

The matrix shows that several links are partially supported, but that the main claim is too strong because “all,” “trained,” and “new safety routine” do not have the same source basis.

The example does not use all audit types with equal weight. The primary tracks are Language, Representation, and Practice. System and Authority support the analysis because report, routine version, and responsibility line affect what the claim can bear.

Identity Audit is used only as a safeguard: missing signature or missing attendance must not become a judgment about person or motive.

Preliminary findings are marked as preliminary because the report author and technical lead have not yet answered. The key preliminary finding is that the claim appears overextended, not that it is a lie or capture.

F6 or F7 is not used. There may be a risk that the report template encourages overly broad formulations, but it is not documented that a frame replaced relevant correction with governing consequence.

Contradiction is formulated as precise questions, not as blame. The report author is asked which source supports “all,” what was meant by “trained,” and which routine version was included.

The response is added as SRC005. It explains that the author meant all had access to the material, but that “trained” was not intended as practically verified training.

After contradiction, the main finding is formulated narrowly: the claim “all participants are trained” is too strong relative to the sources. There is support that the routine was introduced and made available, but not that everyone received practical training in the same routine version.

Correction should therefore not be punishment or personal attack. It should correct the claim, documentation practice, and training practice where the grounds actually failed.

The case is closed only when the corrected report wording, renewed training round, and version log are registered in the example. Closure shows that the method does not stop at critique; it requires correction to reach the proper link.

The example also yields method revision: future cases should distinguish more clearly between access to a routine, theoretical introduction, practical exercise, and confirmed understanding.