Team ownership
Which platform teams own the major Acme Inc domains and systems documented in the default catalog.
Ownership in the default catalog is modelled with team resources. The owning team is responsible for contract changes, service reliability and documentation freshness for its resources.
Teams by capability
| Team | Owns |
|---|---|
| Product PlatformProduct PlatformTeam•vOwns the Product Catalog System — the source of truth for product data at Acme Inc.View docs | CatalogCatalogDomain•v1.0.0The Catalog domain owns everything about products — how they are created, maintained and made discoverable across Acme I...Ownerproduct-platformMapView docs, Product Catalog SystemProduct Catalog SystemSystem•v1.0.0Internal system that is the source of truth for product data. Owns the product database and publishes product change eve...Ownerproduct-platformMapView docs and product APIs/workers. |
| Search PlatformSearch PlatformTeam•vOwns the Search System — keeps the catalog discoverable through fast, relevant product search.View docs | Search SystemSearch SystemSystem•v1.0.0Internal system that keeps product data searchable. Consumes product change events from the Product Catalog System, main...Ownersearch-platformMapView docs, search indexing and search query contracts. |
| Shopping PlatformShopping PlatformTeam•vOwns the Shopping domain — the cart and the promotions applied to it.View docs | ShoppingShoppingDomain•v1.0.0The Shopping domain owns the customer's path to purchase — building a cart, applying promotions, and checking out. It co...Ownershopping-platformMapView docs, Cart SystemCart SystemSystem•v1.0.0Internal system that owns the customer's shopping cart and the checkout flow. It is the source of truth for cart content...Ownershopping-platformMapView docs and Promotion SystemPromotion SystemSystem•v1.0.0Internal system that calculates the discounts and promotions that apply to a cart. It owns promotion rules and returns c...Ownershopping-platformMapView docs. |
| Ordering PlatformOrdering PlatformTeam•vOwns the Ordering domain — turning a checked-out cart into a confirmed order.View docs | OrderingOrderingDomain•v1.0.0The Ordering domain turns a checked-out cart into a confirmed order. It orchestrates checkout — reserving inventory, aut...Ownerordering-platformMapView docs, Checkout SystemCheckout SystemSystem•v1.0.0Internal system that orchestrates checkout. When a cart is checked out it reserves inventory, authorizes payment, and as...Ownerordering-platformMapView docs and Order Management SystemOrder Management SystemSystem•v1.0.0Internal system that is the source of truth for orders. It creates orders, tracks their lifecycle, and publishes events ...Ownerordering-platformMapView docs. |
| Payments PlatformPayments PlatformTeam•vOwns the Payments domain — authorizing payments, processing refunds, and integrating with external payment and fraud pro...View docs | PaymentsPaymentsDomain•v1.0.0The Payments domain takes payment for orders and processes refunds. It orchestrates authorization and capture through an...Ownerpayments-platformMapView docs and Payment Processing SystemPayment Processing SystemSystem•v1.0.0Internal system that orchestrates payment for orders. It authorizes payments, requests charges from the external payment...Ownerpayments-platformMapView docs. |
| Fulfilment PlatformFulfilment PlatformTeam•vOwns the Fulfilment domain — reserving stock, picking and packing orders, and shipping them to customers.View docs | FulfilmentFulfilmentDomain•v1.0.0The Fulfilment domain gets a confirmed order to the customer. It reserves stock, picks and packs orders in the warehouse...Ownerfulfilment-platformMapView docs, inventory, warehouse and shipping systems. |
| Customer PlatformCustomer PlatformTeam•vOwns the Customer domain — customer profiles and authentication across Acme Inc.View docs | CustomerCustomerDomain•v1.0.0The Customer domain owns who our customers are — how they register, how their profile is maintained, and how they are au...Ownercustomer-platformMapView docs, customer profile and identity systems. |
| Reviews PlatformReviews PlatformTeam•vOwns the Reviews & Ratings domain — how customers review products and how those reviews are moderated, published and agg...View docs | Reviews & RatingsReviews & RatingsDomain•v1.0.0The Reviews & Ratings domain owns customer feedback on products — how reviews are submitted, moderated, published and ag...Ownerreviews-platformMapView docs, review moderation and rating aggregation. |
Ownership rules
The owner listed on the producing resource owns the contract. Consumers can request changes, but producers decide versioning and rollout.
When a flow spans multiple teams, the team owning the orchestrator is responsible for keeping the flow page current. For checkout, that is Ordering PlatformOrdering PlatformTeam•vOwns the Ordering domain — turning a checked-out cart into a confirmed order.View docs.
Documentation expectations
Every resource page should explain responsibility, owners and major contracts. These custom docs should explain cross-resource narratives that do not belong to one resource.