How WASTE.LAND works

// START HERE

The big picture

Many repos stop at 60–80% done. They are not worthless: they contain UI, APIs, data models, and lessons. WASTE.LAND is a marketplace where that code can be listed, inspected automatically, and sold or traded under clear rules. Money moves as Scraps inside the platform; sensitive steps go through Vault escrow.

flowchart LR
  subgraph seller["Seller"]
    R[Repo / ZIP]
  end
  subgraph platform["WASTE.LAND"]
    O[Overseer audit]
    M[Marketplace]
    V[Vault escrow]
  end
  subgraph buyer["Buyer"]
    U[Reuse / fork / product]
  end
  R --> O
  O --> M
  M --> V
  V --> U
    

// ROLES

Who does what

You can be a seller, a buyer, or both over time.

flowchart TD
  S[Seller lists project] --> A[Overseer produces report]
  A --> L[Listing goes live]
  L --> C[Buyer starts chat]
  C --> E[Both agree on terms]
  E --> V[Buyer locks Scraps in Vault]
  V --> P[Buyer previews code]
  P --> X{Decision}
  X -->|Accept| R[Scraps to seller, transfer code]
  X -->|Reject| F[Scraps returned to buyer]
    

// CURRENCY

What are Scraps?

Scraps are the in-app unit for listing fees, messages, and trades—platform credit that keeps spam down and aligns buyers and sellers. You earn them from sales and bonuses, and buy packs when you need more.

flowchart LR
  subgraph INFLOW["Into the platform"]
    P[Purchase packs]
    EARN[Earnings from sales]
    B[Bonuses / ranks]
  end
  subgraph USES["Typical uses"]
    L[Listings]
    MSG[Messages]
    T[Trade / escrow]
  end
  P --> L
  EARN --> MSG
  B --> T
    

// AUTOMATED AUDIT

The Overseer & S.P.E.C.I.A.L.

The Overseer is an automated pipeline (build checks, dependency map, heuristics, optional AI). It does not replace a lawyer or a full security pentest; it gives a consistent, comparable snapshot so buyers are not buying blind.

Scores are combined into one Resurrection score. Letters are a mnemonic (same idea as classic RPG stats).

• S Security — secrets, risky deps, obvious holes
• P Product — does the idea and scope still make sense?
• E Economics — effort vs value, license fit
• C Community — docs, tests, how hard to onboard
• I IP — licensing clarity
• A Architecture — structure and technical debt
• L Legal — third-party and compliance flags

flowchart TB
  subgraph AUD["Seven scored axes"]
    S[S Security]
    P[P Product]
    E[E Economics]
    C[C Community]
    I[I IP]
    A[A Architecture]
    L[L Legal]
  end
  AUD --> R[Resurrection score]
  R --> N[Necropsy summary text]
    

// TRUST

Why Vault escrow?

Without escrow, the buyer could vanish after getting the repo, or the seller could take payment and never hand over access. Vault holds the buyer’s Scraps while they verify the goods. Only after acceptance (or after rules for timeout / dispute) does the seller get paid.

sequenceDiagram
  participant Buyer
  participant Vault as Vault escrow
  participant Seller
  Buyer->>Vault: Lock Scraps for this deal
  Vault->>Seller: Seller sees funds held
  Buyer->>Vault: Open preview window
  Vault->>Buyer: Read-only access to agreed scope
  alt Buyer accepts
    Buyer->>Vault: Release
    Vault->>Seller: Scraps credited
  else Buyer rejects within rules
    Buyer->>Vault: Cancel per policy
    Vault->>Buyer: Scraps returned
  end
    

Exact timings, dispute steps, and fees belong in the production contract and help pages.

// WALKTHROUGH

A concrete (made-up) example

Names and numbers are only here to make the flow easy to picture.