Q2 Platform Infrastructure & Enablement Plan
Status: Draft (Stub — Pending Clarence Review)
Created: 2026-03-24
Author: Platform Team
Lead: Clarence
Related: Platform Team Charter, Platform Initialization Initiative, Platform Infrastructure Initiative
Quick Links:
1. Context & Problem Statement
Current State
Platform infrastructure work is spread across two Linear initiatives:
- Platform Initialization (Active) — Website Migration, Dagster merge, Clockify (completed)
- Platform Infrastructure and Exploration (Planned) — RBAC, Global Search, auth, deprecations, spikes
Neither initiative has:
- A target date
- Clear ownership
- Defined milestones
- Documented plan
Problem Statement
- No consolidated infrastructure roadmap — Work is scattered across initiatives
- Tech debt accumulating — Heroku, Azure East US, n8n still need deprecation
- Website migration timeline unclear — Phase 5 cutover date not set
- Core capabilities missing — RBAC, Global Search, better auth not delivered
Goal
Deliver reliable infrastructure foundation by end of Q2:
- Modernized deployment (Railway primary, deprecations in progress)
- Core capabilities (auth, search, RBAC) in production
- Website migration complete
- Reduced tech debt (Heroku/Azure/n8n deprecated or with clear migration path)
2. Connection to Broader Goals
Platform Team Charter
This plan delivers the Infrastructure & Enablement workstream referenced in the Platform Team Charter. It enables:
- Other teams to build on reliable infrastructure
- AI execution harness to have stable deployment targets
- Brainforge to present modern, cohesive web presence
Executive Q2 Planning Operating Model
Fits the internal team planning model:
- Leadership (CEO) acts as sponsor
- Quarter-based planning horizon
- Milestones represent leadership-visible outcomes
3. Work Streams
Stream 1: Website Migration (Product — Marketing Request)
Type: Product requested by Marketing team
Current: Phase 4 in progress (Webflow → Astro)
Goal: Complete Phase 5 (cutover)
Note: While website migration involves deployment/infrastructure, it is fundamentally a product — content, design, SEO, and presenting Brainforge to the world. Platform builds the product; Marketing defines requirements and success criteria.
Open Questions:
- Target date for Phase 5 cutover?
- What content migration remains?
- SEO/redirect strategy?
- Who handles post-cutover monitoring?
- Marketing’s success criteria for launch?
Primitives Supported:
- Safety (deployment rollback capability)
- Verification (smoke tests for website)
Stream 2: Auth & Access
Includes:
- Better auth across all platform apps
- RBAC (role-based access control)
- Global Search
Open Questions:
- Is this net-new RBAC or integrating existing system?
- Priority relative to website migration?
- Scope: Platform only or company-wide?
Primitives Supported:
- Context (user roles, permissions in Honcho)
- Safety (access control is safety layer)
Stream 3: Deprecations & Migration
Includes:
- Heroku deprecation
- Azure East US deprecation
- n8n deprecation
- Namecheap → Cloudflare (if not done)
Open Questions:
- Which is highest risk/most urgent?
- Can AI execution harness help with migration scripts?
- Dependency on Railway setup review completion?
Primitives Supported:
- Safety (rollback if migration fails)
- Verification (migration validation)
Stream 4: Dagster & Data Infrastructure
Current: Dagster merge in progress (Platform Initialization)
Open Questions:
- What remains for Dagster merge completion?
- Is this blocking Delivery team work?
4. Work Type Summary
| Stream | Type | Source | Why Platform |
|---|---|---|---|
| Website Migration | Product | Marketing request | Technical implementation (Astro, deployment) |
| Auth & Access | Infrastructure | Platform-initiated | Foundation for security, enables all other work |
| Deprecations | Infrastructure | Platform-initiated | Tech debt reduction, platform health |
| Dagster & Data | Infrastructure | Platform-initiated | Data platform foundation for Delivery team |
5. Tool Stack (OSS-First, Hybrid-Run)
| Layer | Current | Target | Decision Needed |
|---|---|---|---|
| Deployment | Heroku + Azure | Railway (primary) | Timeline? |
| Auth | TBD | Better auth (which system?) | Which tool? |
| Search | None | Global Search | Build vs. buy? |
| DNS | Namecheap? | Cloudflare | Timeline? |
| Orchestration | n8n | TBD (deprecated) | Replacement? |
5. Work Phases
Phase 1: Audit & Prioritize (Week 1)
- Inventory all infrastructure work in flight
- Assign priorities (P0 = blocking, P1 = Q2 must, P2 = if capacity)
- Set target dates for each stream
- Define milestones (leadership-visible outcomes)
Deliverable: Prioritized infrastructure backlog with dates
Phase 2: Website Migration Completion (Weeks 2-6)
- Complete Phase 4 (content migration)
- Execute Phase 5 (cutover)
- Post-cutover monitoring
- Deprecate Webflow
Deliverable: brainforge.ai on Astro, Webflow archived
Phase 3: Auth & Core Capabilities (Weeks 4-10)
- Better auth implementation
- RBAC foundation
- Global Search (if prioritized)
Deliverable: Auth system in production, RBAC scaffolded
Phase 4: Deprecations (Weeks 6-12)
- Heroku migration path defined
- Azure East US migration path defined
- n8n replacement identified
- Execute highest priority migration
Deliverable: At least one major deprecation completed or with clear Q3 plan
Phase 5: Harden & Document (Weeks 10-13)
- Infrastructure runbooks
- AI execution harness integration (use harness for infrastructure work)
- Q3 infrastructure planning
Deliverable: Infrastructure stable, documented, harness-proven
6. Success Metrics
| Metric | Before | Target (End of Q2) | Owner |
|---|---|---|---|
| Website migration | Phase 4 | Phase 5 complete (cutover done) | Clarence |
| Deployment targets | Heroku + Azure | Railway primary, deprecations started | Clarence |
| Auth system | Fragmented | Unified “better auth” in production | Clarence |
| Major deprecations | 0 started | 1+ complete, others have Q3 plans | Clarence |
| RBAC | None | Foundation in place | Clarence |
7. Risks & Mitigations
| Risk | Mitigation | Owner |
|---|---|---|
| Website migration delays | Weekly check-ins; define “good enough” for cutover | Clarence |
| Auth tool indecision | 3-day evaluation; pick most integrated with existing stack | Clarence |
| Deprecation scope creep | One at a time; others go to Q3 if needed | Clarence |
| AI harness not ready to help | Do first few infrastructure tickets manually; adopt harness when ready | Platform team |
8. Open Questions
- Website: Target date for Phase 5 cutover? What content work remains?
- Auth: Which auth system? Scope (Platform only or company-wide)?
- Deprecations: Which is most urgent — Heroku, Azure East US, or n8n?
- Clarence’s Capacity: Is this primarily Clarence-led with AI support, or shared with Uttam?
- Global Search: In or out of Q2 scope?
9. Next Steps
- Review and complete this plan (owner: Clarence + Uttam) — Due: March 28
- Set target dates for each stream (owner: Clarence) — Due: March 28
- Create Linear project “Platform Infrastructure Q2” with milestones (owner: Clarence) — Due: March 28
- Begin Phase 1: Infrastructure audit (owner: Clarence) — Due: April 4
10. Related Resources
| Resource | Location | Description |
|---|---|---|
| Platform Team Charter | knowledge/platform/TEAM-CHARTER.md | Team purpose, primitives, how we work |
| Website Migration Plan | knowledge/plans/brainforge-website-webflow-to-code-migration-2026/ | Detailed migration plan |
| Platform Initiatives | Linear: Platform Initialization, Platform Infrastructure | Current Linear structure |
| Railway Setup Review | knowledge/engineering/railway-setup-review-2026-03-07.md | Deployment infrastructure analysis |
Last updated: 2026-03-24 (stub — requires Clarence input)