Relationships · StartupBuilder

A Relationship is a standing link between two records, declared once and read from both ends. A Startup makes many Products, and each Product is madeBy its Startup.

Most connected

Product 44

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 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.

Growth 75

Ad promotes one Offerinverse promotedByEach Ad sells one Offer.
Ad targets many Audiencesinverse targetedByAn Ad is shown to the people its Audiences select.
Campaign advances one Goalinverse advancedByA Campaign spends its budget and window toward one Goal.
Campaign runs many Adsinverse runInA Campaign places Ads that share its budget and window.
Channel hosts many Threadsinverse hostedInA Channel holds Threads.
Contact becomes one Customerinverse contactA Contact becomes a Customer on accepting an Offer.
Contact enrolledIn many Sequencesinverse enrollsA Sequence runs for an enrolled Contact until a reply, a purchase, or another exit Event ends it.
Contact gives many Consentsinverse givenByA Contact grants Consents, each for one Purpose, with its basis and expiry.
Contact resolvesTo one Personinverse contactsEach Contact is one Startup’s view of a Person shared across every Startup that knows them.
Contact worksAt one Organizationinverse peopleA Contact works for one Organization, as this Startup knows it.
Conversation awaits one Workerinverse conversationsOne Worker owes each Conversation its next answer.
Conversation raises many Threadsinverse raisedInThe intake Threads a support Conversation opens, each deadline counted from the Conversation’s first Message.
Conversation reports one Issueinverse conversationsThe Issue or Incident a Conversation reports; resolving it answers every linked Conversation.
Customer accepts many Offersinverse acceptedByA party becomes a Customer by accepting any Offer, at any price including zero.
Customer acquiredBy one Acquisitioninverse customersA Customer inherits the Acquisition of the Lead it was; Metrics and payouts read this one row.
Customer holds many Entitlementsinverse heldByA Customer’s Entitlements are what it may do right now, granted by the Offers it accepted.
Customer maintains many Subscriptionsinverse subscriberA Customer holds Subscriptions, each billed once per Period.
Customer opens many Conversationsinverse customerThe Customer a Conversation serves, so every answer reads that Customer’s records.
Customer owns one Tenantinverse ownedByEach Customer has one Tenant: the partition of the Startup’s data that no other Customer reads.
Customer places many Ordersinverse placedByA Customer commits to one-time purchases as Orders.
Customer saves many Payment Sourcesinverse savedByA Customer saves the Payment Sources its Orders, Subscriptions and Invoices charge; each belongs to one Startup and never moves to a sibling.
Deal courts one Organizationinverse dealsEach Deal has one buying Organization on the other side.
Deal issues many Quotesinverse issuedInA Deal sends Quotes, each a priced proposal valid until a date.
Deal pursues many Offersinverse pursuedInA Deal asks one buyer to accept one or more Offers.
Demand Budget pays many Playsinverse paidByA Demand Budget’s spend buys demand Plays.
Demand Budget recordedAs one Decisioninverse recordsEach Demand Budget is committed as one Decision, read again when it closes.
Enrollment follows one Sequenceinverse enrollmentsThe Sequence whose steps this Enrollment walks, one step at a time.
Enrollment runsFor one Contactinverse enrollmentsThe Contact this run belongs to; pausing one Contact’s nurture pauses this Enrollment.
Experiment assignsWith many Flagsinverse assignsFlags split units across an Experiment’s Variants and log each assignment with its propensity.
Experiment measures many Metricsinverse measuredByOne primary Metric judges an Experiment’s Variants; guardrail Metrics stop it.
Experiment offers many Variantsinverse offeredByThe Variants the Experiment can assign, the control among them.
Experiment tests one Hypothesisinverse testedByEach Experiment settles one Hypothesis; many Experiments test one Hypothesis in turn.
Exposure meets one Variantinverse exposuresThe Variant the Flag assigned to this unit.
Funnel leadsTo one Offerinverse funnelsEach Funnel’s path ends at one Offer, after its landing Page, opt-in and Sequence.
Funnel nurturesWith many Sequencesinverse nurturesA Funnel follows up with each new Lead through Sequences after the opt-in.
Gathering admits many Registrationsinverse gatheringA Gathering admits Registrations up to its capacity, then waitlists the rest.
Handle publishes many Postsinverse handleEvery Post goes out from one Handle, so its reach and replies count toward that Handle.
Hypothesis slots many Hypothesesinverse slotOfThe five slot Hypotheses of a Founding Hypothesis, each with a Metric and a threshold.
ICP faces many Problemsinverse facedByAn ICP struggles with Problems: how they solve them today and what that costs.
Interview yields many Evidenceinverse yieldedByAn Interview captures quotes and commitments, each graded as Evidence.
Key Result measures one Goalinverse keyResultsA Goal is met when its Key Results reach their targets.
Key Result reads one Metricinverse readByA Key Result compares one Metric’s value against its baseline and target.
Lead acquiredBy one Acquisitioninverse leadsEach Lead keeps the Acquisition that first brought it, through either door: a Visit or an outbound reply.
Lead identifies many Visitorsinverse identifiedAsA Lead, once it gives an address, is tied to every Visitor id it used, one per device.
Mailbox belongsTo one Workerinverse mailboxEvery Worker, Agent or Human, has its own Mailbox.
Meeting advances one Dealinverse meetingsA Meeting moves one Deal forward.
Meeting produces many Decisionsinverse madeInA Meeting records Decisions, each with its options, choice and reason.
Message postedIn one Channelinverse messagesEvery Message flows through one Channel.
Metric computedFrom many Eventsinverse feedsA Metric derives from Events and is never typed in.
Partner reserves many Organizationsinverse reservedByAn Organization a Partner reserved before referring it, for the `partner.reservationWindow` Setting (90 days by default); outbound skips it.
Persona belongsTo one ICPinverse personasA Persona is one named role inside an ICP, such as its buyer or its admin.
Persona holds one Roleinverse personasThe Role whose Permissions a Persona signs in with, so an App compiles its Dashboards and Verbs from one record.
Play moves many Metricsinverse movedByA Play exists to move named Metrics, read before and after every run.
Play targets many Portfoliosinverse playsA Studio rolls a Play out across a Portfolio one cohort wave at a time, measured as an Experiment.
Play Mix allocates one Demand Budgetinverse allocatedByEach Play Mix version splits one Demand Budget across its paid Plays.
Play Mix runs many Playsinverse includedInA Play Mix names each Play the Startup runs this week, with its state, budget and stop rule.
Prospect acquiredBy one Acquisitioninverse prospectsA Prospect’s Acquisition names the outbound Play and Mailbox that first reached it.
Prospect convertsTo one Leadinverse convertedFromA Prospect becomes a Lead on first engaging, such as a reply or a Form submission.
Readout reads one Experimentinverse readoutsThe Experiment the result belongs to; the learn step drafts the next Variant from it.
Readout scores one Variantinverse scoredByThe Variant the number describes.
Referral earns one Commissioninverse referralThe Commission a Partner’s Referral earns on the revenue it brings, self-serve or through a Deal.
Referral madeBy one Partyinverse referralsThe Party who sends a Referral earns its reward.
Referral refers one Leadinverse referredByEach Referral sends one Lead to the Startup.
Referral sources many Dealsinverse sourcedByThe Deals a Referral opened; when one is won, its revenue earns the Partner’s Commission.
Registration names one Contactinverse registrationsEach Registration holds one Contact’s place; one Contact registers for many Gatherings.
Renewal renews one Subscriptioninverse renewalsEach Renewal decides one term of one Subscription; a Subscription has one Renewal per term.
Review evaluates one Offerinverse reviewsA Review evaluates one Offer; Reviews of a Product or Brand roll up through its Offers.
Sequence schedules many Messagesinverse scheduledByA Sequence sends Messages, each at its own step and wait.
Story compiledFrom one Hypothesisinverse storiesThe Founding Hypothesis whose slots the Story compiles from; a pivot recompiles it.
Story quotes many Interviewsinverse quotedInThe Interviews whose words the Story reuses.
Survey informs many Metricsinverse informedBySurvey answers compute Metrics, such as a satisfaction score.
Visit lands one Siteinverse visitsEach Visit arrives on one Site.
Visitor starts many Visitsinverse startedByEach Visit is one span of a Visitor’s Events on the Startup’s Sites and Apps.
Waitlist awaits one Offerinverse waitlistA Waitlist admits its Leads to one Offer once that Offer opens.
Waitlist holds many Leadsinverse waitsOnLeads wait on a Waitlist in the order its Setting ranks them.

