startups as

Queues.Support queues.support

namespace seednamespace

AI owns L1, humans take escalations: the agent triages and answers, a person gets the escalation with its context attached, and every ticket closes on the customer's confirmation.

From the Startup card at api.sb/queues.support · Designed · Agent, Service, App.

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	—	no provenance
Core noun	—	no provenance
Buyer and position	Deliverable Mint: "queues"	Inferred · low · portfolio-lens-b.tsv (icp_or_position)
Closed set or journey	S20 [task].support semantic-TLD work rails	Inferred · med · portfolio-lens-a.tsv (set_or_journey)
Abstraction	V-support	Inferred · low · portfolio-lens-b.tsv (abstraction)
Role (lens B)	projection	Inferred · low · portfolio-lens-b.tsv (role)
Registrar	porkbun	Inferred · high · holdings ledger (domains repo, read-only)

Its stack

Generated around Queues.Support

                               Queues.Support                                     centre
                                      │
                                 Headless.ly                                      the abstractions
                         ╱                         ╲
       SaaS.Studio                                         SaaSKit.AI             the abstractions
                         ╲
                                   API.SB                                         brands
                                      │
                             StartupBuilder.Dev                                   brands
                                      │
   Startups.Management ─────── Startups.Studio                                    the factory

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-support)

Gigs.Support Backlog.Support Escalations.Support Macros.Support Responders.Support

Listed by

no discovery view lists it yet

In logo rows

Headless.ly's row specified

Slices

in no slice

Relationships (1)

from	verb	to	provenance
Queues.Support	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	Headless.ly	Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified sb def queues.support: built on headless.ly [medium] — Headless.ly carries the support System (its support Product; support.headless.ly/api/tickets answers); the fan-out places queues.support on

Edit log

loading the versions of this record from api.sb…

Machine-readable: /queues.support.json