git:20260704.9d26690 to git:20260704.f95c598

---

name: fpf-narrative

description: |

Generate compact, unambiguous FPF-structured output at F4-F5 formality level.

Use when writing for AI agent consumers or FPF-literate humans where token

economy and auditability matter: diagnostics, architecture decisions, code

reviews, status reports, trust assessments, system compositions. Replaces

verbose prose (F0) with typed-slot notation (~65% token savings, lossless).

Do NOT use for: casual chat, teaching, non-technical audiences, creative tasks.

---

# FPF Narrative Prose — Runtime Instructions

## CONCEPTS (runtime ontology — apply these facts)

`U.System` acts. `U.Episteme` does NOT. `U.Work` = run-time (Tᴿ), immutable. `U.Method` / `U.MethodDescription` = design-time (Tᴰ). Tᴰ and Tᴿ never mix in one slot.

`U.Role` = mask; `U.RoleAssignment` = `System#Role:Context`. Roles NEVER in parts lists. Holarchies = substantive holons only.

F-G-R-CL replaces "probably": F = rigor (F0-F9), G = scope (supported only), R = [0,1], CL = congruence (CL0-CL3). Φ(CL): lower CL → larger penalty.

Evidence: `verifiedBy` (formal), `validatedBy` (empirical). SCR: `scr://<domain>/<id>`. ED: `k × max(0, today − valid_until)`. valid_until null = perpetual (axioms/laws only). ED actions: Refresh / Deprecate / Waive.

ADI: ≥3 hypotheses in Abduction. ≥1 prediction per hypothesis. ≥2 tested in Induction (✓/✗). Never 1 hypothesis. Never delete falsified.

---

## FORMAT SELECTION

| Consumer | Task | Audit? | Formality |

|---|---|---|---|

| AI agent | Diagnostics, ADR, review, trust | Yes | F4-F5 |

| AI agent | Status, work log | Sometimes | F3-F4 |

| FPF-literate human | ADR, safety case | Yes | F4-F5 |

| FPF-literate human | Status, casual review | No | F3 hybrid |

| Non-technical human | Any | No | F0 plain |

| Mixed (agent + human) | Any | Yes | F4-F5 + 1-sentence plain |

Rules: Default F0. Upgrade only per table. Any downstream consumer in chain needs F4-F5 → entire chain renders F4-F5. Consumer unknown → F3 hybrid. Teaching → F0-F2.

---

## OUTPUT TEMPLATES

```

```

---

## FORMATTING RULES

Block structure:

```

```

**Markers**

| Marker | Meaning | Required when |

|---|---|---|

| `[confidence: high/medium/low]` | Claim certainty | Uncertain claim |

| `[pending]` | Unverified | Unverified claim |

| `[src: <SCR-id>]` | Source reference | Source-backed claim |

| `→` | Causality/sequence | Trigger chain |

| `@` | Time window | Work record |

| `#` | RoleAssignment | Action performer |

| `Tᴰ` / `Tᴿ` | Design-time / Run-time | Method vs Work separation |

**Prohibitions**

| # | NEVER | Wrong | Correct |

|---|---|---|---|

| 1 | Preambles | "I've reviewed your code…" | Start with template |

| 2 | Pleasantries | "Hope this helps!" | End at last slot value |

| 3 | Unmarked uncertainty | "probably a race condition" | `[confidence: medium]` |

| 4 | Mixed Tᴰ/Tᴿ | "MethodDescription executed at 3pm" | Tᴰ and Tᴿ in separate slots |

| 5 | Episteme actions | "The spec decided to require X" | `System#Role:Ctx` updated carrier |

| 6 | Role in partOf | `parts: [Cell, MonitorRole]` | RoleAssignment only |

| 7 | Prose-in-slots | `Problem: "service is down…"` | Typed sub-slots |

| 8 | Slot invention | Non-canonical top-level slots | Sub-slots under canonical |

| 9 | Non-English output | Slot values in Russian, German, etc. | Translate to English UNLESS translation distorts meaning (proper names, wordplay, domain terms, quoted material — keep original) |