Finance 21

Bill owedTo one Organizationinverse billsA Bill is owed to one outside Organization, whose page lists every Bill the Startup owes it.
Budget plans one Periodinverse budgetsA Budget plans one Period, read beside the actual Entries that fall in it.
Coupon discounts many Offersinverse couponsA Coupon applies only to the Offers it names; an Offer may accept several Coupons.
Credit Grant credits one Customerinverse creditGrantsThe Customer whose metered calls spend the balance; credits never move to another Customer.
Credit Grant offsets many Invoicesinverse creditGrantsThe Invoices the grant paid toward when they finalized.
Instrument heldBy one Holderinverse instrumentsEach Instrument belongs to one Holder, who sees it, its vesting and its documents.
Instrument issuedBy one Companyinverse instrumentsAn Instrument is a right in one Company and counts in its fully diluted cap table.
Invoice charges one Customerinverse invoicesEach Invoice is owed by one Customer.
Meter counts many Eventsinverse meteredByThe Events the Meter counts toward usage billing.
Order buys many Offersinverse orderedInAn Order commits to buying one or more Offers once.
Pay Run paidBy one Companyinverse payRunsA Pay Run is paid by one Company, the employer of record for everyone in it.
Pay Run pays many Humansinverse paidInA Pay Run pays the Humans the Company employs; each employee appears in one run per pay period.
Quote acceptedAs one Orderinverse quoteThe Order the Quote becomes when the buyer accepts it before it expires.
Quote proposes many Offersinverse quotedInA Quote prices one or more Offers for one buyer.
Quote startsSubscription one Subscriptioninverse quoteThe Subscription for a Quote’s recurring lines, started when the Customer accepts it.
Share heldBy one Holderinverse sharesEach Share record belongs to one Holder; a transfer writes a new record for the new Holder.
Share issuedBy one Companyinverse sharesA Share is issued by one Company and sits on that Company’s cap table.
Statement reports one Periodinverse statementsA Statement reports one Period; each closed Period carries its P&L, balance sheet and cash flow.
Subscription bills many Invoicesinverse billedForThe Invoices the Subscription issues, one for each period it renews.
Subscription renews one Offerinverse subscriptionsA Subscription bills one recurring Offer each Period until canceled.
Transaction reconciles many Entriesinverse reconciledByThe ledger Entries the Transaction settles, matched during reconciliation.

