Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:30:19 UTC

C.32:6 - Bias-Annotation

Scope: Limited to constructing a small candidate architecture palette for one C.30-grounded architecture question about one described holon or holon family. C.32 is not a universal architecting Method, a software-architecture default, a comparison or selection rule, a publication route, or a decision procedure.

LensLikely driftRepair
GovA candidate, front member, generated option, or workshop consensus is treated as selected, authorized, accepted, published, or current.Stop at the palette and use the pattern for the next claim; candidate wording creates none of those relations.
ArchOne visible structure, source diagram, functional graph, or organizational arrangement is treated as the architecture.Ground the exact holon and architecture question, then coordinate only the selected structures and characteristics that actually change the candidate.
Onto-EpistA description artifact, claim, model, role-shaped label, or proposed structure is treated as an obtaining architecture relation or world-side structure.Keep the holon, obtaining relations, selected structures, modal claim content, source artifact, and candidate change distinct; use each direct subject pattern.
PragThe palette becomes a dossier or exhaustive search although two to five useful alternatives would support the next use.Keep the smallest useful set of selected-structure contribution rows, keep one row per candidate, and add richer evidence only when it changes the next architecture use.
DidFormal records or software examples obscure the constructive move for another field.Lead with the ordinary move—structures changed, gain, loss, constraint fit, source return, next use—and use unlike grounded cases; keep the richer record optional.