Library.Reference:9.1.16 - Requalification and guidance refresh

For a changed client fact, configuration, support, use, horizon or service condition, use C.40.RQ to find the smallest affected opportunity result. Preserve independent qualified uses, historical advice and actual prior configurations. A narrowed data class needs its own quantities and comparisons; a missed necessary observation limits only the reliance that needed it.

For a changed development undertaking, C.40.OD reconnects the affected receiving work, provision and continuation. For a changed shared contribution, timing or allocation, STR.16 reconstructs its affected portfolio uses without inventing dependencies for independent branches. Use C.40.RQ for the opportunity claims whose premises changed; it need not absorb the whole enactment or resource decision.

For a changed source claim with several receiving uses, A.10.1 supplies bounded discovery and actual dependence before each direct practice qualifies its result. For source currentness, decay or scoped refresh, use G.11. A moved file with unchanged accessible claims can require only a repaired reference; an uninspected receiver or expired reliance window cannot be declared unchanged for convenience.

When a source or practitioner result defeats the guidance itself, send the precise failed move, receiving use, source difference and candidate repair to the responsible framework maintainer. Change only the dependent body, relation, entry or example unless the field or branch boundary is genuinely defeated. Updating a client account is not automatically a framework revision; updating a publication date is not a new qualification.