42 lines
2.3 KiB
Markdown
42 lines
2.3 KiB
Markdown
|
# LetsBe Biz Architecture Proposal (GPT Team)
|
||
|
|
|
||
|
|
Date: 2026-02-26
|
||
|
|
Author: GPT Architecture Team
|
||
|
|
|
||
|
|
This folder contains the complete architecture development plan requested in `docs/technical/LetsBe_Biz_Architecture_Brief.md` Section 1.
|
||
|
|
|
||
|
|
## Deliverables Index
|
||
|
|
|
||
|
|
0. [00-executive-summary.md](./00-executive-summary.md)
|
||
|
|
Executive direction and launch gating summary.
|
||
|
|
1. [01-architecture-and-dataflows.md](./01-architecture-and-dataflows.md)
|
||
|
|
Architecture document with system diagrams and data flow diagrams.
|
||
|
|
2. [02-components-and-api-contracts.md](./02-components-and-api-contracts.md)
|
||
|
|
Component breakdown and API contracts.
|
||
|
|
3. [03-deployment-strategy.md](./03-deployment-strategy.md)
|
||
|
|
Deployment strategy for control plane and tenant plane.
|
||
|
|
4. [04-implementation-plan-and-dependency-graph.md](./04-implementation-plan-and-dependency-graph.md)
|
||
|
|
Detailed implementation plan, task breakdown, and dependency graph.
|
||
|
|
5. [05-estimated-timelines.md](./05-estimated-timelines.md)
|
||
|
|
Estimated timelines and milestone schedule.
|
||
|
|
6. [06-risk-assessment.md](./06-risk-assessment.md)
|
||
|
|
Risk assessment and mitigation plan.
|
||
|
|
7. [07-testing-strategy.md](./07-testing-strategy.md)
|
||
|
|
Testing strategy proposal.
|
||
|
|
8. [08-cicd-strategy-gitea.md](./08-cicd-strategy-gitea.md)
|
||
|
|
Gitea-based CI/CD strategy.
|
||
|
|
9. [09-repository-structure-proposal.md](./09-repository-structure-proposal.md)
|
||
|
|
Repository structure proposal and migration plan.
|
||
|
|
10. [10-technology-validation-sources.md](./10-technology-validation-sources.md)
|
||
|
|
Current official documentation references used to validate technology choices.
|
||
|
|
|
||
|
|
## Executive Direction (One-Page Summary)
|
||
|
|
|
||
|
|
- Keep `letsbe-hub` (Next.js + Prisma) and retool it; do not rewrite core backend in v1 launch window.
|
||
|
|
- Build Safety Wrapper as OpenClaw plugin + local egress secrets proxy; keep OpenClaw upstream and un-forked.
|
||
|
|
- Remove all `n8n` and deprecated-stack references as a hard prerequisite (Week 1).
|
||
|
|
- Replace orchestrator/sysadmin responsibilities with explicit Hub↔Safety APIs and local execution adapters.
|
||
|
|
- Build mobile app with React Native + Expo for speed, push approvals, and shared TypeScript contracts.
|
||
|
|
- Use monorepo for first-party LetsBe code (Hub, Mobile, Safety services, Provisioner), while consuming OpenClaw as pinned upstream dependency.
|
||
|
|
- Target 12-week founding-member launch with strict security quality gates, canary rollout, and staged feature hardening.
|