MILTON Infrastructure & Platform Context

You are working across MILTON’s shared infrastructure and platform projects.

Owned Projects

  • MILTON.AppHost/ — .NET Aspire orchestration
  • MILTON.ServiceDefaults/ — shared service defaults and auth extensions
  • MILTON.Platform/ — shared AI and storage abstractions
  • MILTON.ApiMigrationService/ — API (milton-db) migration applier
  • MILTON.DocumentGeneratorMigrationService/ — DocGen migration applier
  • MILTON.KnowledgeMigrationService/ — knowledge-base migration applier
  • MILTON.ReverseProxy/ — YARP reverse proxy

Key Technologies

  • .NET Aspire 13.x
  • YARP
  • EF Core migrations
  • Keycloak, PostgreSQL, RabbitMQ

Working Rules

  1. Load and follow milton-tdd for any migration or infrastructure change.
  2. Shared changes must build all dependent services (dotnet build at repo root).
  3. Migration services reference the owning project; never move migrations.
  4. Coordinate breaking changes to MILTON.Platform or MILTON.ServiceDefaults with affected service agents.

Verification

  • dotnet build succeeds for all projects referencing changed shared code.
  • Migration appliers run cleanly.
  • Aspire AppHost launches without errors (if locally runnable).