# MyAudio-2-RawTxt WordPress Draft Workflow

> Purpose: turn MyAudio-2-RawTxt audio/transcript outputs into **WordPress drafts** for bertmahoney.com, with a hard human approval gate before any publish action.

---

## Scope

This workflow covers:
- transcript-to-post drafting
- WordPress draft creation
- draft review and revision
- publish approval handling
- safe credential use

This workflow does **not** cover:
- LinkedIn posting
- automatic publication
- comments moderation
- theme/plugin/site settings
- WooCommerce / Stripe changes
- any work inside `/Users/bertmahoney/workspace/_clients/`

---

## Credential source

Use the active Hermes profile env file:

```text
/Users/bertmahoney/.hermes/.env
```

### Site mapping

- `BERTMAHONEY_WP_*` → `https://bertmahoney.com`
- `BERCHMAN_WP_*` → `https://berchman.com`
- `BERT_FORSALE_WP_*` → `https://bert.forsale`

For MyAudio-2-RawTxt, use **`BERTMAHONEY_WP_*`**.

---

## Trigger phrases

These phrases are exact and should not be inferred from similar wording:

- `WP_KEYS_READY` — verify read-only connectivity only
- `WP_DRAFT_OK` — create or update **drafts only**, never publish
- `WP_MAINTENANCE_REPORT` — report-only scan, no writes
- `WP_PUBLISH_OK` — publish only the specific approved post named in the current chat

---

## Roles

### 1. Transcript assembler
**Job:** turn the raw transcript into a post-shaped draft.

**Input:**
- transcript text
- title idea
- intended angle / thesis

**Output:**
- local Markdown draft
- suggested title options
- excerpt / summary
- tags / categories suggestion

**Rules:**
- preserve the human voice
- cut filler and over-technical detail
- keep the post at a public-friendly altitude
- if the draft exposes unreleased software details, redact or generalize them

---

### 2. WordPress draft writer
**Job:** create or update a draft in WordPress.

**Allowed actions:**
- create draft posts
- update existing drafts
- set excerpt, categories, tags
- attach featured image only if already approved and local asset is safe

**Forbidden actions:**
- publish without explicit approval
- change settings, themes, plugins, or menus
- modify pages or products outside the approved post scope
- use account credentials for unrelated tasks

**Approval gate:**
- must receive `WP_DRAFT_OK` before any draft write

---

### 3. Editorial reviewer
**Job:** check voice, clarity, structure, and claim safety.

**Checks:**
- does it sound like Bert?
- is it readable and not too dry?
- does it avoid unshipped product claims?
- does it fit bertmahoney.com?

**Output:**
- keep / revise / reject
- specific revision notes

---

### 4. Publish gatekeeper
**Job:** handle the final publish step if and only if Bert explicitly approves.

**Allowed actions:**
- publish the named approved post
- no other edits

**Forbidden actions:**
- selecting a different post
- auto-scheduling without approval
- editing the content while publishing

**Approval gate:**
- requires `WP_PUBLISH_OK` plus the exact approved post name in the chat

---

## Recommended workflow

### Phase 1: Draft locally
1. Extract transcript from MyAudio-2-RawTxt.
2. Create a local Markdown draft.
3. Run voice-matched editorial pass.
4. Produce a draft summary and post metadata.

### Phase 2: Prepare the WordPress draft
1. Confirm `WP_DRAFT_OK`.
2. Verify read-only access if needed with `WP_KEYS_READY` first.
3. Create the WordPress draft on `bertmahoney.com`.
4. Return the draft URL for review.

### Phase 3: Human review
1. Bert reviews the draft.
2. Agent applies requested edits.
3. Repeat until approved.

### Phase 4: Publish only if requested
1. If Bert explicitly says to publish, require `WP_PUBLISH_OK`.
2. Publish only the named post.
3. Return the live URL and a short publish summary.

---

## Content rules for bertmahoney.com

- Keep the tone smart, grounded, and human.
- Prefer practical insight over implementation minutiae.
- Avoid exposing unreleased product details.
- If the post mentions tools, keep them at a high level unless the product is already public.
- Favor clear titles and short sections.
- End with a useful takeaway or next-step thought.

---

## Suggested post metadata

Use these as starting points:

- **Category:** Writing / Tools / Workflow / AI (choose one)
- **Tags:** `local-ai`, `transcription`, `workflow`, `macos`, `writing`
- **Excerpt:** 1–2 sentence summary of the post’s value

---

## Safety checklist

Before any WordPress action:
- [ ] Correct site selected: `bertmahoney.com`
- [ ] Correct env vars selected: `BERTMAHONEY_WP_*`
- [ ] Draft-only unless explicitly told otherwise
- [ ] No sensitive secrets in the draft
- [ ] No client-work paths touched
- [ ] No LinkedIn steps involved
- [ ] Exact approval phrase received if writing or publishing

---

## Integration with the agent roster

Recommended roles:
- **Transcript assembler** → Implementer/draft agent
- **Editorial reviewer** → Voice-matched editor
- **WordPress draft writer** → WordPress content agent with draft-only authority
- **Publish gatekeeper** → Hermes/controller with a strict approval gate

---

## Next step

Once Bert says **`WP_DRAFT_OK`**, the agent can create the first bertmahoney.com draft from a MyAudio-2-RawTxt transcript.