Product hardening and production-spec work are already in place.
Lei Growth OSProduction Workspace
Quick Access
Open the production workspace.
Use the private access code and choose your workspace role. Owner access can finish setup, run readiness checks, and operate the v1 workspace.
Choose a workspace role to enter the production app.
Real Version 1 Build
A production shell for the next phase of Lei Growth OS.
The prototype already proved the workflows. This layer translates them into a real application foundation with reusable modules, clearer contracts, and a build sequence the team can actually implement.
Production build, live integrations, and deployment operations remain.
Move the highest-value workflows into a real authenticated product surface.
Core Modules
The production rebuild should follow the business operating model
These are the first lanes worth rebuilding because they carry the highest day-to-day value from the prototype into the real product.
Executive overview and command surfaces
The production rebuild should start with the operator-facing shell: signals, next actions, queueing, and readiness views.
- Overview dashboard
- Execution cockpit
- Risk flags
- Activity timeline
Agency, outreach, and campaign operations
This lane turns the prototype's agency tracker into a shared business workflow with owners, statuses, milestones, and meeting preparation.
- Agency records
- Campaign tracker
- Partner desk
- Follow-up drafting
Editorial planning, approvals, and distribution
The content module should preserve the current social planner while making scheduling, review, and publish readiness collaborative and durable.
- Content calendar
- Approval states
- Draft templates
- Channel planning
Email and Lark-ready operations
Delivery stays abstracted until providers are connected, so message payloads, sender identity, and audit events remain stable through integration work.
- Outbound queue
- Sender settings
- Lark payloads
- Audit trail
Implementation Path
A cleaner sprint sequence for getting to a real internal v1
This path keeps the rebuild focused on shared foundations first, then moves into the highest-leverage workflows before attaching live delivery.
Establish the production shell
Create the authenticated app frame, base routes, environment management, and the first shared domain types.
- App layout
- Typed data contracts
- Module routing
- Environment strategy
Rebuild Overview and Agencies
Bring the daily decision layer and partner workflow into the production stack first so the business gains operational value quickly.
- Overview route
- Agency list and detail
- Campaign model
- Activity feed
Rebuild Content and Settings
Port planning, approval, and configuration flows so delivery readiness can sit on top of real shared application state.
- Content planner
- Publishing calendar
- Workspace settings
- Delivery readiness
Attach delivery providers
Email delivery should come first, followed by Lark notifications, with clear separation between generation, review, and send actions.
- Email provider adapter
- Lark adapter
- Queue actions
- Notification logging
System Contracts
What the production architecture needs to preserve
The real application can change the implementation entirely, but these domain commitments should remain stable.
Operator data model
Agencies, campaigns, content items, templates, settings, and activity events should be preserved as first-class domain objects.
Delivery contract
Generated messages should flow through a provider-agnostic payload model so email and Lark remain interchangeable delivery layers.
Migration rule
Preserve the workflows and priorities from the prototype, but do not carry browser-local assumptions into the production architecture.