Glossary: D–E
Every StartupBuilder term from D–E, with its kind and one-sentence definition.
127 terms from D–E, each with its kind and one-sentence definition.
Terms
| Term | Kind | Definition |
|---|---|---|
| Daily ship | Workflow | Daily ship ranks misses, requests, and steps done by hand three times, then ships the top Issue as one small Change. |
| Dashboard | Noun | A Dashboard is one unified view of a scope, rendered as Markdown for Agents, screens for Humans, and JSON for native clients. |
| Dashboard.ask | Verb | Ask answers a plain-language question with a query over the Startup’s records and shows the query beside the result. |
| Dashboard.schedule | Verb | Schedule sends a Dashboard on a cadence to a Mailbox, a Channel or an Agent’s context, rendered for each. |
| Data broker | Legal floor row | Data broker registers the Company in each state broker registry once it sells personal data about people it has no direct relationship with. |
| Data editor | System | Data editor edits a Startup’s own Nouns directly: tables, saved views, imports, exports and bulk Changes. |
| Data Engineer | Role | The Data Engineer sources, licenses, and refreshes the Datasets a Startup sells, and keeps their quality measured. |
| Data residency | Play | Data residency pins a buyer’s Tenant to one region, adds the residency annex, and quotes the Price tier that includes it. |
| Data stories | Play | Data stories pitch original data to journalists and researchers, scored by mentions on the domains answer engines cite. |
| Database | Capability | Database stores every Thing in an owner database per namespace, with an analytics copy of every Event and reads at any past moment. |
| Dataset | Noun | A Dataset is a Product of curated Things of one Noun, with a promise that they are true. |
| Dataset API | Product Template | A Dataset API sells keyed lookups and queries over a Dataset to developers and Agents, metered per call. |
| Dataset freshness | Metric | Dataset freshness is the share of Datasets refreshed on their promised schedule. |
| Dataset refresh | Capability | Dataset refresh re-reads every Source of a Dataset on its schedule or on request, and backfills a past date range. |
| Datasets | System | Datasets is the System behind each Dataset: curated Things of one Noun, built from Sources plus enrichment, refreshed and checked against its promise. |
| DataTable | Component | DataTable lists one Noun's records in chosen columns; rolled up across scopes, it adds a scope column instead of averaging. |
| Days sales outstanding | Metric | Days sales outstanding is the average days from an Invoice being sent to its payment. |
| Days to first outside Order | Metric | Days to first outside Order counts the days from Live entry to the first paid Order from an outside Customer. |
| db.sb | Product | db.sb is the one database behind api.sb, keeping every record and event of every Startup. |
| Deal | Noun | A Deal is a Startup’s pursuit of one buyer’s acceptance of one or more Offers, ending won or lost. |
| Deal.advance | Verb | Advance moves a Deal to its next stage once every field that stage requires is filled. |
| Deal.assign | Verb | Assign gives a Deal one owner Worker, who carries its next step until it is won or lost. |
| Deal.lose | Verb | Lose closes a Deal as lost and records the reason the buyer gave. |
| Deal.propose | Verb | Propose sends a Deal’s buyer a Quote they accept to place an Order. |
| Deal.win | Verb | Win closes a Deal as won, which places its Order and makes the buyer a Customer. |
| Debt collection | Legal floor row | Debt collection sends a validation notice, caps contact frequency, and never harasses or misleads when a Startup collects debts owed to others. |
| Decision | Noun | A Decision is the immutable record of a choice: its options, the choice, the reason, who decided, and the stakes. |
| Decision.supersede | Verb | Supersede replaces a Decision with a newer one, keeping both on record with the reason for the change. |
| Declared Verb attempts | Metric | Declared Verb attempts counts live calls in 7 days to each Verb no Function runs yet, ranking which Function to build next. |
| Default alive | Metric | Default alive is runway divided by the months to profit at current growth and fully loaded Cost; 1 or more reads alive. |
| Default-alive check | Workflow | Default-alive check forecasts cash and growth forward each week and reports whether the Startup reaches profit first. |
| Define a Product | Workflow | Define a Product turns an Offer’s promise into the Nouns and Verbs that every Interface, Page, and Tool is generated from. |
| Delegated sending | Legal floor row | Delegated sending lets an Agent send as a Human only under that Human’s Mandate, with the disclosure each jurisdiction’s bot law requires. |
| Deliver an outcome | Workflow | Deliver an outcome runs the work an Order bought, gets it confirmed, redoes it once on a miss, and bills only when done. |
| Delivery | Process | Delivery runs the Orders Customers place for Agent and Service outcomes, and bills only on confirmation. |
| Delivery Manager | Role | The Delivery Manager runs each Order a Customer places, gets it confirmed, redoes it once on a miss, and bills only when done. |
| Demand Budget | Noun | A Demand Budget is the money a founder commits each month to demand Plays, recorded as a Decision with a target and a stop rule. |
| Demand generation | Capability | Demand generation runs demand Plays for a Startup inside its own Systems and attributes the revenue each one earns. |
| Deploy reconciliation | Control | Only Versions a merged Change points to run, and any other running fingerprint opens an Incident. |
| Design first run | Workflow | Design first run compiles sample records, empty states and the shortest path to an Offer’s activation event from the definition. |
| Designer | Role | The Designer shapes every App and Site a Startup ships, as data that renders for Humans and Agents alike. |
| Developer relations | Play | Developer relations publishes examples, docs and answers that get a developer or Agent to a first successful call within five minutes. |
| Deviation closure | Control | A failed test opens an Issue that closes only by a Decision recording cause, remediation and management’s response. |
| Digital product | Product Template | A Digital product sells files once, such as an ebook, a template pack or a plugin, delivered the moment the Order is paid. |
| Directory | Product Template | A Directory sells listings: Organizations pay to appear in a searchable Dataset that buyers and their Agents browse free. |
| Directory listings | Play | Directory listings keep a Startup listed and accurate on review sites, business profiles and vertical directories, free from the day it is Live. |
| Disclosure record | Control | Every disclosure of personal data to a third party is an Event that cites its Agreement and Purpose. |
| Discovery | System | Discovery runs buyer research: Interviews, Problems, graded Evidence, ICPs and Personas, so every Offer starts from what buyers said. |
| Discussions | System | Discussions gives Workers and Contacts headless Channels and Threads, where a mention assigns a reply Task and an Approval arrives with buttons. |
| Dispatch | System | Dispatch proposes each job to eligible, available Suppliers, books shifts, and proposes it again on decline before the deadline. |
| Dispute | Noun | A Dispute is a contested payment or delivery, such as a chargeback, a rejected Service outcome, or a buyer’s claim against a Supplier. |
| Dispute response | Capability | Dispute response answers chargebacks and contested deliveries with the Startup’s own records as Evidence, under each Dispute kind’s rules and deadlines. |
| Dispute.accept | Verb | Accept concedes an open Dispute without contest, so the buyer keeps the held amount and the Dispute closes. |
| Dispute.answer | Verb | Answer submits the seller’s Evidence on an open Dispute before its deadline: the contract, the delivered work, and its verdicts. |
| Dispute.appeal | Verb | Appeal asks for one review of a decided Dispute by a Worker who took no part in the first decision. |
| Dispute.decide | Verb | Decide rules on an answered Dispute for the buyer, the seller, or a split, and releases or returns the held amount. |
| DNS | Capability | DNS serves each Domain’s records as data, signs every zone with DNSSEC, and flags missing, drifted or dangling records daily. |
| DNS Record | Noun | A DNS Record is one DNS answer of a Domain: its type, name and value, who owns it, and what the world last answered. |
| DNSRecord.remove | Verb | Remove stops a Startup-owned DNS Record from answering; its history stays and a revert restores it. |
| DNSRecord.set | Verb | Set adds or changes a Startup-owned DNS Record through a Change, previewed against what the Domain answers today. |
| Document | Noun | A Document is structured, versioned material in one of three forms, a document, a deck, or a sheet, rendered to any format. |
| Document.render | Verb | Render produces a file from a Document in the format the reader asks for. |
| Documents | System | Documents keeps every versioned Document, deck or sheet, generated from records and rendered to the web, PDF, slides or spreadsheets. |
| Domain | Noun | A Domain is a hostname that points at a Thing, with a role, a status, and a lifecycle tracked as data. |
| Domain registration | Capability | Domain registration registers and renews each Startup’s Domains in a registrar account of its own, with its owner of record as registrant. |
| Domain.authenticate | Verb | Authenticate writes a Domain’s SPF, DKIM and DMARC records and verifies them before its first send. |
| Domain.benchmark | Verb | Benchmark measures a Domain’s estimated traffic, ranking Keywords, authority and referring domains beside the competitors named. |
| Domain.claim | Verb | Claim gives a Startup a one-label name under an issuing Domain, or assigns it a held Domain through an approved Change. |
| Domain.connect | Verb | Connect attaches a hostname a Startup already holds and verifies ownership through DNS. |
| Domain.register | Verb | Register buys a hostname for a Startup and points it at the Startup’s address. |
| Domain.release | Verb | Release lets a Domain’s registration or claim end, keeping its record, history and aliases. |
| Domain.renew | Verb | Renew extends a Domain’s registration by whole years at its renewal price, paid by its owner of record. |
| Domain.search | Verb | Search lists candidate names with availability, first-year price, renewal price and the rules of each extension. |
| Domain.transfer | Verb | Transfer moves a Domain’s registration to another holder or registrar, with its records intact. |
| Domain.verify | Verb | Verify checks a Domain’s DNS, ownership and certificate again and records each result, with the fix for any failure. |
| Domains | Capability | Domains connect names, DNS Records and certificates to a Startup’s Sites, Apps, Interfaces and Mailboxes, signed with DNSSEC by default. |
| Dormant | Lifecycle state | Dormant is the state of a Startup with no work running on it, whose records, site, and domain stay kept until it returns to Live. |
| Drill a restore | Workflow | Drill a restore restores each Capability’s records in isolation on its cadence, checks both recovery objectives, and opens an Issue on a miss. |
| Dropship store | Product Template | A Dropship store sells physical goods from a catalog while an upstream holds the stock and ships each Order, with tracking passed through. |
| Dunning | Workflow | Dunning retries failed payments on a schedule, tells the Customer once per retry, and pauses access only after the last attempt. |
| E2E managed service | Product Template | An E2E managed service runs a whole business function for the Customer, with Agents doing the work and Humans in the loop. |
| Earned mentions | Metric | Earned mentions counts the articles, Posts and podcasts each month that name the Startup without being paid. |
| Earnings | System | Earnings pays Suppliers, Partners and affiliates their earnings through Stripe, holds disputed amounts, and sends statements and year-end tax filings. |
| Editorial SEO | Play | Editorial SEO publishes guides, comparisons and alternative Pages that rank for searches a market already makes, refreshed on a fixed cadence or pruned. |
| Eligibility | Legal floor row | Eligibility refuses any declared use of Person data to decide credit, insurance, employment, or housing unless the Product is built as a consumer report. |
| Email delivery | Capability | Email delivery sends and receives email from warmed, authenticated Mailboxes, and checks Consent and Suppression before every send. |
| Email list | System | Email list keeps each Newsletter a Startup sends: its subscribers with their Consent, every issue, and the paid tier its Offer gates. |
| Email routing | Capability | Email routing receives mail for a Startup’s Domains, routes each address to a Mailbox or the sink, and publishes SPF, DKIM and DMARC. |
| Employment eligibility | Capability | Employment eligibility verifies each new employee’s right to work, records the employer’s attestation and keeps it for its retention period. |
| Encryption | Capability | Encryption protects every namespace in transit and at rest under its own keys, rotated on schedule with every old key kept. |
| Encryption | Control | Every record is encrypted at rest under its namespace’s key, and every connection is encrypted in transit. |
| Endorsements | Legal floor row | Endorsements bans fake or bought reviews and requires every Referral payment, insider review, and sibling recommendation to disclose its connection. |
| Engagement bridge | Play | Engagement bridge drafts public answers that a Human posts, or the agent posts when summoned, then messages only a Person who engaged, quoting that act. |
| Engineering Lead | Role | The Engineering Lead builds and runs the Startup’s Products: it implements each Change, deploys it behind replay, and owns uptime of every Interface. |
| Engineering seals | Legal floor row | Engineering seals has a licensed engineer or architect in the project’s state seal every drawing or report the law reserves to them. |
| Engineering Team | Team | The Engineering Team builds and runs every Product: it implements Nouns and Verbs, ships Changes behind replay, and keeps every Interface up. |
| Enrichment | Capability | Enrichment finds and fills in people and Organizations, with provenance on every field and Suppression checked first. |
| Enrollment | Noun | An Enrollment is one person’s run through one Sequence: the current step, when the next fires, the branches taken, and why it ended. |
| Enrollment.cancel | Verb | Cancel ends one Contact’s run through a Sequence for good, with the reason it records as exitReason. |
| Enrollment.pause | Verb | Pause stops one Contact’s run through a Sequence at its current step, without ending it. |
| Enrollment.resume | Verb | Resume restarts a paused run at the step it stopped on and sets when that step fires. |
| Entitlement | Noun | An Entitlement is what a Customer gets from an accepted Offer: a Verb on a Noun in its Tenant, optionally bounded by a Limit. |
| Entitlement.check | Verb | Check says whether a Customer may call a Verb now, how much of its Limit remains, when that resets, and which Offer lifts it. |
| Entry | Noun | An Entry is one line of a double-entry posting: an amount to one account in the chart of accounts, caused by one Event. |
| Entry.post | Verb | Post records a manual Entry pair that no Verb caused, once a second Role approves it. |
| Entry.settle | Verb | Settle nets a Period’s intercompany Entries between two Companies into one transfer through Stripe and reconciles both sides. |
| Environment separation | Control | Actions in test never touch live records, move real money or send Messages to a real Person. |
| Environments | Capability | Environments give every namespace a test and a live environment, with separate keys, records and money over one shared definition. |
| Equity | System | Equity is the core System that keeps the cap table of each Company: shares, SAFEs, options and their holders, grants, vesting and conversions. |
| Escaped defects | Metric | Escaped defects counts the Issues a Customer reports each week that an existing check should have caught. |
| Evals | System | Evals grades outputs with versioned Evaluators, gates every Change before merge, and keeps each Worker’s track record. |
| Evaluator | Noun | An Evaluator is a versioned Function that grades an output against a rubric and returns a verdict. |
| Event | Noun | An Event is the immutable record of something that happened to a Thing, named by its Noun and past-tense Verb. |
| Event streams | Capability | Event streams record every completed Action as an immutable Event and deliver it, in order, to subscribers, Watches and replays. |
| Event.capture | Verb | Capture records an Event from a Site, App or API call that no Verb emits, such as a page view or a click. |
| Events and webinars | Play | Events and webinars host sessions for mid-market and enterprise Customers, turn each into on-demand content, and enroll attendees in a Sequence within a day. |
| Evidence | Noun | Evidence is a recorded quote, reading, or artifact that supports or refutes a claim, graded as behavior, commitment, or opinion. |
| Evidence-backed Decisions | Metric | Evidence-backed Decisions is the share of product Decisions that cite at least one piece of Evidence from buyers. |
| Expansion revenue | Metric | Expansion revenue is the recurring revenue outside Customers paying at the window’s start add in it: more units, a higher Price or another Offer. |
| Expense approval | Process | Expense approval checks every card charge against its Mandate and the spender’s Limit, asks the Founder above it, and codes each charge with its receipt. |
| Experiment | Noun | An Experiment is a test of a Hypothesis that varies copy or behavior through Flags and judges the variants by a primary Metric. |
| Experiment.conclude | Verb | Conclude ends an Experiment with a decision to ship, kill, or iterate, recorded as a Decision. |
| Experiment.start | Verb | Start opens an Experiment, splits traffic across its variants, and begins measuring its primary and guardrail Metrics. |
| Experimentation | Process | Experimentation tests one change against a control, with the threshold fixed before the start. |
| Experiments | System | Experiments tests Hypotheses by varying copy, Price or behavior through Flags and decides each winner from primary and guardrail Metrics. |
| Export controls | Legal floor row | Export controls classifies Software with encryption before export and refuses delivery to embargoed destinations and listed parties. |
| Exposure | Noun | An Exposure is the moment one unit meets the Variant its Flag assigned, logged with every option and its propensity. |