domain

name	domain
description	Use when creating domain layer artifacts for a NestJS bounded context — entities (AggregateRoot), value objects, domain events, repository interfaces, domain services, validators, or data builders. Covers Hexagonal Architecture + DDD patterns with NestJS CQRS native event support.
argument-hint	Artifact type or entity name (e.g., "entity Order", "vo OrderStatus", "event OrderCreated")

Domain Layer

The domain layer contains the pure business logic of a bounded context. It has zero framework dependencies except @nestjs/cqrs for AggregateRoot (entity base class). No @Injectable, no PrismaService, no HTTP concerns.

---

Decision Tree

What are you creating?

Domain artifact needed?
│
├── An entity (aggregate root with lifecycle methods)
│   └── Go to: Entity Pattern
│
├── A simple value (email, amount, name, phone)
│   └── Go to: VO — Scalar
│
├── A grouped value (address, bank details, money)
│   └── Go to: VO — Composed
│
├── A fixed set of values (payment method, channel type)
│   └── Go to: VO — Enum
│
├── A status with allowed transitions (order status, withdrawal status)
│   └── Go to: VO — State Machine
│
├── The persistence contract for the entity
│   └── Go to: Repository Interface
│
├── Something that happened in the domain
│   └── Go to: Domain Events
│
├── Logic that belongs to the domain but not to one entity
│   └── Go to: Domain Services
│
├── A domain-specific error with context
│   └── Go to: Domain Errors
│
├── Entity invariant enforcement (field-level rules)
│   └── Go to: Validators
│
└── Fake data for tests
    └── Go to: Data Builders

---

Entity Pattern

Full reference: references/entity-patterns.md

An entity is identified by its UniqueEntityID, not by its value. It extends AggregateRoot from @nestjs/cqrs so that events flow through the NestJS EventBus once committed.

Two factory methods are mandatory:

• static create(props, id?) — for new instances; calls this.apply(new XCreatedEvent(...))
• static restore(props, id) — for DB hydration; emits no events

Event lifecycle (every entity follows this):

entity.apply(event)            // 1. records the event in memory
publisher.mergeObjectContext(entity)  // 2. wires EventBus (in handler)
await repo.save(entity)        // 3. persists
entity.commit()                // 4. publishes events to EventBus

Condensed template:

// domain/entities/<name>.entity.ts
import { Entity } from '@/shared/base-classes/entity';
import { <Name>CreatedEvent } from '../events/<name>-created.event';

export interface <Name>Props {
  tenantId: string;
  // ... business fields
  createdAt: Date;
  updatedAt?: Date;
}

export class <Name>Entity extends Entity<<Name>Props> {
  private constructor(props: <Name>Props, id?: string) {
    super(props, id);
  }

  static create(
    input: Omit<<Name>Props, 'createdAt' | 'updatedAt'>,
    id?: string,
  ): <Name>Entity {
    const entity = new <Name>({ ...input, :  () }, id);
    entity.( <>(entity.));
     entity;
  }

   (: <>, : ): <> {
      <>(props, id);
  }

  
  (: ):  {
    .. = name;
    .();
    .( <>(., name));
  }

   ():  {  ..; }
  

   ():  {  ..; }
   ():  |  {  ..; }
}

See references/entity-patterns.md for: child entities, validate() integration, toJSON() override, and the full test template.

---

Value Object Variants

Full reference: references/value-object-patterns.md

All VOs extend ValueObject<T> from @/shared/base-classes/value-object. Rules:

• Constructor is private — only static factories create instances
• validate() throws on invariant violations; it is called automatically in the constructor
• Never import @nestjs/* or class-validator in a VO

Scalar VO (single value)

// domain/value-objects/email.vo.ts
import { ValueObject } from '@/shared/base-classes/value-object';
import { InvalidArgumentError } from '@/shared/domain-errors/errors';

export class EmailVO extends ValueObject<string> {
  private constructor(value: string) { super(value); }

  protected validate(): void {
    if (!/^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(this._value)) {
      throw new InvalidArgumentError(`Invalid email: "${this._value}"`);
    }
  }

  static create(email: string): EmailVO {
    return new EmailVO(email.toLowerCase().trim());
  }

  get domain(): string { return this._value.()[]; }
}

Composed VO (multiple props)

// domain/value-objects/address.vo.ts
import { ValueObject } from '@/shared/base-classes/value-object';
import { InvalidArgumentError } from '@/shared/domain/errors';

interface AddressProps { street: string; city: string; country: string; }

export class AddressVO extends ValueObject<AddressProps> {
  private constructor(props: AddressProps) { super(props); }

  protected validate(): void {
    if (!this._value.street) throw new InvalidArgumentError('Street is required');
    if (!this._value.city)   throw new InvalidArgumentError('City is required');
    if (!this._value.country)   ();
  }

   (: ):  {
      (props);
  }

   ():   {  ..; }
   ():     {  ..; }
   ():  {  ..; }
}

Enum VO (fixed set of named values)

// domain/value-objects/payment-method.vo.ts
import { ValueObject } from '@/shared/base-classes/value-object';

export enum PaymentMethodEnum { CREDIT = 'CREDIT', DEBIT = 'DEBIT', PIX = 'PIX' }

export class PaymentMethodVO extends ValueObject<PaymentMethodEnum> {
  private constructor(value: PaymentMethodEnum) { super(value); }

  protected validate(): void {
    if (!Object.values(PaymentMethodEnum).includes(this._value)) {
      throw new InvalidArgumentError(`Unknown payment method: ${this._value}`);
    }
  }

  static credit(): PaymentMethodVO { return new PaymentMethodVO(PaymentMethodEnum.CREDIT); }
   ():   {   (.); }
   ():     {   (.); }

   (: ):  {
      (value  );
  }

  ():  {  . === .; }
  ():     {  . === .; }
}

State Machine VO (controlled transitions)

// domain/value-objects/order-status.vo.ts
import { ValueObject } from '@/shared/base-classes/value-object';

export enum OrderStatusEnum {
  PENDING = 'PENDING', CONFIRMED = 'CONFIRMED', SHIPPED = 'SHIPPED', COMPLETED = 'COMPLETED',
}

const ALLOWED_TRANSITIONS: Record<OrderStatusEnum, OrderStatusEnum[]> = {
  [OrderStatusEnum.PENDING]:    [OrderStatusEnum.CONFIRMED],
  [OrderStatusEnum.CONFIRMED]:  [OrderStatusEnum.SHIPPED],
  [OrderStatusEnum.SHIPPED]:    [OrderStatusEnum.COMPLETED],
  [OrderStatusEnum.COMPLETED]:  [],
};

export class OrderStatusVO extends ValueObject<OrderStatusEnum> {
  private constructor(value: OrderStatusEnum) { super(value); }

  protected validate():  {
     (!.().(.)) {
        ();
    }
  }

   ():    {   (.); }
   ():  {   (.); }

   (: ):  {
      (value  );
  }

  (: ):  {
     [.].(target);
  }

  (: ):  {
     (!.(target)) {
        (
        ,
      );
    }
      (target);
  }

  ():    {  . === .; }
  ():  {  . === .; }
}

See references/value-object-patterns.md for full VO test templates and edge-case guidance.

---

Repository Interface

Full reference: references/repository-interface.md

The repository interface is the domain's port for persistence. It lives in domain/repositories/. The implementation lives in infrastructure/. No @Injectable or Prisma imports here.

// domain/repositories/<name>.repository.ts
import type { <Name>Entity } from '../entities/<name>.entity';
import {
  SearchParams as DefaultSearchParams,
  SearchResult as DefaultSearchResult,
  SearchableRepositoryInterface,
} from '@/shared/repository-contracts/searchable-repository-contracts';

export namespace <Name>Repository {
  export type Filter = string;
  export class SearchParams extends DefaultSearchParams<Filter> {}
  export class SearchResult extends DefaultSearchResult<<Name>Entity, Filter> {}

  export interface Repository
    extends SearchableRepositoryInterface<
      <Name>Entity, Filter, SearchParams, SearchResult
    > {
    findById(: ): <<> | >;
    (: ): <<>[]>;
    (: <>): <>;
    (: ): <>;
  }
}

  <>_REPOSITORY = ();

See references/repository-interface.md for: extended SearchParams with custom filters, domain-specific query methods, and the in-memory test double pattern.

---

Domain Events

Full reference: references/domain-event-patterns.md

Domain events capture what happened in the domain. They implement IEvent from @nestjs/cqrs.

Naming: <Entity><PastTenseVerb>Event (e.g., OrderPlacedEvent, CustomerActivatedEvent)

// domain/events/<name>-created.event.ts
import { IEvent } from '@nestjs/cqrs';

export class <Name>CreatedEvent implements IEvent {
  constructor(
    public readonly <name>Id: string,
    public readonly tenantId: string,
    // include all data handlers will need
  ) {}
}

Rules:

• Events are applied via entity.apply(event) inside entity methods
• The handler calls publisher.mergeObjectContext(entity) then entity.commit() to publish
• Event handlers use @EventsHandler + IEventHandler — never @OnEvent for new code
• Include enough payload so handlers do not need to re-fetch the entity

See references/domain-event-patterns.md for: full event catalog pattern, testing uncommitted events, and handler template.

---

Domain Services

Full reference: references/domain-service-patterns.md

Use a domain service when a domain operation involves multiple entities or rules that do not belong to a single entity. Domain services are pure classes — no decorators, no DI, no I/O.

// domain/services/<name>.service.ts
export class FeeCalculationService {
  static calculate(amount: number, feePercentage: number): number {
    if (amount <= 0) throw new InvalidArgumentError('Amount must be positive');
    return Math.round(amount * (feePercentage / 100));
  }
}

When to use:

• Logic spans two or more aggregates
• A calculation or rule is shared by multiple entity methods
• The operation is stateless and has no side effects

When NOT to use:

• Logic belongs clearly to a single entity → put it in the entity
• Logic requires I/O (DB, queue) → use an application service in the application/ layer

See references/domain-service-patterns.md for: stateful services, integration examples, and test templates.

---

Validators

Full reference: references/validator-patterns.md

Validators enforce entity invariants (field-level rules) using class-validator decorators on a Rules class, executed via ClassValidatorFields. This is for domain validation only — not for HTTP input validation.

// domain/validators/<name>.validator.ts
import { IsString, IsNotEmpty, IsUUID, IsOptional, MaxLength } from 'class-validator';
import { ClassValidatorFields } from '@/shared/base-classes/class-validator-fields';
import type { <Name>Props } from '../entities/<name>.entity';

class <Name>Rules {
  @IsUUID() @IsNotEmpty() tenantId: string;
  @IsString() @IsNotEmpty() @MaxLength(255) name: string;
  @IsOptional() @IsString() description?: string;

  constructor(props: <Name>Props) { Object.assign(this, props); }
}

class <Name>Validator extends ClassValidatorFields<<Name>Rules> {
  validate(: <>):  {
     .( <>(data));
  }
}

  <> {
   (): <> {   <>(); }
}

Usage in entity:

static validate(props: <Name>Props): void {
  const validator = <Name>ValidatorFactory.create();
  if (!validator.validate(props)) {
    throw new EntityValidationError(validator.errors);
  }
}

See references/validator-patterns.md for: the ClassValidatorFields base, nested validation, and full test template.

---

Data Builders

Full reference: references/data-builder-patterns.md

Data builders provide deterministic fake data for unit tests. They live in domain/testing/helpers/.

// domain/testing/helpers/<name>.data-builder.ts
import { faker } from '@faker-js/faker';
import type { <Name>Props } from '../../entities/<name>.entity';

export function <Name>DataBuilder(overrides?: Partial<<Name>Props>): <Name>Props {
  return {
    tenantId: overrides?.tenantId ?? faker.string.uuid(),
    name:     overrides?.name     ?? faker.commerce.productName(),
    createdAt: overrides?.createdAt ?? new Date(),
    updatedAt: overrides?.updatedAt,
    ...overrides,
  };
}

See references/data-builder-patterns.md for: composed builders, state-specific variants (Active, Pending, Rejected), and how to wire builders into test describe blocks.

---

Domain Errors

Specialized errors that extend the shared error hierarchy (DomainError, NotFoundError, ConflictError, etc.) with domain-specific context.

Live in <bc>/domain/errors/. Name convention: <Entity><Condition>Error.

// domain/errors/order-not-found.error.ts
import { NotFoundError } from '@/shared/domain/errors';

export class OrderNotFoundError extends NotFoundError {
  constructor(public readonly orderId: string) {
    super(`Order ${orderId} not found`);
  }
}

// domain/errors/invalid-order-status-transition.error.ts
import { DomainError } from '@/shared/domain/errors';

export class InvalidOrderStatusTransitionError extends DomainError {
  constructor(
    public readonly currentStatus: string,
    public readonly targetStatus: string,
  ) {
    super(`Cannot transition from ${currentStatus} to ${targetStatus}`);
  }
}

When to specialize: When the error carries domain context (IDs, amounts, statuses) that helps debugging. Don't specialize if the generic message is sufficient.

See references/domain-error-patterns.md for: full error catalog, naming conventions, error filter mapping, testing patterns.

---

Rules and Anti-Patterns

What belongs in the domain layer

• Entity classes, VO classes, domain events, repository interfaces, domain service classes, validators
• Types and interfaces that describe domain concepts

What does NOT belong here

Anti-pattern	Correct approach
import { Injectable } from '@nestjs/common'	Only allowed in infrastructure/ and application/services/
import { PrismaService }	Only in Prisma repository implementations
import { IsEmail } from 'class-validator'	Only in validators (not in VOs)
new PrismaClient() inside an entity	Repositories handle persistence
Calling another aggregate's repository	Use a domain service or application service
Throwing HTTP exceptions (NotFoundException)	Throw domain errors; HTTP mapping is in infrastructure/
entity.addDomainEvent() / entity.pullDomainEvents()	Use entity.apply(event) (NestJS CQRS native)

Event invariants

• create() ALWAYS calls this.apply(new XCreatedEvent(...))
• restore() NEVER emits events
• Mutating methods call this.touch() then this.apply(new XUpdatedEvent(...))
• The repository saves the entity; the CQRS handler commits events

VO invariants

• VOs are immutable — mutating methods return a NEW VO instance
• State Machine VOs always validate transition legality in transitionTo()
• Enum VOs provide named static factories (static pending()) — callers never pass raw strings

---

Testing

Entity spec skeleton

// domain/entities/__tests__/unit/<name>.entity.spec.ts
import { describe, it, expect, beforeEach } from 'vitest';
import { <Name>Entity } from '../../<name>.entity';
import { <Name>DataBuilder } from '../../../testing/helpers/<name>.data-builder';
import { <Name>CreatedEvent } from '../../../events/<name>-created.event';

describe('<Name>Entity', () => {
  describe('create()', () => {
    it('should create entity with valid props', () => {
      const props = <Name>DataBuilder();
      const entity = <Name>Entity.create(props);

      expect(entity.id).toBeDefined();
      expect(entity.name).toBe(props.name);
      expect(entity.createdAt).toBeInstanceOf(Date);
    });

    it('should apply <Name>CreatedEvent',  {
       entity = <>.(<>());
       events = entity.();

      (events).();
      (events[]).(<>);
    });
  });

  (,  {
    (,  {
       props = <>();
       entity = <>.(props, faker..());

      (entity.()).();
    });
  });

  (,  {
    (,  {
       entity = <>.(<>());
      entity.(); 

      entity.();

      (entity.).();
      (entity.).();
    });
  });
});

VO spec skeleton

// domain/value-objects/__tests__/<name>.vo.spec.ts
import { describe, it, expect } from 'vitest';
import { EmailVO } from '../email.vo';

describe('EmailVO', () => {
  it('should create from valid email', () => {
    const vo = EmailVO.create('[e-mail]');
    expect(vo.value).toBe('[e-mail]');
  });

  it('should throw on invalid email', () => {
    expect(() => EmailVO.create('not-an-email')).toThrow();
  });

  it('should be equal when value matches', () => {
    expect(EmailVO.create('[e-mail]').equals(EmailVO.create('[e-mail]'))).toBe(true);
  });
});