• Product Vision - strategy, product goals, and business positioning.
• Architecture Portal - architectural overview, bounded contexts, domain model.
• Domain Model - ubiquitous language, bounded contexts, aggregates.
• Master Index - complete documentation navigation.
• Evolith Upstream - corporate reference base inherited by Tracker.

• Architects: start with Target Architecture, then review DECISIONS.md and Core Integration Design.
• Backend developers: start with .NET Backend Design, then review PostgreSQL Data Design and Platform Implementation.
• Frontend developers: start with React Frontend Design, then review Web Integration.
• Product and PM: start with Product Vision, then review User Stories and GAP Register.
• DevOps and SRE: start with Infrastructure Plan, then review Observability Spec.
• AI contributors: start with AGENTS.md, then review BMAD Agents.

• Discovery Domain
• Design Domain
• Construction Domain
• QA Domain
• Release Domain
• Governance Domain
• Artifacts Domain
• Metrics Domain
• Integration Domain
• Security Specification
• UMS Authentication Integration

• Tracker inherits reusable architecture standards, governance rules, ADR patterns, and documentation practices from Evolith.
• Tracker keeps product-specific implementation, bounded contexts, schemas, and runtime behavior in this repository.
• Product ADRs may be promoted upstream when Tracker provides executable evidence that the decision is reusable across products.
• Multi-tenancy is enforced primarily at the application layer. PostgreSQL policies, constraints, schema ownership, and row-level security are secondary infrastructure failsafes.

Run technical commands from src/ unless the command explicitly targets the backend solution.

# Install frontend dependencies
cd src
npm install

# Frontend: React 19 and Vite
npx vite build --config apps/tracker-web/vite.config.mts

# Backend: .NET 10
cd apps/tracker-api
dotnet build
dotnet run

# Backend tests
dotnet test

# From the repository root
python3 .bmad-core/scripts/cleanup_markdown_encoding.py

Documentation changes must keep English and Spanish artifacts synchronized, preserve UTF-8 integrity, and avoid decorative icons or non-standard Markdown characters.