fix: offer to use collection instead of tenant

docs/architecture.md

@@ -51,9 +51,9 @@ interface Offer {
   aggregate: PieceCID
   // CID of all the segments part of the aggregate
   pieces: PieceCID[]
-  // identifier of the tenant for the storefront `did:web:web3.storage`
-  // spade relies on tenant naming, so we map it here to tenant
-  tenant: string
+  // identifier of the collection for the tenant `did:web:web3.storage`
+  // spade relies on collections to identify different replication constraints.
+  collection: string
   // enables ordering of offers to handle.
   // Being it the number of ms since epoch, also means offers that fail and are retried will have "priority"
   // It can also have lower numbers to prioritize certain actors in the future

packages/core/src/data/offer.ts

@@ -20,7 +20,7 @@ export const encode = {
     const value = {
       aggregate: dealRecord.aggregate.toString(),
       pieces: dealRecord.pieces.map(p => p.toString()),
-      tenant: dealRecord.storefront,
+      collection: dealRecord.storefront,
       orderID: dealRecord.insertedAt || Date.now()
     } satisfies Offer
 
@@ -53,7 +53,7 @@ export const decode = {
     return {
       aggregate: parseLink(record.aggregate),
       pieces: record.pieces.map(p => parseLink(p)),
-      storefront: record.tenant,
+      storefront: record.collection,
       insertedAt: record.orderID
     }
   },
@@ -74,6 +74,6 @@ export type EncodedRecord = {
 export type Offer = {
   aggregate: string
   pieces: string[]
-  tenant: string
+  collection: string
   orderID: number
 }