Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:25:20 UTC

C.30:6 - Bias-Annotation

Lenses: Arch, Onto, Epist, Prag, Did, Gov. Scope: FPF architecture-description use over holons.

Bias riskMitigation
Module-diagram biasKeep module structure and interface relation as one structure family among several; use C.30.ASV and the module-and-interface repair pattern when a module or interface claim is being made.
Tool-model biasTreat notation, tool model, generated relation graph, diagram, and dashboard as description, specification-use, or publication forms unless a direct relation gives the source material a more specific use.
Check-only biasReturn an architecture action with its needed basis; a clear ordinary account can supply it.
Assurance or gate biasArchitecture descriptions do not certify safety, evidence sufficiency, release, or gate passage; use the applicable pattern for each such claim.
Didactic-thinning riskThe practitioner situation, payoff, stop condition, and first architecture move explain why the distinctions matter.

Use the following checklist for the architecture claim or action being considered. Its conditions may already be established in the working account; completing a separate form adds no missing relation or argument.