Contribution Units (CUs)

Contribution Units (CUs) are the core modular components of the Rebel Earthling License (RE License), allowing every piece of a project to be independently attributed, modified, and traced back to its contributor. CUs enable collaborative development while preserving the unique contributions of each individual within a project, whether it involves text, audio, code, or visual elements.

Purpose of Contribution Units

Contribution Units are essential for:

Independent Attribution: Each CU is individually signed, giving clear credit to contributors and preserving their work within the broader project.
Modular Development: CUs allow projects to grow and evolve layer by layer, with each contribution acting as an independent building block.
Traceable History: CUs provide a fully traceable record of all modifications and contributions, allowing users to follow a clear lineage back to the original project.

CUs are structured to retain metadata, making it easy to see who contributed what, when, and how it fits into the project as a whole.

Key Elements of a Contribution Unit

Every CU within a project has a standard set of metadata fields, ensuring consistency across RE-licensed projects. The primary elements include:

1. Contributor Signature

Each CU is independently signed by the contributor using their preferred identifier, which could be a name, pseudonym, digital wallet, or another form of ID. This signature:

Authenticates the contribution within the CU.
Allows the contributor to retain credit and recognition for their work as the project evolves.
Supports a range of signature types for flexibility, accommodating contributors across different fields.

2. Role and Contribution Type

Each CU records the contributor’s specific role and the type of contribution made:

Role: A description of the contributor’s involvement, such as “artist,” “developer,” “mixer,” or “writer.”
Contribution Type: A brief note on what was added, adapted, or created, such as “audio enhancement,” “code optimization,” “layout design,” or “translation.”

3. Timestamps and Version Control

Every CU logs the date and time of the contribution, providing chronological traceability. Each version of a CU is sequentially numbered or, if on the blockchain, assigned a unique cryptographic hash. This ensures:

A fully traceable timeline of contributions.
Clear differentiation between original contributions and modifications.
Compatibility with blockchain and non-blockchain storage.

4. Linkages to Related CUs

CUs can link to other related CUs, creating a Contribution Chain that connects complementary pieces within a project. For instance:

A CU containing a guitar track may link to another CU for mixing, indicating how the pieces interact.
Visual elements within a multimedia project might link to their design notes or textual descriptions.

Linking related CUs provides an organized, traceable structure, especially useful for projects with layered media or technical dependencies.

5. Licensing and Ethical Tags

Each CU includes tags indicating its specific permissions and ethical considerations:

Licensing Tag: Notes any additional permissions or restrictions attached to the CU (e.g., “non-commercial only” or “open for remix”).
Sustainability and Ethics Tags: Optional fields where contributors can note eco-friendly practices or ethical guidelines specific to their contribution.

These tags help users interact with each CU responsibly, in alignment with the values of the Rebel Earthling License.

Practical Workflow for Using Contribution Units

Contribution Units are designed to be easy to incorporate, modify, and track within any RE-licensed project. Here’s a typical workflow involving CUs:

1. Initial CU Creation: The original creator sets up the first CUs with metadata, role, signature, and any ethical tags. This establishes the foundational elements of the project. 2. Adding and Modifying CUs: Each new contributor adds or modifies CUs, recording their role, signature, and timestamps in the CU metadata. Contributors can add new CUs or use Adaptive Contribution Units (ACUs) to adapt existing content. 3. Linking Related CUs: Contributors link CUs to other relevant units, creating Contribution Chains. This maintains project structure and coherence, showing how different elements connect. 4. Versioning and Updates: Every CU update is versioned, ensuring clear differentiation between original work and modifications. Blockchain-stored CUs will create a unique hash for each update. 5. Final Project Assembly: Once all CUs are in place, the project’s Aggregate Metadata compiles CU information into a single, cohesive view, displaying each contributor’s role and involvement.

Benefits of Contribution Units

Contribution Units enhance RE-licensed projects by making every input modular, transparent, and easy to trace. Key benefits include:

Clear Attribution: CUs enable contributors to retain ownership of their work and receive clear credit for their contributions.
Easy Collaboration: The modular structure allows for smooth, organized collaboration, where each contributor can focus on specific parts without overwriting others.
Traceability and Integrity: CUs provide a full record of contributions, allowing users to understand the lineage of the project from the original work through each derivative or modification.

Adaptive Contribution Units (ACUs)

In addition to standard CUs, RE L-to-RE L projects can include Adaptive Contribution Units (ACUs), which are designed for modifications or updates to existing content within a layer. ACUs provide:

A flexible way to adapt prior contributions without altering original metadata.
Independent logging of changes, so that each adjustment remains traceable.
Integration into Contribution Chains, maintaining connectivity across all related CUs.

Explore Further

Contribution Units are just one element of the Rebel Earthling License’s modular, community-centered structure. To understand more about how CUs work within layered projects, see the RE L-to-RE L page. For a full overview of the license, visit the Creating RE License Development Overview page.