#FPF Pillar-Adequacy Evaluation CharacteristicSpace

E.2.DA · Stable · Definitional pattern · Normative · Part E - The FPF Constitution and Authoring Guides

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Definitional pattern Status: Stable Normativity: Normative

Use E.2.DA when the FPF object under improvement is FPF as a whole, one FPF corpus slice, one release candidate, one pattern family, one projection set, or one host set, and the question is whether that object under improvement realizes the E.2 Pillars well enough for a declared working use.

#Relations

#Content

#Problem frame

Use E.2.DA when the FPF object under improvement is FPF as a whole, one FPF corpus slice, one release candidate, one pattern family, one projection set, or one host set, and the question is whether that object under improvement realizes the E.2 Pillars well enough for a declared working use.

E.2 is the constitutional source: it names the Pillars and their meaning. E.2.DA is the object-under-improvement evaluation: it turns those Pillars into a declared characteristic space with ordinal values, evidence loci, stop conditions, and reopen conditions for FPF-level adequacy reads.

Use it when an improvement loop is trying to make FPF easier to enter, search, read, compose, repair, and extend while preserving constitutional force: for example after a broad lexical cleanup, after a new pattern cluster lands, after recurring external-review returns expose repeated wording failures, or when several front-like vocabularies such as all 5s, exceptional, SoTA, Pareto front, NQD Q movement, proposal portfolio, and shortlist must become discoverable without becoming synonyms.

FPF-local scope. E.2.DA is not a generic quality pattern for any pattern language. It refines E.2 for FPF. External pattern-language traditions may supply source stance or comparison pressure, but they do not create an intermediate "any pattern language" object-under-improvement evaluation. A non-FPF corpus can use this pattern only after a bounded decision declares that the corpus is being read as an FPF-conformant corpus under E.2; otherwise it needs a separate object-under-improvement evaluation.

Not this pattern when. Use E.2 for the Pillars themselves. Use E.21 for one authored FPF pattern version. Use E.9.DA for one DRR decision-adequacy claim. Use E.22 to frame one improvement-oriented quality read. Use E.23 for the repeated improvement-loop method. Use E.11 for first-practical entry and pattern-use discoverability. Use E.10, A.6.P, C.2.P, C.16.Q, or F.18 when the live defect is one local wording, relation, source-transfer, quality-term, or durable-name repair. Use E.8 when the live defect is the authoring form of one pattern body.

First useful move. Name the FPF object under improvement, the working reader and use, the qualification window, and the first Pillar whose realized adequacy may be below the declared floor.

Cheap stop. If the defect is local to one pattern version, return to E.21. If the defect is local wording, return to E.10 or the exact precision-restoration pattern. If the defect is local to one DRR, return to E.9.DA. Open E.2.DA only when the adequacy problem is visible across several patterns, entry projections, relation rows, source-use posture, quality vocabulary, Pillar realization, or corpus projections.

What goes wrong if missed. FPF can have many good patterns and still fail the FPF constitution. A local edit improves one pattern while harming P-2 didactic primacy or P-5 layering elsewhere. A broad cleanup makes text admissible but inert. A new cluster adds precision but damages entry, composition, or open-ended evolution. Pillars remain named in E.2 but stop being recoverable enough through declared coordinates to guide FPF-level improvement.

What this buys. E.2.DA gives FPF one object-under-improvement evaluation for Pillar adequacy. It lets E.23 improve FPF as one object under improvement while keeping Pillar values, evidence, stop meanings, and neighbour exits explicit.

Governed object in plain terms. The governed object is the Pillar adequacy claim for one FPF object under improvement under one declared working use and qualification window.

Primary working reader. The first reader is an FPF author, reviewer, or steward improving FPF. The downstream reader is the practitioner or manager who must use FPF as action guidance.

#Problem

Pillars are not decorative values. They are the first-principles commitments that make FPF recognizable as FPF: decisive structure, teachability, maturing formality, open kernel, layering, register discipline, practical payoff, cross-scale consistency, explicit state, open-ended evolution, and SoTA renewal.

But E.2 alone does not say how to read whether FPF currently realizes those commitments well enough in a concrete corpus slice. Without an object-under-improvement evaluation, Pillar talk becomes either essay prose or informal approval.

The recurring failures are:

