startups.as

startups as

Triggers.Studio triggers.studio

on-stagepremiumSoftware

contested · 1 tension
  • stage: next400 · top100 one lens puts it in its top 100, the other does not (sketch R10: 68 shared, 32 each)

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

TierpremiumInferred · med · portfolio-lens-a.tsv (tier)
Statuson-stageInferred · med · lens A stage next400
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 nounWorkflowInferred · low · seed rule: the unit noun of lens B abstraction B-workflow (portfolio-lens-b.md §1)
Buyer and positionNo-code trigger builderInferred · high · portfolio-lens-b.tsv (icp_or_position)
Closed set or journeyS3 Integration trio · trigger UI doorInferred · med · portfolio-lens-a.tsv (set_or_journey)
AbstractionB-workflowInferred · high · portfolio-lens-b.tsv (abstraction)
Role (lens B)projectionInferred · high · portfolio-lens-b.tsv (role)
RegistrardynadotInferred · high · holdings ledger (domains repo, read-only)

Its stack

  1. Generated around Triggers.Studio

No runs-on, made-by or meets-at Relationships touch this name yet.

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 (0)

None yet.

Sign in to curate.

Edit log

loading the versions of this record from api.sb…

Machine-readable: /triggers.studio.json