How CosX Nerves works
Everything is scoped to a project, and projects live inside a workspace. A personal workspace (private to you) is your draft space; the org workspace is the shared, reviewed knowledge base. Documents, pages, questions, and promotions all belong to one project.
The source material you feed in — meeting notes, specs, PDFs, markdown, code, even Claude Code session transcripts. Raw docs are stored as-is (de-duplicated by content hash) and are the input to ingestion. They are not the knowledge base themselves; they're the ore the wiki is refined from.
The compiled, structured knowledge base. Ingestion turns raw docs into clean, typed pages — patterns, architecture templates, gotchas, lessons learned, and more. Pages carry YAML frontmatter (type, labels, links) and are what the Ask feature reads when answering.
Things the system produces for you — saved Q&A answers, briefings, and reports. Outputs are generated from the wiki rather than uploaded. A good output can be promoted back into the wiki so the insight becomes reusable knowledge.
Private to you. Upload raw docs, ingest them into draft wiki pages, and ask questions freely. Nothing here is visible to the rest of the org until you promote it.
The shared, reviewed knowledge base. Pages arrive here through promotion, not direct upload, and writes are role-gated. This is the source of truth the whole firm queries.
Upload raw docs (one file, many files, or a whole folder). Gemini reads them and proposes wiki pages, classifying each as a new page or an update to an existing one. You review word-level diffs and accept or reject per page before anything lands in the wiki.
Ask a question and get an answer grounded in your project's wiki pages, with cited sources. Citations are scored for groundedness, and answer text is checked against the cited pages to guard against hallucination. Save a useful answer as an Output.
Move a polished draft from your personal workspace into the shared org wiki. Promotion is reviewed: path collisions, similar existing pages, and merge conflicts are surfaced for resolution, and cross-project promotions are scrubbed for client names, credentials, and pricing.
Upload a Claude Code session transcript (.jsonl) to get mechanical metrics (tokens, tools, cost), a private critique, and an extracted digest. The digest flows through the normal ingestion pipeline into your personal playbook, ready to promote.
Every new engagement should begin by asking the wiki what the firm already knows.