Search docs
Docs searchValidation category
Database Rules
Review implemented validation rules for database setup evidence, tenant model support, and schema artifacts used by validation.
Database findings ensure ArchPilot has enough schema and tenant-model context to evaluate data-access risk accurately.
Overview
Review implemented validation rules for database setup evidence, tenant model support, and schema artifacts used by validation.
Database findings ensure ArchPilot has enough schema and tenant-model context to evaluate data-access risk accurately.
Why it matters
Cloud uses this guidance to help teams interpret local validation findings in organization context without turning the docs into implementation notes.
When this domain drifts, findings become harder to triage, ownership becomes less clear, and architecture review depends too much on individual memory.
Good architectural practices
- Tenant model evidence for database validation.
- SQL or schema baseline artifacts present for query analysis.
- Database setup that supports tenant isolation and data/query risk checks.
Common anti-patterns
- Tenant discriminator column exists for same-schema model
- SQL baseline artifact exists
Relationship to other architecture areas
This domain usually overlaps with neighboring validation categories. Use the related pages below to understand the adjacent architecture concerns before changing policy, suppressing a finding, or accepting risk.
Implemented rules
These are the currently implemented rules in this category. Use this table for category-level orientation, then open the Rule Catalog when you need rule-specific examples and remediation guidance.
| Rule ID | Rule title | Category | Severity | Short explanation | Example violation | Remediation guidance | Rule detail |
|---|---|---|---|---|---|---|---|
| AP-DB-001 | Tenant discriminator column exists for same-schema model | Database | error | Checks that same-schema multi-tenant tables include tenant discriminator evidence. | An orders table is shared across tenants but has no tenant_id column. | Add the tenant discriminator column where required. Update schema artifacts and migrations. If the system uses a different tenant isolation model, update the architecture configuration and ADRs. | View rule page |
| AP-DB-002 | SQL baseline artifact exists | Database | error | Checks that the SQL baseline artifact exists for database validation. | Database validation is enabled but db/sql baseline artifacts are absent. | Generate or restore the SQL baseline artifact. Update configuration if the baseline moved. Keep schema artifacts current with migrations. | View rule page |
Related pages
Next steps