platform-initiatives-and-plans-reflection-2026-03

Platform Initiatives, Milestones, and Projects — Reflection and Suggestions

Date: 2026-03-18
Status: Draft
Purpose: Reflect on the current state of Platform initiatives, milestones, and projects; map plans in vault and .cursor to Linear; suggest alignment changes.

---

1. Current state: Platform initiatives

Initiative	Status	Target date	Platform projects (count)	Notes
Sales Engineering Q2	Planned	2026-06-30	6	Demos, enablement, Partner mapping & Demo Agents, Pipeline & Backlog Canvas, Case Study, Sales Workflows. Well-scoped.
Q2 2026 Platform Planning	Active	—	2	Platform Ideas, Platform Archive. No target date; acts as backlog container.
Platform Initialization	Active	—	4	Website Migration, Per-User Clockify (Completed), Dagster merge, (others). No initiative-level target.
OpenWork Initialization	Active	—	5	OpenWork Integration, OpenCode A/B/C, Slack-Triggered Agent. Plan in knowledge/engineering.
Delivery & Finance Analytics	Active	—	6	Phase 1–5 + Pipeline & Backlog Canvas. Plan in knowledge/plans; phases have no target dates in Linear.
Platform infrastructure and exploration	Planned	—	7	RBAC, Global Search, Railway setup review, Better auth, Heroku/East US deprecations, Spikes and exploration (Turbopuffer, PoCs).

Gaps observed:

• Milestones: Almost no Linear project milestones or initiative target dates are set. Delivery & Finance has phased projects (1–5) but no targetDate on projects; initiative has no targetDate. Q2 2026 Platform Planning and Platform/OpenWork Initialization have no target dates.
• Single initiative with a date: Sales Engineering Q2 (2026-06-30).
• Ownership: Most initiatives have no owner set in Linear.

---

2. Current state: Plans vs Linear

2.1 Plans that have clear Linear linkage

Plan location	Linear linkage	Notes
knowledge/plans/delivery-and-finance-analytics-2026/delivery-and-finance-analytics-2026.md	Initiative: Delivery & Finance Analytics; Projects: Phase 1–5, Phase 5 Later, Pipeline & Backlog Canvas	Plan §6 phases map to projects; Rill deployment (DP-195–DP-200) are issues, not a project.
knowledge/plans/per-user-clockify-platform-2026.md	Project: Per-User Clockify — Platform Calendar Sync (Completed)	Done; project description references plan.
knowledge/plans/idea-to-tickets-skill-2026.md	AI-833; skills (idea-to-tickets, document-council, linear-status-sync)	Implemented in Platform Ideas / completed work; no dedicated “Idea-to-Tickets” project.
knowledge/platform/plans/company-okrs-in-platform.plan.md	Project: Company Objectives in Platform	Phases 2/3 in plan; project exists, status Planned.
knowledge/platform/plans/paperclip-platform-railway.plan.md	No Linear project	Paperclip in-repo + Railway is platform work; no “Paperclip” or “Railway (Paperclip)” project.
knowledge/engineering/openwork-platform-integration/openwork-platform-integration-plan.md	Initiative: OpenWork Initialization; Project: OpenWork Platform Integration	Strong link; project description points to plan.

2.2 Plans with weak or no Linear linkage

