Library / Development Opportunity Construction and Development-Direction Advising Principles Framework
Jump to passage
In this reading

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 07:05:20 UTC

DOCA.8:2 - Problem

Practitioners can respond to change too broadly or too narrowly. They repeat every assessment because a source version changed, or merely replace a link while the supported use has narrowed. They discard an independent manual route when one AI configuration loses permission, or carry an old whole-use estimate into a smaller data class.

Another error rewrites the past. A revised opportunity description makes a previous recommendation seem different from what was delivered. A later step is treated as implemented because it was retained in a path. A missed observation is interpreted as evidence that nothing changed.

The practitioner needs a local account of what changed, what actually depended on it, what is now supported, and who must act on the resulting question.