Choose the job first. Each choice opens its own clean page so the main screen stays simple.
Use this once for a new project packet or an existing project intake packet. After this, use File Project Update for normal updates.
Use this after a project has already been onboarded. It saves version notes, updates the changelog, and stores the build/source files. No release-note file is created.
Use this to save the actual app file too. ZIP files go to builds/. HTML files go to source_files/current/.
Choose a M.A.D.S. app zip. The app reads it, fills the update fields, and creates a simple filing plan for review.
For loose files — screenshots, prompts, templates, samples, source files, or a single build zip. This is not the one-time onboarding flow.
Use this for a markdown handoff from a long chat. M.A.D.S. will read it, show what it found, then save it to the project’s context_handoffs/ folder and update shared project context after you confirm.
Talk to Elden Mug, the M.A.D.S. control assistant. Mug gets app rules, workspace structure, Drive project metadata, and current settings with each question.