1. Pillar-as-slogan failure. A DRR or review names P-2 or P-7, but no content evidence shows how the result helps comprehension or practical action.
2. Good-pattern, weak-FPF failure. Individual patterns read well, but the corpus becomes harder to enter, compose, refresh, or keep coherent.
3. Local win, Pillar loss. One pattern edit improves local precision while harming didactic force, layer boundaries, register discipline, or open-ended evolution elsewhere.
4. Hidden scalarization. Several Pillars are collapsed into one "FPF quality" score.
5. Sterile precision. Lexical repair removes overread but also removes the first useful reason to act.
6. Decorative currentness. Source and SoTA posture varies by section; current practice is cited without changing the move, boundary, example, or stop rule.
7. Second ontology growth. An entry projection, publication companion, review packet, source packet, or local table starts carrying semantics that belong in a governing pattern.
8. No FPF-level stop. Improvement continues endlessly because no object-under-improvement evaluation says when the selected FPF object under improvement is adequate for the declared use.

#Forces

#Solution

State the FPF-level read as a FPFPillarAdequacyQBundle, not as one score and not as many independent E.21 reads.

#Architectural position

E.2.DA is the object-under-improvement evaluation for claims of the form "this FPF object under improvement adequately realizes the E.2 Pillars for this working use."

E.2 remains the constitutional pattern. It names the Pillars and their authority. E.2.DA imports the Pillars as coordinate heads and supplies ordinal value meanings for the adequacy read. Pattern-local coordinates in E.21, E.9.DA, E.11, E.23, or other patterns may supply evidence or mechanisms that move an FPF object under improvement along these Pillar coordinates; they do not add new Pillars.

E.2.DA governs only these questions:

1. Which exact FPF object under improvement and exact version is being evaluated for Pillar adequacy?
2. For which reader, use, object-under-improvement role, and qualification window?
3. Which E.2 Pillars are active, and which are not live for this read?
4. Which eligibility blockers make Pillar-coordinate comparison meaningless?
5. Which Pillar adequacy coordinates are active?
6. Which pattern, projection, source, relation, or entry loci justify those readings?
7. Which FPFPillarAdequacyStatus follows?
8. Why may improvement stop, narrow, continue under E.23, or return to exact neighbours?

E.2.DA does not govern:

• changing the Pillar list or Pillar meanings, which stays with E.2;
• writing one pattern body, which stays with E.8;
• reading one pattern version, which stays with E.21;
• reading one DRR, which stays with E.9.DA;
• framing one read, which stays with E.22;
• running the repeated loop, which stays with E.23;
• local lexical, relation, source-transfer, quality-term, or durable-name repair, which stays with E.10, A.6.P, C.2.P, C.16.Q, and F.18;
• first-practical entry coordination, which stays with E.11;
• evidence, assurance, gate, work, release, safety, compliance, or project-world claims.

#Local names and kind settlement

These names are local to E.2.DA. They do not mint a new kernel kind, ordered process state, pattern kind, entry kind, evidence kind, assurance kind, or release kind.

#FPFPillarAdequacyQBundle

FPFPillarAdequacyQBundle := <FPFObjectUnderImprovementRef, FPFAdequacyUseScope, FPFAdequacyReaderScope, FPFAdequacyQualificationWindow, QualityReadQuestionFrameRef?, PillarAdequacyEligibilitySet, PillarAdequacyDominanceSet, PillarAdequacyEvidenceRefs, FPFPillarAdequacyStatus, StopOrRepairCondition>

The bundle is replayable when another reader can recover the same FPF object under improvement, use, reader scope, active eligibility rows, active Pillar coordinates, evidence loci, status, and stop or repair reason without chat memory or administrative state.

QualityReadQuestionFrameRef? may cite E.22 when the read purpose needs to distinguish floor read, exceptional improvement, Pareto trade-off, open-question discovery, absorption, or proposal portfolio return.

#Eligibility set

Check these hard filters when live:

#Ordinal coordinate scale

FPFPillarAdequacyEvaluationCharacteristicSpace uses the same neutral zero-based six-value ordinal shape as E.21 and E.9.DA.

The scale is ordinal. Do not average it, convert it to a percentage, or treat it as a maturity ladder. A value says how well one Pillar is realized for the declared FPF object under improvement and use.

#Orthogonalized Pillar coordinate set

Activate the Pillar coordinates that the declared FPF use makes live. A whole-FPF or release-candidate read normally activates all eleven. A narrower corpus-slice read may activate only the Pillars that the change can materially affect, but it must state the inactive Pillars and why they are not live.

The eleven Pillars are not independent in ordinary language. E.2.DA orthogonalizes them by primary failure question. A coordinate value names the first Pillar whose primary question would fail; the same evidence may be cited as a secondary effect for another Pillar only when the read says why that second effect changes stop, repair, or reopen.

