startups as

Statements.Email statements.email

namespace seednamespace

Statement delivery as an evidence-carrying record rather than an attachment, on the email rail: what was sent, when, and proof it was delivered, plus the same statement parsed for the agent that receives it.

From the Startup card at api.sb/statements.email · Designed · Service, App.

contested · 1 tension

tier: namespace · projection lens A reads namespace (namespace); lens B reads projection (brand)

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

Tier	namespace	Inferred · med · portfolio-lens-a.tsv (tier)
Status	namespace seed	Inferred · med · lens A tier namespace
Product kind	—	no provenance
Core noun	Ledger	Inferred · low · seed rule: the unit noun of lens B abstraction V-ledger (portfolio-lens-b.md §1)
Buyer and position	Deliverable Mint: "statements"	Inferred · med · portfolio-lens-b.tsv (icp_or_position)
Closed set or journey	S20 [task].email semantic-TLD work rails	Inferred · med · portfolio-lens-a.tsv (set_or_journey)
Abstraction	V-ledger	Inferred · med · portfolio-lens-b.tsv (abstraction)
Role (lens B)	projection	Inferred · med · portfolio-lens-b.tsv (role)
Registrar	dynadot	Inferred · high · holdings ledger (domains repo, read-only)

Its stack

Generated around Statements.Email

                              Statements.Email                  centre
                                      │
                                APIs.Finance                    the businesses
                                      │
                                 Headless.ly                    the abstractions
                                      │
                                 SaaS.Studio                    the abstractions
                                      │
                                   API.SB                       brands
                                      │
   Startups.Studio ───────── StartupBuilder.Dev                 brands

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

Same abstraction (V-ledger)

MonthEnd.Finance Accruals.Finance Amortizations.Finance Controllers.Finance Forecasts.Finance Reconciliations.Finance Variances.Finance Accounting.do Accounts.do Billing.do Bookkeeper.do Budgeting.do Close.do Collections.do Dunning.do Financial.do Financials.do Forecasting.do Invoices.do Invoicing.do Ledger.do Ledgers.do Payables.do Receivables.do Reconcile.do Bookkeepi.ng Coas.Click Fluxanalysis.co Journalentries.co Reconcile.Click Reconciliations.Click Reimbursements.Click Trialbalance.co

Listed by

no discovery view lists it yet

In logo rows

APIs.Finance's row specified
MonthEnd.Finance's row buildable

Slices

in no slice

Relationships (2)

from	verb	to	provenance
Statements.Email	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	APIs.Finance	Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified sb def statements.email: built on apis.finance [high] — "Its page: a work product of the apis.finance family register, contact keys@apis.finance."
Statements.Email	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	MonthEnd.Finance	Inferred · low · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvbuildable sb def statements.email: built on monthend.finance [low] — Statements are prepared from the closed period (the r2 route placed it on the books spine; stated, not observed, F-B3-09).

Edit log

loading the versions of this record from api.sb…

Machine-readable: /statements.email.json