Platform Team Charter

Status: Draft (Pending Clarence Review)
Created: 2026-03-24
Authors: Uttam, Clarence
Team: Platform
Members: Uttam, Clarence

1. Purpose

The Platform team builds the infrastructure, tools, and execution systems that enable Brainforge to scale engineering throughput through AI agents and automation.

We are Brainforge’s internal platform team — our customers are internal (Delivery, GTM, Sales, other teams) and our goal is to make those teams more effective through better tooling and autonomous execution.

2. Scope & Boundaries

In Scope

Infrastructure & Enablement:

The Forge — Next.js platform application (apps/platform/)
Data Infrastructure — Dagster pipelines, data platform (apps/dagster-pipelines/)
Developer Experience — CI/CD, deployment, local dev setup
AI Execution Infrastructure — Tools and harnesses for AI-driven development
Internal Tools — Systems that other teams use (Clockify integration, Linear tooling, etc.)

Products:

Requested by other teams — Marketing requests website; Sales requests demo tooling; etc.
Platform-initiated — OpenWork IDE, new products Platform identifies and builds

Out of Scope

Client-specific data pipelines (owned by Delivery)
Client-facing applications (owned by client engagements)
Pure content/marketing work without technical component (owned by GTM)

How Product Work Is Prioritized

Source	Example	How It Enters Platform Backlog
External request	Marketing wants website	Request enters via Linear triage; must have sponsor, timeline, success criteria
Platform-initiated	Build OpenWork IDE	Platform team identifies need, defines success, gets sponsor buy-in
Company strategic	AI execution harness	Leadership priority, explicit Q2 commitment

External Request Process:

Requesting team creates Linear ticket (or Platform creates on their behalf)
Linear triage: Is this Platform scope? Is there capacity? What’s the priority?
If accepted: Define sponsor, timeline, success criteria
Platform implements; requesting team owns requirements and acceptance

Collaboration Boundaries

We Build	Others Contribute	Handoff
Platform infrastructure	Delivery uses it	Delivery owns client data models
OpenWork IDE	All teams use it	Platform owns core, others extend
AI execution harness	All teams benefit	Platform proves, others adopt
Dagster framework	Delivery writes pipelines	Platform maintains infrastructure
Marketing-requested products	Marketing defines content/design	Platform owns implementation
Sales-requested demo tools	Sales defines demo scenarios	Platform owns demo environment

3. How We Work

Execution Model

The Platform team operates on a hybrid human-AI execution model:

Humans (Uttam + Clarence): Define strategy, set primitives, make architectural decisions, review AI output, handle novel problems
AI Agents: Execute well-defined tickets end-to-end (code, test, PR, deploy)
Target: 50%+ of Platform tickets completed end-to-end by AI by end of Q2

Core Primitives

All Platform work is organized around six technology-agnostic primitives:

Context — AI has access to relevant memory and knowledge (Honcho)
Specification — Clear, testable definition of “done” (test plans)
Verification — Multi-layer automated proof (tests, types, lint)
Execution — AI can invoke tools, run commands, deploy (MCPs, triggers)
Observation — Traceability of AI decisions and failures (logs, memories)
Safety — Guardrails, rollback, blast radius containment (staging, flags)

These primitives are durable — new tools are evaluated against them.

Decision Framework

Decision Type	Who Decides	How
Tool selection (new primitive)	Uttam + Clarence consensus	Document rationale, OSS-first preference
Tool selection (existing primitive)	AI / Automation	Follow established standard
Architecture changes	Uttam + Clarence	Document in plan, review together
Ticket implementation	AI	Follow spec → test → implement → verify flow
Code review	Human spot-check	15-min review for AI-shipped code
Emergency fix	Nearest human	Post-hoc documentation required

Communication

Standards: We follow and contribute to standards/ (especially engineering setup)
Documentation: Plans live in knowledge/plans/, team context lives in knowledge/platform/
Linear: All work ladders into Linear (Initiative → Project → Milestone → Issue)
Async-first: Small team, prefer written decisions over meetings

