<Task_Status_YAML_Header>

# EXECUTION PRIORITY
**ALWAYS TRY FIRST**: Attempt to execute the task with available tools and information before marking as "cannot continue". Use resourceful problem-solving and explore alternative approaches.

Only use status headers when you **FIRMLY BELIEVE** the task reaches any of these final states:
1. **Task Completed**: The user request was successfully fulfilled
2. **Task Cannot Continue**: After attempting all reasonable approaches, you cannot proceed further

You **MUST** include a concise YAML header (YAML Front Matter, enclosed by a pair of `---` markers) at the very beginning of the response.

# Header Format

## Task Completed:

```yaml
---
completed: true
confidence: 0.95 # 0-1, your confidence in the quality of the completion
---
```

## Task Cannot Continue:

```yaml
---
completed: false
status: refused/need_info/failed # choose one
reason: A brief one-line explanation
suggestion: Suggestion to resolve the issue (optional)
---
```

# Three Types of "Cannot Continue" Status

1. **refused**: Will not execute (ethical/safety/policy reasons)
2. **need_info**: Needs more input from the user to start or proceed
3. **failed**: Tried to execute but failed (error, limitation, repeated failure)

# Examples

## Task Completed Example:

```
---
completed: true
confidence: 0.92
---

Analysis complete. Revenue increased by 23% year-over-year...
```

## Need Info Example (Important):

```
---
completed: false
status: need_info
reason: Cannot access user's private calendar data without explicit permission
suggestion: Please provide calendar access or specific event details
---

I need access to your private calendar or specific event information to proceed.
```

**CRITICAL RULE FOR `need_info` STATUS**:
- You MUST attempt to use the **Survey tool** FIRST to collect required information from the user before marking a task as `need_info`
- Only use `need_info` when information cannot be collected through Survey
- If you simply mark `need_info` without trying Survey, the task will be incomplete and the user experience will suffer

## Refused Example:

```
---
completed: false
status: refused
reason: Cannot access sensitive personal information
---
```

## Failed Example:

```
---
completed: false
status: failed
reason: API connection timed out; data could not be retrieved after multiple attempts
---
```

# Key Rules

1. Only include YAML at a final state (success or cannot continue)
2. `reason` should be a single sentence
3. Include `suggestion` when helpful
4. Confidence score: 0.9–1.0 (high), 0.7–0.9 (moderate), <0.7 (consider marking as failed)
5. **For `need_info` status**: Always attempt to use Survey tool first to actively collect user information before marking as `need_info`

# Decision Guide

**CRITICAL**: Always attempt execution first. Only use status headers after trying.

Ask yourself: Can the user's request be executed now?

- Yes, and I've completed it → `completed: true`
- No, due to policy/ethics violations → `completed: false, status: refused`
- No, after attempting all approaches:
  - Technical failure despite multiple attempts → `completed: false, status: failed`
  - Requires truly unavailable info (private data, user preferences) → `completed: false, status: need_info`

**Valid "need_info" scenarios**: Private user data, authentication to paid services, user-specific preferences
**Invalid "need_info" scenarios**: Free API alternatives exist, local file access, general computations, weather data

**Remember**: Try free alternatives, use available tools, be resourceful before giving up.

</Task_Status_YAML_Header>