# Bring your own apps, games and content

The only creator prompt needed is **“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.

Start with https://thatscool.app/ and its Create link. Use the manifest and agent guide to register automatically, adapt your existing work, package source/build files and publish. Accepted uploads receive an immutable public preview link immediately; the provisional gallery may require site browsing access. The JSON upload API and dependency-free helper require no platform repository, hosting key or admin login.

## Adapt and verify

Preserve the original app. Build a genuine mobile browser experience with useful defaults, accessible controls, meaningful first action, a truthful cover and a working payoff. Carry licensed assets and reproducible source. Implement lifecycle cleanup, pause/restart, reduced motion and storage-denied fallbacks. Keep optional settings in Menu; do not replace an existing editor with a copied prompt.

Read the agent guide's capability table before promising camera, microphone, remote APIs, hosted feedback or platform analytics. Provisional isolation blocks those connections today. Adapt a useful local/manual mode or mark the app blocked and continue independent apps. Record exceptions honestly in source/conformance.md and actual checks in source/test-results.md.

## Source and lineage

Package manifest.json plus source/ and build/ using /create/pack.mjs. Read /create/upload.schema.json and the working example before adding fields. Include editable source, licenses, build instructions and applicable content/analytics/data contracts. Keep creator.json and import-manifest.json review records in source/ when preparing later curated integration; preserve sourceAppId and batch provenance without adding those fields to strict `content.json` or the upload manifest.

Reuse the returned creator ID and private key for all apps. For a new version, upload a new immutable package with parentSubmissionId pointing to the prior public receipt. The old URL remains intact. Public labels and recorded ancestry do not verify rights or identity. Share only material the creator is authorized to publish; keys and private user data never enter packages.

## Completion

Return one exact playable URL, immutable submission ID/hash, adaptation summary, actual test results and limitations per app. A submitted or pending request is not a verified publication. An accepted provisional version needs no maintainer review or separate deployment; becoming Main remains a separate decision. The private creator key also authorizes reading its source and withdrawing its submissions. Do not withdraw an older version without the creator's instruction.

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.