English {#english}

PREGO Planning & Implementation

Starting points

Fork-ready platform hub — Multi-repo master plan (cleanup, platform extraction, contracts, tenant standardization, fork checklist, IDE guide). See also API contracts and dependency inspection for AI.
Implementation index — v4.0 implementation index (migrations, workflows, workers, config) and links to Phase summaries.
Deployment checklist — Phase checklist before first deploy and run.
- Verification: QA checklist
Control Platform v4 implementation plan — Implementation plan (tasks, dependencies, completion criteria).
API overview — Workers, API endpoints, Cron summary.
Operations runbook — Operations runbook summary (Pulumi, Purge, Secrets, manual triggers).
Gateway (Zuplo) operators — Browser CORS, Portal ALLOWED_ORIGINS, optional x-trace-id: prego-zuplo docs/runbook/README.md (index) · folder (this site’s /runbook/ is infra/ops for the monorepo, not Zuplo). Tenant & trust boundaries.

Phase summaries

Phase	Summary doc
1	Phase 1 implementation summary
2	Phase 2 usage R2/KV
3	Phase 3 governance
4	Phase 4 US autoscaler
5	Phase 5 EU GDPR

Consolidated plans

Tenant provisioning E2E rollout — Zuplo, control plane, GitHub Actions, Hetzner, Ansible, Zuplo sync checklist; staging onboarding funnel debug and scripts/export-funnel-events.sh.
OTP and email consolidated — OTP, email flow, templates, Resend, dashboard. Has Implementation status table.
OTP verify consolidated — OTP verification, CORS, passcode flow. Has Implementation status table.
prego-docker build troubleshooting — Build failures (exit 128/167, yarn, uv resolver). Korean section has 적용 체크 table.

Plans with implementation-status tracking

my-ai-cloudflare-flow-and-access-plan — §8.3 Phase 8 MCP, §8.4 Phase 9 Agent; §8.6 summary; §8.7 backlog (Phase 8: wire get_payslip/get_attendance when backend defined; OTP/email 적용됨).
my-ai-chat-ui-changes-plan — Placeholder, input-row layout (engine dropdown), history/delete; implementation status and §5.6 backend verification at end.
ansible-frappe-bench-rc127-resolution-plan — §16 (Korean) checklist: workspace mount, image bench, sites-only volume, Provisioner Job (item 4 미적용; 비고 참고).
otp-and-email-consolidated, otp-verify-consolidated — Status tables: 적용됨 (Resend, OTP body/input, CORS, dashboard green/red, B6 KV).
build-troubleshooting — 적용 체크 table: Exit 128, yarn §4 적용; uv §5 확인됨.

API Control Plane

www /trial — Zuplo·Cloudflare 통합 기획 — 현재 /trial 플로우 정리, 공개 API를 Zuplo로 수렴·Cloudflare(Pages·Zone·Workers) 역할 분리, 구현 단계. 코드 없음.
Trial 이메일 필터 — HTTP 오류 원인 분석·대응 기획 — 404/405·unmatched-path 구분, GET /favicon.ico 노이즈, 점검 순서. 코드 변경 없음.
Trial 이메일 — 회사/공용 구분 메시지·분류 개선 기획 — gmail vs 회사 도메인 동일 메시지 체감; www /trial 카드 UI·세로 중앙 정렬(m.pregoi.com 정렬); 회사 검증 후 m.pregoi.com/?plan=free&region=sg → preset·Send verification code; 관리자: 내부 무료 dictionary CRUD, 외부 API 단계별 테스트, 최종 회사메일 판정·manual 안내 로그; 카피·분류·수용 기준. 구현 요약: 기획서 §0 — CP·Zuplo·www 게이트; 남은 UX·카피는 기획서 본문.
Bird SMS replaces Twilio — verification + Stripe API keys — 아카이브: 수동 승인 SMS는 제거됨; Stripe·웹훅 서술은 참고용.
Remove phone SMS OTP — email-only manual approval — Delete Twilio/Bird SMS OTP; email verification only. Implemented (CP, Zuplo, www; runbooks updated).
API Control Plane implementation plan — Control Plane stages, contract, queues, observability, security, runbook, backup, Phase A–D. Implementation: prego-control-plane (see Implementation index).
Onboarding, provisioning, logpath, admin console — Free/Paid → D1 → placement → Docker Hub / Ansible → Zuplo / Cloudflare → provision-complete; logpath IDs; unified internal monitoring console plan.
m.pregoi.com (admin-web) UX — implementation note — OTP verify routes, layout/footer, cookie sync, Zuplo mail language; repo file map.
m.pregoi.com — Company Profile, cookie UI, Employee Portal label (plan) — Invite row red-X, remove Cookie settings & copyright footer, drop Employee Portal; www vs direct-URL access (security); planning only.

m.pregoi.com — detailed implementation plans (A–D)

Plan A — Stripe checkout & Pay button — CP URL, UX on failure, test matrix, phases.
Plan B — Auth, commerce & email funnel observability — funnel_events, internal APIs, admin UI.
Plan C — Logpath across full onboarding — trace_id, Stripe metadata, x-trace-id, per-repo checklist.
Plan D — Activate readiness, portals & email — Readiness gates, job API, cross-repo order.

www /trial

trial-page-gate-error-footer-input-plan — pregoi.com/trial: persistent “Email verification isn’t available…”, footer still in first viewport, Work email input disabled; root-cause checklist and layout notes. Planning only.
trial-page-free-email-zuplo-layout-plan — Free-email phase-2 via npm free-email-domains-list, keep admin custom dictionary, fix “Email verification isn’t available…”, first-viewport footer layout. Planning only.

Cloudflare Pages (monorepo)

cloudflare-pages-build-watch-paths-monorepo-plan — Build watch paths per Pages project (prego-www, prego-devdoc, etc.) to reduce simultaneous builds; dashboard-only; include/exclude path tables and test scenarios. Planning only.

Other

Resource optimization safe adoption — Resource tuning (Redis, Gunicorn, CDN, Docker) adoption order. Summary: Quick reference.
SaaS unified architecture — Unified architecture and folder structure.
Tenant provisioning flow — Signup, payment → queue → GitHub Actions/Worker, Pulumi→Ansible→Zuplo→Cloudflare.
Tenant subdomain DNS design — Approach C: canonical tenant-{short_id}.pregoi.com + user CNAME.
Pregoi infrastructure R2 API update — R2 and API update plan.
Prego Pulumi migration and automation — Pulumi move to prego-pulumi and GitHub-based execution (or see pulumi-ansible-step1-step2-plan for automation).
Prego Phase 2 — Corporate platform roadmap (Phase 2) — Goals, non-goals, boundaries, risks; multi-ERP connectors, Zuplo, MCP, external AI engines; Mermaid concept diagram. English + Korean.

Cloudflare-based feature plans (신규 기능 기획)

Frappe 인스턴스별 이메일 서버 구축 — 테넌트 격리형 이메일 인프라, Cloudflare Email Workers/Queue, 중앙 관리 앱, Frappe 훅 통합. English + Korean.
Scheduled automation 앱 스케줄러 (Frappe 인스턴스별) — 하이브리드 스케줄러 (중앙 Cron + Frappe 스케줄러), 타임존 지원, Queue 기반 실행, 엔터프라이즈 옵션. English + Korean.
온라인 예약 시스템 (Reservation) — Cloudflare Workers + Durable Objects + D1 기반, 슬롯 잠금, Frappe Event 동기화, 임베드 위젯. English + Korean.

flowchart TB
  A[Planning] --> B[Implementation index]
  A --> C[Deployment checklist]
  A --> D[v4 Implementation plan]
  A --> E[API overview]
  A --> F[Phase 1-5 summaries]
  B --> F

한국어 {#korean}

시작점

IMPLEMENTATION_INDEX — v4.0 구현 산출물 전체 목록 (migrations, workflows, workers, config) 및 Phase별 요약 문서 링크.
DEPLOYMENT_CHECKLIST — Phase별 첫 배포·첫 실행 전 점검 항목. 검증: QA_CHECKLIST.
prego-saas-control-platform-v4-implementation-plan — 구현 기획서 (태스크, 의존성, 완료 기준).
API_OVERVIEW — Worker·API 엔드포인트·Cron 요약.
OPERATIONS — 운영 Runbook 요약 (Pulumi, Purge, Secrets, 수동 트리거).
Zuplo 게이트웨이 운영 — 브라우저 CORS·Portal ALLOWED_ORIGINS·선택적 x-trace-id: prego-zuplo docs/runbook/README.md (색인) · 폴더 (이 사이트 /runbook/ 과 별개). 테넌트 신뢰 경계.

Phase 요약

Phase	요약 문서
1	phase1-implementation-summary
2	phase2-usage-r2-kv
3	phase3-governance-summary
4	phase4-us-autoscaler-summary
5	phase5-eu-gdpr-summary

통합 기획 (Consolidated)

tenant-provisioning-e2e-rollout — Zuplo·CP·GitHub·Hetzner/Ansible/Zuplo E2E 점검표; 스테이징 퍼널 디버그(NEXT_PUBLIC_PREGO_ONBOARDING_DEBUG) 및 export-funnel-events.sh.
otp-and-email-consolidated — OTP·이메일 플로우·템플릿·Resend·대시보드. 구현 상태 표 있음.
otp-verify-consolidated — OTP 검증·CORS·passcode 플로우. 구현 상태 표 있음.
build-troubleshooting — prego-docker 빌드 실패(exit 128/167, yarn, uv resolver). 한국어 적용 체크 표 있음.

구현 상태 추적이 있는 기획서

my-ai-cloudflare-flow-and-access-plan — §8.3 Phase 8 MCP, §8.4 Phase 9 Agent, §8.6 요약; §8.7 백로그(Phase 8: get_payslip·get_attendance 백엔드 정의 후 연동; OTP/이메일 적용됨).
my-ai-chat-ui-changes-plan — placeholder·입력창 레이아웃(엔진 드롭다운)·히스토리/삭제; 문서 말단 구현 상태 및 §5.6 백엔드 점검 결과.
ansible-frappe-bench-rc127-resolution-plan — §16 체크리스트(workspace 마운트, 이미지 bench, sites 전용 volume, Provisioner Job; 4번 미적용·비고 참고).
otp-and-email-consolidated, otp-verify-consolidated — 상태 표 적용됨(Resend, OTP 본문·입력, CORS, 대시보드 green/red, B6 KV).
build-troubleshooting — 적용 체크 표: Exit 128, yarn §4 적용; uv §5 확인됨.
m-pregoi-admin-web-ux-implementation — m.pregoi.com(admin-web) OTP 분리 페이지·레이아웃·쿠키·Company Profile 모바일. 구현: apps/admin-web, prego-zuplo OTP 이메일 영문.

m.pregoi.com 상세 기획 A–D

Plan A — Stripe·Pay 버튼 — CP URL, 실패 UX, 테스트 매트릭스.
Plan B — 로그인·구매·메일 퍼널 관측 — funnel_events, 내부 API, 어드민 UI.
Plan C — logpath 전 구간 — trace_id, Stripe metadata, x-trace-id.
Plan D — Activate·readiness·포털·메일 — 검증 게이트, job API, 레포 순서.

API Control Plane

Bird SMS replaces Twilio — 인증·Stripe API 키 — 아카이브: SMS 경로 제거됨; Stripe·웹훅은 참고.
Remove phone SMS OTP — 이메일만 수동 승인 — Twilio/Bird SMS OTP 삭제, 이메일 인증만. 반영 완료 (CP, Zuplo, www; 런북 갱신).
api-control-plane-implementation-plan — Control Plane 5단계·Contract·Queues·Observability·보안·Runbook·백업·Phase A–D. 구현: prego-control-plane (별도 레포) — IMPLEMENTATION_INDEX prego-control-plane 항목.
onboarding-provisioning-logpath-admin-console-plan — Free/Paid → D1 → placement → Docker Hub·Ansible → Zuplo·Cloudflare → provision-complete 흐름, logpath, 통합 internal 관리 콘솔 기획.

www /trial

trial-page-gate-error-footer-input-plan — pregoi.com/trial 노란 배너·푸터 노출·입력 불가(게이트·레이아웃) 원인 점검·검증 체크리스트. 기획만.
trial-page-free-email-zuplo-layout-plan — 무료메일 2단계(npm free-email-domains-list)·dictionary 유지, Email verification isn't available… 원인·대응, 첫 뷰포트 푸터 비노출 레이아웃. 기획만.

Cloudflare Pages (모노레포)

cloudflare-pages-build-watch-paths-monorepo-plan — 동일 저장소 다중 Pages 프로젝트의 Build watch paths·include/exclude 경로 표·lockfile·스킵 예외·검증 시나리오. 기획만.

기타

resource-optimization-safe-adoption-plan — 리소스 절감(Redis·Gunicorn·CDN·Docker 제한) 적용 순서·선행 조건. 요약: resource-optimization-quick-reference.
saas-unified-architecture-hetzner-cloudflare-zuplo-plan — 통합 아키텍처·폴더 구조.
tenant-provisioning-flow — 가입·결제 → 큐 → GitHub Actions/Worker, Pulumi→Ansible→Zuplo→Cloudflare 단계.
tenant-subdomain-dns-design — 테넌트 DNS 채택 방식 C: 내부 canonical tenant-{short_id}.pregoi.com + 사용자 CNAME.
pregoi-infrastructure-r2-api-update-plan — R2·API 업데이트 기획.
prego-pulumi-removal-plan / pulumi-ansible-step1-step2-plan — Pulumi 이전·GitHub 기반 실행 기획.
prego-phase-2-corporate-ai-platform-roadmap — Phase 2 Corporate AI 플랫폼 로드맵(목표·비목표·경계·리스크), 멀티 ERP·Zuplo·MCP·외부 AI 엔진, Mermaid 컨셉 도식. 영어 상단·한국어 하단.