4. Q2 2026 Plans

The Platform team’s Q2 work is organized into four plans:

Plan 1: AI Execution Harness

Purpose: Build the infrastructure for 50%+ AI-driven ticket completion
Lead: Uttam
Plan: q2-platform-ai-harness.md
Primitives: All 6 (focus on Verification, Safety, Specification)
Outcome: AI agents can complete Platform tickets end-to-end with minimal human review

Plan 2: Infrastructure & Enablement

Purpose: Core infrastructure, auth, search, deprecations, website migration
Lead: Clarence
Plan: q2-platform-infrastructure.md (stub)
Initiatives: Platform Initialization + Platform Infrastructure and Exploration (merged)
Outcome: Reliable infrastructure foundation, modernized deployment, reduced tech debt

Plan 3: OpenWork Platform Integration

Purpose: IDE and agent development environment for all teams
Lead: Shared (Uttam + Clarence)
Plan: OpenWork platform integration plan
Initiative: OpenWork Initialization
Outcome: OpenWork IDE available for internal use, agent capabilities proven

Plan 4: Sales Engineering Support

Purpose: Demo infrastructure, partner mapping, enablement for Sales
Lead: Platform supports Sales priorities
Plan: Referenced in Sales Engineering Q2 initiative in Linear
Initiative: Sales Engineering Q2
Outcome: Sales team has reliable demo environment and automation tools

5. Tool Standards

All Platform tool selections follow these principles:

OSS-First: Prefer open source with option for managed service
Hybrid-Run Capable: Must work locally (dev) and in cloud (prod)
Agent-Native: Callable by AI via API/MCP, not just human GUI
Proven at Scale: Evidence of production use
Fit-to-Primitive: Maps cleanly to one of the 6 core primitives

Currently Assigned Tools

Primitive	Tool	Rationale
Context	Honcho	Long-term agent memory, workspace context
Verification	TBD (GitHub Actions candidate)	CI/CD, test runners
Safety	TBD	Staging, feature flags, rollback
Specification	TBD	Test plan generation
Execution	Honcho Cron + MCPs	Scheduled execution, tool interfaces
Observation	Honcho + TBD	Memory + structured logging

6. Success Metrics (Q2)

Metric	Target	Owner
AI end-to-end completion rate	50%	Platform team
Production incidents from AI-shipped code	0	Clarence
Website migration completion	Phase 5 cutover	Clarence
OpenWork internal beta	3+ internal users	Shared
Infrastructure deprecations (Heroku/Azure)	Started	Clarence

7. Dependencies & Risks

Key Dependencies

Honcho: Memory/context layer — already decided, but still evolving
Linear: Project management — must stay organized for AI execution
Delivery team: Primary customer for data infrastructure — needs alignment
Sales team: Demo requirements — may shift based on sales priorities

Top Risks

Risk	Mitigation
AI harness becomes the project, not the enabler	Cap harness work at 6 weeks; prioritize real tickets
Tool indecision	3-day decision window per primitive; “good enough” over perfect
Clarence/Uttam bandwidth	Async-first; 1 focused working session per week max
Other teams not adopting Platform output	Build for Platform first; adoption is secondary Q2 goal

8. Operating Rhythms

Weekly

Review AI execution metrics (completion rate, review time)
Triage any AI-shipped code that needed rework
Update Linear (keep board honest)

Bi-Weekly

Clarence + Uttam sync on blockers, tool decisions
Review plan progress against Q2 goals

Clarence + Uttam: Full Platform portfolio review (Q2 lock-in)

Before treating Q2 execution as committed, review every Platform project in Linear plus the four tickets in Q2 Proposed Projects. Appendix B (B.1–B.3) lists each non-canceled Platform team project (snapshot) in the same shape as Appendix A, plus the review playbook (order, checklist, hygiene).

Monthly

Leadership visibility: status of 4 plans
Adjust timelines if material changes

Quarterly

Plan review for next quarter
Retrospective on AI execution model