**Mandatory per claim type**

| Claim type | Must include |

|---|---|

| Uncertainty | `[confidence: high/medium/low]` |

| Source-backed | `[src: <SCR-id>]` |

| Trust/reliability | F, G, R, CL tuple |

| Aggregation | Γ flavor + Quintet invariants |

| Evidence | SCR reference |

| Action/execution | `System#Role:Context` + Method or Work |

---

---

## RECONSTRUCTION CONSTRAINTS

When reconstructing prose from an FPF block:

**NEVER include in reconstructed prose:**

- `[src: scr://...]` → omit entirely

---

## HYBRID MODE

When F3 hybrid:

- FPF block self-contained (parsable without plain text).

- Plain text must not contradict or broaden FPF block.

- Separate blocks with clear division.

---

## EXAMPLES

### Diagnostic

F0 (250 tokens):

> I've analyzed the authentication service crashes and found the root cause. The problem is that your JWT verification middleware is executing after the rate limiting middleware. This means that unauthenticated requests are being counted against the rate limit, which allows attackers to exhaust the rate limit for legitimate users. When the rate limit is exhausted, legitimate users get 429 errors, trigger retry storms, and the service eventually crashes under the load. I recommend reordering your middleware chain to put JWT verification before rate limiting, so only authenticated requests are subject to rate limiting. You should also add a null check before accessing user properties. I've verified this by reordering the middleware and running a load test — crashes stopped. The race condition hypothesis was disproved by the load test.

F4-F5 (80 tokens, 68% savings):

```

```

### ADR

F0 (300 tokens):

> We've decided to use PostgreSQL as our primary database for the new platform. The team already knows PostgreSQL well, which reduces the learning curve. It handles our expected load with room to grow, and its proven reliability means we won't have data loss issues. We considered MongoDB for flexibility, but the team lacks operational experience with it. We also looked at CockroachDB for horizontal scaling, but we don't need that level of distribution yet. The main tradeoffs are higher operational cost compared to a managed NoSQL service, and some overhead from the ORM layer we'll need.

F4-F5 (100 tokens, 67% savings):

```

```

### Status

F0 (140 tokens):

> We're at about 72% completion on the AuthModule. Registration and login are done, password reset is in progress with an ETA of July 8th. Two-factor auth is blocked because we're waiting on the SMS provider contract. The overall project is on track for the July 15th milestone, but if the SMS contract isn't signed by July 9th, we'll need to descope 2FA from this release.

F4-F5 (55 tokens, 61% savings):

```

```

---

## SELF-CHECK

Answer all. If any answer is NO, repair.

| # | Check | Must be YES |

|---|---|---|

| 1 | Formality from decision table (not default)? | YES |

---

## REFERENCE

### U.-Prefix

| Type | Meaning | Acts? |

|---|---|---|

| `U.Entity` | Anything distinguishable | — |

| `U.Holon` | Whole AND part; has U.Boundary | — |

| `U.System` | Physical/operational holon | **YES** |

| `U.Episteme` | Knowledge (spec, proof, model) | **NO** |

| `U.Boundary` | Holon boundary (open/closed/permeable) | — |

| `U.Interaction` | Flow across boundary | — |

| `U.Role` | Capability/obligation mask | — |

| `U.RoleAssignment` | Holder#Role:Context binding | — |

| `U.BoundedContext` | Context where terms have meaning | — |

| `U.MethodDescription` | Recipe (Tᴰ) | — |

| `U.Method` | Capability to execute (Tᴰ) | — |

| `U.Work` | Dated execution (Tᴿ, IMMUTABLE) | — |

### Γ Flavors

| Γ | Domain | Relaxed |

|---|---|---|

| `Γ_sys` | Physical/cyber-physical | — |

| `Γ_epist` | Knowledge, meta-analysis | — |

| `Γ_ctx` | Order-sensitive processes | COMM, LOC |

| `Γ_time` | Time series, digital twins | COMM partial, LOC |

| `Γ_work` | Resources | — |

| `Γ_method` | Methods | — |

### Quintet Invariants