Plan location	Gap	Suggestion
knowledge/plans/amplitude-brainforge-setup-2026.md	No initiative; no Platform project for “Amplitude for demos”	Create project Amplitude for sales demos (or Amplitude setup — Brainforge), add to Sales Engineering Q2 (or a “Platform observability” initiative if you prefer).
knowledge/plans/delivery-and-finance-analytics-2026/data-platform-scaling-harnesses-and-retro.md	Tied to PR #236 (Agent-powered data environment). No dedicated project for “Data platform harnesses / retro”; Agent-powered data environment project exists.	Either add a Data platform harnesses (CI, rules, retro) project under Delivery & Finance or Agent-powered data environment, or add a milestone “Harnesses + retro” to Agent-powered data environment and create issues from the plan.
knowledge/plans/brainforge-website-webflow-to-code-migration-2026/brainforge-website-webflow-to-code-migration-2026.md	Project Brainforge Website Migration exists and references this plan.	OK as-is; ensure project targetDate or milestones reflect Phase 5 cutover when decided.
knowledge/platform/plans/instagantt-to-linear-migration.plan.md	No Linear initiative or project for “Instagantt → Linear migration” or “Linear as single source of truth for timelines”.	Create initiative Instagantt → Linear migration (or Linear timeline migration) and a project Instagantt to Linear migration with phases/milestones from the plan; link plan in project description.
knowledge/engineering/paperclip-railway-deployment-learnings-2026-03.md	Learnings doc; no project.	If Paperclip gets a project, link this as “Learnings” in the project description.
knowledge/engineering/railway-setup-review-2026-03-07.md (if present) / PR #357	Project Railway setup review exists (from earlier session).	Ensure project description links to the vault memo or PR #357.
knowledge/plans/agent-powered-data-environment/roadmap.md	High-level data platform roadmap; not phased. Part of agent-powered data environment (PR #236).	Optionally add a short “Data platform roadmap” section to Delivery & Finance initiative description, or keep as internal reference only.

2.3 Other plans (moved from .cursor/plans/ into knowledge/)

• knowledge/engineering/codex-setup-new-worktree.plan.md — Setup task; no need for a dedicated initiative/project unless you track “Developer experience” as an initiative.
• knowledge/gtm/sales/lmnt-renewal-sheet.plan.md — Client-specific (LMNT renewal); not Platform portfolio.

---

3. Standalone Platform projects (no initiative or plan link)

These Platform projects exist but are not under a plan or initiative (or only loosely):

• CSO Skills, SL Skills, Agent powered data environment, Railway setup review, RBAC, Global Search, N8N deprecation, Partner mapping automations and Demo Agents — Created from PRs; some are under Platform Ideas (Eden Command Center) or Sales Engineering Q2 (Partner mapping & Demo Agents). The rest are “roadmap” projects with no parent initiative.
• Better auth across all platform apps, Complete deprecation of n8n, Complete setup of Codex/Cursor/OpenCode, Migration Namecheap → Cloudflare, Deprecation East US Azure, Deprecation of Heroku — No initiative; no vault plan reference in description.

Update (2026-03-18): Infrastructure and exploration is now under initiative Platform infrastructure and exploration, with projects: RBAC, Global Search, Railway setup review, Better auth, Deprecation of Heroku, Deprecation of East US Azure, and Spikes and exploration (catch-all for time-boxed spikes: Turbopuffer, RBAC approaches, PoCs; promote to a dedicated project when work becomes a track).

Suggestion: Set Platform infrastructure and exploration targetDate when the team commits; use Spikes and exploration for one-off spikes and move issues to RBAC / Global Search when they become delivery tracks.

---

4. Suggested changes (prioritized)

High impact

1. Set initiative target dates

   • Delivery & Finance Analytics: Set targetDate (e.g. end of Phase 2 or Phase 4) from knowledge/plans/delivery-and-finance-analytics-2026/delivery-and-finance-analytics-2026.md or team agreement.
   • Q2 2026 Platform Planning: Set to 2026-06-30 if it’s the Q2 bucket.
   • Platform Initialization / OpenWork Initialization: Set a target (e.g. end of Labs or Phase 2) so roadmap view is meaningful.

2. Add project target dates or milestones for phased work

   • Delivery & Finance Phase 2–5: set targetDate (or use Linear milestones on the initiative/projects) so “when will Phase 3 ship?” is visible.
   • Brainforge Website Migration: set a targetDate for cutover (Phase 5) when decided.

3. Create missing project for Amplitude

   • Add project Amplitude for sales demos (or similar), link to knowledge/plans/amplitude-brainforge-setup-2026.md, add to Sales Engineering Q2 (or a dedicated observability initiative). Create issues for Phase 0, Phase 1, etc.

4. Instagantt → Linear migration

   • Create initiative Instagantt to Linear migration and project Instagantt to Linear migration; link knowledge/platform/plans/instagantt-to-linear-migration.plan.md in the project description; create milestones or issues for the migration steps.

Medium impact

5. Paperclip

   • Create project Paperclip (in-repo, Railway) under Platform Initialization (or Q2 2026 Platform Planning), description linking to knowledge/platform/plans/paperclip-platform-railway.plan.md and knowledge/engineering/paperclip-railway-deployment-learnings-2026-03.md.

6. Data platform harnesses

   • Either add a Data platform harnesses & retro project under Delivery & Finance / Agent-powered data environment with issues from knowledge/plans/delivery-and-finance-analytics-2026/data-platform-scaling-harnesses-and-retro.md, or add a milestone to Agent powered data environment and tickets for CI, rules, retro.

7. Assign initiative owners

   • Set owner on Sales Engineering Q2, Delivery & Finance Analytics, OpenWork Initialization, Q2 2026 Platform Planning so accountability is clear in Linear.

Lower priority

8. Vault plans README

   • Update knowledge/plans/README.md with a short “Linear” column or sentence per plan: which initiative/project (and optional link) so plans and Linear stay discoverable.

9. Roadmap initiatives

   • If the number of ungrouped Platform projects feels noisy, introduce Platform roadmap Q2 or Platform reliability and attach the relevant projects (RBAC, Global Search, N8N deprecation, Railway setup review, Better auth, Heroku/Azure deprecation, etc.).

10. Company Objectives in Platform

• Project exists and is Planned; ensure Phase 2/3 issues exist and are estimated so progress is trackable.

---

5. Summary table: Plan → Initiative / Project (after suggestions)

Plan	Initiative	Project	Action
delivery-and-finance-analytics-2026/ (plan + scaling doc)	Delivery & Finance Analytics	Phase 1–5, Pipeline & Backlog	Set initiative/project target dates; optional milestones.
per-user-clockify-platform-2026.md	Platform Initialization	Per-User Clockify	Done.
idea-to-tickets-skill-2026.md	—	Platform Ideas (skills done)	No change.
amplitude-brainforge-setup-2026.md	Sales Engineering Q2 (or new)	Create Amplitude for sales demos	Create project + issues.
data-platform-scaling-harnesses-and-retro.md (under delivery-and-finance-analytics-2026/)	Delivery & Finance or Agent-powered data	Create Data platform harnesses or milestone on Agent-powered	Create project/milestone + issues.
brainforge-website-webflow-to-code-migration-2026/ (plan + council review)	Platform Initialization	Brainforge Website Migration	Set targetDate for cutover when known.
knowledge/platform/plans/company-okrs-in-platform.plan.md	—	Company Objectives in Platform	Ensure Phase 2/3 issues exist.
knowledge/platform/plans/paperclip-platform-railway.plan.md	Platform Initialization / Q2 Planning	Create Paperclip (in-repo, Railway)	Create project; link plan + learnings.
knowledge/platform/plans/instagantt-to-linear-migration.plan.md	Create Instagantt → Linear	Create Instagantt to Linear migration	Create initiative + project; link plan.
openwork-platform-integration-plan.md	OpenWork Initialization	OpenWork Platform Integration	Set initiative target if desired.
railway-setup-review (PR #357)	—	Railway setup review	Confirm description links to knowledge/PR.

---

6. Next steps

1. Review this reflection with the platform lead; decide which suggestions to adopt.
2. Apply high-impact changes in Linear (target dates, Amplitude project, Instagantt initiative/project).
3. Optionally add a “Linear” line to each plan in knowledge/plans/README.md.
4. In a few weeks, re-check that new plans (e.g. in knowledge/engineering or knowledge/clients) that imply platform work have a corresponding Linear initiative or project.