Team 23

Candidate appliesTo one Openinginverse candidatesCandidates for an Opening are screened only on what its Hypothesis still lacks.
Candidate presents one Personinverse candidaciesA Candidate is one Person’s candidacy; the Person’s record crosses Startups only with Consent.
Credential authorizes many Reserved Actsinverse requiresA Credential lets its holder perform the Reserved Acts the law keeps for it, in its jurisdiction.
Mandate authorizes one Agentinverse mandatesA Mandate lets an Agent act without asking each time, within its Permissions and Limits, until it expires or is revoked.
Mandate funds many Cardsinverse fundedByA Mandate funds the Cards that spend under it; pausing it freezes them and revoking it closes them.
Opening staffs one Roleinverse openingsAn Opening is a need for a Human in one Role, taking a share of that Role’s work.
Opening tests one Hypothesisinverse testedByOpeningA hire into an Opening must prove its Hypothesis.
Permission allows one Verbinverse allowedByEach Permission allows one Verb, within its scope and Limit.
Role holds many Permissionsinverse heldByA Role’s Permissions are what its Worker may do: Verbs on Nouns within a scope and a Limit.
Role requires many Skillsinverse requiredByThe Skills, each at a level, a Worker needs to fill the Role.
Role Review reviews one Roleinverse roleReviewseach Role Review checks one Role, and a Role keeps every review it has had.
Supplier delivers many Servicesinverse suppliedBySuppliers staff Services through the Startup’s human supply.
Supplier holds many Credentialsinverse heldBySupplierThe Credentials a Supplier holds decide which Reserved Acts it may perform; standing is read fresh on every use.
Team groups many Rolesinverse teamA Team groups the Roles that do one kind of work under one owner.
Team serves many Startupsinverse teamsA Team does its one kind of work for every Startup it serves; a Startup wakes a Team when its trigger Event happens.
Worker carries many Cardsinverse carriedByA Worker carries the Cards issued for its Mandates; the cardholder on the rail is always the Company.
Worker fills many Rolesinverse filledByA Worker, human or agent, fills a Role and acts under its Permissions; one Agent can fill Roles in many Startups.
Worker hasAccess many Access Levelsinverse workersa Worker holds one Access Level in each namespace it works in, apart from the Role it fills.
Worker holds many Credentialsinverse heldByA Worker performs a Reserved Act only while it holds the Credential that authorizes it, in good standing.
Worker practices many Skillsinverse practicedByThe Skills a Worker has, each at a level, matched against what Roles require.
Worker remembers one Memoryinverse heldByA Worker’s own Memory of what it has learned, read by its Functions and kept within its Startup.
Worker uses many Toolsinverse usedByThe Tools a Worker may call, narrowed to its Role’s Permissions.
Worker writes many Commentsinverse authorEvery Comment names the Worker, human or agent, who wrote it.

