Fill these in. Remove half the ambiguity from your AI project.
Copy-paste templates for the decisions classic design files do not cover: behaviour, grounding, evaluation, failure, approval, escalation and change. Free to use. No login.
17 working artifacts15 primary sources reviewedDaily source sweep · publish only on real change
OPEN AI-NATIVE DESIGN SYSTEM06 / Specify
WHY THIS EXISTS
The interface is the visible part. These decisions are the product.
An AI project goes vague when nobody owns what the model may do, what good means, where evidence comes from, or when a person steps in. This kit makes those choices reviewable before they turn into bugs.
01TemplateReviewed 30 Aug 2026
Template / WORKING PREVIEWCapability + boundary brief
User job
Model-assisted task
What the system can do reliably
What varies by context
Capability + boundary brief
Define what the system can do, where it becomes unreliable, and what it must never imply.
Use it whenBefore scope or interface work. It stops a promising demo becoming a dishonest product promise.
# Capability + boundary brief
User job:
Model-assisted task:
What the system can do reliably:
What varies by context:
What it cannot know:
What it must never imply:
Evidence required before showing a result:
Safe fallback when confidence is low:
Owner of the final decision:
02TemplateReviewed 30 Aug 2026
Template / WORKING PREVIEWModel behaviour spec
Role in the product
Primary objective
Priority order when goals conflict
Must do
Model behaviour spec
Turn product intent into explicit rules for behaviour, priorities, refusals and uncertainty.
Use it whenWhen teams disagree about how the AI should act. Review it whenever model or policy changes.
# Model behaviour spec
Role in the product:
Primary objective:
Priority order when goals conflict:
Must do:
Must not do:
How to express uncertainty:
When to ask a question:
When to refuse:
When to escalate to a person:
Examples of good behaviour:
Counterexamples:
Version / owner:
03TemplateReviewed 30 Aug 2026
Template / WORKING PREVIEWGrounding + source brief
Decision this evidence supports
Allowed sources
Source of truth
Minimum freshness
Grounding + source brief
Specify which sources are allowed, how fresh they must be, and how claims stay traceable.
Use it whenBefore an answer, recommendation or action depends on external knowledge.
# Grounding + source brief
Decision this evidence supports:
Allowed sources:
Source of truth:
Minimum freshness:
Required fields / claims:
How conflicts are handled:
What counts as missing evidence:
Citation shown to the user:
Fallback when a source is unavailable:
Data owner / review date:
04TemplateReviewed 30 Aug 2026
Template / WORKING PREVIEWPrompt contract
Job to be done
Inputs available
Inputs that may be missing
Required output
Prompt contract
Define the job, inputs, output shape and non-negotiable rules before polishing prompt wording.
Use it whenWhen a prompt is becoming hidden product logic that nobody owns.
# Prompt contract
Job to be done:
Inputs available:
Inputs that may be missing:
Required output:
Output schema / length:
Rules that cannot be relaxed:
Tools the model may use:
Actions it may never take:
Questions it should ask first:
Failure response:
Test examples:
05TemplateReviewed 30 Aug 2026
Template / WORKING PREVIEWEvaluation rubric
Task / user segment
Dataset or scenarios
Criterion 1 + pass threshold
Criterion 2 + pass threshold
Evaluation rubric
Make "good" testable with criteria, examples, thresholds and a release decision.
Use it whenBefore comparing prompts or models, and before every meaningful release.
# Failure taxonomy
Failure name:
What the user sees:
Likely cause:
Frequency:
Severity / user harm:
Can the system detect it?
Recovery shown in the interface:
Data saved or rolled back:
When a person takes over:
How this becomes an eval case:
Owner / status:
07TemplateReviewed 30 Aug 2026
Template / WORKING PREVIEWHuman approval matrix
Action
User impact: low / medium / high
Reversible: yes / partly / no
Money or external representation: yes / no
Human approval matrix
Place human checkpoints according to impact, reversibility and confidence.
Use it whenBefore an agent sends, spends, deletes, publishes or changes real-world state.
# Human approval matrix
Action:
User impact: low / medium / high
Reversible: yes / partly / no
Money or external representation: yes / no
Evidence required:
Confidence threshold:
Auto-run allowed when:
Approval required when:
What the approval card must show:
Timeout / cancellation behaviour:
Audit record:
08TemplateReviewed 30 Aug 2026
Template / WORKING PREVIEWHandoff + escalation rule
Trigger condition
Why automation stops here
Person or team receiving it
Context already gathered
Handoff + escalation rule
Define when the AI stops, what context transfers, and who owns the next move.
Use it whenFor every workflow that can hit ambiguity, risk or a tool failure.
# Handoff + escalation rule
Trigger condition:
Why automation stops here:
Person or team receiving it:
Context already gathered:
Evidence attached:
Decision still needed:
Safe state while waiting:
What the user sees:
Response deadline:
Resume rule:
Audit owner:
09TemplateReviewed 30 Aug 2026
Template / WORKING PREVIEWFeedback + control plan
Decision or output users can correct
Control available before generation
Control available after generation
Undo / rollback
Feedback + control plan
Design correction, override, undo and learning as product flows rather than thumbs icons.
Use it whenWhen users need to shape, correct or recover from AI output.
# Feedback + control plan
Decision or output users can correct:
Control available before generation:
Control available after generation:
Undo / rollback:
What feedback is captured:
What feedback changes immediately:
What requires review before learning:
How the user sees the effect:
Privacy constraint:
Owner:
10ProcessReviewed 30 Aug 2026
Process / WORKING PREVIEWAgent state map
State
What the system is doing
What evidence it has
What the user sees
Agent state map
Map what the agent is doing, waiting for, blocked by and handing back to the user.
Use it whenBefore designing progress, tool-use or long-running-task interfaces.
# Agent state map
State:
What the system is doing:
What evidence it has:
What the user sees:
Can the user interrupt?
Can the user edit the plan?
Tool or dependency in use:
Timeout behaviour:
Failure state:
Recovery action:
Next state:
11ProcessReviewed 30 Aug 2026
Process / WORKING PREVIEWRelease + change record
Date / version
What changed
Model / prompt / data / tool / UI
Reason for change
Release + change record
Tie model, prompt, data and interface changes to eval evidence and observed impact.
Use it whenEvery time behaviour changes, even when the UI does not.
# AI release + change record
Date / version:
What changed:
Model / prompt / data / tool / UI:
Reason for change:
Eval set run:
Before / after result:
New failure mode introduced:
Human review completed by:
Rollback trigger:
User-facing note:
Next review date:
12PrimitiveReviewed 30 Aug 2026
Primitive / WORKING PREVIEWReasoning disclosure
Status / current step
Plan the user can inspect
Evidence used
Checks completed
Reasoning disclosure
Show a useful plan, evidence and limits without exposing or inventing private chain-of-thought.
Use it whenWhen the user needs to judge why an answer deserves trust.
# Reasoning disclosure
Status / current step:
Plan the user can inspect:
Evidence used:
Checks completed:
Assumptions:
Known limits:
What remains uncertain:
Next action:
User control: pause / edit / continue
13PrimitiveReviewed 30 Aug 2026
Primitive / WORKING PREVIEWTool call card
Tool / system
Why it is being used
Input summary
Permission level: read / write
Tool call card
Make an agent action legible before, during and after it touches another system.
Use it whenWhenever the AI searches, reads, writes or acts through a tool.
# Approval card
Proposed action:
Recipient / destination:
Exact content or change:
Evidence supporting it:
Cost / consequence:
Can it be undone?
What happens on approve:
What happens on reject:
Edit option:
Approval expires:
15PrimitiveReviewed 30 Aug 2026
Primitive / WORKING PREVIEWAgent progress row
Step name
State: queued / active / blocked / done
Started at
Evidence or output
Agent progress row
Show what finished, what is running, what is waiting and what needs the user.
Use it whenFor work that spans tools, steps or more than a few seconds.
# Uncertainty + recovery state
What is uncertain:
Why it matters:
What is known:
What is missing or conflicting:
Risk of continuing:
Best next question:
Alternative safe action:
Can the user override?
How recovery is confirmed:
CHANGELOG
Changed when the field changes. Not when a timer ticks.
30 Aug 2026 · v1.0
Published the first 17 artifacts from Google PAIR, Microsoft HAX, OpenAI, Anthropic, NIST, Apple and AI SDK guidance.
A daily source sweep is planned. Entries publish only after a relevant source change is reviewed. Every entry keeps its source and honest review date.