startups as
Expediting.Services expediting.services
namespace seednamespaceService
A service that never clocks out: every open PO line watched against its need date, suppliers chased in their own time zone, escalations logged as tasks, and freight or a second source booked within the buyer's approval.
From the Startup card at api.sb/expediting.services · Designed · Service, 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 | Service | Inferred · low · seed rule: name grammar .click/.services: a paid task or outcome; 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 | Deliverable Mint: "expediting" | Inferred · med · portfolio-lens-b.tsv (icp_or_position) | |
| Closed set or journey | S20 [task].services semantic-TLD work rails | Inferred · med · portfolio-lens-a.tsv (set_or_journey) | |
| Abstraction | V-trace | Inferred · med · portfolio-lens-b.tsv (abstraction) | |
| Role (lens B) | projection | Inferred · med · portfolio-lens-b.tsv (role) | |
| Registrar | dynadot | Inferred · high · holdings ledger (domains repo, read-only) |
Its stack
Expediting.Services centre
│
Visibility.Cloud brands
│
Outbound.Marketing support:stock
│
APIs.Credit brands
╱ │ ╲
Searches.Dev Gigs.Loans MongoLake.Dev the abstractions
│
APIs.Finance 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-trace)
Barcodetransition.comBarcoding.DevEPCIS.DevTransactions.DevVisibility.AssociatesVisibility.CloudWorklists.AppWorklists.DevEPCIS.org.aiEvents.org.aiGS1.org.aiLogistics.org.aiBarcodetransition.orgBarcodi.ngCyclecounts.coExpediters.WorkFulfilli.ngLoadlabel.comLumpers.ServicesManifests.ClickMispick.ClaimsPacklists.coPayonscan.DevPickups.ClickPunchout.ClickPurchasi.ngPurchasing.ToolsRfqs.ClickScanni.ngShipp.ngSourc.ngStor.ngSuppliers.ClickSuppliers.ExchangeWorking.GamesWorklists.co
Listed by
no discovery view lists it yet
In logo rows
- Visibility.Cloud's row buildable
- Worklists.Dev's row specified
Slices
in no slice
Relationships (2)
| from | verb | to | provenance | |
|---|---|---|---|---|
| Expediting.Services | runs-on logo row: "Powering" / "Built on" (customer runs on supplier) | Visibility.Cloud | Inferred · low · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvbuildable sb def expediting.services: built on visibility.cloud [low] — Stated by r2-horizontal; a part's shipment events tell it when a line has moved. | |
| Expediting.Services | runs-on logo row: "Powering" / "Built on" (customer runs on supplier) | Worklists.Dev | Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified sb def expediting.services: built on worklists.dev [medium] — Stated by r1-live; each chase and escalation is a task, and worklists.dev's file names expediting.services among those that rebrand it. |
Sign in to curate.
Edit log
loading the versions of this record from api.sb…
Machine-readable: /expediting.services.json