Tenant discriminator column exists for same-schema model

How to fix

1. Add the tenant discriminator column where required.
2. Update schema artifacts and migrations.
3. If the system uses a different tenant isolation model, update the architecture configuration and ADRs.

What it means

A same-schema tenant model is configured, but ArchPilot could not confirm tenant discriminator coverage.

Why it matters

Tenant discriminators are the foundation for keeping tenant data isolated in shared tables.

Common causes

• A table is missing tenantId or equivalent.
• Schema metadata is stale.
• The tenant model setting does not match the database design.

Example bad pattern

An orders table is shared across tenants but has no tenant_id column.

Example good pattern

Shared tenant tables include tenant_id and application queries filter by it.

Related files/config

• db/sql
• packages/db/prisma/schema.prisma
• .archpilot/architecture.json

Related CLI commands

• archpilot validate
• archpilot validate --ci