Editing Adaptive Contribution Units (ACUs)

= Adaptive Contribution Units (ACUs) =

**Adaptive Contribution Units (ACUs)** are an extension of the Contribution Unit (CU) structure within the Rebel Earthling License (RE License). ACUs are designed specifically for making adaptations or updates to existing contributions within a project. With ACUs, contributors can add or modify content independently without overwriting prior contributions, preserving each version’s integrity within a layered, traceable structure.

== Purpose of Adaptive Contribution Units ==

ACUs enhance the RE License by allowing each modification to be:
* '''Independent and Traceable''': Each adaptation is logged as a distinct unit, making it possible to trace changes over time.
* '''Modular and Non-Destructive''': ACUs allow for modifications without altering the original CU, so each adaptation adds value while preserving the original content.
* '''Compatible Across Media''': ACUs apply to various media, from code and text to music and visual art, allowing modular updates in any RE-licensed project.

== Key Elements of an Adaptive Contribution Unit ==

Each ACU is structured similarly to a CU but includes specific fields that track modifications and link back to the original CU. The primary elements of an ACU include:

=== 1. Modification Record ===
The core purpose of an ACU is to record any adaptation made to an existing CU. Each ACU’s metadata includes:
* '''Original CU Reference''': A link to the CU that the ACU is adapting, creating a clear lineage for each modification.
* '''Modification Description''': A summary of what was changed, added, or improved, such as “remixed audio,” “translated text,” or “updated code dependencies.”
* '''Adaptation Tags''': Specific tags noting the type of adaptation (e.g., “audio remix,” “visual enhancement”), helping categorize and organize ACUs within the project.

=== 2. Independent Contributor Signature ===
Like CUs, each ACU is signed independently by the contributor using their preferred identifier (name, pseudonym, digital wallet, etc.), allowing contributors to:
* Retain credit for their specific adaptations.
* Authenticate their contributions as distinct from the original work.
* Maintain a unique identity across multiple ACUs and other layers in the project.

=== 3. Timestamps and Version Tracking ===
ACUs record the date and time of each modification, preserving the project’s full development timeline. Each version is either:
* Sequentially numbered for non-blockchain files, or
* Given a unique cryptographic hash if stored on the blockchain, allowing for transparent, traceable versioning of each adaptation.

=== 4. Linkages and Contribution Chains ===
ACUs are designed to link directly to the CUs they adapt, forming a **Contribution Chain** that maintains a clear relationship between original content and all modifications. This allows contributors and users to:
* Follow a logical progression of changes, from the original CU to each ACU.
* Understand how each adaptation contributes to the overall project.
* Access both the original CU and any ACUs for a complete view of a particular element’s evolution.

=== 5. Layered Metadata and Aggregate Summary ===
ACUs contribute to the project’s **Aggregate Metadata Layer**, which compiles information from all CUs and ACUs into a comprehensive summary. This metadata layer provides:
* '''Contributors’ Manifest''': Listing all contributors and their roles across both CUs and ACUs.
* '''Adaptation Overview''': A brief summary of each ACU and its changes, allowing users to see modifications at a glance.
* '''Guidance for Use and Adaptation''': Notes on permissions, ethical considerations, and intended uses for each ACU and CU, ensuring responsible and aligned use within the project’s ethical framework.

== Practical Workflow for Using Adaptive Contribution Units ==

ACUs are designed for flexibility, making it easy for contributors to adapt content within an RE-licensed project. Here’s how the workflow typically looks:

1. **Identify Original CU for Adaptation**: The contributor selects a CU within the project that they want to adapt or enhance.
2. **Create an ACU with Metadata**: The contributor establishes a new ACU, linking it to the original CU and adding metadata, including their signature, timestamps, and a description of the modification.
3. **Linking and Contribution Chain Update**: The ACU is linked to the CU it adapts, forming part of the Contribution Chain. The Contribution Chain now reflects both the original CU and the new ACU.
4. **Version Tracking and File Update**: If stored on the blockchain, the ACU is assigned a unique hash, which preserves its integrity and position in the chain. Each ACU update adds to the project’s version history.
5. **Aggregate Metadata and Project View**: The ACU contributes to the project’s Aggregate Metadata Layer, allowing users to view the full set of CUs and ACUs in one place for a clear project overview.

== Benefits of Adaptive Contribution Units ==

ACUs provide key advantages for projects under the RE License, including:

* '''Non-Destructive Adaptation''': ACUs enable modifications without altering or removing original content, supporting a cumulative approach to project development.
* '''Full Traceability''': Each ACU retains its own metadata and is connected to its source CU, allowing users to understand the complete lineage of each adaptation.
* '''Enhanced Collaboration''': ACUs allow multiple contributors to build on one another’s work without interference, encouraging a layered, collaborative evolution of the project.

== Example Use Cases ==

ACUs support adaptable, modular development across various media and projects:

* '''Music Production''': A music project might start with an instrumental CU, to which contributors can add ACUs for vocal tracks, remixes, or new instrumentation.
* '''Coding Projects''': In a software project, an original function or module can be adapted through ACUs, tracking updates like optimization, bug fixes, or localization.
* '''Textual Adaptations''': For written content, an original CU can include ACUs that add translations, expansions, or annotations, making the content accessible to a broader audience.

== Explore Further ==

To learn more about how ACUs integrate with Contribution Units in layered, modular projects, visit the [[Contribution Units (CUs)]] page. For an overarching view of the RE License and its features, see the [[Creating RE License Development Overview]] page.