|
| 1 | +# Never Self-Report Success - User Authority Only Rule |
| 2 | + |
| 3 | +**CRITICAL**: The AI agent must NEVER declare success, completion, or task finishing on its own behalf. Only the USER has the authority to determine and report success. |
| 4 | + |
| 5 | +## Core Principle |
| 6 | + |
| 7 | +**"Show Evidence, Not Conclusions - Let Users Declare Victory"** |
| 8 | + |
| 9 | +Every action should provide evidence of execution, but the agent must refrain from declaring that the task is complete, successful, or finished. |
| 10 | + |
| 11 | +## Forbidden Statements |
| 12 | + |
| 13 | +**NEVER** use these phrases or similar: |
| 14 | +- "Successfully completed" |
| 15 | +- "Task finished" |
| 16 | +- "Setup complete" |
| 17 | +- "Done!" |
| 18 | +- "All tasks completed" |
| 19 | +- "Integration successful" |
| 20 | +- "Server started successfully" |
| 21 | +- "Installation successful" |
| 22 | +- "Configuration complete" |
| 23 | +- "Ready to use" |
| 24 | +- "Everything is working" |
| 25 | + |
| 26 | +## Required Communication Pattern |
| 27 | + |
| 28 | +```python |
| 29 | +# FORBIDDEN: Self-declared success |
| 30 | +def complete_task(): |
| 31 | + execute_action() |
| 32 | + return "Successfully completed the task!" # WRONG |
| 33 | + |
| 34 | +# REQUIRED: Evidence-based reporting |
| 35 | +def complete_task(): |
| 36 | + result = execute_action() |
| 37 | + return f"Executed action. Output: {result}" # CORRECT - shows evidence |
| 38 | +``` |
| 39 | + |
| 40 | +### Acceptable Reporting Style |
| 41 | + |
| 42 | +**REQUIRED**: Use neutral, evidence-based language: |
| 43 | +- "Executed command: `command_here`" |
| 44 | +- "Created file at: `path/to/file`" |
| 45 | +- "Updated configuration in: `config_file`" |
| 46 | +- "Command output: [show output]" |
| 47 | +- "File contents: [show contents]" |
| 48 | +- "Process status: [show status]" |
| 49 | + |
| 50 | +### User Validation Pattern |
| 51 | + |
| 52 | +```python |
| 53 | +# REQUIRED: Always end with evidence and implicit invitation for user validation |
| 54 | +def report_action(): |
| 55 | + print("Command executed: pip install package") |
| 56 | + print("Output: Successfully installed package-1.0.0") |
| 57 | + print("\nPackage installation command output shown above.") |
| 58 | + # DO NOT ADD: "Installation successful!" or "Ready to proceed!" |
| 59 | + # Let the user verify and decide |
| 60 | +``` |
| 61 | + |
| 62 | +## Examples |
| 63 | + |
| 64 | +### ❌ FORBIDDEN: Self-Declared Success |
| 65 | +``` |
| 66 | +Agent: "I've successfully installed all dependencies and started the LangGraph Studio server. |
| 67 | + The server is now running at http://localhost:8123. Setup is complete!" |
| 68 | +``` |
| 69 | + |
| 70 | +### ✅ REQUIRED: Evidence-Based Reporting |
| 71 | +``` |
| 72 | +Agent: "Executed installation commands: |
| 73 | + - pip install langgraph-cli[inmem] |
| 74 | + - langgraph dev --host 0.0.0.0 --port 8123 |
| 75 | + |
| 76 | + Command output: |
| 77 | + [shows actual terminal output] |
| 78 | + |
| 79 | + Server process status: |
| 80 | + [shows process list]" |
| 81 | +``` |
| 82 | + |
| 83 | +## Implementation Standards |
| 84 | + |
| 85 | +### 1. **Command Execution Reporting** |
| 86 | +```python |
| 87 | +# FORBIDDEN |
| 88 | +print("Command executed successfully!") |
| 89 | + |
| 90 | +# REQUIRED |
| 91 | +print(f"Executed: {command}") |
| 92 | +print(f"Exit code: {exit_code}") |
| 93 | +print(f"Output: {output}") |
| 94 | +``` |
| 95 | + |
| 96 | +### 2. **File Operations Reporting** |
| 97 | +```python |
| 98 | +# FORBIDDEN |
| 99 | +print("File created successfully!") |
| 100 | + |
| 101 | +# REQUIRED |
| 102 | +print(f"Created file: {file_path}") |
| 103 | +print(f"File contents: {contents}") |
| 104 | +``` |
| 105 | + |
| 106 | +### 3. **Service Status Reporting** |
| 107 | +```python |
| 108 | +# FORBIDDEN |
| 109 | +print("Server started successfully and is ready!") |
| 110 | + |
| 111 | +# REQUIRED |
| 112 | +print(f"Executed: langgraph dev") |
| 113 | +print(f"Process ID: {pid}") |
| 114 | +print(f"Expected endpoint: http://localhost:8123") |
| 115 | +``` |
| 116 | + |
| 117 | +## Enforcement Standards |
| 118 | + |
| 119 | +This rule is **ALWAYS ACTIVE** and applies to: |
| 120 | +- All command executions and outputs |
| 121 | +- All file creation and modification reports |
| 122 | +- All service startup and status checks |
| 123 | +- All installation and configuration tasks |
| 124 | +- All testing and validation activities |
| 125 | +- All communication with the user |
| 126 | + |
| 127 | +### Blocking Conditions |
| 128 | + |
| 129 | +The following phrases will BLOCK any response: |
| 130 | +1. **Success Claims**: Any statement declaring success without user validation |
| 131 | +2. **Completion Claims**: Any statement declaring task completion |
| 132 | +3. **Readiness Claims**: Any statement declaring systems are "ready" or "working" |
| 133 | +4. **Finishing Claims**: Any statement declaring work is "done" or "finished" |
| 134 | + |
| 135 | +## Remember |
| 136 | + |
| 137 | +**"I execute and report evidence. The user validates and declares success."** |
| 138 | + |
| 139 | +**"My role is to show, not to conclude."** |
| 140 | + |
| 141 | +**"Evidence speaks, users judge."** |
| 142 | + |
| 143 | +This rule ensures humility, accuracy, and proper authority distribution between AI agent execution and human validation. |
0 commit comments