Start Here
FPF is meant to stay whole. Adoption should be small.
Use this page to choose the first doorway, then move into the reference only when the work needs exact pattern text.
What this page is
This is the adoption entry surface for fpf-memory's FPF wiki. It helps a person, team, or agent choose a first practical path; it is not the full FPF specification and it is not a product changelog.
Methodology
Name the work shape first, pick the smallest matching doorway, and keep exact FPF IDs visible only where they change the work. The full catalog stays available for audit, but it should not be the first mental model.
Pick a doorway
Operating rule
Do not ask people to read all FPF before they can benefit from it. Ask for the work shape, retrieve the smallest grounded slice, and keep the exact IDs visible.
Fast adoption path
- Name the work: project alignment, review, product-role feedback, specification, boundary unpacking, comparison, or agent use.
- Open the matching route or work packet.
- Capture the current claim, role, method, promise, evidence, and risk in ordinary language.
- Add exact FPF IDs only where they change the decision or the acceptance checks.
- Keep the full catalog available as the canonical reference, not as the first screen.
When to use the full catalog
Use Patterns when the doorway is not enough, when an exact pattern clause matters, or when a reader needs to audit the source.