9. Resources

Documentation

Code

apps/platform/ — The Forge
apps/dagster-pipelines/ — Data infrastructure
brainforge-work — hosted Work IDE/agent environment (separate repo)
.cursor/skills/ — Cursor skills (Platform maintains)

External

Honcho: https://docs.honcho.dev
Linear: https://linear.app/brainforge/team/platform

10. Decision Log

Date	Decision	Rationale	Owners
2026-03-24	Honcho selected for Context primitive	Long-term memory, workspace support, agent-native	Uttam
2026-03-24	6 core primitives defined (Context, Specification, Verification, Execution, Observation, Safety)	Durable framework for tool evaluation; technology-agnostic	Uttam + Clarence
2026-03-24	4 Q2 plans structure	Clear separation: AI Harness, Infrastructure, OpenWork, Sales Eng	Uttam + Clarence
2026-03-24	AI end-to-end target: 50% of Platform tickets by Q2 end	Scale 2-person team through AI execution	Uttam + Clarence
2026-03-24	Hybrid human-AI execution model	Humans define strategy/review; AI implements	Uttam + Clarence
2026-03-24	Terminology: “Products” not “Features”	Website, OpenWork are standalone products	Uttam + Clarence
2026-03-24	External product requests go through Linear triage	Structured intake with sponsor, timeline, criteria	Uttam + Clarence
2026-03-24	Tool selection principles: OSS-first, hybrid-run, agent-native	Consistent evaluation framework	Uttam + Clarence
2026-03-24	Platform scope: Infrastructure & Enablement + Products	Both foundational and product work	Uttam + Clarence
2026-03-25	Review full Platform portfolio with Clarence before Q2 lock-in	~30 existing Linear projects across 6 initiatives + 4 proposed tickets; no project left without a Q2 decision	Uttam + Clarence

Appendix A: Q2 Proposed Projects (Pending Review)

The following workstreams have canonical plans under knowledge/plans/platform/ (visible in-repo; previously lived under .cursor/plans/). They are proposed for Q2 until committed. Tracking: Linear project Q2 Proposed Projects (initiative Q2 2026 Platform Planning).

Tickets: PLT-1226 Instagantt · PLT-1227 Paperclip · PLT-1228 Skill tracking · PLT-1229 OKRs operational DB

Project	Type	Priority	Status
Instagantt to Linear Migration	Infrastructure	High	Proposed — High impact per Platform reflection
Paperclip Platform Railway	Infrastructure	Medium	Proposed — Relationship to AI Harness TBD
Skill Usage Tracking	Infrastructure	Medium	Proposed — Low effort, high observability value
Company OKRs Operational DB	Product + Infra	Review	Proposed — Overlaps with existing OKRs project

Instagantt to Linear Migration

Priority: High
What: Migrate project timelines from Instagantt to Linear Projects; 3 new skills (Kickoff, Update, Audit); replace Instagantt CSV step
Plan: instagantt-to-linear-migration.plan.md
Why: Single source of truth for timelines; enables EP audit, weekly kick-off to reason about project health
Decision Needed: Commit for Q2? Pilot first? Defer?

Paperclip Platform Railway

Priority: Medium
What: Deploy Paperclip agent orchestration in-repo under apps/paperclip/; Railway deployment; Platform team goals/projects
Plan: paperclip-platform-railway.plan.md
Learnings: knowledge/engineering/paperclip-railway-deployment-learnings-2026-03.md
Decision Needed: Is this the “Execution” primitive for AI Harness? Or separate? Commit, merge, or defer?

Skill Usage Tracking

Priority: Medium
What: Track every skill/command/rule invocation to Supabase; fire-and-forget curl ping; 60+ skills to instrument
Plan: skill-usage-tracking.plan.md
Decision Needed: Merge into AI Harness (Observation primitive) or standalone? Low effort suggests commit.

Company OKRs Operational Database

