Tenant isolation model undocumented or inconsistent

How to fix

1. Update the tenant model ADR or architecture overview.
2. Name the tenant discriminator and ownership model.
3. Link tenant isolation docs from security-sensitive workflows.

What the rule validates

Implementation evidence and documentation do not clearly agree on how tenants are isolated.

Why it matters

Teams need durable tenant-model context to review data access, migrations, and authorization behavior.

Common causes

• The tenant model changed without updating docs.
• Code uses organization scope but docs use generic account language.
• ADR and overview documentation disagree.

Typical violation example

The schema uses organizationId everywhere, but the architecture overview never describes tenant isolation.

Typical compliant example

The overview and ADR describe organization-scoped tenant isolation and data-access expectations.

Related rules

Adjacent categories

Related files/config

• docs/adrs
• docs/architecture/overview.md
• .archpilot/architecture.json

Related CLI commands

• archpilot validate
• archpilot validate --ci