# Agent-managed revenue projects board

Purpose: keep Bert’s existing software projects moving with dedicated agent lanes, oversight, and revenue focus. This board is for existing projects only. Do not spawn a new project unless Bert explicitly asks.

## Operating rules

1. No new project creation by default.
2. No direct commits to `main`.
3. Every implementation task gets a scoped plan before work starts.
4. Implementation agents work in branches or isolated worktrees.
5. Reviewer agents check spec compliance first, then code quality.
6. Bert gets a checkpoint before merge, deploy, or public release.
7. Each technical task must tie back to a revenue hypothesis or project stabilization goal.
8. Protected workspace rule: do not inspect, summarize, traverse, or modify `/_clients/` without explicit override.

## Current connection status

```text
git: installed
gh CLI: not installed
local managed software repos live under /Users/bertmahoney/workspace/_projects
GitHub repos: connected via existing credentials when available
```

## Needed from Bert

Add repo URLs or local paths below.

```text
Project 1 repo/path:
Project 2 repo/path:
Project 3 repo/path:
Project 4 repo/path:
```

If private repos are involved, preferred setup:

```bash
brew install gh
gh auth login
```

Alternative: clone via HTTPS/SSH with git only.

---

# Project lanes

## Project 1 — TBD

**Repo/path:** TBD  
**Revenue hypothesis:** TBD  
**Current state:** unknown  
**Next monetizable milestone:** TBD  
**Primary agent lane:** TBD  
**Reviewer lane:** spec + quality  
**Test command:** TBD  
**Deploy command:** TBD  
**Risks/blockers:** repo not connected

### Next actions

- [ ] Connect repo
- [ ] Run repo audit
- [ ] Identify quickest revenue/stability milestone
- [ ] Write implementation plan
- [ ] Assign first agent task

## Project 2 — TBD

**Repo/path:** TBD  
**Revenue hypothesis:** TBD  
**Current state:** unknown  
**Next monetizable milestone:** TBD  
**Primary agent lane:** TBD  
**Reviewer lane:** spec + quality  
**Test command:** TBD  
**Deploy command:** TBD  
**Risks/blockers:** repo not connected

### Next actions

- [ ] Connect repo
- [ ] Run repo audit
- [ ] Identify quickest revenue/stability milestone
- [ ] Write implementation plan
- [ ] Assign first agent task

## Project 3 — TBD

**Repo/path:** TBD  
**Revenue hypothesis:** TBD  
**Current state:** unknown  
**Next monetizable milestone:** TBD  
**Primary agent lane:** TBD  
**Reviewer lane:** spec + quality  
**Test command:** TBD  
**Deploy command:** TBD  
**Risks/blockers:** repo not connected

### Next actions

- [ ] Connect repo
- [ ] Run repo audit
- [ ] Identify quickest revenue/stability milestone
- [ ] Write implementation plan
- [ ] Assign first agent task

## Project 4 — TBD

**Repo/path:** TBD  
**Revenue hypothesis:** TBD  
**Current state:** unknown  
**Next monetizable milestone:** TBD  
**Primary agent lane:** TBD  
**Reviewer lane:** spec + quality  
**Test command:** TBD  
**Deploy command:** TBD  
**Risks/blockers:** repo not connected

### Next actions

- [ ] Connect repo
- [ ] Run repo audit
- [ ] Identify quickest revenue/stability milestone
- [ ] Write implementation plan
- [ ] Assign first agent task

## Support lane — WordPress drafts for MyAudio-2-RawTxt

**Repo/path:** `_projects/audio2blog-macos-whisper-metal`  
**Revenue hypothesis:** convert transcripts and writing into bertmahoney.com drafts  
**Current state:** draft workflow defined; publish stays gated  
**Next monetizable milestone:** first approved WordPress draft from a real MyAudio transcript  
**Primary agent lane:** WordPress draft workflow + editorial review  
**Reviewer lane:** voice-matched editor + approval gatekeeper  
**Test command:** `python3 03_publish_to_wordpress.py --dry-run` or read-only REST connectivity check  
**Deploy command:** manual publish only after explicit `WP_PUBLISH_OK`  
**Risks/blockers:** WordPress creds must stay outside chat; no LinkedIn dependency

### Next actions

- [ ] Confirm the first transcript/post to turn into a draft
- [ ] Run read-only WordPress connectivity check
- [ ] Create/update the draft in WordPress
- [ ] Review and revise copy
- [ ] Hold publish until Bert says `WP_PUBLISH_OK`

---

# Standard agent workflow per project

```text
repo audit
→ revenue/stability milestone
→ implementation plan
→ implementer subagent
→ spec reviewer subagent
→ quality reviewer subagent
→ Bert checkpoint
→ branch/PR/merge/deploy
```

## Repo audit checklist

- README and stated purpose
- install/build/test commands
- deployment target
- current branch status
- open TODOs/issues
- package/dependency health
- obvious revenue path
- shortest useful demo or saleable milestone
- CI status if connected
- security or secret exposure risks

## Agent roles

### Implementer agent

Builds one scoped task at a time.

### Spec reviewer agent

Checks whether the implementation matches the task exactly.

### Quality reviewer agent

Checks maintainability, tests, edge cases, security, and repo conventions.

### Hermes/controller

Maintains context, asks Bert for decisions, protects scope, routes work, and summarizes outcomes.