Skip to content
Strata v1.6.3

Data Model

Entity-Relationship Diagram (Database / ORM)

Section titled “Entity-Relationship Diagram (Database / ORM)”

👉 Persistence-oriented

erDiagram
    ASSET ||--o{ TRANSACTION : has
    ASSET ||--o{ ASSET_SNAPSHOT : "has (manually entered)"
    ASSET }o--|| ASSET_TYPE : "typed as"
    ASSET }o--o{ ASSET_CATEGORY : ""
    ASSET_CATEGORY }o--|| CATEGORY : ""
    ASSET }o--o{ ASSET_TAG : ""
    ASSET_TAG }o--|| TAG : ""

    PORTFOLIO_SNAPSHOT {
        uuid id PK
        decimal value
        string currency
        string notes
        datetime observed_at
        datetime created_at
    }

    FINANCING_SCENARIO {
        uuid id PK
        string name
        string currency
        string inputs_json
        datetime created_at
        datetime updated_at
    }

    ASSET {
        uuid id PK
        uuid asset_type_id FK
        string name
        decimal quantity
        boolean disposed
        datetime created_at
        datetime updated_at
    }

    ASSET_SNAPSHOT {
        uuid id PK
        uuid asset_id FK
        decimal value
        datetime observed_at
        datetime created_at
    }

    TRANSACTION {
        uuid id PK
        uuid asset_id FK
        string type
        decimal unit_price
        decimal quantity
        string currency
        datetime occurred_at
    }

    ASSET_TYPE {
        uuid id PK
        string code UK
        string label
        string group
    }

    CATEGORY {
        uuid id PK
        string name UK
        uuid parent_id FK
    }

    TAG {
        uuid id PK
        string name UK
    }

    ASSET_CATEGORY {
        uuid asset_id FK
        uuid category_id FK
    }

    ASSET_TAG {
        uuid asset_id FK
        uuid tag_id FK
    }

PORTFOLIO_SNAPSHOT is standalone — it has no foreign key to any other table. It records the total net worth at a moment in time, computed from asset snapshots.

FINANCING_SCENARIO is also standalone. Its inputs_json stores a saved assumption snapshot, including asset names, balances, explicit availability, and individual return rates. It has no foreign keys to assets or accounting records. Projections are calculated from those inputs when requested and are not stored as PortfolioSnapshots.

👉 Behavior-oriented

graph TD
    A[Asset] --> B[AssetSnapshot]
    B --> C["Sum of latest values\n(non-disposed assets)"]
    C --> D[PortfolioSnapshot]
    D --> E[Net Worth Chart]

Each asset belongs to an AssetType, which has a code, a human-readable label, and a group.

The group field organises the 13 type codes into 7 groups:

GroupType Codes
FINANCIALCHECKING_ACCOUNT, CASH, STOCKS, CRYPTO, BONDS
SAVINGSSAVINGS_ACCOUNT and user-defined savings products
REAL_ESTATEREAL_ESTATE
PERSONAL_PROPERTYPERSONAL_PROPERTY, VEHICLE
PHYSICAL_COLLECTIONSCOLLECTIBLES
LIABILITIESLOAN
OTHERBUSINESS, OTHER

The group field drives chart color-coding (LIABILITIES group = red bars below the zero axis) and the “By group” filter mode in the net worth history chart. Financing scenarios offer only active assets in the SAVINGS group as candidate funding sources; users still confirm each asset’s availability per scenario.

  • ACQUIRE: Buying/receiving an asset (increases quantity)
  • DISPOSE: Selling/giving away an asset (decreases quantity)
  • ADJUST: Manual correction/adjustment

There is no Portfolio table. Categories and tags handle all grouping and organization needs. An asset can belong to multiple categories (hierarchical or cross-cutting) and carry any number of tags. A dedicated “portfolio” row would just be an extra layer of indirection with no added value for a single-user app.

PortfolioSnapshot captures the total net worth at a moment in time. It is not “owned” by a portfolio because there is no portfolio entity. It is a global snapshot of everything you track — a record of the sum, not a sub-view of a group.

3. Base currency: EUR (hardcoded for alpha)

Section titled “3. Base currency: EUR (hardcoded for alpha)”

All monetary values are stored in EUR. Multi-currency support is planned for a future version. currency fields on snapshots are informational and currently always "EUR".

Liabilities (asset type LOAN) store negative values in AssetSnapshot.value (e.g., -€180,000 for a mortgage). Net worth sums all asset snapshot values — positives increase it, negatives decrease it.

Net Worth = Sum of latest AssetSnapshot.value per non-disposed asset
Example:
Checking Account: +€10,000
Paris Apartment: +€420,000
Mortgage Loan: -€180,000
─────────────────────────────
Net Worth: +€250,000

5. Financing Scenarios are detached planning records

Section titled “5. Financing Scenarios are detached planning records”

Saving or recalculating a scenario does not write assets, liabilities, transactions, or PortfolioSnapshots. An edit-and-save refreshes source balances in the scenario’s input snapshot; a recalculation reuses the saved snapshot.