MOTK Web now creates a complete, creator-owned production workspace in Google Drive

MOTK Web's public beta now creates a complete production workspace inside the signed-in user's own Google Drive. One project name produces a Project Root containing the main MOTK Sheet, a separate ADMIN Sheet, Originals/01shots and Originals/02assets folders, and a Proxies folder. A first-time user no longer needs to copy headers, prepare a blank Sheet, or manually assemble the expected Drive structure.

Ownership stays with the creator. The Google account that performs the create action owns every new Sheet and folder; Cloudflare supplies the Web interface, authentication checks and input validation, but does not become the owner of the production files or keep a competing canonical copy. Access therefore continues to follow Google Drive and Sheets sharing, while MOTK's existing Users and ProjectMembers layers continue to describe workbook access and production roles.

The update is deliberately non-destructive for productions that already exist. If an older MOTK resource still sits loose at the top of My Drive, re-provisioning the same project can adopt it into the Project Root. If a user has already organized a Sheet or folder elsewhere, MOTK preserves that location instead of silently rearranging it. Google Workspace organization policies still apply to the account that creates or shares the project.

This changes onboarding more than it changes the underlying MOTK contract: Google Sheets remains the production-data source of truth, Google Drive remains the media store, and the hosted Web edition continues to coexist with the downloadable ZIP and self-managed Google Apps Script edition. The practical gain is a project that is easier to understand, share, back up and hand to another production team from its first minute.