#Didactic Primacy & Cognitive Ergonomics

Pattern E.12 · Stable Part E - The FPF Constitution and Authoring Guides

The FPF is designed as an "Operating System for Thought," a tool intended to augment and clarify human (and artificial) reasoning. This mission places a unique demand on its architecture: the framework's internal elegance and formal power are secondary to its primary function of being understandable and usable. A perfectly consistent but incomprehensible system fails in its didactic purpose. As formal mechanisms like Assurance Levels and epistemic scores are introduced, there is a significant risk that the pursuit of these metrics becomes an end in itself, overshadowing the ultimate goal of fostering clearer thought.

#Keywords

• didactic
• cognitive load
• ergonomics
• usability
• Rationale Mandate
• HF-Loop.

#Relations

#Content

#Problem Frame

The FPF is designed as an "Operating System for Thought," a tool intended to augment and clarify human (and artificial) reasoning. This mission places a unique demand on its architecture: the framework's internal elegance and formal power are secondary to its primary function of being understandable and usable. A perfectly consistent but incomprehensible system fails in its didactic purpose. As formal mechanisms like Assurance Levels and epistemic scores are introduced, there is a significant risk that the pursuit of these metrics becomes an end in itself, overshadowing the ultimate goal of fostering clearer thought.

#Problem

If the framework's design prioritizes theoretical purity or formal completeness over cognitive ergonomics, it becomes vulnerable to two critical failure modes:

1. Goodhart's Law: When a measure (like AssuranceLevel:L2) becomes the primary target, it ceases to be a good measure of genuine understanding. Teams may start "gaming the metrics," producing artifacts that are formally perfect but conceptually shallow or pragmatically useless.
2. Cognitive Overload & Rejection: The framework becomes so dense, jargon-laden, and procedurally complex that its users—the very agents it is meant to serve—either burn out or abandon it in favor of simpler, albeit less rigorous, methods. The "Operating System for Thought" devolves into a bureaucratic machine for certification.

#Forces

#Solution

FPF elevates Didactic Primacy (Pillar P-2) to a normative architectural principle, operationalized through two conceptual mechanisms designed to act as a permanent counterbalance to excessive formalism.

#The Principle of Didactic Primacy (Expanded Definition)

The primary purpose of the FPF is to enhance the cognitive capabilities (U.Capability/Mastery) of an Agent (U.Agent) in service of its Objectives (U.Objective). The creation of artifacts with high assurance levels and epistemic scores is a means to that end, not the end itself. Any architectural decision that increases formal rigor at the cost of clarity or usability must be explicitly justified by a demonstrable gain in the agent's ability to reason effectively.

#Mechanism 1: The Rationale Mandate

Every key assurance artifact (such as a U.AssuranceCase or Proof) MUST contain a mandatory, human-readable rationale component.

• Nature: The rationale is not a technical description but a narrative explanation.
• Content: It MUST answer the question: "How does achieving this level of formal assurance tangibly help the agent better understand the problem or make a more reliable decision?"
• Purpose: This mandate forces a moment of reflection, formally linking the act of formalization back to its pragmatic, cognitive purpose. An empty or perfunctory rationale indicates that the assurance work may be an exercise in formalism for its own sake.

Didactic Note for Managers: The "So What?" Test

The Rationale Mandate is FPF's built-in "So What?" test. When your team presents a complex, formally verified artifact (AssuranceLevel:L2), the rationale is where they answer your fundamental question: "This is impressive, but so what? How does this help us ship a better product, make a smarter investment, or avoid a critical risk?" If the answer isn't clear and compelling in the rationale, the formal work may have been a waste of resources. It keeps your most brilliant minds focused on creating value, not just elegant proofs.

#Mechanism 2: The Human-Factor Loop (HF-Loop)**

To provide a continuous, self-correcting mechanism against cognitive overload, FPF introduces a conceptual feedback loop.

• Core Concept: The HF-Loop is a formal method of inquiry designed to distinguish between the essential complexity of the problem being solved and the incidental complexity introduced by the FPF itself.
• Trigger Concept: A review is triggered when the subjective cognitive workload associated with using the framework exceeds a conceptual threshold. This is not about performance metrics, but about the perceived mental effort required to use FPF's concepts and structures.
• Review Concept: When triggered, a formal review is conducted by individuals in roles that specialize in human-centric perspectives, such as the Ethicist and UX Design Critic.
• Output Concept: The review produces a set of proposed conceptual simplifications or didactic improvements to the framework's patterns. These are then submitted as formal change proposals (DRRs).

#Conformance Checklist

• CC-E12.1 (Rationale Mandate): Every U.AssuranceCase or Proof artifact at AssuranceLevel:L2 MUST contain a non-empty rationale component that satisfies the "So What?" test.
• CC-E12.2 (HF-Loop Trigger Condition): Each pattern that defines a significant workflow SHOULD specify a conceptual condition for triggering an HF-Loop review, based on the principle of managing cognitive load.
• CC-E12.3 (HF-Loop Review Mandate): If a trigger condition is met, a review involving the designated human-centric roles MUST be initiated. Its outcome MUST be a documented set of conceptual refinement proposals.
• CC-E12.4 (Didactic Primacy in DRRs): Any DRR proposing a change to a normative pattern MUST include a section analyzing its impact on cognitive ergonomics and didactic clarity.

#Common Anti-Patterns and How to Avoid Them

#Consequences

#Rationale

This pattern operationalizes Didactic Primacy (P-2), transforming it from a philosophical statement into an enforceable architectural Standard. The Rationale Mandate ensures that every act of formalization is tied to a clear purpose. The Human-Factor Loop ensures that the cost of using the framework is measured not just in resources, but in the most critical resource of all: the cognitive capacity of its users.

This pattern does not weaken the formal rigor established by other ADRs; it complements it. It guarantees that the powerful machinery of FPF is always directed towards a meaningful, human-relevant goal. It is the constitutional guarantee that FPF will remain, first and foremost, an "Operating System for Thought."

#Relations

• Implements: Pillar P-2 Didactic Primacy.
• Complements: E.13 Pragmatic Utility & Value Alignment (which focuses on the relevance of the problem, while this pattern focuses on the usability of the framework).
• Is constrained by: The overall governance process (DRRs), which is the vehicle for implementing the conceptual simplifications proposed by the HF-Loop.

#E.12:End