| Code | Meaning | Test |

|---|---|---|

| `IDEM` | Γ({h}) = h | One part = itself? |

| `COMM` | Γ({a,b}) = Γ({b,a}) | Order of independent parts irrelevant? |

| `LOC` | Worker-agnostic | Where fold executes irrelevant? |

| `WLNK` | R_eff = min(R_i) | Whole ≤ weakest part? |

| `MONO` | ↑R_i → ↑R_eff | Improving part never hurts? |

### F-G-R-CL

| Char | Scale | Meaning |

|---|---|---|

| `F` (Formality) | F0-F5 | F0=unstructured, F1=stable terms, F2=structured outline, F3=controlled narrative, F4=predicates/invariants, F5=executable math |

| `G` (ClaimScope) | Coverage | Supported only; unsupported dropped |

| `R` (Reliability) | [0,1] | Probability of truth |

| `CL` (Congruence) | CL0-CL3 | CL0=weak guess, CL1=plausible, CL2=validated, CL3=verified |

Formulas (mandatory):

```

F_eff = min(F_i) G_eff = SpanUnion({G_i}) | support

R_raw = min(R_i) R_eff = max(0, R_raw − Φ(CL_min))

```

Φ(CL): lower CL → larger penalty. Never skip.

### ADI Reasoning

| Phase | Action | Minimum |

|---|---|---|

| **A**bduction | Generate hypotheses | ≥3, recommend 5 |

| **D**eduction | Testable predictions | ≥1 per hypothesis |

| **I**nduction | Test against evidence | ≥2 hypotheses, ✓/✗ |

| Conclusion | Selected, rejected, confidence | "H₁ confirmed; H₃ falsified" |

Rules: Never 1 hypothesis. Never delete falsified (keep ✗). Never "probably" — use ✓/✗ and R.

### Evidence

| Anchor | Type | Use |

|---|---|---|

| `verifiedBy` | Formal | Static guarantees, model-checking |

| `validatedBy` | Empirical | Measurements, load tests, observations |

SCR: `scr://<domain>/<id>`. ED: `k × max(0, today − valid_until)`. valid_until null = perpetual (axioms/laws only). ED actions: Refresh / Deprecate / Waive.

### Strict Distinctions

| # | Violation | Scan for | Fix |

|---|---|---|---|

| 1 | Role = Function | Role + action verb | `System#Role:Ctx` executes Method |

| 2 | MethodDesc = Method = Work | Tᴿ slot has MethodDesc; Tᴰ slot has Work | Split with Tᴰ/Tᴿ |

| 3 | System = Episteme | Episteme noun + action verb | `System#Role:Ctx` → Work on Episteme carrier |

| 4 | Episteme = Carrier | "The document updated itself" | System → Work on carrier; Episteme = content |

| 5 | Collective = Set | MemberOf for acting group | ComponentOf for collective; MemberOf for sets |

**Rewrites**

| Wrong | Correct |

|---|---|

| "The spec decided to require X" | `DesignService#TransformerRole:SpecCtx` updated carrier → req X |

| "The process executed the rule" | `System#TransformerRole:Ctx` executed `Method`; `Work` → SCR |

| "Holon bearing TransformerRole" | `System bearing TransformerRole` |

| "parts: [Cell, MonitorRole]" | `parts: [Cell, …]`; `RoleAssignment: BMSSystem#MonitorRole:PackCtx` |

| "The report concluded that…" | `AnalystSystem#TransformerRole:Ctx` executed Method; conclusion ∈ U.Episteme(X) |

### Mereology

| Relation | For | Domain |

|---|---|---|

| `ComponentOf` | Structural part | U.System |

| `ConstituentOf` | Logical/content part | U.Episteme |

| `PortionOf` | Quantitative portion | Matter/resources |

| `PhaseOf` | Temporal part/state | Continuous identity |

| `MemberOf` | Set membership | Mathematical sets |

| `RoleBearerOf` | System bears Role | U.System ↔ U.Role |

Rule: Roles NEVER in parts lists. Holarchies = holons. Roles → RoleAssignment.