- Postgres: every table has a uuid `id` (gen_random_uuid()); the event store keeps its relay order in `seq`, and the lookup tables their uniqueness in constraints of their own. - MongoDB: `_id` is Mongo's ObjectId; `id` is the domain id (the same uuid as the aggregate's stream in Postgres), unique, and every query goes by it. Production starts from empty databases. - Web: linking tickets and hanging one from a parent are picked from a searchable select (links across projects, parents within the project) instead of typing a key; every checkbox is @pi/ui's pi-checkbox. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
api-identity-infrastructure
Adaptadores de salida de identidad.
- Import:
@task-stream/api/identity/infrastructure - Capa:
infrastructure· Tags:scope:api-identity,type:infrastructure
Contenido
PireonIdentityProvider:GET /api/user,/api/usersyPOST /oauth/tokende Pireon.RedisSessionCache: tokens validados, guardados por hash SHA-256 y con TTL.MongoUserRegistry: copia local de usuarios (colecciónusers).
Comandos
npx nx lint api-identity-infrastructure
npx nx test api-identity-infrastructure # Jest
Reglas de dependencia entre capas: Arquitectura.