#Coordinate separation guards

Use these guards when two Pillars both look live:

If the separation cannot be stated, the read must not hide the uncertainty under a broad Pillar-adequacy sentence. It returns repairBeforeFPFUse, narrows the FPF use, or opens holdForArchitectureDecision.

#Cross-coordinate evidence organization rows

Some corpus-level defects affect several Pillars at once. Use these evidence organization rows only to group evidence loci for a Pillar-adequacy read; they are not extra Pillars.

#Status and stop condition

FPFPillarAdequacyStatus uses these values:

Improvement can stop for the declared FPF use only when:

StopCondition :=
  PillarAdequacyEligibilitySet passes
  AND all active PillarAdequacyDominanceSet coordinates meet the declared floor
  AND no active Pillar coordinate has hidden loss from an unstated evidence locus or relation claim
  AND the first useful reader move survives
  AND front-like vocabulary is assigned to exact governing patterns where live
  AND remaining weaknesses are expressed as bounded non-use or exact neighbour exits

An all-5 or all-exceptional result is local to the named FPF object under improvement, use, reader scope, qualification window, and comparison basis. It can close this read without claiming that FPF cannot improve further.

#Projection from E.21 and E.9.DA

E.21 and E.9.DA remain local object-under-improvement evaluations. They do not add up into E.2.DA, and their coordinate values are not averaged into FPF adequacy. They may supply contribution evidence when a read states:

ContributionToPillarAdequacy :=
  <sourceObjectUnderImprovementEvaluationRef, sourceObjectUnderImprovementRef, sourceCoordinateOrEligibilityRef,
   sourceValueOrStatus, affectedFPFObjectUnderImprovementRef, affectedPillarCoordinate,
   contributionKind, evidenceLocus, protectedTradeoffOrLoss, reopenCondition>

contributionKind is one of raises, preserves, lowers, blocks, or opensQuestion. A high local value with no named affected FPF object under improvement and Pillar coordinate is not FPF-level improvement evidence.

Common projections:

The projection may be negative. A pattern can improve under [E.21](/generated/patterns/E.21) for a narrow use while lowering whole-FPF P2 or P5 because it increases entry cost or relation fanout. A DRR can become more adequate for one authoring use while lowering P1 or P10 if it adds apparatus that makes the selected FPF object under improvement harder to maintain. [E.2.DA](/generated/patterns/E.2.DA) asks for that trade-off explicitly before stop.

#Neighbour and self-application boundaries

E.2.DA is an A.19.ECS-style evaluation characteristic-space specialization for FPF Pillar adequacy. It relies on A.19 for CharacteristicSpace structure, A.17 and A.18 for characteristic and scale discipline when exact measurement or comparability is live, and C.16 when a Pillar-adequacy reading becomes a measurement or metric characterization claim. It does not define those neighbouring objects, scales, or measurement conditions.

Entry and projection loci may trigger an E.2.DA read when they show FPF-level Pillar loss or gain, but they do not define Pillar meaning, pattern semantics, or entry authority. E.11, J.4, E.17, and I.2 keep their governing roles; E.2.DA reads only their contribution to active Pillar coordinates for the named FPF object under improvement.

Admissible entry cues include "FPF-level Pillar adequacy read", "whole-FPF object under improvement", "FPF corpus-slice adequacy", "Pillar loss from local repairs", and "front-like vocabulary across FPF". Wrong-entry stops are equally important: not one pattern-quality read, not one DRR adequacy read, not local precision repair, not release approval, not generic pattern-language quality, and not glossary synonym assignment. A thin echo in J.4, a table of contents row, or a review packet may point to these cues, but it must point back here rather than defining them.

Self-application is admissible only as a Pillar-adequacy read of an FPF object that includes E.2.DA or a campaign package that changes E.2.DA. Local defects inside this pattern, such as a bad name, weak example, outdated source row, or malformed conformance line, return to E.21, E.10, E.19, or E.9.DA. E.2.DA cannot close E.2.DA adequacy by mentioning Pillars; the read must state the affected FPF object, active Pillars, evidence loci, comparison basis, stop condition, and neighbouring-pattern exits.

#Relationship to E.23

E.23 supplies the repeated improvement-loop method. E.2.DA supplies one possible object-under-improvement evaluation for that method when the object under improvement is whole-FPF or FPF-corpus Pillar adequacy.

The loop instance is declared as:

ObjectUnderImprovementRef: FPFObjectUnderImprovementRef
ObjectUnderImprovementEvaluationRef: E.2.DA
QualityReadQuestionFrameRef: E.22 when a nontrivial read purpose is live
Method: E.23

This is the same [E.23](/generated/patterns/E.23) method used for pattern versions, DRRs, OEE/NQD candidates, architecture descriptions, or other objects under improvement. The object under improvement and object-under-improvement evaluation change; the loop method does not.

#Worked slices

Show, broad precision cleanup. A hard lexical pass made many pattern sections more admissible but some Problem frames now explain less about why the distinction matters. E.2.DA reads the corpus slice through P2DidacticPrimacyAdequacy, P6LexicalStratificationAdequacy, P7PragmaticUtilityAdequacy, and PrecisionRepairDistribution. Local wording defects return to E.10; FPF-level Pillar loss stays in E.2.DA; repeated repair uses E.23.

Show, front-like vocabulary harmonization. Readers use "all 5s", "Pareto", "SoTA", "NQD front", and "shortlist" as if they were the same. E.2.DA reads the effect on P1, P5, P6, P7, P10, and P11 through FrontLikeVocabularyGoverningPatternAssignment. The repair is not one glossary synonym row; it assigns each phrase to the exact object-under-improvement evaluation or neighbouring pattern that governs the live claim.

Show, local pattern edit with FPF-level loss. One pattern improves its examples but introduces a broad source-or-evidence-role phrase that other patterns may copy. If the issue is only that pattern, E.21 and E.10 suffice. If the phrase starts creating cross-pattern source, evidence, or projection ambiguity, E.2.DA opens and sends exact local repairs back to the governing patterns.

Show, whole-FPF improvement loop. A steward wants FPF itself to become easier for project teams while staying current and open-ended. E.22 frames the read, E.2.DA supplies the Pillar coordinates, and E.23 governs repeated proposal application and re-read. Stop is local: the declared FPF object under improvement may reach the current comparison basis, while future uses and source changes can reopen the loop.

Show, anti-semio substitution check. A campaign improves language around engineering work, but the resulting prose mostly explains how to talk about decisions, evidence, or work instead of making clear which decision record, evidence path, work plan, gate decision, or call-planning pattern is live. E.2.DA reads the FPF-level effect through P7PragmaticUtilityAdequacy, P5FPFLayeringAdequacy, P9StateExplicitnessAdequacy, and TalkForWorkSubstitutionResistance. The repair names the exact neighbouring pattern for the real work, evidence, assurance, gate, decision, or call-planning claim, or demotes the prose to recognition guidance.

Near miss, E.21 overreach. A reviewer applies E.21 to ten patterns and averages the results. This is non-conforming. E.21 reads each pattern version; E.2.DA reads the FPF-level Pillar adequacy claim without scalarizing pattern-quality results.

#Conformance checklist

#Common anti-patterns

#Relations

#Rationale

FPF needs an FPF-level object-under-improvement evaluation because local pattern quality does not guarantee constitutional adequacy. E.21 can say that one pattern is good for one use. It cannot by itself say that the selected FPF object under improvement realizes E.2 Pillars across incoming vocabulary, neighbour exits, source stance, projections, and front-like improvement claims.

This pattern keeps E.2 clean. E.2 remains the constitution: it states the Pillars and their meaning. E.2.DA supplies the characteristic space for reading realized adequacy against those Pillars. That makes Pillar-based improvement actionable without turning E.2 into a review harness.

A general "any pattern language" layer would be a weak umbrella unless that language had declared pillars, authoring form, entry discipline, source stance, and quality values. FPF already has those loci in E.2, E.8, E.11, E.21, E.22, E.23, E.10, and neighbouring precision and quality patterns. E.2.DA therefore reads FPF adequacy directly instead of inserting a generic intermediary.

#SoTA-Echoing

E.2.DA does not import source authority directly. It reuses source stance already carried by exact neighbouring patterns and reads only the FPF-level Pillar effect:

#Consequences

E.2.DA makes it possible to improve FPF as FPF without pretending that one pattern-quality score, one DRR adequacy score, or one lexical cleanup proves constitutional adequacy.

It also adds a discipline cost: FPF-level adequacy claims must name their FPF object under improvement, use, evidence loci, active Pillars, coordinate values, and stop condition. That cost is only justified when the problem is genuinely FPF-level. Local defects should stay local.

#E.2.DA:End

Last Updated: 2026-05-29 — this section last modified in upstream FPF commit 2e112078 (github.com/ailev/FPF)