Roblox Creator Passport

Inspiration

Roblox creators make 3D assets, clothing, environments, and scripts that can be copied, remixed, scraped, or sent to AI tools without a reliable way to communicate whether that use is allowed. The asset travels between tools, but the creator’s intent often stays in a private message or platform-specific setting. The missing moment is the check between “the tool found the asset” and “the tool is allowed to use it.”

What we built

Roblox Creator Passport is a creator-controlled consent, licensing, attribution, and provenance layer for Roblox assets. Each published asset carries a public, versioned JSON-LD manifest with the creator’s declared boundaries for AI training, remix, attribution, commercial use, purpose, expiry, and revocation. Private drafts, hidden notes, face scans, documents, and raw biometrics never travel with the passport.

The primary user is a Roblox creator or small studio. The requesting system can be a Roblox Studio plugin, catalog workflow, or AI agent that needs to check whether it may train on, remix, commercialize, or reference a published asset.

How the AI Passport moment works

1. A Studio-style requester reads a public JSON-LD manifest.
2. It presents the exact asset, requesting system, purpose, scope, and expiry.
3. The creator approves, denies, edits the policy, or revokes a grant.
4. Approval creates a time-bound grant and a chained SHA-256 receipt.
5. A later check sees the current manifest version and revocation state instead of silently trusting an old copy.

The Build Lane prototype makes this normally invisible decision visible through trust-state cards, a plain-language setup guide, an animated requesting-agent moment, a public passport ticket, and an accessible guide surface. Color is never the only signal.

What travels and what stays private

The portable claim includes the asset identifier, public creator handle, JSON-LD policy fields, manifest version or hash, training/remix/attribution/commercial boundaries, expiry, revocation pointer, and receipt reference. Private drafts, source files not explicitly published, private negotiations, family information, face scans, documents, and raw biometrics remain outside the response.

Why the prototype is honest

A portable passport cannot force an unrelated tool to comply by itself. A production Studio or catalog adapter must enforce the returned decision before passing an asset to a model or remix pipeline. Consent withdrawal cannot retroactively erase a downstream copy, so the first version uses short-lived grants, re-checks at action time, revocation pointers, and inspectable receipts. Guardian or parent approval is intentionally out of scope for this Creative Track asset-consent claim; RoPass is a separate future Identity Track concept.

Built with

React 19, TypeScript, Tailwind CSS, Express, tRPC, Drizzle ORM, MySQL, JSON-LD, SHA-256 receipt chaining, Vitest, and a simulated Roblox Studio/MCP-style request bridge.

What we learned

The engineering challenge was not only storing a permission field. It was making creator intent portable, readable to a requesting system, changeable over time, and understandable to a human at the moment of approval. The MVP is production-shaped, but it does not claim Roblox adoption or automatic legal authorship adjudication.

The next step is a small Studio SDK and webhook adapter that fetches a manifest, submits the bounded request, receives the grant or refusal, and re-checks revocation before an asset reaches an AI or remix pipeline.

Built With

• react
• typescript