Guides
General tasks
Operational and cross-functional work grounded in full company context — research, drafts, follow-ups, and coordination with approval gates.
General tasks are the everyday operational work HiveBase runs with full company context: follow-ups, research, drafts, coordination, and cross-tool prep. Product surface: /tasks/general.
Overview of the whole system: Tasks.
What makes them “general”
| General | Coding | Content | |
|---|---|---|---|
| Primary ground | Full Brain + tools | Repo + Brain | Brand voice + Brain |
| Typical output | Brief, email draft, research pack, checklist | Diff / PR | Draft post or asset |
| Gate emphasis | Outbound messages and external writes | Merge / review | Publish + unsourced claims |
How a general task runs
Intent
You create a task, or a squad / signal detection opens one with sources attached.
Ground
The agent reads the Brain — accounts, decisions, prior threads — so the output is not a blank-prompt guess.
Work
Research, draft, or coordinate steps run inside HiveBase with tool access you have connected.
Hold outbound
Anything that leaves HiveBase (email, Slack post, CRM update, etc.) holds for approval unless that category has earned autonomy.
Receipt
Applied actions leave an action receipt.
Good fits
- Prep an account brief before a renewal call
- Draft a follow-up from a meeting + CRM context
- Research a competitor move and propose next steps
- Turn a scattered Slack thread into a clear decision + tasks
Not the right type
- Large code changes → Coding tasks
- On-brand publishable content with claim holds → Content tasks
- Board-wide dedupe / prioritization → Autonomous PM