How a job works.

The canonical flow from "I've got a job for you" to finished output. Drop files in the inbox, email HiveAccess, and the system takes it from there.

Team member Ed, Sam, anyone with HiveAccess drops files in inbox 01 Inbox folder Brief, assets, reference files plus email: "Hey, I've added a job" new email watcher, 2 min Main agent reads inbox files + inbound email checks knowledge base for context reading Main responds questions, proposed plan, or request for clarification drafting Person clarifies or says go back and forth via email Wayne review needed? No Yes Wayne reviews approves or redirects awaiting Route by job type main decides which agent fits running Strategist thinking, planning Content engine SHWR publishing Main inline simple operations Future writer, researcher Output delivered email reply + 03 Output folder LOG event written to task folder done Done

The email that starts it

Anything like: "Hey, it's Ed. I've added a job in the inbox. Come back with questions or your plan." That's the trigger. Keep it brief, the files do the talking.

The 2-minute loop

The email watcher checks every 2 minutes. On the next heartbeat, the main agent reads what's in the inbox and picks up the email. No need to chase it.

Wayne review

Not needed for every job. For anything strategic, client-facing, or sensitive, the main agent flags it before running. Wayne approves or redirects, then it proceeds.

Status states

Each task folder gets a LOG file updated at every step. You can always see where a job is by looking at its folder. Nothing runs silently.

Giving someone access

Wayne controls who can email HiveAccess. Share the inbox Drive folder and add their email. They follow the same flow everyone else does.

Job classes the team uses

Strategy

Thinking and planning

Briefs, frameworks, positioning, research. Goes to the Strategist agent. Output is a structured document in 03 Output.

Content

Content publishing

SHWR-style content work. Content engine handles scheduling, formatting, and distribution logic.

EDM

Email comms

Email copy, subject lines, campaign structure. Main agent handles this inline or routes to a writer when one exists.

New biz

New business support

Creds research, competitive context, pitch prep. Handled by the main agent or Strategist depending on depth needed.

Archive

Archive lookups

Finding past work, client history, reference material. Searches the knowledge base. Phase D will get a dedicated researcher agent.

Ad hoc

Simple requests

Short tasks, quick edits, questions. Main agent handles these directly without dispatching. Fast turnaround.

Every job leaves a record.

Each task folder gets a LOG file. Every step writes to it: when it was read, what the main agent decided, which agent ran it, what was produced. If something goes wrong or needs reviewing, the log shows exactly what happened and when.