Origin Structure Market

Origin Structure Market is a protocol-oriented framework for registering AI-era ideas, structures, prompts, schemas, workflows, and conceptual systems as Origin Assets, tracing their derivatives, auditing derivative claims, allocating royalties, and preparing them for marketplace listing.

It is designed as an experimental standard for the AI creator economy, where value should not only accumulate at the final product or platform layer, but also flow back to the structural origin.

---

Core Principle

Value should flow back to the structural origin.

In the AI era, ideas are no longer consumed only as finished content. They are transformed into prompts, workflows, GPT instructions, schemas, agents, articles, applications, business models, and new intellectual systems.

Origin Structure Market provides a machine-readable way to record:

• who created an origin structure
• when it was registered
• what canonical form it had
• how it may be reused
• what derivative assets were created from it
• how derivative claims can be audited
• how revenue can be allocated back to contributors
• how assets can be listed, licensed, discovered, and monetized

This project does not attempt to claim ownership over abstract ideas themselves.

Instead, it records structured origin expressions, their fingerprints, permissions, lineage, audit evidence, allocation paths, and marketplace listing metadata.

---

Problem

Modern AI and platform ecosystems have a broken value loop:

• Original ideas are reused without attribution
• AI-generated derivatives obscure upstream contributors
• Platforms capture most of the value
• Creators lose traceability once their work is transformed
• Conceptual frameworks are difficult to register, compare, audit, reward, and list
• Revenue distribution rarely reaches the structural origin
• Marketplace listings often hide upstream lineage and royalty obligations

In short:

Creation does not reliably lead to traceable compensation.

Origin Structure Market addresses this by treating reusable structures, derivative lineage, audit records, allocation graphs, and marketplace listings as first-class protocol objects.

---

What Is an Origin Asset?

An Origin Asset is a structured registration record for an upstream intellectual structure.

Examples include:

• GPT instructions
• Prompt architecture
• AI workflow schemas
• Trace receipt schemas
• Royalty allocation templates
• Origin audit rubrics
• Article frameworks
• Book frameworks
• Business models
• Conceptual frameworks
• AI structure frameworks

An Origin Asset is not merely raw text. It is a structured record containing:

• title
• creator
• asset type
• description
• canonical hash
• timestamp
• permission policy
• royalty policy
• trace links
• supporting evidence hashes

---

What Is a Derivative Asset?

A Derivative Asset is a downstream asset derived from one or more upstream Origin Assets or Derivative Assets.

It records:

• upstream asset ID
• upstream asset role
• contribution claim
• transformation type
• shared concepts
• shared structure
• evidence hashes
• output metadata
• proposed royalty split
• human review status

This allows a downstream asset to declare:

This asset was created from these upstream structures, through these transformations, with this claimed contribution weight.

---

What Is an Origin Audit Record?

An Origin Audit Record is a structured audit record for evaluating whether a derivative claim is credible.

It records:

• target asset ID
• target asset type
• auditor
• audit method
• audit scope
• compared upstream assets
• structural similarity
• conceptual similarity
• lineage similarity
• workflow similarity
• overall similarity
• contribution scores
• royalty relevance
• audit judgment
• supporting evidence
• human review boundary

This layer does not make AI the final judge. It records structured audit evidence and preserves a human review boundary.

---

What Is a Royalty Allocation Graph?

A Royalty Allocation Graph is a structured record for converting a revenue event, audited lineage, contribution scores, and allocation policy into a proposed distribution of value.

It records:

• revenue event ID
• revenue-generating product or derivative asset
• gross revenue
• net revenue
• revenue source
• allocation basis
• audit record references
• contribution scores
• allocation policy
• recipient allocation entries
• settlement mechanism
• human review status
• trace links and evidence hashes

This layer does not execute payment by itself.

Instead, it provides a machine-readable allocation graph that can be used by:

• off-chain accounting systems
• marketplace logic
• royalty OS layers
• smart contracts
• human reviewers
• future settlement systems

