Vision

ChargeAid documentation should provide a single private source of truth for:

• current architecture
• integration boundaries
• deployment topology
• runtime behavior
• data model and migrations
• engineering decisions
• operational procedures
• near-term roadmap

Documentation principles

1. Facts should be generated where possible.
2. Intent should be documented explicitly by humans.
3. Architecture diagrams should live in source control.
4. Every important design choice should have an ADR.
5. The docs portal should be readable by engineering, product, and operations.

Success criteria

A new engineering session should be able to answer these quickly:

• What exists today?
• Which modules own which responsibilities?
• How does the UI talk to the backend?
• Which provider adapters exist and why?
• Which databases, services, and domains are involved?
• What is being built next?