Declare AI capability and boundaries before reliance
Every AI surface states the supported task, important limits, data/tool boundary, freshness and expected latency before users depend on it.
実践ガイダンス
Describe observable capability in user language. Disclose provider/model/version only where it changes assessment or accountability. Re-evaluate the contract when tools, data, model or autonomy change.
推奨
- Show unsupported scope before or at the decision point
- Name required data and tools
- Test missing-tool and out-of-scope requests
非推奨
- Promise general intelligence from a narrow workflow
- Use an AI badge as capability disclosure
- Hide material data or latency constraints
検証契約
Contract review plus unsupported-task, missing-tool, stale-data and changed-model test cases
根拠リファレンス
ref.apple.hig-machine-learning— Apple HIG — Machine Learningref.google.pair-guidebook— Google PAIR Guidebookref.ibm.carbon-for-ai— Carbon for AIref.microsoft.human-ai-guidelines— Microsoft Guidelines for Human-AI Interaction