This page shows how Brown Biotech turns a request into a brief, a route, a local action, and a reusable proof asset — with Notion as the source of truth, Telegram as the approval rail, and the harness improving from every review.
flowchart LR
A[Inbound request] --> B[Intake]
B --> C[Triage]
C --> D{Approve?}
D -->|Yes| E[Route]
D -->|No| F[Nurture]
E --> G[Execute]
G --> H[Proof]
H --> I[Weekly review]
I --> J[HQ update]
J --> K[Visual HQ]
K --> AThe graph is intentionally narrow: intake, route, execute, proof, review, then update the HQ.
Request state
Intake → triage → route
One request ID, one owner, one next action.
Approval rail
Human gate
Money, contracts, deployment, public claims, medical claims.
Delivery proof
Receipt + update
Every output leaves a reusable record in Notion.
Harness loop
Improve the workflow
Weekly review feeds routing, wording, and templates back into the system.
Notion = source of truth
Brown Biotech site = intake + proof
Open Design = local operator console
Claude Code = deep repo work
Codex = scoped fast work
Telegram = human approval
1. Intake
Request enters from site or Telegram and gets a request ID.
2. Triage
Fit, urgency, and approval risk decide the route.
3. Execute
Open Design launches the right local agent for the task.
4. Publish
Receipt, proof, and HQ updates are written back.
Evidence stack
Briefs
Decision-ready summaries and scoped requests.
Visual evidence
Screenshots, figures, slides, and chart captures.
Audio notes
Meeting clips and spoken context tied back to the brief.
Approved snippets
Reusable language only after human review.
Human approval stays on money, contracts, deployment, public claims, and medical claims.
Brown Biotech's intake flow becomes legible when every request produces route, owner, approval gate, and next action in one place.
Intake
Capture the request, source, and outcome in one record.
Keep the initial brief small but specific enough to score fit, urgency, and risk.
Triage
Score fit, urgency, and approval risk with shared rules.
Use the same logic across the website, browser demo, Telegram, and Notion.
Route
Assign one owner, one route, and one next action.
Every request ends with a short receipt that can be reused in Notion or chat.
Human gate
Hold money, legal, contract, deployment, public-claim, and medical-claim items.
High-stakes requests do not move without Dr.OCM review.
Roche × PathAI (2026-05-07)
Diagnostics value now sits in the workflow, not only the model.
Brown Biotech should sell decision-ready routing and review loops, not generic AI.
Nemotron persona team
Small, specialized roles can improve throughput when the handoff is crisp.
The router should output route, owner, approval gate, and next action every time.