Company Brain

Start

How it works: source files to reviewed pack

The product workflow is a narrow loop. It starts with real source material from one bounded team corpus and ends with reviewed, exportable operational knowledge.

You should be able to explain the full path from upload to export without treating the draft as automatically correct.

1. Set up the knowledge pack

A trial run begins by naming the team or function, corpus boundary, reviewer, expected use this week, and current mishandling impact.

  • Good corpus: support refund and replacement escalation artifacts.
  • Weak corpus: clean up all support docs.
  • Required before extraction: a bounded corpus and readable source material.

2. Add source files

Company Brain accepts pasted text and local file uploads. Browser-readable extraction currently covers text-like files such as TXT, Markdown, CSV, JSON, HTML, VTT, SRT, text-layer PDFs, readable DOCX files, and supported text-like entries inside ZIP uploads.

  • Scanned or image-only PDFs are not OCRed; empty, protected, or image-only DOCX files cannot produce extracted text.
  • ZIP entries preserve archive paths when parsed; unsupported, nested, unsafe, too-large, corrupt, encrypted, or password-protected archive content is skipped or failed clearly.
  • Current public trial upload limits are 50 MB per file, 250 MB total staged upload, 20 staged files, and 500,000 readable characters. Authenticated new runs allow 500 MB total staged upload and 50 staged files before the same extraction preflight.
  • Folder upload works in browsers that expose directory entries.

3. Extract draft operational knowledge

The extraction creates draft items with source context where available. It may produce SOP drafts, decision rules, workflow steps, internal FAQ entries, gaps, conflicts, outdated-content notes, support macro drafts, and agent-ready skill-file drafts.

4. Human review decides what is usable

Each item starts as draft. The reviewer can approve, reject, edit, or mark needs edit. Needs-edit items block finalization until they are edited and then approved or rejected.

5. Finalize and export

Finalization creates a clean deliverable from the current review statuses. Approved items become usable output. Rejected items are excluded from SOPs, workflows, decision rules, and skill files, but listed in an excluded summary.

Read next

Source materialSource material means the existing team artifacts and pasted excerpts Company Brain uses to extract one reviewed operational knowledge pack.Knowledge packsAn operational knowledge pack is the reviewed output from one bounded team artifact corpus.Human reviewCompany Brain outputs are drafts until a human reviewer approves, edits, rejects, or marks them needs edit.