Product relationships · StartupBuilder

Each Relationship below starts from one of these Nouns and reads from both ends: its predicate one way, its inverse the other. Relationships lists the most connected Nouns and every area.

API Key reaches one Tenantinverse apiKeysEvery call it signs reads and writes only that Customer’s records.
App guides many Flowsinverse appThe Flows an App runs on first sign-in, one per Persona and Offer, each ending at the activation Event.
App presents many Dashboardsinverse presentedInAn App opens on Dashboards for the people signed in to it.
Brand brands many Offersinverse brandedByEach Offer carries exactly one Brand, whose name, voice and logo the buyer sees.
Brand themedBy one Themeinverse themesA Theme sets a Brand’s color, type, spacing and motion.
Change implementsDecision one Decisioninverse changesEvery merged Change traces back to the Decision that authorized it.
Change resolves many Issuesinverse resolvedByA Change names the Issues it fixes; each resolves when the last open Change naming it reaches all traffic.
Dashboard shows many Metricsinverse shownOnA Dashboard reads out Metrics, each computed from Events and never typed in.
Dashboard views one Thinginverse dashboardsA Dashboard summarizes one scope, such as a Studio, a Startup, a Team, or a Role.
Dataset builtFrom many Resourcesinverse datasetsa Dataset is built from Resources at its Sources, plus enrichment.
Dataset curates one Nouninverse curatedInA Dataset collects and vouches for the Things of exactly one Noun.
DNS Record answersFor one Domaininverse recordsA Domain answers DNS from its records; each record belongs to one Domain.
Domain hosts one Siteinverse hostedAtA Site answers on one or more Domains; each Domain serves one Site.
Domain registeredTo one Startupinverse domainsA Startup holds each Domain registration and pays for the hostname.
Domain serves one Tenantinverse hostnamesA Tenant answers on the names its Customer connects; each such Domain serves one Tenant.
Form captures many Leadsinverse capturedByEach Form submission creates a Lead.
Implementation runs one Productinverse implementationsAn Implementation runs an Interface, System or Verb of one Product.
Issue addresses many Problemsinverse addressedByAn Issue addresses the Problems its Evidence came from, so the Customers behind that Evidence hear when it ships.
Issue reports one Thinginverse issuesAn Issue is about one Thing, such as a Product, a Page, or an Order.
Mapping translates one Sourceinverse mappingsA Source reaches the registry’s Nouns and Verbs through its Mappings, one per Verb it serves.
Member Directory provisions one Tenantinverse provisionedByA Member Directory fills and empties Roles in one Tenant as people join and leave the Customer.
Monitor opens many Incidentsinverse monitorA failing internal Monitor opens an Incident, which names the Monitor that saw it first.
Offer grants many Entitlementsinverse grantedByAn accepted Offer grants Entitlements, each a Verb on a Noun, optionally bounded by a Limit.
Offer includes one Productinverse includedInEach Offer sells one Product; one Product sits inside many Offers at different prices and terms.
Offer pricedAt one Priceinverse priceOfEvery Offer embeds one Price: amount, currency, unit and tiers; zero is a Price.
Offer soldIn one Motioninverse sellsEach Offer sells through one Motion, which says who buys and who acts for them.
Offer targets many Personasinverse targetedByAn Offer speaks to and is priced for named Personas.
Outcome Contract governs one Offerinverse governedByAn Outcome Contract warrants the result an Offer sells: its done state, acceptance, assurance and remedy.
Page displays many Contentinverse displayedOnPages display published Content; one piece appears on many Pages.
Page embeds many Formsinverse embeddedInForms sit on Pages; one Form appears on many Pages.
Page targets many Keywordsinverse targetedByA Page is written to rank for, or be cited on, its Keywords.
Page uses many Componentsinverse usedOnA Page is assembled from Components, each filled from records.
Portal serves many Customersinverse signsIntoCustomers sign in to a Portal to order, track delivery, accept work, and pay.
Product builtFrom many Productsinverse buildsIntoA Product composes other Products; a change to a part reaches every Product built from it.
Product drawsOn many Sourcesinverse suppliesA Product keeps its promise with Sources it did not build: owned, wrapped, or recruited.
Project advances one Goalinverse projectsA Project’s work serves one Goal.
Project plans many Tasksinverse projectA Project is made of Tasks.
Publication publishes one Productinverse publicationA Product reaches its Customers through one Publication; nothing inside it names the platform.
Recording replays one Visitinverse recordingA Recording replays one Visit, linked from every funnel step that Visit reached.
Service requires many Workersinverse staffsA Service’s outcome is delivered by the Agents and Humans who fill its Roles.
Site contains many Pagesinverse containedInA Site serves its Pages, each at its own path.
Site includes one Portalinverse includedInA Site includes one Portal, the signed-in part where each Customer sees only their own records.
Site styledBy one Brandinverse stylesA Site renders one Brand’s name, voice and Theme.
Software packages many Systemsinverse packagedAsSoftware ships Systems to its Customers as one Product, headless or with an App.
Voice soundsLike one Personinverse voicesA cloned Voice sounds like one real person, and exists only while that person’s Consent holds.