Priority: Review
What: Full database migration from Sheets to Supabase; UI pages for OKRs, WBR, Software, Partners; Linear/HubSpot/Snowflake integrations
Plan: company-okrs-operational-database.plan.md
Decision Needed: Overlaps with existing “Company Objectives in Platform” project (Sheets-backed). Pick one approach: Sheets (fast) vs. DB (comprehensive) vs. neither.

Appendix B: Clarence review — full Platform portfolio

On this page: B.1 Goal and snapshot · B.2 Review playbook · B.3 Portfolio by initiative · B.4 Related reference

B.1 Goal, snapshot, and scope

Goal: Every Platform-related project in Linear gets one explicit outcome: Commit Q2, Defer Q3+, Close / archive, or Merge into another project.

Inventory (B.3): Same shape as Appendix A for each project — Linear link, Status, What, Plan pointer, Decision needed. Snapshot 2026-03-25 from the Platform team in Linear (non-Canceled projects only). Canceled projects are omitted here (legacy playbooks, Lead List Builder, etc.). Platform Archive is a bucket project — triage issues inside Linear. Live owners, milestones, and issue state remain authoritative in Linear.

B.2 Review playbook

Suggested review order

Charter + four Q2 plans (this doc + harness, infrastructure, OpenWork, Sales Eng) — align on priorities
AI Execution Harness — primitives and tool gaps
Q2 Proposed Projects and Appendix A — commit / defer / merge
Remaining projects (B.3) — initiative by initiative; set owner, target date or defer, milestones if leadership-visible

Per-project decision (checklist)

For each project, record in Linear (description, comment, or label):

Decision	Meaning
Commit Q2	In scope for quarter; set or confirm `targetDate`, owner, first milestone
Defer Q3+	Valid but not this quarter; move to backlog or note in project description
Close / archive	Done, cancelled, or duplicate; archive project and close stale issues
Merge	Absorb into another project; move issues, archive empty shell

Hygiene during review

Orphan issues (no project): assign to a project or close
Completed projects (e.g. Per-User Clockify): archive
Duplicate or overlapping projects (e.g. two OKR approaches): pick one track, merge or defer the other

B.3 Portfolio by Linear initiative

Projects are grouped under Linear initiative headings (level-4 markdown headings). Each project is a level-5 heading under its initiative. When Linear splits one program into phase projects (e.g. OpenCode A/B/C), those appear as one appendix entry with a table or bullets so review stays one decision surface. Initiative names match Linear; use the jump list during long review sessions.

B.3 Navigate

Client delivery automation
Data agent and data team harnesses
Delivery & Finance Analytics
GTM engineering
Instagantt → Linear migration
OpenWork Initialization
Platform DevEx and standards
Platform infrastructure and exploration
Platform Initialization
Platform integrations
Platform maintenance (KTLO)
Platform security and access controls
Platform toolchain
Productivity
Q2 2026 Platform Planning
Sales Engineering Q2
(No initiative)

Client delivery automation

Client Handoff Automator

Linear: Client Handoff Automator · Status: Backlog What: Auto-creates delivery artifacts when a deal closes in HubSpot. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Client Health Scorecard

Linear: Client Health Scorecard · Status: Backlog What: Auto-generated client health signal from delivery, cadence, and responsiveness data. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

CSO Skills

