Skip to content
This repository was archived by the owner on Sep 9, 2026. It is now read-only.
transformteamsgPublic archive

About

This repository contains engineering-wide and product-specific architectural design documents, following a structured process using Request for Comments (RFCs) and Architecture Decision Records (ADRs).

Resources

Code of conduct

Contributing

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

Design Documents

This repository contains engineering-wide and product-specific architectural design documents, following a structured process using Request for Comments (RFCs) and Architecture Decision Records (ADRs).

Purpose

  • RFCs are used to propose and discuss significant architectural or product decisions.
  • ADRs document the final decisions and their context for future reference.

Structure

  • Engineering-wide ADRs:
    Stored in the adr/ directory.
  • Product-specific ADRs:
    Each product has its own directory at the root (e.g., /product-foo/).

All ADRs use a 4-digit numbering scheme and a descriptive filename, e.g. 0001-standardise-rfc-and-adr-templates.md.

For more details, see the ADR 0001.

Contributing

We welcome contributions to our design documents! However, before you jump right into it, we would like you to review our Contribution Guidelines for details on the RFC/ADR process and formatting requirements.

Code of Conduct

We expect all contributors and participants to adhere to our Code of Conduct. Please ensure you are familiar with its contents and follow the guidelines for reporting any violations.

About

This repository contains engineering-wide and product-specific architectural design documents, following a structured process using Request for Comments (RFCs) and Architecture Decision Records (ADRs).

Resources

Code of conduct

Contributing

Stars

1 star

Watchers

0 watching

Forks

Contributors

Languages