ADR-0012 — Diamond Cloud holding workspace
Relocate Frawl while preserving its repository, runtime boundaries and development context.
ADR-0012 — Diamond Cloud holding workspace
Status: Accepted through the owner's migration mission, 2026-09-23.
Context
Frawl is the independent affiliate platform defined in ADR-0011. Diamond Cloud AI
(diamondcloudai.com) is its parent holding ecosystem. Specialized operational projects live under
/Users/fares-wdeftksa/diamond/projects/, while core holding services belong to platform/.
Existing editor sessions, tools and local servers reference the previous development path.
Decision
Move the complete Frawl directory from /Users/fares-wdeftksa/development/frawla.io to
/Users/fares-wdeftksa/diamond/projects/frawl. Immediately install a symbolic link at the old path
pointing to the new path. New development uses the canonical location; existing references remain valid.
Preserve the .git directory, all branches and history, architectural records, task and handoff files,
fixtures, custom scripts, localization resources and ignored local configuration. Use the private root
workspace name @diamond/frawl; keep the existing application package names and imports.
Register Frawl in the holding's master README. The Git remote stays alswat1222/frawl; this move is
not a repository transfer or reconnection to the source template. Master holding documentation is
outside this repository and is not currently version-controlled by a holding Git root.
Runtime and product boundaries
The existing Next.js/Node, PostgreSQL, Better Auth and Cloudflare Workers architecture remains in effect. English remains the default product locale, with Arabic and full RTL support. Product design tokens, deployment regions, databases and billing credentials do not change with a directory relocation.
Edge Gateway, Shared Storage, Sovereign Identity, ZATCA and Dammam Compute are potential holding integration surfaces. They are not implemented or enabled by this organizational migration. Any later integration must retain tenant isolation and distinguish Frawl subscriptions, merchant sales and affiliate payout records. Its architecture and rollout require a separate explicit decision.
Verification and consequences
- The directory moves within one filesystem, preserving its inode and file permissions.
- Compare file digests and Git references across the move without displaying local secrets.
- Run installation, formatting, lint, type checking and the complete unit/integration suite from the new path.
- Verify the compatibility path and existing applications, including hydrated browser navigation.
- Keep the compatibility symlink for existing IDE/tool references; do not remove it during cleanup.
- This is neither a production deployment nor evidence that external launch gates have passed.
Commercial impact
Expected direct recurring revenue change from this directory migration: SAR 0/month, high confidence. Channel: Frawl subscriptions, whose prices and behavior are unchanged. Any benefit from holding-wide distribution or shared services is unquantified and requires a separate commercial assessment.