V3 Core Implementation

Start with base classes for Entity, ValueObject, and AggregateRoot, then organize code into bounded contexts under a domains directory. Each domain contains entities, value objects, services, repositories, and events, with use cases in an application layer orchestrating the aggregates.

Separate code into core domains, a shared kernel with base domain classes and infrastructure, and an application layer with use cases, commands, and queries. Use path aliases like @core and @domains in tsconfig to enforce clean import boundaries.

Inversify works with TypeScript decorators when experimentalDecorators and emitDecoratorMetadata are enabled in tsconfig. Bind interfaces to implementations in a container using symbols as service identifiers, then resolve dependencies through constructor injection.

Unit test entities by verifying state transitions and emitted domain events, such as checking that assigning a task changes its status and raises a TaskAssignedEvent. For repositories, run integration tests against an in-memory SQLite database to validate save and query behavior.

Use the repository pattern when domain logic must stay independent of persistence details. Define an interface like ITaskRepository in the domain, then provide a SQLite implementation that maps database rows back to reconstituted aggregates.