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 14:30:10 UTC

E.8.ECSPF:3 - Forces

ForceTension
Recognition first vs coordinate completenessAn evaluation-characteristic-space pattern needs tables, but the reader must first see the working situation and first evaluation use.
Generic E.8 form vs evaluation contentThe canonical pattern skeleton stays fixed, but the evaluation has special content fields from A.19.ECS.
Reusable FPF pattern vs local evaluationFPF publication is useful only when the evaluation is durable and reusable beyond one local project.
Values named by value vs checklist feelValues and statuses must be named by value without making the pattern feel like an administrative form.
Related-pattern statements vs second ontologyFor each outside claim, the pattern must state the concrete contribution it uses from neighbouring content, without forcing every contribution into one verb list or becoming a directory of possibly related patterns.
Evaluation of object vs evaluation of FPF pattern versionThe evaluation judges its evaluated object; E.21 may separately evaluate whether the authored FPF pattern publication form is good enough.