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

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:35:10 UTC

Professional and AI-source qualification

Source and qualified readingReceiving contributionScope limit and return
NCDA Code of Ethics, 2024, A.2, A.10 and E.2.Adapted in DOCA.7’s career-service participation, assessment-competence, information-use and referral boundaries.The identified professional scope does not establish local law or the adviser’s actual competence. Determine the applicable service and local requirements before relying on those claims. A changed code or use reopens the affected condition.
ICMCI competence framework v4.0, approved October 2021, identified C.1/C.2 engagement and E.3.5 impartiality clauses.Bounded clause reliance for client involvement and material conflict treatment in DOCA.7.The official ICD 2026 page lists an update presentation. Its existence does not make this older framework the complete current standard or establish that the full update was inspected. A complete current certification claim remains outside this reliance.
ICMCI Code of Responsible Use of Artificial Intelligence, v1.0, May 2026, sections 1.2, 2.2, 3.1–3.4, 5 and 7.Adopted within professional scope in DOCA.7: responsibility, human content review, protected information, competence and material-use disclosure.Routine tool availability is not warrant. Actual adoption, contract and applicable requirements determine the service conditions. The code does not evaluate an AI development subject.
NIST AI RMF Playbook, MAP 1.1 and MAP 4.1: receiving context, assumptions, third-party components and support risks.Adapted in DOCA.5 and DOCA.8 for configuration-specific joint premises and changed-use effects.These Map contributions do not provide the client’s evaluation, causal result or permission. The source describes RMF revision in progress; this is not reliance on a claimed completed replacement edition. Reopen the affected configuration or source claim.

For a concrete currentness episode, suppose an adviser needs to know whether “ICMCI compliant” establishes all required engagement conditions. The identified v4.0 clauses support the bounded involvement/conflict contribution, and the May 2026 AI Code supplies a separate scoped AI-use contribution. Neither closes the broader complete-current-standard claim. The visible 2026 update cue returns that precise claim to the professional source owner; the adviser can retain the identified qualified contributions while withholding the broader assertion. Local legal and professional applicability still needs its own result. A newer label alone supplies none of these conclusions.