startups as

Jointcheck.Dev jointcheck.dev

namespace seednamespaceSoftware

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	Obligation check	Inferred · low · seed rule: the unit noun of lens B abstraction V-compliance (portfolio-lens-b.md §1)
Buyer and position	Deliverable Mint: "jointcheck"	Inferred · med · 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-compliance	Inferred · med · portfolio-lens-b.tsv (abstraction)
Role (lens B)	projection	Inferred · med · portfolio-lens-b.tsv (role)
Registrar	porkbun	Inferred · high · holdings ledger (domains repo, read-only)

Its stack

Generated around Jointcheck.Dev

                            Jointcheck.Dev                                    centre
                                   │
                             APIs.Finance                                     the businesses
                                   │
                              Headless.ly                                     the abstractions
                       ╱                        ╲
     SaaS.Studio                                       SaaSKit.AI             the abstractions
                       ╲
                                API.SB                                        brands
                                   │
   Startups.Studio ────── StartupBuilder.Dev                                  brands

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

Compliance.do Dirreg.Dev Redact.do SOC2.do Attestations.Services Batterycheck.Dev Bottledeposit.Dev Carriercomp.Dev Ciac.Dev Cleantruck.Dev Complyi.ng Databroker.Report Datecode.Dev Fflcheck.Dev Fifra.Dev Floodi.ng Lawlabel.Dev Ld2.Dev Lm2.Report Mattressfee.Dev Minesafety.Dev Neshap.Dev Pentesters.Work Pest.Report Pilotrecords.Dev Regf.Dev Tankcheck.Dev Tirefee.Dev Trustnotice.Dev

Listed by

no discovery view lists it yet

In logo rows

APIs.Finance's row specified

Slices

in no slice

Relationships (1)

from	verb	to	provenance
Jointcheck.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 jointcheck.dev: built on functions/payments [medium]; apis.finance is its preferred provider [medium]

Edit log

loading the versions of this record from api.sb…

Machine-readable: /jointcheck.dev.json