Bring your existing apps to cool*
Tell your agent: Go to https://thatscool.app and follow its instructions to submit our apps. The agent follows /create/agent.md, prepares and uploads your apps first, and returns a private personalized claim link plus public preview/share links. You see the apps before Google sign-in; claim them explicitly when you want to manage them and see private analytics.
An owner email is optional: the agent asks once or uses a high-confidence address, and continues without one if unavailable. If supplied, the platform automatically attempts the provisional welcome; no email request step is needed. The email never establishes ownership. Self-approval is available only to the verified owning creator while the temporary test flag is enabled.
Social/profile porting: /create/docs/docs/onboarding/SOCIAL_PORTING.md. Favorites are private saves; creator social-count totals are not available. Preserve app state, original families, attribution, and exact parent revisions.
Rajeev: submit all your apps through cool*
The scope remains all of Rajeev's apps, starting with a useful pilot and continuing the remaining inventory. The prompt is simply “Go to https://thatscool.app and follow its instructions to submit our apps.”
Canonical Rifflet Spec 2.15.0 remains the adaptation target. The authoritative provisional transport guide is [Submit our apps to cool*](AGENT_SUBMISSION.md), publicly available at https://thatscool.app/create/agent.md . An accepted upload is immediately public and provisional; it does not promote content to Main or certify full RCF conformance. No Git, PR, invitation or maintainer handoff is required for this route.
Work through the entire inventory
Inventory existing apps, source and licenses. A demo URL shows behavior; it does not establish source rights or authorize copying users' data. Preserve the working originals. Use the public agent guide to choose one self-contained pilot, implement and validate its adaptation, then apply the pattern to every remaining independent app. Keep unsupported server/sensor requirements explicit; never substitute a screenshot for a working experience.
Use submit.mjs batch --name "Creator name" with the plan, private credentials and private receipt paths, plus --publish-provisional; add --email only when an owner address is available. The helper preflights locally, registers without Google sign-in, uploads, and returns privateClaimUrl. Give that link privately to the owner. Existing creators reuse their existing key without --name; after claim, future edits require explicit builder delegation. The platform assigns creator_<UUID>; the public label remains unverified. GitHub collaboration is optional and is not required for submission.
Per-app ledger
Record creatorId, optional batch_<UUID>, sourceAppId, title/slug, source path/ref or checksum, stack/build command, license status, capabilities, conformance exceptions, actual tests, package path/hash, submission ID, parent ID and verified public preview URL. Keep creator.json and import-manifest.json review records in source/ for optional later Main integration. Do not add batch/creator review fields to strict content.json or the strict upload manifest.
Acceptance evidence
- Source and build: editable source, browser entry, relative modules/assets, lockfiles, reproducible build instructions and file inventory.
- Assets and licenses: accurate attribution, licensed code/art/media and the creator's authority to submit.
- Permissions and services: declare requirements; test useful fallbacks for the provisional sandbox's blocked sensors, persistence, external network and platform services.
- Metadata and contracts: truthful description, audience, cover, RCF target and explicit exceptions; honest first-action, milestone and completion semantics.
- Evidence: real first-action/playback checks, narrow/desktop layout, keyboard/reduced-motion/cleanup checks, exact test coverage and a public receipt verified after upload.
All technically accepted packages are published provisionally by default. No automatic Main-feed publishing proxy is used: Main remains a separate curated promotion. There is no human review gate for provisional uploads. Update content by submitting a new package with parentSubmissionId and keep both exact receipts. Finish with links for the full inventory and concrete blockers for anything that could not be made useful under the current hosting profile.
Submission lifecycle: follow the RCF 2.7.0 revision/approval protocol in [the canonical spec](CANONICAL_RIFFLET_SPEC.md). Use the same creator key and slug plus submissionKind: "revision", exact parentSubmissionId, and revisionNotes for an update; use remix for a separate family. Return previewUrl and adminApprovalUrl from the receipt. An authenticated admin approves an exact version for feed/library placement; later uploads stay pending. Approval preserves the sandbox and does not enable hosted analytics or restricted capabilities.