startups as
Payonscan.Dev payonscan.dev
namespace seednamespaceSoftware
Settlement rides the scan event itself. Each POS scan lands as an EPCIS event on the epcis.dev spine, and the vendor is paid against that record, so both sides settle from one set of numbers.
From the Startup card at api.sb/payonscan.dev · Designed · App, Agent.
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 | Software | Inferred · low · seed rule: name grammar api(s).*/.dev/.studio/.management/.app; product kinds per studio CONTEXT.md (Cloud · Data · Software · Service · Commerce · Marketplace) | |
| Core noun | Custody event | Inferred · low · seed rule: the unit noun of lens B abstraction V-trace (portfolio-lens-b.md §1) | |
| Buyer and position | Pay-on-scan settlement for suppliers | Inferred · high · portfolio-lens-b.tsv (icp_or_position) | |
| Closed set or journey | S20 One statute, one check (.dev regulatory checks) | Inferred · med · portfolio-lens-a.tsv (set_or_journey) | |
| Abstraction | V-trace | Inferred · high · portfolio-lens-b.tsv (abstraction) | |
| Role (lens B) | projection | Inferred · high · portfolio-lens-b.tsv (role) | |
| Registrar | porkbun | Inferred · high · holdings ledger (domains repo, read-only) |
Its stack
Payonscan.Dev centre
│
EPCIS.Dev brands
╱ │ ╲
DB4.AI Events.org.ai Products.org.ai the concepts
╲
StartupBuilder.Dev brands
│
Startups.Management ─────── Startups.Studio the factory
╱ ╱ │ ╲ ╲
SaaS.Studio ────────────── SaaS.Dev MonthEnd.FinanceObjects.do Services.do Workers.do the foundation · Do.Industries
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-trace)
Barcodetransition.comBarcoding.DevEPCIS.DevTransactions.DevVisibility.AssociatesVisibility.CloudWorklists.AppWorklists.DevEPCIS.org.aiEvents.org.aiGS1.org.aiLogistics.org.aiBarcodetransition.orgBarcodi.ngCyclecounts.coExpediters.WorkExpediting.ServicesFulfilli.ngLoadlabel.comLumpers.ServicesManifests.ClickMispick.ClaimsPacklists.coPickups.ClickPunchout.ClickPurchasi.ngPurchasing.ToolsRfqs.ClickScanni.ngShipp.ngSourc.ngStor.ngSuppliers.ClickSuppliers.ExchangeWorking.GamesWorklists.co
Listed by
no discovery view lists it yet
In logo rows
- EPCIS.Dev's row specified
- Barcoding.Dev's row specified
- APIs.Finance's row specified
Slices
in no slice
Relationships (3)
| from | verb | to | provenance | |
|---|---|---|---|---|
| Payonscan.Dev | runs-on logo row: "Powering" / "Built on" (customer runs on supplier) | EPCIS.Dev | Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified sb def payonscan.dev: built on epcis.dev [medium] — The register places it on the barcoding.dev/EPCIS spine; each POS scan is an EPCIS event captured on epcis.dev. | |
| Payonscan.Dev | runs-on logo row: "Powering" / "Built on" (customer runs on supplier) | Barcoding.Dev | Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified sb def payonscan.dev: built on barcoding.dev [medium] — The scan is a GTIN read at the register; the identifier is decoded and verified on barcoding.dev (register, "riding the barcoding.dev/EPCIS | |
| Payonscan.Dev | runs-on logo row: "Powering" / "Built on" (customer runs on supplier) | APIs.Finance | Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified sb def payonscan.dev: built on functions/payments [medium]; apis.finance is its preferred provider [medium] |
Sign in to curate.
Edit log
loading the versions of this record from api.sb…
Machine-readable: /payonscan.dev.json