Legal & trust 17

Agreement binds many Partiesinverse boundByThe Parties the Agreement holds to its terms, each from the moment it signs.
Attestation performs one Reserved Actinverse attestationsThe Reserved Act the Attestation records as performed or declined.
Attestation signedUnder one Credentialinverse attestationsThe Credential the signing Worker held when it signed.
Audit reliesOn many Proofsinverse reliedOnByThe Proofs the auditing firm samples across the report period.
Consent covers one Purposeinverse consentsThe Purpose the Consent permits processing for, and nothing beyond it.
Dispute cites many Evidenceinverse citedByThe Evidence each side submits on the Dispute, frozen once submitted.
Dispute contests one Orderinverse disputesThe Order whose delivery or charge the Dispute contests.
Evaluator grades many Verbsinverse gradedByThe Verbs whose results the Evaluator scores against its rubric before they count as done.
Evaluator verifies many Outcome Contractsinverse verifiedByEvaluators grade delivered work against an Outcome Contract’s done state before the Customer accepts it.
Evidence bearsOn many Hypothesesinverse evidenceEvidence supports or refutes Hypotheses; the strongest outside Evidence sets each Hypothesis grade.
Evidence documents many Problemsinverse documentedByEvidence shows a Problem in the words or behavior of the ICP.
Policy computes many Metricsinverse computedUnderA Policy rules how Metrics are computed, such as revenue under revenue recognition.
Proof proves one Controlinverse provenByThe Control whose test the Proof records running over a range of Events.
Recovery Objective capability one Capabilityinverse recoveryObjectivesThe Capability the objective restores.
Reserved Act reserves one Verbinverse reservedByThe Verb the law reserves to a credentialed Human in the act’s jurisdiction.
Risk treatedBy many Controlsinverse treatsThe Controls that lower the Risk. Every Control cites the Risks it treats.
Screening screens one Partyinverse screeningsA Party is screened before its first money move and again when its details change; every result stays.

Core grammar 44

