# Collaboration memo starter

> A plain-language discussion starter for a Vibehub project. This is not legal advice and is not a substitute for advice from a qualified lawyer, especially where money, equity, confidential information, employment, patents, or regulated work are involved.

## 1. Project

- Project name:
- Canonical Vibehub idea URL:
- Canonical Vibehub project URL:
- Repository URL:
- Effective date:

## 2. People and roles

- Idea source:
- Project steward(s):
- Builder(s):
- Other contributors:

Each person can leave the collaboration. Leaving does not erase accurate attribution for work already completed.

## 3. Attribution

The original idea source remains linked from the project. Material design, implementation, review, documentation, and launch contributions should be recorded with evidence through the Vibehub project when practical. Attribution is a factual credit record, not equity, royalties, wages, inventorship, or ownership by itself.

Add any exact public credit language here:


## 4. Code and other materials

- Repository code license:
- Ownership of newly written code (if different from the default rights of its author):
- License for designs, documentation, data, or other non-code materials:
- Third-party material that must keep its original license or notice:

If this section is left blank, public visibility alone does not grant permission to copy or reuse code.

## 5. Publicity and confidentiality

The project is public by default. Do not contribute trade secrets, confidential employer/client information, personal data you cannot share, or patent-sensitive details.

List any information that must stay confidential and who may access it:


## 6. Money, equity, and expenses

Unless written below, nobody is promised payment, equity, royalties, revenue share, reimbursement, employment, or future work.

Record any agreed terms, payment triggers, amounts, ownership percentages, vesting, expenses, and tax responsibility here. Obtain legal advice before relying on this section:


## 7. Decisions and release authority

- Who decides scope and roadmap changes:
- Who may merge code:
- Who may publish releases or connect production services:
- Who may approve public contribution records:
- How disagreements are resolved:

## 8. Ending or changing the collaboration

- How a participant gives notice:
- What happens to repository and service access:
- What licenses survive:
- What happens to unfinished work and expenses:
- How this memo can be amended:

## 9. Signatures

By signing, each participant confirms that this memo reflects their current understanding and that they have authority to agree to it.

- Name / signature / date:
- Name / signature / date:
- Name / signature / date: