lcbp3/.agents/rules/05-forbidden-actions.md

Forbidden Actions

❌ Never Do This

❌ Forbidden	✅ Correct Approach
SQL Triggers for business logic	NestJS Service methods
.env files in production	docker-compose.yml environment section
TypeORM migration files	Edit schema SQL directly (ADR-009)
Inventing table/column names	Verify against lcbp3-v1.9.0-schema-02-tables.sql
any TypeScript type	Proper types / generics
console.log in committed code	NestJS Logger (backend) / remove (frontend)
req: any in controllers	RequestWithUser typed interface
parseInt() on UUID values	Use UUID string directly (ADR-019)
Exposing INT PK in API responses	UUIDv7 (ADR-019)
AI accessing DB/storage directly	AI → DMS API → DB (ADR-023)
Direct file operations bypassing StorageService	StorageService for all file moves
Inline email/notification sending	BullMQ queue job
Deploying without Release Gates	Complete 04-08-release-management-policy.md
AI direct cloud API calls	On-premises Ollama only (ADR-023)
AI outputs without human validation	Human-in-the-loop validation required (ADR-023)
n8n calling Ollama/Qdrant directly	n8n → DMS API → BullMQ → Ollama/Qdrant (ADR-023A)
Qdrant query without projectPublicId filter	QdrantService.search(projectPublicId: string) required (ADR-023A)

Schema Changes (ADR-009)

• NO TypeORM migrations — edit SQL schema directly
• Always check specs/03-Data-and-Storage/lcbp3-v1.9.0-schema-02-tables.sql before writing queries
• Update Data Dictionary when changing fields

UUID Handling

See 01-adr-019-uuid.md for complete UUID rules.

Quick reminder:

• ❌ parseInt(uuid) → NEVER
• ❌ Number(uuid) → NEVER
• ✅ Use UUID string directly