README

Knowledge plans

Canonical planning docs for internal initiatives (delivery, finance, analytics, platform features).

Structure

• Planned (approved direction, not yet in flight) → planned/ — executive plans, roadmap decisions, and upcoming initiatives that should be socialized before execution starts.
• Active (in flight) → active/ — initiatives currently being executed.
• Completed (shipped) → completed/ — move here when done; add Shipped in PR link (see completed/README.md).
• Single document at top level → still allowed (e.g. initiative-2026.md), but prefer planned/, active/, or completed/ when status is clear.
• Multiple documents for one initiative → one folder named after the initiative (e.g. pulse-audio-video-data-intelligence-2026/) containing a README.md index and all related files. Do not scatter sibling files at the top level of knowledge/plans/.

Status guidance

• Use planned/ when the document is an approved or proposed direction that should inform prioritization, resourcing, or Linear structure, but is not yet an active workstream.
• Use active/ when the initiative has started execution and is being actively managed.
• Use completed/ when the initiative has shipped and the plan is now historical context.

Active initiative tracker

• Delivery charter, rubric, CSO matrix & operating page (2026)

Planned initiatives

• HubSpot engineering backlog — Robert asks (2026-04) — Platform + Sales alignment: outbound orchestrator (PLT-1273), HeyReach JSON ingest, HubSpot MCP enablement, CRM completeness tickets, SAL-1001 / Outbound campaign links.
• Executive Q2 planning operating model (2026) — Executive planning standard for internal teams and client engagements entering Q2, including plan review and Linear laddering.

Reflection (platform initiatives ↔ Linear)

• Platform initiatives and plans reflection (2026-03) — Current state of Platform initiatives, milestones, and projects; map of plans to Linear; suggested alignment changes.
• Platform team plans (index) — Specs and long-lived platform planning docs (OKRs, skills, Instagantt→Linear, Paperclip, etc.).

Current plans

• Q2 2026 — Legal, Finance & Sales Engineering (hub) — Index to Legal Q2 roadmap, Finance Q2 roadmap, Sales Engineering Q2 roadmap.
• Legal — Q2–Q3 roadmap & vault — Org legal planning: roadmaps/, plans/ (incl. Q2 roadmap and phased q2-2026), playbooks/. Optional mirror: plans/legal/q2-2026.md.
• video data intelligence (2026) — Folder: roadmap, implementation plan, and Pulse proactive intelligence layer.
• Delivery & finance analytics (Rill) + data platform scaling — Rill on Snowflake (delivery health, revenue, financial control) and companion doc on harnesses, CI, skills, and retro (PR #236).
• Agent-powered data environment — Strategy bundle for PR #236: cloud agent data environment report, phased internal→client rollout, self-learning agents, focus areas, roadmap, and research notes.
• Brainforge website — Webflow to code migration — Astro migration plan and document-council review.
• Amplitude Setup — Brainforge Internal (2026) — Phased plan to instrument the platform (Next.js) and website (Webflow) with Amplitude for Greg’s sales demos. Dogfoods the Brainforge Amplitude ramp-up methodology.
• Per-User Clockify — Platform Calendar Sync — Allow each platform user to connect their own Clockify API key and workspace for the Calendar Clockify Sync tool (/ai-tools/calendar-clockify), with env fallback. Includes Linear project and small-ticket breakdown for incremental delivery.
• Idea-to-Tickets Skill (2026) — Cursor skills to walk ideas through plan → phases → project → tickets; includes document-council (stress-test) and linear-status-sync. AI-833.
• Agent-browser for cloud agents — Platform proposal: shell-first browser automation for cloud agents (agent-browser.dev); comparison to Playwright and phased spike.

---

Last updated: 2026-04-15