Create an ARCHITECTURE.md File

Purpose

The overall purpose of this task is twofold:

1. Precisely map the end-to-end call graph for each feature the project provides.
2. Build a crisp state machine that captures each feature’s flow.

Strategy

Work in a layered approach. Like an oil painter, treat the codebase as the canvas and your task as the drawing. Make multiple passes over the codebase to cultivate a deep understanding of it:

• Start by getting a sense of the overall structure and how the pieces fit together
• Add detail gradually, pass by pass
• Refine the whole system together instead of finishing one part completely before moving on
• Block in the broad areas first, then build up layers of detail across the entire codebase

The end result should be a sharp and precise ARCHITECTURE.md with a clear specification of available user interactions → state transitions (#purpose-1), and user interactions → call graphs (#purpose-2).