fpf.tools
Library / Development Opportunity Construction and Development-Direction Advising Principles Framework
Jump to passage
In this reading
Source · lines 2274–2285

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:00:20 UTC

DOCA.8:11 - SoTA-Echoing

Practice question. How can a development inquiry respond to changed premises without either replaying every result or preserving unsupported opportunities and advice?

Best-known line for this use. Qualify the claim-sized change, establish actual reliance, and return the affected question to its direct owner. This pattern adopts A.10.1’s bounded source-to-use discovery only for that source-change question in :4.2, and adapts PSD.14’s distinction among observation, interpretation, advice, decision, and implementation in :4.5–:4.6. DOCA.3–DOCA.7 supply the opportunity-specific result being reconsidered; G.11 retains currentness and refresh work.

Serious alternatives and trade-off. Rechecking everything can be justified when the affected basis cannot be separated. It is unnecessary for the independently permitted manual route in :5.1. Updating only a source pointer is cheaper but misses the corrected support claim in :5.2. At comparable inspection effort, recovering the actual receiving premise distinguishes the two cases and identifies the smallest needed result. Bounded discovery costs more than a citation scan and may end with unresolved coverage; that is preferable to unsupported complete-preservation claims. No measured efficiency advantage is asserted.

AI-specific source return. The current NIST AI RMF Playbook, MAP 1.1 emphasizes receiving context, assumptions, operational requirements, and downstream effects of system changes. This pattern adapts that line in :4.1, :4.3, and :5.1: a changed configuration or use requires qualification of the receiving contribution, not merely a fresh product label. The source does not supply the client’s evaluation, permission, or causal result.

Limits and reopen. The cases are constructed probes of the distinctions, not evidence of field effectiveness. Reopen the relevant requalification rule when actual uses reveal missed dependence, an inadequate discovery frame, unaffordable burden, or a stronger direct-domain method. Changes to the guidance itself go to its maintainer; a new client fact does not alone require changing the pattern.