Skip to main content

Core Concepts

This section defines the vocabulary of Subscriberbot. Understanding these few concepts is enough to navigate the rest of the documentation and the API.

The mental model​

Everything in Subscriberbot reduces to a small set of ideas:

  1. Entities — the nouns of the domain (Identity, Provider, Relationship, Plan, and so on). See Domain Entities.
  2. The Relationship — the single most important entity. A Relationship is any recurring digital relationship: a subscription, a membership, a license, or a contract. Almost every feature is, at its core, an operation on Relationships.
  3. The Graph — entities are nodes; their connections are edges. See The Unified Relationship Graph.
  4. Events — meaningful changes (a renewal detected, an invoice received, a trial ending) are emitted on an event bus that drives automations. See Events.
  5. Scores — derived signals that summarize health and risk for users, providers, and vendors. See Scores.

How the pieces fit​

A typical flow ties the concepts together:

Provider adapter syncs a Relationship
   → graph is updated, an event is emitted (RenewalDetected)
   → an automation runs (Cost Agent evaluates the policy)
   → the Relationship's Health Score is recomputed
   → the Concierge surfaces a recommendation to the Identity

Read the entity reference next to see each noun in detail.