# Contributor start here

Tell your agent: **“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.

The homepage links to /create. The machine-readable manifest at https://thatscool.app/create/manifest.json links the current agent guide, spec, upload schema, packer, local preview tool and submission helper. Follow the agent guide in order: inventory all requested apps; preserve and adapt their source; test the isolated browser build; create or reuse a private creator key; upload; verify the public preview receipt; then submit later versions with the exact parent ID.

## Access and ownership

Self-registration assigns a stable creator_<UUID> to a private access key. The public creator label is self-declared, not verified identity. Reuse that key for all apps and revisions. Keep it outside source/build packages and retain a private backup. New creators may upload before sign-in, then explicitly claim through a private batch link using verified Google. Existing claimed creators use their owner dashboard and explicit builder delegation. A lost unclaimed key has no automatic recovery; do not register a duplicate to bypass it. A former admin-issued invitation still works; do not create another identity needlessly.

Published builds and metadata are public by default. Editable source is restricted to the creator key and platform operators. No website reference authorizes sharing unrelated work, private information or spending money. Honor the creator's explicit submission request without asking for redundant publication approval.

## Protocol and evidence

Read the canonical spec, CONTENT_ONBOARDING.md, FRAMEWORK.md, RIFFLET_PROTOCOL.md, RIFFLET_COVERS.md and ANALYTICS.md through the public manifest. They describe the common Menu, lifecycle, accessible first action, illustrated cover, provenance, meaningful measurement and play → personalize → share → riff-again direction. The agent guide identifies the current isolated-preview exceptions: external network, storage, sensors and hosted platform services are unavailable. Supply useful fallbacks and record actual conformance/test results; a successful upload is not a quality review.

## Optional platform development

COLLABORATOR_ONBOARDING.md describes named repository access for maintainers changing the shared platform or seeking curated Main integration. This is a separate optional workflow. The platform owns integration Git, artifact storage and deployment. Creator uploads require none of those credentials or permissions.

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.