---

What Is a Marketplace Listing?

A Marketplace Listing is a structured record for preparing an Origin Asset, Derivative Asset, final product, royalty bundle, or related structural asset for discovery, licensing, pricing, and monetization.

It records:

• listing ID
• listed asset ID
• listing type
• marketplace-facing summary
• long description
• listing status
• pricing model
• license terms
• royalty requirements
• Royalty Allocation Graph reference
• discovery metadata
• quality signals
• human review status
• trace links

This layer does not create a full marketplace by itself.

Instead, it defines the listing metadata that a marketplace, registry, agent, or external platform can consume.

In short:

v0.5 turns traceable structures into listable market records.

---

Repository Status

Version: v0.5.0-candidate Stage: Experimental protocol Current scope: Origin Asset registration + Derivative Asset registration + Origin Audit Record + Royalty Allocation Graph + Marketplace Listing

The current version implements five core layers:

Origin Asset
    ↓
Derivative Asset
    ↓
Origin Audit Record
    ↓
Royalty Allocation Graph
    ↓
Marketplace Listing

v0.1 established the origin registration layer. v0.2 added the derivative lineage layer. v0.3 added the origin audit layer. v0.4 added the royalty allocation layer. v0.5 adds the marketplace listing layer, allowing assets and their trace, audit, license, pricing, and royalty metadata to be prepared for discovery and monetization.

---

Current Features

• JSON Schema for Origin Asset registration
• YAML example for an Origin Asset record
• JSON Schema for Derivative Asset registration
• YAML example for a Derivative Asset record
• JSON Schema for Origin Audit Record
• YAML example for an Origin Audit Record
• JSON Schema for Royalty Allocation Graph
• YAML example for a Royalty Allocation Graph
• JSON Schema for Marketplace Listing
• YAML example for a Marketplace Listing
• Python validation script
• GitHub Actions workflow for CI validation
• Protocol overview document
• Derivative Asset registration documentation
• Origin Audit Record documentation
• Royalty Allocation Graph documentation
• Marketplace Listing documentation

---

Directory Structure

origin-structure-market/
├── .github/
│   └── workflows/
│       └── validate.yml
├── docs/
│   ├── origin-structure-market-overview.md
│   ├── derivative-asset-registration.md
│   ├── origin-audit-record.md
│   ├── royalty-allocation-graph.md
│   └── marketplace-listing.md
├── examples/
│   ├── origin-asset.example.yaml
│   ├── derivative-asset.example.yaml
│   ├── origin-audit-record.example.yaml
│   ├── royalty-allocation-graph.example.yaml
│   └── marketplace-listing.example.yaml
├── schemas/
│   ├── origin-asset.schema.json
│   ├── derivative-asset.schema.json
│   ├── origin-audit-record.schema.json
│   ├── royalty-allocation-graph.schema.json
│   └── marketplace-listing.schema.json
├── scripts/
│   └── validate_examples.py
├── CHANGELOG.md
└── README.md

---

Origin Asset Schema

The Origin Asset schema is located at:

schemas/origin-asset.schema.json

It defines the structure of an upstream origin registration record.

A valid Origin Asset record must include:

• id
• title
• creator
• asset_type
• description
• canonical_hash
• timestamp
• permission
• royalty_policy
• trace

---

Derivative Asset Schema

The Derivative Asset schema is located at:

schemas/derivative-asset.schema.json

It defines the structure of a downstream asset derived from one or more upstream Origin Assets or Derivative Assets.

A valid Derivative Asset record must include:

• id
• title
• creator
• asset_type
• description
• timestamp
• derived_from
• output
• proposed_royalty_split
• trace

The derived_from section records:

• upstream asset ID
• upstream asset role
• contribution claim
• transformation type
• optional evidence

---

Origin Audit Record Schema

The Origin Audit Record schema is located at:

schemas/origin-audit-record.schema.json

It defines the structure of an audit record used to evaluate a derivative claim.

