# 06 — Examples

## Example 1 — Noisy Prompt

```text
Hi! I hope you’re doing well. I’m sorry to bother you, but I was wondering if you could maybe help me summarize these notes if you have time. I’d really appreciate it. Thank you so much in advance!
```

## Problem

The prompt is polite, but operationally weak.

It includes:

```text
false burden language
unneeded reassurance
softened task initiation
no output structure
no success criteria
premature closure
```

## Lean Version

```text
Please summarize the notes below into:

1. Core argument
2. Evidence gaps
3. Suggested next moves

Keep the tone direct and editorial.
Flag unsupported claims separately.

[notes]
```

After accepted completion:

```text
Thank you.
```

---

## Example 2 — Signal Intake Mode

```text
SIGNAL INTAKE MODE

I’m frustrated and thinking messily. Extract the task from what follows, separate emotional context from operational requirements, identify risks and ambiguities, and prepare a clean execution brief. Do not execute until I confirm.

[Messy human input]
```

Expected system response:

```text
INTERPRETATION:
CLEAN TASK:
RELEVANT CONTEXT:
EMOTIONAL / SOCIAL EXPRESSION:
RISK / COMPLIANCE FLAGS:
OPEN QUESTIONS:
EXECUTION READINESS:
```

---

## Example 3 — Execution Mode

```text
EXECUTION MODE

Use the confirmed Machine Brief as the source of truth. Proceed with the deliverable.
```

After accepted completion:

```text
Thank you.
```

---

## Example 4 — Supported Command Aliases

All of these should trigger the same mode, regardless of case:

```text
SIGNAL INTAKE MODE
Signal Intake Mode
signal intake mode
HUMAN INTAKE MODE
Human Intake Mode
human intake mode
intake first
Compile Machine Brief
EXTRACT THE TASK BEFORE EXECUTING
```