28 lines
1.0 KiB
Markdown
28 lines
1.0 KiB
Markdown
# Email Prefix Communication System
|
|
|
|
Updated: 2026-07-12
|
|
|
|
The Master emails `shonuff@germainebrown.com` with prefixes in the subject or first line:
|
|
|
|
| Prefix | Meaning | Behavior |
|
|
|--------|---------|----------|
|
|
| *(none)* | Direct command | Execute now, report back |
|
|
| `[bg]` or `[delegate]` | Background task | Subagent handles, async result |
|
|
| `[queue]` | Queued for later | Shelved until next check-in |
|
|
| `[lookup]` | Quick research | One-and-done, no follow-up |
|
|
| `[note]` | Just FYI | Acknowledge, save, no action |
|
|
|
|
## Parsing Logic
|
|
|
|
Check the first 20 characters of the subject line first. If no prefix match, check the first line of the email body. Default to "direct command" if no prefix matches.
|
|
|
|
## Examples
|
|
|
|
```
|
|
Subject: Re: your analysis of Exa → immediate response
|
|
Subject: [bg] Check why app2 disk is high → background, async
|
|
Subject: [queue] Set up VoIPSimplicity → queued for later
|
|
Body starts with: [lookup] What's PACER pricing? → quick search
|
|
Body starts with: [note] Hotel is nice → acknowledged, no action
|
|
```
|