startups as

Stocksync.Trade stocksync.trade

namespace seednamespaceCommerce

contested · 1 tension

tier: namespace · projection lens A reads namespace (namespace); lens B reads projection (brand)

The two lenses (and any ledger statement) are kept side by side, not resolved. Most names carry one; it is a reading to explore, not an error.

What it is

Tier	namespace	Inferred · med · portfolio-lens-a.tsv (tier)
Status	namespace seed	Inferred · med · lens A tier namespace
Product kind	Commerce	Inferred · low · seed rule: lens B abstraction V-commerce; product kinds per studio CONTEXT.md (Cloud · Data · Software · Service · Commerce · Marketplace)
Core noun	—	no provenance
Buyer and position	Deliverable Mint: "stocksync"	Inferred · low · portfolio-lens-b.tsv (icp_or_position)
Closed set or journey	S20 [task].trade semantic-TLD work rails	Inferred · med · portfolio-lens-a.tsv (set_or_journey)
Abstraction	V-commerce	Inferred · low · portfolio-lens-b.tsv (abstraction)
Role (lens B)	projection	Inferred · low · portfolio-lens-b.tsv (role)
Registrar	dynadot	Inferred · high · holdings ledger (domains repo, read-only)

Its stack

Generated around Stocksync.Trade

                              Stocksync.Trade                                           centre
                                     │
                             Transactions.Dev                                           brands
                        ╱                          ╲
    Triggers.Dev                                          Barcoding.Dev                 the abstractions
                                     ╱                          │
  Visibility.Cloud                                      APIs.Accountants                brands
                                                   ╱
                                 Gigs.Tax                                               brands
                        ╱                          ╲
     API.Lawyer                                           Preparers.Tax                 the businesses

Click any node to re-centre the stack on it; the trail above keeps the nesting. Each node's own page is one more click.

Neighbours

Same abstraction (V-commerce)

Equipment.org.ai Instruments.org.ai Manufacturing.org.ai Marketplace.org.ai Offers.org.ai Procurement.do Products.org.ai Retail.org.ai Sourcing.do Bulk.Markets Buyers.Exchange Cartsave.Trade Catalogi.ng Catalogs.Trade Catchup.Click Cellar.Markets Clearout.Markets Closeout.Cheap Crosslist.Click Drops.Markets Dropshippi.ng Einkauf.Markets Feeaudit.Trade Fraudcheck.Trade Giftcard.Tools Landedcost.Click Liquidate.Markets Listings.Monster Mapguard.Trade Matchi.ng Matchprice.Bid Metering.Click Pricepolice.Bid Promoguard.Trade Proofs.Click Refunds.Bid Refunds.Trade Reimburse.Trade Reorders.Tools Replenish.Click +26 more

Listed by

no discovery view lists it yet

In logo rows

Transactions.Dev's row buildable
API.ForSale's row buildable

Slices

in no slice

Relationships (2)

from	verb	to	provenance
Stocksync.Trade	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	Transactions.Dev	Inferred · low · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvbuildable sb def stocksync.trade: built on transactions.dev [low] — A retailer's inventory feed is an EDI 846 and its orders 850s, on the transactions.dev record (inferred).
Stocksync.Trade	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	API.ForSale	Inferred · low · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvbuildable sb def stocksync.trade: built on functions/sales [low]; api.forsale is its preferred provider [medium]

Edit log

loading the versions of this record from api.sb…

Machine-readable: /stocksync.trade.json