Facet
DeutschInstall

FOR ENGINEERING LEADS AND DOMAIN TEAMS

Your release was green. Ours is broken now.

Team A changes a rule, team B quietly depended on it, and both find out in the incident channel. FACET makes visible who depends on which rule — before the change goes live, not after.

Orders teamcheckout/

RECORDdocs/facets/features/checkout/orders/cancellation.yaml
id: checkout/orders/cancellationlineage:  owner:    team: orders  depended_on_by:    - billing/invoicing/cancelled-order-no-invoice

Billing teambilling/

RECORDdocs/facets/features/billing/invoicing/cancelled-order-no-invoice.yaml
id: billing/invoicing/cancelled-order-no-invoicelineage:  owner:    team: billing  depends_on:    - checkout/orders/cancellation

Illustrative example · two registries, declared in .facetrc.yaml

THE CHANGE AT A TEAM BOUNDARY

Orders changes a rule. Billing hears about it before the release.

“It is cancelled on our side.” — “It is billable on our side.” Two teams, two repositories, one product. When the cancellation window grows, FACET shows which other team depends on that rule — and the review knows whom to ask.

RECORDcheckout/orders/cancellation.yaml
contract:  scenarios:    - id: cancel-before-shipping      when: the order is cancelled before shipping      when: the order is cancelled up to 24 h after shipping      then: the order is cancelled and leaves picking

lineage · who depends on this?

recordedbilling/invoicing/cancelled-order-no-invoice

The billing team wrote this relationship into its record. That is why it is named — not because FACET searched both teams' code.

unknownWhat nobody recorded stays invisible.

Illustrative example · facet registries shows which registry documents which feature ids; facet lint checks every depends_on reference

ONE SHARED VOCABULARY

“Cancelled” means the same to us as it does to you.

What only concerns one team stays with that team. Terms both of them use are defined once — and both teams point at the same definition instead of two opinions.

GLOSSARYdocs/facets/glossary.yaml
terms:  - term: cancelled    category: order-state    definition: the buyer or the shop ended the order; nothing is shipped and nothing is invoiced
Used in
checkout/orders/cancellation

A cancelled order leaves picking.

billing/invoicing/cancelled-order-no-invoice

A cancelled order produces no invoice.

Illustrative example · facet lint warns when a word in intent.summary is only nearly a glossary term

WHAT FACET DOES NOT DO HERE

Deliver independently. Understand together.

FACET only knows recorded relationships. It is not a complete automatic impact analysis.