company-brain-harness

Help a Team Member contribute knowledge safely through a short guided interview or simple drop-zone flow. Use when the user says I want to add what I know, document my role, share my process, add an SOP, update stale facts, suggest team sources, I added a file, or tell the brain about my work.

Stage or process one document, link, pasted text, transcript, note, or raw artifact into the company brain flow. Use when the user says add this to the brain, ingest this doc, file this note, where should this go, turn this into a brain note, add this document from ADD_TO_BRAIN, or stage this for review.

Run the daily operator loop for a Company Brain. Use when the user says run today's brain check, do the morning review, check the queue, what needs review, show blockers, check sources, run maintenance, process the ADD_TO_BRAIN folder, I added something to the company brain folder, or give me the next actions.

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.

Create or update the Company Brain operating schedule for human-gated or autonomous runs. Use when the user says schedule the brain check, set the morning review, automate daily checks, run without a human, keep human in the loop, set cron, or define auto-capture guardrails.

Scaffold a new team-first Company Brain root without populating company data. Use when the user asks to create the brain files, generate the scaffold, initialize a brain root, create routing, create config, create policy, create source registry, choose the simple automated team model, or run the setup step after owner guidance.

Front door for plain-English Company Brain requests when the user's role or next step is unclear. Use when the user says I want to set up my company brain, help me start, I want to use the brain, what should I do next, create a company brain, operate the brain, or add knowledge but the right role is not clear.

Review the company brain staging queue and approve, reject, revise, or promote proposed notes. Use when the user says review pending notes, approve these notes, clear the queue, publish approved knowledge, inspect proposals, or promote staged brain updates.

Check whether a company brain is connected, policy-safe, healthy, and ready for team use. Use when the user says is the brain ready, check health, check setup, verify connections, are integrations working, can the team use this, or show readiness status.

Run a structured onboarding interview to collect company, role, strategy, customer, brand, SOP, or source context into staged notes. Use when the user says interview me, onboard me, ask me questions, help populate the brain, collect company context, or turn my answers into notes.

Convert company-approved meeting material into staged brain notes with decisions, action items, and reusable knowledge. Use when the user says process this meeting, add meeting notes, summarize a transcript, import a Fireflies recap, extract action items, or turn a Zoom, Meet, Teams, or call recording export into brain updates.

Keep prototypes and proof-of-concepts aligned with the company's repo map, GitHub org, stack conventions, and build patterns. Use when the user says build a POC, prototype this, where should this code live, check existing repos, use our stack, make the agent repo-aware, or plan an MVP.

Guide Brain Owners and Operators through safe setup of email, Slack, Confluence, Google Workspace, Fireflies, CRM, GitHub, Notion, or other source instances. Use when the user says connect a source, connect Gmail, connect email, connect Slack, connect Confluence, connect CRM, approve a workspace, scope a personal source, or decide what a tool may feed into the brain.

Run source-governed capture from approved source instances into private evidence and staged brain proposals. Use when the user says sync sources, pull new emails, pull Slack updates, pull Confluence pages, sync CRM changes, process approved sources, update from source data, run source capture, or stage new source updates.

Run read-only maintenance lint for stale knowledge, missing provenance, duplicate notes, dead links, and possible contradictions. Use when the user says what is outdated, find stale notes, check broken links, find contradictions, cleanup the brain, or can we rely on this.

Validate source registry entries and decide whether a specific account, workspace, channel, folder, inbox, calendar, repo org, or API key may feed staged capture. Use when the user says connect a source, can Slack or Gmail or Calendar or Fireflies or Apollo feed the brain, is this personal account allowed, check source ownership, or validate capture eligibility.