---
id: barter-marketplace/001
title: Spec the listing/offer data model
epic: barter-marketplace
state: backlog
priority: 1
blocked_by: ["server-architecture/002"]
estimate: M
created: 2026-08-05
updated: 2026-08-05
claimed_by: null
claimed_at: null
delivers: []
review_artifact: null
---

## What to do

Design the listing/offer data model for player-to-player barter — direct 1:1 listings and bundle-for-one-rare-ingredient offers, per `overview.md`'s scope. Needs a real inventory/ownership data shape to design against, which depends on `server-architecture` settling how player inventory is authoritatively stored.

## Definition of done

A data model doc: listing shape (offered items, wanted item(s)), how a match/acceptance is recorded, and how it ties into whatever ownership model `server-architecture` lands on. No currency, no scalar value field — see `overview.md`'s non-goals.

## Where the work lands

`land-of-lor` repo.

## Docs to read first

`overview.md`'s no-currency constraint (read this first, it's load-bearing) and its open question on offer-matching without a common value unit; `server-architecture`'s eventual ownership/inventory model.