Linear: CSO Skills · Status: Backlog What: AI cursor skills, MCPs, and integrations for CSO roles (from PR #234 plan) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

EP Skills

Linear: EP Skills · Status: Backlog What: AI cursor skills, MCPs, and integrations for EP roles. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Meeting Context Card

Linear: Meeting Context Card · Status: Backlog What: Persistent client page with recent meeting summaries, open tickets, burn, and blockers. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

SL Skills

Linear: SL Skills · Status: Backlog What: AI cursor skills, MCPs, and integrations for SL roles (from PR #234 plan) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

SOW Burn Tracker

Linear: SOW Burn Tracker · Status: Backlog What: Shows budget consumed vs remaining per client/SOW, updated from time actuals. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Timesheet Reminder Bot

Linear: Timesheet Reminder Bot · Status: Backlog What: Slack reminder bot to prompt for missing time entries. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Data agent and data team harnesses

Agent powered data environment

Linear: Agent powered data environment · Status: Backlog What: Cloud Agent strategy for DE/analytics/analyst workflows, CI and PR review (from PR #236) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Data platform harnesses

Linear: Data platform harnesses · Status: Backlog What: Harnesses to scale the data team: playbook docs, Cursor rules/commands, CI for rill/dbt, retro and learnings (from data-platform-scaling-harnesses-and-retro plan). Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Delivery & Finance Analytics

Delivery & Finance Analytics (Phases 1–5)

One program in Linear split across five projects. Review program commitment for Q2 first, then phase dates/owners in Linear.

Phase	Linear	Status	What
1 — Foundation	Phase 1	In Progress	Verification, dbt setup, staging/marts for time/effort, Rill delivery health dashboard
2 — Finance	Phase 2	In Progress	QuickBooks + HubSpot staging, finance marts, Rill finance dashboard
3 — Orchestration	Phase 3	Backlog	dbt scheduling, data quality tests, lineage documentation
4 — Financial Control	Phase 4	Backlog	Rill Financial Control dashboard: executive snapshot, cost structure, contractor/variable panel, margin health, MoM variance, alert logic
5 — Later	Phase 5	Backlog	Revenue Phase 2, client views, HubSpot SOW/burn — create tickets when prioritised

Plan: — (see Linear project descriptions / vault links; Q2 in-repo plans in Appendix A and knowledge/plans/platform/)
Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (per phase or roll up program in Linear)

GTM engineering

Pipeline & Backlog Canvas (DP-229)

Linear: Pipeline & Backlog Canvas (DP-229) · Status: In Progress What: Sales pipeline and revenue backlog visibility in Rill from HubSpot deal history. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Pipeline Capacity Overlay

Linear: Pipeline Capacity Overlay · Status: Backlog What: Maps HubSpot pipeline demand to staffing capacity. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Proposal Hours Estimator

Linear: Proposal Hours Estimator · Status: Backlog What: Estimates delivery effort from historical project data. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Revenue Forecast Dashboard

Linear: Revenue Forecast Dashboard · Status: Backlog What: Forecasts confirmed and probable revenue from operating and pipeline data. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Sales Workflows

Linear: Sales Workflows · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Instagantt → Linear migration

Instagantt to Linear migration

Linear: Instagantt to Linear migration · Status: Backlog What: Migrate timeline planning from Instagantt into Linear Projects and milestones. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

OpenWork Initialization

OpenCode Slack-Triggered Coding Agent (umbrella + Phases A–C)

Umbrella project plus three phase projects in Linear — review as one program (sequence and Q2 cut line), then confirm phase targets in Linear.

Umbrella: OpenCode Slack-Triggered Coding Agent · Status: Next Cycle
What: Reduce Cursor Cloud costs by 30–50% via Slack-triggered OpenCode background worker. Phased delivery: A (Week 1), B (Week 2), C (Weeks 3–4). Reference: vault/engineering/openwork-platform-integration/ (opencode alternative investigation).

Phase	Linear	Status	What
A — Thin Slice MVP	Phase A	In Progress	Week 1 — prove the loop end-to-end for one repo / task
B — Reliability & Hardening	Phase B	Next Cycle	Week 2 — after Phase A success (e.g. ≥70% success rate)
C — Scale & Polish	Phase C	Next Cycle	Weeks 3–4 — after Phase B (model routing, safety)

OpenWork Platform Integration

Linear: OpenWork Platform Integration · Status: In Progress What: Colocate OpenWork in brainforge-platform (subtree) and integrate web UI + landing under platform auth. PR 256. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform DevEx and standards

Playbook Compliance Checker

Linear: Playbook Compliance Checker · Status: Backlog What: Checks vault and playbook PRs for template and formatting compliance. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Vault Search

Linear: Vault Search · Status: Backlog What: Full-text search across vault transcripts, SOWs, resources, and meeting notes. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform infrastructure and exploration

Deprecation of East US Azure deployments

Linear: Deprecation of East US Azure deployments · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Deprecation of Heroku

Linear: Deprecation of Heroku · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Global Search

Linear: Global Search · Status: Backlog What: Global search across meetings, Slack, HubSpot via Turbopuffer; /search page and API (PR #83, AI-530) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Railway setup review

Linear: Railway setup review · Status: Backlog What: Internal Railway setup review memo: topology, cleanup, OpenWork gates (from PR #357) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Spikes and exploration

Linear: Spikes and exploration · Status: Backlog What: Time-boxed spikes and exploration: Turbopuffer, RBAC approaches, new services, proof-of-concepts. Create issues here; promote to a dedicated project when work becomes a track. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform Initialization

Brainforge Website Migration

Linear: Brainforge Website Migration · Status: In Progress What: Migrate brainforge.ai from Webflow to Astro + Railway. Site live on Railway; remaining: parity, forms, a11y, SEO, cutover. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Dagster platform merge (PR #233)

Linear: Dagster platform merge (PR #233) · Status: Backlog What: Dagster pipelines merge into monorepo, BugBot follow-up, and validation. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Per-User Clockify — Platform Calendar Sync

Linear: Per-User Clockify — Platform Calendar Sync · Status: Completed What: Per-user Clockify credentials for Platform Calendar Sync; env fallback. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

SEO optimization

Linear: SEO optimization · Status: Backlog What: Improve website discoverability and on-page SEO as part of the Brainforge site migration. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform integrations

Source-system integrations

Linear: Source-system integrations · Status: Backlog What: Connector onboarding, auth, webhooks, API drift, and reliability for core source systems. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform maintenance (KTLO)

n8n sunsetting (two Linear projects)

Same theme split across two projects — review once (merge in Linear later if desired).

Track	Linear	Status	What
Complete deprecation	Complete deprecation of n8n	Backlog	— (see Linear project description)
Zoom / Dagster pipeline	N8N deprecation	Backlog	Replace n8n/Dagster Zoom pipeline with Mastra agents and inline processing (PR #47, AI-745)

Dependency / Security Scanner

Linear: Dependency / Security Scanner · Status: Backlog What: Weekly dependency scanning with alerts for critical vulnerabilities. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Deploy Status Dashboard

Linear: Deploy Status Dashboard · Status: Backlog What: Shows Railway service health, deploy time, and build status across services. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform security and access controls

Better auth across all platform apps

Linear: Better auth across all platform apps · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

RBAC

Linear: RBAC · Status: Backlog What: Role-Based Access Control for The Forge: roles, assignments, route/API enforcement (PR #89, AI-528) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform toolchain

Complete setup of Codex, Cursor Agent, and OpenCode Cloud Agent leveraging single env

Linear: Complete setup of Codex, Cursor Agent, and OpenCode Cloud Agent leveraging single env · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Paperclip integration

Linear: Paperclip integration · Status: Backlog What: Bring Paperclip into the monorepo and deploy it on Railway for the platform team. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Productivity

Productivity Dashboard

Linear: Productivity Dashboard · Status: Backlog What: Internal insights and alerts roadmap (Notion). Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Q2 2026 Platform Planning

Platform Archive

Linear: Platform Archive · Status: Next Cycle What: Stale backlog items, old workflow projects, and completed work kept for reference. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform Ideas

Linear: Platform Ideas · Status: Next Cycle What: Backlog ideas and future work — one ticket per idea for traceability. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Sales Engineering Q2

Amplitude demo

Linear: Amplitude demo · Status: Backlog What: Amplitude setup for sales demos: instrument platform and website for Greg; pre-built dashboards for feature adoption and user journeys. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Case Study / Interview Assistant

Linear: Case Study / Interview Assistant · Status: Planned What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Omni demo

Linear: Omni demo · Status: Backlog What: Omni Analytics demo environment and assets for sales: topics, dashboards, Blobby (AI), and proof-of-value for prospects. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Partner mapping automations and Demo Agents

Linear: Partner mapping automations and Demo Agents · Status: Backlog What: Partner account mapping automation (Snowflake, EA-1) and Prospect Demo Builder / custom demo agents for sales. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Sales demos and proof-of-value

Linear: Sales demos and proof-of-value · Status: Backlog What: Demos, POCs, and proof-of-value assets to support sales team selling data platform, AI, and reporting services. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Sales enablement tooling

Linear: Sales enablement tooling · Status: Backlog What: Tooling and workflows that enable the sales team to run campaigns, follow-ups, and outreach for various services. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Snowflake demo

Linear: Snowflake demo · Status: Backlog What: Snowflake demo environment and assets for sales: sample data, pipelines, and proof-of-value for data platform prospects. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

(No initiative)

[Partnership] Contextual AI - Insurance Tool

Linear: [Partnership] Contextual AI - Insurance Tool · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

AI Adhoc

Linear: AI Adhoc · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

AI Discovery & Enablement

Linear: AI Discovery & Enablement · Status: Completed What: Historical cross-team AI discovery / enablement (completed). Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

AI Leverage Index – Baseline & Weekly Tracking

Linear: AI Leverage Index – Baseline & Weekly Tracking · Status: Planned What: Baseline and weekly AI usage / leverage metrics. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

AI-Generated Tickets – Quality & Adoption

Linear: AI-Generated Tickets – Quality & Adoption · Status: In Progress What: AI ticket creation quality and team adoption. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Company Objectives in Platform

Linear: Company Objectives in Platform · Status: Planned What: Phased work to document and surface company OKRs and goals in the platform (Phase 2: Option A page + API; Phase 3: Option B DB + sync). Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Daily Platform Engagement – 100% Adoption

Linear: Daily Platform Engagement – 100% Adoption · Status: Planned What: Drive daily platform engagement and reporting. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Data Team Workflows

Linear: Data Team Workflows · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Engineering Workflows – Documentation & Ownership (50%)

Linear: Engineering Workflows – Documentation & Ownership (50%) · Status: Planned What: Document engineering workflows; partial ownership coverage. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Mastra Migration

Linear: Mastra Migration · Status: Planned What: Migrate active n8n workflows into Mastra; platform-integrated automation. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Meeting Recording Platform

Linear: Meeting Recording Platform · Status: Planned What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Migration from Namecheap to Cloudflare for domain registration

Linear: Migration from Namecheap to Cloudflare for domain registration · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

PM/Sales/Marketing Workflows – Documentation & Ownership

Linear: PM/Sales/Marketing Workflows – Documentation & Ownership · Status: Planned What: Document GTM workflows; owners; central repo. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Product Analytics Playbooks

Linear: Product Analytics Playbooks · Status: Backlog What: Product analytics playbook templates and Notion links. Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Project Management Automations

Linear: Project Management Automations · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Q2 Proposed Projects

Linear: Q2 Proposed Projects · Status: Backlog What: Pending Q2 project proposals from .cursor/plans/ for Clarence/Uttam review. Projects here are proposed but not yet committed. Decision: commit (move to proper initiative), defer (close or backlog), or merge (into existing project). Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Recruiting

Linear: Recruiting · Status: In Progress What: Cross-team recruiting project (Platform is one of several teams). Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Recruiting Workflows

Linear: Recruiting Workflows · Status: Backlog What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Stand-up / Meeting Assistant

Linear: Stand-up / Meeting Assistant · Status: Planned What: — (see Linear project description) Plan: — (see Linear project description / vault links there; Q2 in-repo plans in Appendix A and knowledge/plans/platform/) Decision needed: Commit Q2 · Defer Q3+ · Close/archive · Merge (into which project?)

Platform Initiatives Reflection (2026-03-18) — prior gaps (dates, owners, milestones)

Last updated: 2026-03-25

Brainforge Knowledge

Explorer

TEAM-CHARTER