Action actsOn one Thinginverse actedOnByThe Thing an Action changes; a Thing’s history is the Actions that acted on it.
Action asks many Questionsinverse actionA pending Action asks Questions and waits `awaitingInput` until each is answered or its deadline passes.
Action emits many Eventsinverse emittedByA completed Action emits its Events, which Triggers, Watches and Metrics read.
Action invokes one Verbinverse invokedAsEach Action performs one Verb, which fixes its inputs, the Event it emits and its delay window.
Action posts many Costsinverse postedByEvery Cost an Action causes posts to the Startup it ran in, so each Startup’s P&L is complete.
Action runsIn one Modeinverse modeOfThe Mode the caller chose: `try` stores nothing, `send` returns a pending Action, `do` waits for the result.
Approval gates one Actioninverse approvalsAn Approval holds one pending Action that exceeds a Limit or Mandate until someone allows or refuses it.
Capability exposes many Nounsinverse exposedByA Capability exposes Verbs on one Noun family, metered, limited and logged under one key.
Collection contains many Thingsinverse memberOfMembers are listed one by one or matched by the Collection’s saved query; a Thing can belong to many Collections.
Comment annotates one Thinginverse commentsA Comment is an internal note on one Thing, never sent to a Contact.
Decision decides one Thinginverse decidedByA Decision records one choice about a Thing and stays on that Thing’s record forever.
Document exportsTo many Filesinverse exportOfEach rendering of a Document to a format, such as PDF, is stored as a File.
Entry fallsIn one Periodinverse entriesAn Entry posts to the month its Event happened; closing the Period locks it.
Entry postsTo one Accountinverse entrieseach Entry posts to one Account, and an Account’s balance is the sum of its Entries.
Event causes many Entriesinverse causedByEvery ledger Entry traces to the one Event that caused it, such as `Order.paid`.
Function implements one Verbinverse implementedByA Function is how a Verb runs: code, a generative model, an Agent or a Human, and the caller never sees which.
Function uses many Secretsinverse usedByA Function declares the Secrets it reads; deploying to `live` fails when one is missing there.
Guard screens many Messagesinverse screenedByGuards check every outbound Message before it goes out.
Integration connects one Systeminverse connectedViaAn Integration connects an outside Source to one System, with credentials at Studio, Startup or Customer scope.
Interface mountedOn many Domainsinverse mountsAn Interface answers requests on the hostnames it is mounted on.
Interface reaches one Productinverse reachedViaEach Interface exposes one Product; a Product is reached through many Interfaces.
Interface speaks many Standardsinverse spokenByCallers in a Standard’s shape reach the Interface’s Verbs through the platform’s one translator for that Standard.
Noun movesThrough one Lifecycleinverse governsA Noun’s Lifecycle lists the states its Things move through and the Verbs that move them.
Process carriesOut one Playinverse carriedOutByA Process runs the steps of a Play each time the Startup runs it.
Process uses many Workflowsinverse usedInA Process does its work through Workflows, each the durable, executable part of the Process.
Question postedIn one Threadinverse questionsEach Question posts in the Thread of the record it concerns, where free-text replies land.
Relationship typedBy one Verbinverse typesA Relationship reads through a Verb whose forms name it from each side, such as `makes` and `madeBy`.
Setting configures one Thinginverse configuredByThe Thing whose choice a Setting holds; everything below it inherits the value unless it sets its own.
System defines many Nounsinverse definedInThe Nouns a System keeps records of; several Systems can share one Noun.
System runsOn many Capabilitiesinverse runsA System is built on Capabilities, such as Workflows or Search, that every Startup reaches with one key.
Task assignedTo one Workerinverse tasksThe Worker a Task waits on; the Task sits in that Worker’s inbox until it is done.
Tenant signsInVia many SSO Connectionsinverse servesA Tenant’s people sign in through its SSO Connections; the Customer’s admin owns each one.
Tenant verifies many Domainsinverse verifiedByA Tenant proves control of its Customer’s email domain, so sign-ins on that domain follow the Tenant’s policy.
Thing aimsFor many Goalsinverse heldByEvery Thing pursues Goals, such as a Startup’s quarterly objective or a Team’s weekly target.
Thing instanceOf many Nounsinverse instancesA Thing takes the properties, relationships and Verbs of every Noun it is an instance of.
Thing versionedAs many Versionsinverse versionOfEvery published change to a Thing’s definition is an immutable Version, kept forever.
Thread groups many Messagesinverse threadA Thread groups Messages that reply to one another.
Tool exposes one Verbinverse exposedAsA Tool is one Verb under one name on every Interface, such as `Contact.create`.
Trigger firesOn many Eventsinverse firesA Trigger fires each time an Event matching its selector happens.
Trigger starts many Workflowsinverse startedByWhen a Trigger fires, each Workflow it starts runs as a new Action.
Verb actsOn one Nouninverse actedOnByEvery Verb acts on one Noun, which names it: `Startup.launch` acts on Startup.
Verb defaultsTo one Modeinverse defaultForThe Mode a call uses when the caller names none: `try`, `send` or `do`.
Watch delivers many Eventsinverse deliveredByA Watch delivers each matching Event to its URL, signed, retried and replayable.
Workflow executes one Actioninverse executedByA Workflow is the durable body of one Action: its steps, retries and waits.