# Database Schema

`vp run db:generate-erd-docs` generates the diagrams below from the migrated schema. If you change Liquibase migrations, regenerate them. The command rewrites `docs/contributor/erd/`.

Each Spring Modulith module has its own diagram. A table belongs to the module whose entity maps it. A dashed entity is a table of another module, and its label names that module. A foreign key to it appears in this diagram, and the table itself appears in the diagram of its module.

<!-- -->

<!-- -->

## Activity

<!-- -->

## Agent

<!-- -->

## Core

<!-- -->

## Integration

<!-- -->

## Mentor

<!-- -->

## Notification

<!-- -->

## Practices

<!-- -->

## Productfeedback

<!-- -->

## Workspace (Tenancy)

<!-- -->

## Tables without an entity

<!-- -->

## Practice model relationships

The diagram below comes from the migrated schema. The [practice data model](/contributor/practice-feedback-schema.md) explains its invariants without repeating the column inventory. Product reviews and scan membership remain durable when execution jobs expire.