A valid Origin Audit Record must include:

• id
• target_asset_id
• target_asset_type
• auditor
• timestamp
• audit_scope
• compared_assets
• similarity
• judgment
• evidence
• human_review

The Origin Audit Record layer allows the protocol to record:

• compared upstream assets
• structural similarity
• conceptual similarity
• lineage similarity
• workflow similarity
• contribution scores
• royalty relevance
• audit judgment status
• evidence
• human review boundary

---

Royalty Allocation Graph Schema

The Royalty Allocation Graph schema is located at:

schemas/royalty-allocation-graph.schema.json

It defines the structure of a proposed revenue allocation graph.

A valid Royalty Allocation Graph must include:

• id
• revenue_event_id
• product_id
• timestamp
• currency
• gross_revenue
• allocation_basis
• allocations
• settlement
• human_review
• trace

The Royalty Allocation Graph layer allows the protocol to record:

• revenue events
• revenue-generating products
• gross and net revenue
• audit-based allocation basis
• contribution scores
• allocation policy
• recipient roles
• allocation rates
• allocation amounts
• settlement status
• human review boundary

This transforms audited lineage into a proposed economic distribution.

---

Marketplace Listing Schema

The Marketplace Listing schema is located at:

schemas/marketplace-listing.schema.json

It defines the structure of a marketplace-facing listing record.

A valid Marketplace Listing must include:

• id
• title
• listing_type
• listed_asset
• summary
• timestamp
• status
• pricing
• license
• royalty
• discovery
• human_review
• trace

The Marketplace Listing layer allows the protocol to record:

• listed asset metadata
• pricing model
• license terms
• royalty requirements
• Royalty Allocation Graph references
• discovery categories
• search tags
• target users
• quality signals
• human review status
• marketplace trace links

This transforms traceable structures into discoverable and licensable market records.

---

Validation

Install dependencies:

pip install jsonschema PyYAML

Run validation:

python scripts/validate_examples.py

Expected output:

[validate] Origin Asset
  schema : schemas/origin-asset.schema.json
  example: examples/origin-asset.example.yaml
[ok] Origin Asset example is valid
[validate] Derivative Asset
  schema : schemas/derivative-asset.schema.json
  example: examples/derivative-asset.example.yaml
[ok] Derivative Asset example is valid
[validate] Origin Audit Record
  schema : schemas/origin-audit-record.schema.json
  example: examples/origin-audit-record.example.yaml
[ok] Origin Audit Record example is valid
[validate] Royalty Allocation Graph
  schema : schemas/royalty-allocation-graph.schema.json
  example: examples/royalty-allocation-graph.example.yaml
[ok] Royalty Allocation Graph example is valid
[validate] Marketplace Listing
  schema : schemas/marketplace-listing.schema.json
  example: examples/marketplace-listing.example.yaml
[ok] Marketplace Listing example is valid
[done] all examples are valid

---

GitHub Actions

This repository includes a validation workflow:

.github/workflows/validate.yml

The workflow runs on:

• push to main
• pull requests to main
• manual workflow dispatch

It validates YAML examples against the JSON Schemas.

---

Conceptual Architecture

Origin Asset
    ↓
Derivative Asset
    ↓
Origin Audit Record
    ↓
Royalty Allocation Graph
    ↓
Marketplace Listing
    ↓
Value Returned to Origin

v0.1 implements:

Origin Asset Registration

v0.2 implements:

Derivative Asset Registration

v0.3 implements:

Origin Audit Record

v0.4 implements:

Royalty Allocation Graph

v0.5 implements:

Marketplace Listing

Together, v0.1 to v0.5 establish the first verifiable market lineage stack:

source structure → downstream derivative → audit record → allocation graph → marketplace listing

---

Design Philosophy

Origin Structure Market is based on five principles.

1. Structure over content

The important unit is not only the finished text or product, but the reusable structure that generates future work.

2. Trace over ownership

