#Non-framework programme product

Preface node heading:non-framework-programme-product:70485

#What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

#Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

#Content

A cross-domain inquiry need recurs, but practitioners do not need another pattern language. The decision compares a DPF, a maintained inquiry-programme boundary, a separate inquiry evidence-package episteme, a curated route, and no maintained product. It selects the programme boundary because named users need continuing access to inquiry Methods, bounded-project intake, and result return. The answer does not invent a Programme or Product kind.

Its first usable version is a current programme-description episteme that names the users and questions, inquiry Methods, project intake, result return, access, change, and retirement rules. Capable provider and maintaining Systems accept the needed commitments; when a service is claimed, the answer also names the admitted service state. Each bounded inquiry project is separate Work, and each returned result is a separate episteme. A subject pattern may instead admit the programme itself as a System or another exact arrangement, in which case the answer names it. A bounded project may end while the managed programme continues and evolves. The inquiry evidence package remains its own editioned episteme.

---

Last Updated: 2026-08-30 — upstream FPF commit e400eab3 (github.com/ailev/FPF)