Legal roadmap — Q2 & Q3 2026
Status: Draft
Created: 2026-03-30
Updated: 2026-03-30
Owners: Rico Rejoso (Operations — legal rolls up to Ops), Holly Condos (part-time internal counsel), Bend Law (external counsel); executive signatory: Uttam Kumaran
Related: SE) · Legal Q2 roadmap · Plan log · Legal vault README (comms, materials map)
1. Context
Brainforge runs high-volume contracting (client MSA/SOW, NDAs, IC agreements, amendments, partner paper). Legal rolls up into Operations: Rico leads ops routing (Documenso, batched updates, coordination with Finance). Holly Condos is part-time internal counsel (redlines, template strategy, deal judgment). Bend Law is external counsel for overflow or specialty. Day-to-day coordination is mostly in Slack #legal; Linear can mirror triage. The gap is structured initiatives, inventory, and AI-era templates/policies—not starting templates from zero (BrainForge Contract Templates 2026 + Notion Master Contract Directory and Changelog already exist). Flowcharts for “which paper when” are not yet centralized — see vault README.md (Where materials and flowcharts live).
This doc is the canonical strategic backlog. Quarter tags are provisional until DRIs sign off.
2. Suggested quarter split (draft)
| Quarter | Focus |
|---|---|
| Q2 | Foundation: contract inventory linked to Notion/Drive, AI + data-use clauses in templates, no unauthorized LLM + internal AI governance, contractor IP fixes, top-20 assignability scan, deal-desk triage habits with Linear. |
| Q3 | Scale & external posture: client-facing AI addendum, trademark/copyright kickoff, AI incident playbook, quarterly legal-readiness cadence, sales-claims sweep, IP asset map refinement, deal-room package v1. |
3. Strategic priorities (with rationale)
| # | Priority | Why |
|---|---|---|
| 1 | Contract inventory tracker (client, MSA/SOW, NDA, renewal, assignment, AI clauses, indemnity, governing law) | You cannot manage risk, diligence, or valuation if obligations are scattered. Align to Notion Master Contract Directory + Changelog. |
| 2 | Redline and standardize AI clauses across templates (MSA/SOW/NDA/vendor/contractor) | Inconsistency creates hidden liability and weak negotiating leverage. |
| 3 | Define “permitted AI use” by contract (tasks/tools/environments allowed) | Avoids breach claims and prevents team-by-team improvisation. |
| 4 | Explicit data-use disclosures and consent (inputs, purpose, retention, training/no-training) | “Client knows we use AI” is not legally specific enough. |
| 5 | Strict “no unauthorized LLM upload” policy (esp. NDA / diligence data) | Most immediate breach risk is confidential data in consumer AI tools. |
| 6 | Internal AI governance policy (approved tools, prohibited uses, human review, logging, escalation) | Contracts only help if operational behavior matches them. |
| 7 | Client-facing AI policy / addendum (plain-English controls) | Improves trust and reduces ambiguity in disputes. |
| 8 | Fix contractor/freelancer IP assignment gaps (WMFH + assignment + confidentiality + moral rights where applicable) | Chain-of-title gaps can make deliverables or IP non-transferable. |
| 9 | Top-20 client assignability review (change-of-control, consent, anti-assignment) | Fastest way to surface M&A/partnership deal blockers. |
| 10 | Map and classify Brainforge IP (brand, methods, content, code/tools, datasets, prompts/playbooks) | Documented IP increases monetization and exit narrative. |
| 11 | Trademark and copyright strategy for core assets (brand + flagship frameworks/content) | Protection takes time; waiting reduces defensibility. |
| 12 | AI incident response playbook (confidentiality leak, hallucination harm, IP complaint) | Response speed and consistency reduce legal and reputational damage. |
| 13 | Align sales claims with legal/technical reality (security, privacy, AI in decks/proposals/site) | Overpromising in GTM creates deceptive-practice exposure. |
| 14 | Quarterly legal-readiness reviews (contracts, AI policy, vendor stack, jurisdiction updates) | AI and regulatory expectations move too fast for annual-only review. |
| 15 | “Deal-room readiness” package (contract matrix, IP schedule, policy binder, vendor/subprocessor list) | Lowers transaction friction, fees, and retrade risk. |
4. Operating signals from #legal (Slack)
Condensed from channel history 2025-10-13 → 2026-03-30 (paginated read). Use for prioritization, not as records of individual deals.
- Throughput: MSA/SOW (incl. entity transitions e.g. Pungo→Brainforge), NDAs/mNDAs (incl. M&A-style targets), IC/amendments/terminations, partner redlines (e.g. Inteleos, Ellie, Calybre). Rico runs ops throughput; Holly handles redlines; escalate to Bend Law when needed.
- Template baseline: Holly Templates 2026 + Loom; gap = AI, payment rails (ACH/CC up-front), insurance minimums / waiver thresholds, transition clauses.
- Inventory / CMDB: Notion Master Contract Directory and Changelog — explicit ops ask; Holly endorsed changelog + DB-style contract management (GenAI called out Oct 2025).
- Decision flowcharts: Holly agreed to flowcharts for new client / contractor paths and clause selection — matches cross-functional roadmap intake fields + clause library.
- Risk patterns: MSA vs SOW sequencing (don’t block delivery), executed vs draft hygiene (e.g. partner agreements in drive), customer warranties (originality, OSS/GPL) and pre-existing IP lists, inventions agreement pushback from team.
- Governance: AI-assisted NDA review threads → need permitted use + upload policy.
- Linear: Triage notifications to Slack; clarify Legal vs Ops ticket boundaries when structuring initiatives.
- Optional HR/legal: Employee handbook discussion (Lauren/Holly) — versioned “legal shield” vs Notion culture doc.
5. Success metrics (from prior Q2 legal draft)
| Metric | Target (end Q2) | Owner |
|---|---|---|
| Contract review turnaround | Under 5 days (standard), under 2 days (urgent) | Legal |
| Legal request tracking | 100% in Linear (or agreed system) | Legal/Ops |
| Legal risks | Proactive register vs reactive only | Legal |
| Playbooks | Top scenarios documented | Legal |
6. Appendix A — Questions for broader legal peers
Contracting and liability
- Preferred baseline for AI indemnity allocation (provider vs client vs mutual)?
- How do you draft AI output ownership/licensing when copyrightability is uncertain?
- Language to disclaim output guarantees without destroying commercial trust?
- Standard for limiting liability on confidentiality breaches involving third-party AI tools?
Confidentiality and NDA boundaries
- NDA wording for AI tools during diligence/advisory?
- How do you define “disclosure to subprocessors/tools” under NDAs?
- Explicit client opt-in before external model providers see their data?
Data governance and privacy
- Minimum AI data-handling disclosure set in MSAs/SOWs?
- Retention/deletion for prompts, outputs, logs?
- Which U.S. state laws drive most conservative AI/privacy drafting?
- Line between “processing client data” and “training/improving systems”?
IP and chain of title
- Contractor clauses for assignable rights to AI-assisted deliverables?
- Treatment of prompts, workflows, methodologies in IP schedules?
- Carving IP in/out during agency asset sales?
- Diligence artifacts buyers expect for IP ownership in AI-heavy businesses?
Operations and evidence
- What controls are “defensible” if dispute tests policy vs practice?
- How firms evidence compliance (allowlists, logs, training, audit trails)?
- Triggers for legal review before new AI tool on client data?
- Strong AI incident commitments — contractual vs operational?
Regulatory outlook
- Near-term U.S. regulatory developments to draft for now vs monitor?
- Future-proof clause structures as AI law evolves?
7. Appendix B — Scratch / follow-ups
| Item | Notes | Owner / target |
|---|---|---|
| AI clause in contracts | Slot-in language (Holly offered); align across template types | TBD |
| Contracts in repo + decision flowcharts | Holly + Uttam thread; pair with Notion directory | TBD |
| Evaluate Brandon’s law firm (if distinct from current stack) | Bend Law is external counsel today; immigration/specialty often via Bend — confirm routing with Rico/Holly | TBD |
| M&A process | Olivo mNDA pattern; assignability + deal-room package | TBD |
Last updated: 2026-03-30 (folder layout: roadmaps/; governance: Ops, Holly, Bend Law)