startups as

Schedul.ng schedul.ng

namespace seednamespace

Scheduling as a metered verb: the booking rail every booking-shaped vertical rides, exposed as one endpoint.

From the Startup card at api.sb/schedul.ng · 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	—	no provenance
Core noun	Business system	Inferred · low · seed rule: the unit noun of lens B abstraction B-systems (portfolio-lens-b.md §1)
Buyer and position	Scheduling system	Inferred · high · portfolio-lens-b.tsv (icp_or_position)
Closed set or journey	S20 Word-forming / domain-hack namespace (ing, .ng, .at, com.se)	Inferred · med · portfolio-lens-a.tsv (set_or_journey)
Abstraction	B-systems	Inferred · high · portfolio-lens-b.tsv (abstraction)
Role (lens B)	projection	Inferred · high · portfolio-lens-b.tsv (role)
Registrar	dynadot	Inferred · high · holdings ledger (domains repo, read-only)

Its stack

Generated around Schedul.ng

                                 Schedul.ng                                       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 (B-systems)

Cntnt.Management FAQ.Management Headless.ly Management.Studio Platforms.Management Tags.Management Headless.Delivery Dashboard.do Hubspot.do Kpis.do Management.do Mgmt.do Okr.do Okrs.do Onboarding.do Payload.do Product.md Projects.do Roadmap.md Salesforce.do Servicenow.do Servicetitan.do Tasks.do Analytics.Monster Assignments.Team Backoffice.Ninja Busywork.Agency Kpi.Cards Papework.Army Plann.ng Prototyp.ng Roadmapp.ng Scorecards.Click Shadmin.App Standups.Team Subtasks.Tools Taski.ng Todoi.ng Workflow.Associates Workflow.Engineer +4 more

Listed by

no discovery view lists it yet

In logo rows

Headless.ly's row specified
API.ForSale's row buildable

Slices

in no slice

Relationships (2)

from	verb	to	provenance
Schedul.Ng	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 schedul.ng: built on headless.ly [medium] — Headless.ly carries the scheduling System (its scheduling Product; the deck's umbrellas slide); the fan-out places schedul.ng on it (r6-stac
Schedul.Ng	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 schedul.ng: built on api.forsale [low] — The register's default provider for meeting scheduling sits on the sales spine (r2-horizontal).

Edit log

loading the versions of this record from api.sb…

Machine-readable: /schedul.ng.json