Skip to content

ERP / Frappe domain

Scope

  • Repository: prego_saas (Frappe app on ERPNext).
  • Owns: DocTypes, validations, workflows, server-side ERP business logic.
  • Does not own: Zuplo policies, Cloudflare Worker AI pipelines, or control-plane orchestration internals.

Integration

  • Expose whitelisted HTTP APIs consumed by prego-zuplo (forward/proxy) or by Workers through the gateway.
  • Treat the gateway as the trust boundary for browser clients; Frappe sessions and API keys remain Frappe concerns.

Platform rule

From the Master plan: Frappe is an external adapter. The reusable platform standardizes tenant mapping (site / hostname ↔ tenant_id), not arbitrary DocType layouts.

  • Existing planning: search Planning for prego_saas, Frappe, ERP.
  • Repo responsibility matrix
  • App repo: root README.md and docs/README.md in prego_saas (bench install, contributing) — mirror the platform hub link there when cloning the Frappe app.

한국어

도메인 계층은 prego_saas(Frappe) 에만 두고, 게이트웨이·워커의 제품 로직과 섞지 않습니다. 플랫폼은 테넌트 매핑 수준만 알고 DocType 내부는 캡슐화합니다.

Help