# Naming exploration

Nonfinal architecture review · 0.4.0. Generated from `assets/fixtures-cost.js`; edit that source and rerun `node tools/generate-docs.js`.



## canonical

Product Resolver OpenDesign Workbench Prompt.md

## note

Shortlist for a future product name. The canonical project is not renamed. Domain availability is unverified — not checked; no registrar was queried and nothing was purchased.

## names

### name

Sameitem

### rationale

States the core job — finding the same exact item across sources — in plain words.

### name

Itemwise

### rationale

Neutral, category-agnostic; suggests careful, item-level comparison.

### name

Listbound

### rationale

Listings bound to one canonical item; hints at identity resolution without jargon.

### name

Truecart

### rationale

Consumer-facing: the delivered basket as it really is, including shipping answers.

### name

Canonry

### rationale

From canonical; short, distinctive, fits the resolver role.

### name

Partwise

### rationale

Keeps the "PC Part Picker" lineage without being limited to PCs.

### name

Shelfsure

### rationale

Scoped inventory and freshness: knowing what is actually on the shelf.

## root Default

example.com

## origins

### sub

app

### role

Consumer frontend (search, comparison, shipping answers)

### exposure

Public

### calls

Product API only (read-only)

### label

PROP

### sub

api

### role

Product API (product service)

### exposure

Public, rate-limited

### calls

Product projections

### label

PROP

### sub

ingest

### role

Resolver intake (capture submissions, heartbeats)

### exposure

Authenticated collectors only

### calls

Resolver core, R2, Queues

### label

PROP

### sub

admin

### role

Operator frontend + resolver administrative API

### exposure

Access-controlled (operators)

### calls

Resolver administrative API

### label

PROP

### sub

### role

Raw evidence (R2 private bucket)

### exposure

Private — no public origin

### calls

Read via resolver only

### label

PROP