Public versus remixable
Source Visibility and Remix Rules
Vibecodr keeps public runtime output, public metadata, remixable source, private source, and trusted setup in separate planes.
Public contract for Vibecodr source visibility and remix-safe source projection.
Implementation focus
Use this before changing visibility, preparing a remixable project, or explaining what another creator can copy from a public app.
Expected outcomes
- Explain why public runtime does not automatically expose public source.
- Prepare source for safe remixing.
- Keep secrets and owner-only setup out of remixable material.
- Understand when built output cannot reconstruct missing source.
Public runtime is not public source
A published vibe is runnable by viewers, but that does not mean every source file is readable by every viewer. Vibecodr separates public runtime output, public metadata, remixable source, private source, owner-only setup, secrets, logs, and provider credentials.
This separation lets Vibecodr stay social and remixable without turning a live app into a private-data leak. Viewers can open the public runtime. Remixers can use source only when visibility and policy allow it.
- Public posts and player routes expose the viewer-facing app and metadata.
- Unlisted work can be reachable by link without becoming a broad discovery target.
- Private source stays owner-controlled unless the owner changes visibility or publishes a remixable surface.
- Sensitive files such as `.env`, raw tokens, and credential-bearing config are not remix material.
Remix uses safe source projection
Remixing should preserve creator intent while filtering material that should not be copied into someone else's project. A good remix source includes the files needed to learn from and modify the app, not private credentials, logs, or platform state.
Built-only output has limits. If a project was imported or built without preserving the source needed for a clean remix, Vibecodr can publish the runtime artifact but cannot invent missing backend source later.
- Prepare projects for remix by keeping source organized and secrets external.
- Use clear descriptions and setup notes when another creator will need context.
- Treat source visibility, runtime visibility, and embed visibility as related but separate choices.
Example and read next
Example: you want people to remix a public app without receiving private setup. Keep secrets out of source, publish clear setup notes, and remember that public runtime does not automatically mean public source.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: Source & Versions
- Read next: Profiles & Social
- Read next: Blueprints
- Read next: Troubleshooting