Current Stage 3 Scope

Scoped acceptance, not full launch acceptance.

Current Stage 3 validates the accepted active path after the Theme/Plugin boundary reset. This page is a public skeleton explanation, not a PRD replacement or full launch checklist.

Completed in current Stage 3

  • S3-1 shared shell and design baseline.
  • S3-2 Merchant Portal productization.
  • S3-3 Ops Console productization.
  • S3-6 Domain Workflow + Minimal Audit.

Active late path

  • S3-7A Content Skeleton.
  • S3-7B Retained Cleanup.
  • S3-7C Acceptance / Dry-run.

Deferred dedicated modules

  • S3-4 Theme implementation is deferred by owner decision. Theme work resumes as a dedicated Theme Module.
  • S3-5 Plugin implementation is deferred by owner decision. Plugin work resumes as a dedicated Plugin Module.
  • Merchant-facing theme and plugin operations remain in Runtime Admin.
  • Future CP scope is platform-admin registry and governance.
  • Real/sandbox payment gateway integration is deferred.
  • Content Fill / Marketing Copy is deferred beyond this skeleton.
  • Theme Uplift / First Launch Theme is deferred or folded into the future Theme Module.

Content boundary

S3-7A does not integrate a CMS. A future Content CMS module may evaluate mature CMS or landing sources from the source pool, including Wowy/Botble, Infinia, Quland, Landrick, Bione, Apexa, Gerow, Gratech, or similar candidates. No CMS source is integrated or ported in S3-7A.

Open Help Back Home