Guided implementation
From the boundary to a verifiable result.
- 01
Constrain the source
Define which approved source this exact step needs. Project and sandbox data must not be confused with private Clarity content.
- 02
Separate proposal from execution
Generated text is not yet an action. Show the draft, affected data and expected consequence before any C2 effect.
- 03
Design the receipt and way back
Success and failure need a server-confirmed receipt. Reversible changes need a visible undo path.
- 04
Treat uncertainty as a state
If permission, source or target cannot be confirmed safely, keep the flow closed and explain the next safe step.
Complete when …
- Source and purpose appear with the action
- C2 waits for an explicit yes
- C4 is never executed autonomously
- Failures do not claim success