Legal (internal)

Purpose: Canonical internal legal planning for Brainforge: Q2–Q3 backlog, operating signals, diligence questions, and links to systems of record (Notion, Drive, Linear).

Not client-specific matter work — that stays in client vault folders or #legal Slack.

Folder layout

knowledge/legal/
  README.md                 ← you are here
  *.docx                    ← legacy Word templates (see `#legal` for current pack)
  roadmaps/                 ← time-horizon roadmaps (priorities, Q2/Q3 split)
  plans/                    ← execution plan logs + phased quarterly checklists
    phased/                 ← week-by-phase Q2 legal plan (metrics, sign-offs)
  playbooks/                ← future: flowcharts, SOPs, routing (“which paper when”)

Operating model

LayerWho / what
Roll-upLegal rolls up into Operations. Ops owns routing, templates execution, Documenso, and day-to-day contract throughput.
Ops leadRico Rejoso — primary DRI for legal operations (signing links, Monday-style batched updates, coordinating with Finance as needed).
Part-time internal counselHolly Condos — redlines, template strategy, deal-structure judgment, escalations.
External counselBend Law — matters that need outside firm capacity or specialty (e.g. immigration has been discussed alongside Bend in #legal; route other specialist work the same way).
ExecutiveUttam Kumaran — signatory and policy direction on material terms.

Communications

  • Primary channel: Slack #legal — default place for requests, document links, and status (Linear notifications also land here when configured).
  • Email: Use the legal@ Google group (see #legal for who is on it) when you need a durable thread or formal CC.

Where materials and flowcharts live

There is no single canonical path yet for “all legal materials” or decision flowcharts (new client vs contractor vs partner — discussed with Holly as a 2026 goal). Use this as the working map; update this section when flowcharts are filed.

ArtifactLikely home todayStatus
Contract templates (2026 pack)Google Drive — BrainForge Contract Templates 2026 (Holly shared Loom + folder link in #legal)Source of truth for paper
Directory + changelogNotion — Master Contract Directory and ChangelogOps + Holly to keep current
Executed agreements archiveDrive — e.g. “executed agreements” / partnership drives (see #legal references)Filing discipline is an active theme
Decision flowcharts (routing: which template, which counsel path)TBD — target home: playbooks/ or Notion under the Contract DirectoryNot yet centralized
This vaultknowledge/legal/Strategy, backlog, peer questions — not a substitute for signed PDFs or Notion ops DB

Action: When flowcharts ship, add a row above and link from here + Notion changelog.

Documents

DocUse
roadmaps/roadmap-q2-q3-2026.mdStrategic backlog (15 themes + Q2/Q3 split + appendices + Slack-informed signals)
plans/q2-2026-roadmap.mdLegal Q2 outcomes + initiatives (canonical quarter narrative)
plans/plan-legal-q2-q3-pr585.mdPlan log for vault + PR #585
plans/phased/q2-2026.mdPhased Q2 legal plan (checklists, metrics, sign-offs)
../plans/legal/q2-2026.mdOptional mirror under knowledge/plans/legal/ — keep aligned with phased doc + roadmap

Cross-functional Q2 context

Systems of record (do not duplicate)

  • Notion — Master Contract Directory and Changelog — ops-facing options + changelog (Rico/Holly ownership discussed in #legal).
  • Drive — BrainForge Contract Templates 2026 — Holly Loom + template pack (link in #legal; not duplicated here).
  • Linear — Legal team — triage; structure initiatives after roadmap sign-off.

Linear alignment (when ready)

After owners and quarter split are confirmed, scaffold initiatives/issues from roadmaps/roadmap-q2-q3-2026.md using the repo skill linear-roadmap-to-structure (.cursor/skills/linear-roadmap-to-structure/SKILL.md).


Last updated: 2026-03-30 (folder layout: plans/, roadmaps/, playbooks/)