The protocol focuses on traceable contribution rather than absolute ownership claims over abstract ideas.

3. Audit before allocation

Derivative claims should be evaluated before they influence economic distribution.

4. Allocation before settlement

Revenue should be mapped before payment systems execute settlement.

5. Listing before market automation

Marketplace records should preserve trace, license, pricing, royalty, and review metadata before automated discovery or monetization.

---

Relation to Other Protocols

Origin Structure Market is designed to connect with related Kazene ecosystem projects:

• AI Search Trace Receipt Standard
• Synchronization Audit Protocol
• Compute Access Royalty OS
• OKF Royalty OS Bridge
• Kazene Trace Receipt Protocol
• Structural Rumination Layer
• Multi-Wing Architecture

Together, these projects form a broader stack for:

traceability → origin audit → contribution scoring → royalty allocation → marketplace listing

---

Roadmap

v0.1 — Origin Asset Registration

Implemented:

• Define origin-asset.schema.json
• Add example YAML
• Add validation script
• Add GitHub Actions workflow

v0.2 — Derivative Asset Registration

Implemented:

• Define derivative-asset.schema.json
• Add derivative asset example YAML
• Track upstream origin or derivative assets
• Record transformation types
• Record contribution claims
• Record trace evidence
• Declare proposed royalty splits
• Add Derivative Asset validation to CI

v0.3 — Origin Audit Record

Implemented:

• Define origin-audit-record.schema.json
• Add origin audit record example YAML
• Compare target assets with upstream assets
• Record structural, conceptual, lineage, workflow, and overall similarity
• Record contribution scores
• Record royalty relevance
• Record audit evidence
• Preserve human review boundary
• Add Origin Audit Record validation to CI

v0.4 — Royalty Allocation Graph

Implemented:

• Define royalty-allocation-graph.schema.json
• Add royalty allocation graph example YAML
• Record revenue events
• Reference audit records
• Use contribution scores as allocation inputs
• Define allocation policy
• Record recipient roles, rates, amounts, and settlement status
• Preserve human review boundary
• Add Royalty Allocation Graph validation to CI

v0.5 — Marketplace Listing

Implemented:

• Define marketplace-listing.schema.json
• Add marketplace listing example YAML
• Record listed asset metadata
• Record pricing and commercial access model
• Record license and usage terms
• Reference royalty allocation graph
• Record discovery categories, tags, keywords, language, and target users
• Record quality signals
• Preserve human review boundary
• Add Marketplace Listing validation to CI

v0.6 — License Template Registry

Planned additions:

• Define reusable license template records
• Connect license templates to Marketplace Listings
• Add license compatibility metadata
• Add attribution requirements
• Add downstream commercial use rules
• Prepare for external license registry integration

---

Non-Goals

This project does not attempt to:

• enforce legal ownership over all abstract ideas
• replace copyright law
• act as a court or final dispute resolver
• guarantee automatic royalty enforcement by itself
• execute payments directly
• run a full marketplace by itself
• require blockchain usage in early versions

Instead, it provides a structured protocol foundation for future trace, audit, allocation, listing, licensing, and settlement systems.

---

License

License information will be defined in a future version.

Suggested initial direction:

Kazene-Origin-Market-License-0.5

or a compatible open license for experimental protocol development.

---

Summary

Origin Structure Market is an experimental protocol for the AI era.

It asks a simple question:

What if the origin of an idea could remain traceable after AI transforms it, audits it, monetizes it, and lists it on a marketplace?

The answer is a new kind of market:

not only a market for finished products,
but a market for reusable structures,
derivative lineage,
audit evidence,
royalty allocation,
and marketplace listing metadata.

A system where:

• ideas become structured Origin Assets
• derivatives preserve lineage
• audits evaluate contribution
• revenue events generate allocation graphs
• listings preserve license, pricing, discovery, and royalty metadata
• value can flow back upstream
• creators are recognized as structural sources

In short:

A market where value returns to the origin.