# PIXIE / 50 Ways Ecosystem Continuity

## Principle

> **The system should make extraction harder and attribution easier.**

This is the continuity principle connecting the 50 Ways / PIXIE work across creative production, music, licensing, collaboration, education, accessibility, platforms, and technical architecture.

The goal is not to prohibit reuse or collaboration. The goal is to make provenance, contribution, authority, compensation, consent, and exit difficult to erase as work moves downstream.

## The two flows

### Value flow

```text
PERSON
  ↓
CREATION
  ↓
COLLABORATION
  ↓
TRANSFORMATION
  ↓
DISTRIBUTION
  ↓
AUDIENCE
  ↓
ECONOMIC / CULTURAL VALUE
```

### Accountability flow

```text
WHO CREATED IT?
WHO CONTRIBUTED?
WHO AUTHORIZED IT?
WHO OWNS WHAT?
WHO GOT PAID?
WHO GETS CREDIT?
WHO CAN SAY NO?
WHO CAN LEAVE?
WHO CAN CONTINUE?
WHO GETS REMEMBERED?
```

The design objective is to make the second flow first-class rather than leaving it behind when the first flow creates value.

## Continuity across the ecosystem

| Layer | Continuity question |
|---|---|
| Creative work | Does the contribution remain identifiable after transformation? |
| Music | Is the rights record kept separate from the media file? |
| Collaboration | Can contribution, credit, compensation, and exit survive a project change? |
| Licensing | Is the actual use explicit, and is provenance documented? |
| Platforms | Is a public profile treated as discovery evidence rather than ownership proof? |
| Sponsorship | Are inquiry, response, proposed terms, and executed agreement kept distinct? |
| Education | Can participation produce a defined contribution without making labor invisible? |
| Accessibility | Does the system create an accessible path into contribution? |
| Technical art | Does presentation remain downstream of authoritative state? |
| PIXIE | Can attribution and provenance remain visible as the network grows? |

## The architectural analogy

```text
AUTHORITATIVE REALITY
        ↓
PROVENANCE / RIGHTS / CONTRIBUTION
        ↓
CONTRACT / PARTICIPATION
        ↓
TRANSFORMATION
        ↓
PRESENTATION / EXPERIENCE
        ↓
AUDIENCE
```

In the technical-art architecture, state flows down and presentation does not become authoritative game state.

In the rights architecture, provenance and authority should travel with the work rather than being silently discarded when the work is transformed or distributed.

These are analogous design principles, not a claim that the systems are legally or technically identical.

## What this changes

**Reuse:** Reuse is not the enemy. Untraceable extraction is the design problem. Reuse becomes easier to govern when provenance travels with the work.

**Collaboration:** Collaboration becomes safer when contribution survives the project, participation is specific, and an exit does not erase the record.

**Licensing:** Licensing becomes clearer when the requested use is explicit rather than hidden inside a generic permission.

**Attribution:** Attribution becomes easier when the system already records who did what.

**Compensation:** Compensation becomes recordable when roles and deliverables are defined rather than treated as informal goodwill.

**Consent:** Consent becomes meaningful when it is specific to participation and use.

**Exit:** A creator can leave without requiring the system to erase their contribution.

## Operational sequence

```text
EXTRACTION HARDER
        ↓
PROVENANCE VISIBLE
        ↓
ATTRIBUTION PERSISTENT
        ↓
CONTRIBUTION LEGIBLE
        ↓
COMPENSATION RECORDABLE
        ↓
CONSENT SPECIFIC
        ↓
EXIT POSSIBLE
        ↓
NEW PARTICIPATION POSSIBLE
```

## PIXIE

PIXIE is the experimental expression of this principle in the open network.

It should not be understood as a promise that an automated system can determine authorship, ownership, motive, reputation, or legal rights. Those questions remain contextual and, where necessary, human/legal decisions.

The design target is narrower and more practical:

- preserve visible provenance;
- make contribution legible;
- distinguish evidence from authority;
- avoid turning platform presence into ownership claims;
- keep consent and participation explicit;
- preserve an exit path;
- respect accessibility constraints;
- avoid automated behavior that creates unwanted durable social records.

## Stable-build boundary

This document is a design/research record. It is not legal advice, a rights opinion, a license, or a guarantee that any particular asset or relationship is cleared.

The public 50 Ways site has **not been legally cleared**. Rights-dependent use remains subject to applicable agreements, verified provenance, and review by an attorney retained for the project.

> **Nothing downstream should be able to erase the upstream record.**