Skip to main content

Asset Lifecycle

This document explains the full lifecycle of an asset in the Open UGC & Beyond ecosystem, from creation to reuse, composition, and long-term persistence.

The lifecycle is intentionally simple: assets are created once, reused freely, and optionally composed into higher-order value without ever losing their identity.

Lifecycle Principles​

Every stage of the asset lifecycle follows a few core rules:

  • Assets have a single canonical identity
  • Ownership is explicit and enforced
  • Reuse does not require permission
  • Monetization is optional and opt-in
  • Assets outlive applications and markets

The lifecycle is designed to compound value, not trap it.

Lifecycle diagram showing definition, registration, reuse, updates, packaging, consumption, and discovery.
Figure 1: End-to-end asset lifecycle from creation to market discovery.

Stage 1: Asset Definition (Off-Chain)​

What Happens​

An asset begins as a conceptual definition created by a human or system.

Examples:

  • A game level
  • A character model
  • An item definition
  • A simulation component
  • A dataset or configuration

At this stage:

  • The creator defines content
  • Metadata is authored
  • Files may be generated or assembled
  • Nothing is yet registered on-chain

This stage is unrestricted and permissionless.

Stage 2: Asset Registration (On-Chain via OGAL)​

What Happens​

The creator explicitly registers the asset with OGAL.

OGAL assigns:

  • Canonical asset ID
  • Owner authority
  • Mutability and update rules
  • Provenance reference (metadata URI + hash)

Key Properties​

  • Registration requires explicit intent
  • Ownership is enforced by protocol state
  • Mutability is gated by authority
  • No monetization is applied

Once registered, the asset becomes:

  • Portable
  • Verifiable
  • Reusable everywhere

OGAL does not care where the asset is used.

Stage 3: Free Reuse (Default State)​

What Happens​

Any developer or platform may reuse the asset.

Typical flow:

  1. Asset state is read from OGAL
  2. Ownership and permissions are verified
  3. Metadata is resolved
  4. Asset is reconstructed at runtime

Key Properties​

  • No fees
  • No royalties
  • No approvals
  • No platform lock-in

Free reuse is not a limitation. It is the default posture of the system.

This stage maximizes:

  • Distribution
  • Visibility
  • Adoption
  • Network effects

Stage 4: Optional Updates & Versioning​

What Happens​

If the asset is mutable, the owner may:

  • Update metadata
  • Improve content
  • Fix issues
  • Publish new versions

Key Properties​

  • Only the owner can update
  • Update rules are enforced by OGAL
  • Previous versions remain verifiable
  • Consumers choose what to adopt

Ownership controls evolution. Not platforms. Not markets.

Stage 5: Composition into OPP Packages (Optional)​

What Happens​

A developer or curator may package assets into an OPP bundle.

This may include:

  • Multiple OGAL assets
  • Code and logic
  • Metadata
  • Media files
  • Runtime instructions

An SBOM is generated that declares:

  • Included assets
  • Ownership of each asset
  • Usage semantics
  • Value intent (if monetized)

Key Properties​

  • Packaging is explicit
  • Monetization intent is explicit
  • Base assets remain reusable outside the package
  • OGAL ownership is unchanged

Packaging creates new value without destroying base value.

Stage 6: Application-Level Consumption​

What Happens​

Applications consume:

  • Individual OGAL assets
  • OPP packages
  • Or both

Applications decide:

  • How assets are used
  • How users interact
  • Whether monetization applies
  • How value is enforced

Key Properties​

  • Applications remain sovereign
  • No protocol mandates UX
  • No forced business model
  • No centralized gatekeeper

Applications consume infrastructure. They do not define it.

Stage 7: Market & Discovery (Optional)​

What Happens​

Assets and packages may be:

  • Indexed
  • Displayed
  • Traded
  • Discovered

Ownership transfers update OGAL directly.

Key Properties​

  • Markets are optional
  • Markets are replaceable
  • Discovery does not affect truth
  • Ownership always resolves to OGAL

Markets compete on UX, not authority.

Stage 8: Long-Term Persistence​

What Happens Over Time​

  • Assets continue to exist independent of platforms
  • Ownership history remains auditable
  • Reuse may increase or decline
  • Value may compound through composition

Assets are not deprecated by shutdowns. They are not orphaned by platform failure.

Lifecycle Guarantees​

This lifecycle ensures:

  • Assets never lose identity
  • Ownership never becomes ambiguous
  • Reuse is always possible
  • Monetization never becomes mandatory
  • Evolution is controlled by owners

What the Lifecycle Avoids​

  • Platform capture
  • Forced exclusivity
  • Silent ownership changes
  • Hidden monetization
  • Fragile dependencies

One-Sentence Summary​

Assets are created once, registered under OGAL, reused freely by default, optionally composed via OPP, and persist independently of platforms, markets, or applications.

Where to Go Next​