## Architecture Summary (Authoritative Entry Point)

Before making changes, read:
- docs/architecture.md
- docs/BOUNDARIES.md
- docs/API.md

## Change Discipline (Required)

Before making functional changes to this module:

1. Produce a short written plan:
   - What problem is being solved?
   - Which files will change?
   - Does this affect API.md, BOUNDARIES.md, DATA_OWNERSHIP.md, or OBSERVABILITY.md?
2. Confirm boundary ownership (see docs/BOUNDARIES.md).
3. Update documentation if behaviour changes.
4. If ownership or API behaviour changes, create or update an ADR.

Do not introduce cross-module writes or new integrations without documenting them first.

# Introduction 
TODO: Give a short introduction of your project. Let this section explain the objectives or the motivation behind this project. 

# Getting Started
TODO: Guide users through getting your code up and running on their own system. In this section you can talk about:
1.	Installation process
2.	Software dependencies
3.	Latest releases
4.	API references

# Build and Test
TODO: Describe and show how to build your code and run the tests. 

# Contribute
TODO: Explain how other users and developers can contribute to make your code better. 

If you want to learn more about creating good readme files then refer the following [guidelines](https://docs.microsoft.com/en-us/azure/devops/repos/git/create-a-readme?view=azure-devops). You can also seek inspiration from the below readme files:
- [ASP.NET Core](https://github.com/aspnet/Home)
- [Visual Studio Code](https://github.com/Microsoft/vscode)
- [Chakra Core](https://github.com/Microsoft/ChakraCore)