cbd catalog

The catalog holds 12 documents, 2 events, 4 repositories, 2 services and 41 relationships.

Explore

---

5 places

• Knowledge graph

  Every resource and relationship, with where each fact was read from.
• Services

  What each service publishes and consumes, inferred from the events.
• Fields

  Every field across every event, and who a change to it would reach.
• Owners

  The teams the catalog names, and everything each one owns.
• For agents

  llms.txt, a Markdown twin of every document, and the graph as JSON.

Documents

---

12 documents from 4 repositories

cbd-dashboard

3 documents

• Reading the payments contract from the dashboard

  Owned by web-platform, updated 26 Sept 2026

  frontend, contracts, openapi
• Web platform team

  Owned by web-platform, updated 26 Sept 2026

  team
• What the dashboard shows

  Owned by web-platform, updated 26 Sept 2026

  product, dashboard, payments

cbd-handbook

2 documents

• Incident communications: who says what, when

  Owned by customer-operations, updated 26 Sept 2026

  incident, communications, policy
• Repository layout

  Owned by platform, updated 18 Oct 2026

  conventions, docs, contracts

cbd-payments-service

4 documents

• One contract from browser to broker

  Owned by payments-platform, updated 26 Sept 2026

  architecture, contracts, frontend, messaging
• How a payment works

  Owned by payments-platform, updated 26 Sept 2026

  domain, payments, lifecycle
• Payments service runbook

  Owned by payments-platform, updated 26 Sept 2026

  runbook, payments
• Payments platform team

  Owned by payments-platform, updated 26 Sept 2026

  team, on-call

cbd-reporter

3 documents

• The daily settlement report

  Owned by data-platform, updated 26 Sept 2026

  product, finance, reporting
• Data platform team

  Owned by data-platform, updated 26 Sept 2026

  team
• Validating payment events in Python

  Owned by data-platform, updated 18 Oct 2026

  python, events, json-schema

By tag

---

23 tags

Tag	Documents
architecture	One contract from browser to broker
communications	Incident communications: who says what, when
contracts	Reading the payments contract from the dashboard, Repository layout, One contract from browser to broker
conventions	Repository layout
dashboard	What the dashboard shows
docs	Repository layout
domain	How a payment works
events	Validating payment events in Python
finance	The daily settlement report
frontend	Reading the payments contract from the dashboard, One contract from browser to broker
incident	Incident communications: who says what, when
json-schema	Validating payment events in Python
lifecycle	How a payment works
messaging	One contract from browser to broker
on-call	Payments platform team
openapi	Reading the payments contract from the dashboard
payments	What the dashboard shows, How a payment works, Payments service runbook
policy	Incident communications: who says what, when
product	What the dashboard shows, The daily settlement report
python	Validating payment events in Python
reporting	The daily settlement report
runbook	Payments service runbook
team	Web platform team, Payments platform team, Data platform team