startups.as

startups as

Pilotrecords.Dev pilotrecords.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

TiernamespaceInferred · med · portfolio-lens-a.tsv (tier)
Statusnamespace seedInferred · med · lens A tier namespace
Product kindSoftwareInferred · low · seed rule: name grammar api(s).*/.dev/.studio/.management/.app; product kinds per studio CONTEXT.md (Cloud · Data · Software · Service · Commerce · Marketplace)
Core nounObligation checkInferred · low · seed rule: the unit noun of lens B abstraction V-compliance (portfolio-lens-b.md §1)
Buyer and positionDeliverable Mint: "pilotrecords"Inferred · med · portfolio-lens-b.tsv (icp_or_position)
Closed set or journeyS20 One statute, one check (.dev regulatory checks)Inferred · med · portfolio-lens-a.tsv (set_or_journey)
AbstractionV-complianceInferred · med · portfolio-lens-b.tsv (abstraction)
Role (lens B)projectionInferred · med · portfolio-lens-b.tsv (role)
RegistrarporkbunInferred · high · holdings ledger (domains repo, read-only)

Its stack

  1. Generated around Pilotrecords.Dev

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

Relationships (2)

fromverbtoprovenance
Pilotrecords.Devlisted-by
logo row on a catalog venue (listed by)
API.QA Inferred · high · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvruns today
sb def pilotrecords.dev: checked by functions/quality [medium] — The fan-out's edge is "Evidence signed by api.qa"; api.qa signs its verification reports (Ed25519 attestation).
Pilotrecords.Devruns-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 pilotrecords.dev: built on visibility.cloud [low] — targets.jsonl places it on supply-chain and relates it to visibility.cloud; the reading kept is that each hazard, assessment and action is a

Sign in to curate.

Edit log

loading the versions of this record from api.sb…

Machine-readable: /pilotrecords.dev.json