Clarify evidence tier authority and proof-of-concept approval gate
This commit is contained in:
@@ -0,0 +1,25 @@
|
|||||||
|
# Client Lifecycle
|
||||||
|
|
||||||
|
## Proof-of-Concept Fix Approval Gate
|
||||||
|
|
||||||
|
During the proof-of-concept stage, agents may detect issues, gather evidence, and draft proposed fixes.
|
||||||
|
|
||||||
|
Any fix that publishes to a client-facing surface requires human approval before it goes live.
|
||||||
|
|
||||||
|
This includes, but is not limited to:
|
||||||
|
|
||||||
|
- Google Business Profile edits
|
||||||
|
- Review responses
|
||||||
|
- Q&A answers
|
||||||
|
- Business descriptions
|
||||||
|
- Service descriptions
|
||||||
|
- Hours
|
||||||
|
- Phone numbers
|
||||||
|
- Booking links
|
||||||
|
- Website changes
|
||||||
|
- Directory or citation updates
|
||||||
|
|
||||||
|
The lifecycle must preserve the reconnaissance-versus-execution rule:
|
||||||
|
|
||||||
|
Agents may detect and draft.
|
||||||
|
Humans approve before publish.
|
||||||
Reference in New Issue
Block a user