Posts, code, and agreements are separate.

The default Vibehub public-post permission lets Vibehub display, quote, index, and link the submitted post, and lets linked builders reference it. The poster retains rights in their original written expression and uploaded assets. The permission does not create exclusive rights in the underlying idea.

A poster may instead apply CC BY 4.0 or CC0 1.0 to the post text. These choices concern the post’s expression—not software later written by a builder.

The repository’s license governs reuse of implementation code. If no license is detected or selected, default copyright rules apply; public visibility alone does not grant permission to copy, modify, or redistribute the code.

Casual public builds use the community default: public communication, visible contribution evidence, repository-license control of code, and freedom to leave. Compensation, equity, confidentiality, invention assignment, or revenue sharing require a separate agreement signed outside Vibehub.

If a project needs an explicit agreement, write down the people and roles, exact attribution language, code and asset rights, confidentiality, money or equity, decision authority, and what happens when someone leaves. Vibehub provides a plain-language memo starter so collaborators can surface those choices before signing through their preferred provider.

This starter is educational, not legal advice. Get qualified advice for compensation, equity, confidentiality, employment, patents, or regulated work.

Posting, discussing, following, or starting a build does not by itself create employment, partnership, agency, fiduciary duties, payment obligations, or a joint venture.