Start
How it works: artifacts to reviewed pack
The product workflow is a narrow loop. It starts with real source material for one issue 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 issue pack
A trial run begins by naming the recurring problem and capturing the workflow area, reviewer, expected use this week, and current mishandling impact.
- Good issue: refund exception handling for SMB customers.
- Weak issue: clean up all support docs.
- Required before extraction: an issue name and readable source material.
2. Add source artifacts
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, and text-layer PDFs.
- Scanned or image-only PDFs are not OCRed; DOCX and ZIP can be accepted as controlled trial uploads, but they are metadata-only unless readable text is also provided.
- Prototype limits are 20 MB per file and 100 MB total upload size.
- 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.