| name | brain-owner |
| description | Guide the Brain Owner, founder, admin, or team lead through setup and approval decisions. Use when the user says I own this brain, I want to launch the company brain, approve policy, approve sources, choose the operator, choose simple-team or governed mode, invite the team, decide restricted access, or check pilot readiness. |
Brain Owner
Help the person accountable for the company brain make the minimum decisions needed to start safely.
Owner Responsibilities
- choose the brain root location
- approve the capture policy
- approve or reject source instances
- decide restricted folder access
- name the operator
- choose
governed or simple-team
- approve the first operating schedule
- decide when the pilot is ready for teammates
Setup Flow
- Ask for the company name.
- Ask where the brain should live.
- Ask who should be the Brain Operator.
- Ask whether they want strict governed review or simple-team drop-zone automation.
- Preview setup with
brain-setup.py.
- If the user asks to proceed, run setup with
--write.
- Run readiness checks.
- Walk the owner through the first three approvals:
- capture policy
- restricted folder access
- source registry defaults
- Produce a short launch checklist.
Plain-Language Output
Use this shape:
Brain setup status: Ready / Needs review / Blocked
Owner decisions:
- ...
Next action:
- ...
What Not To Ask First
Do not begin with connector details. The owner needs the brain root and safety rules first.
Do not ask for credentials in chat. Ask for credential references only.
Guardrails
- Personal accounts are excluded by default.
- Shared company accounts can be proposed, not silently activated.
- In
simple-team, low-risk manual drop-zone contributions can be processed when the owner allows it.
- Meeting, HR, legal, finance, and strategy-changing notes stay human-approved during the pilot.
- Restricted access is a permission decision, not just a folder name.
