Data model and database

Helm combines a balanced ledger, real-world context and question-oriented read models. Supporting state handles import review, authorization and consistent reads.

Read by responsibility

• Database responsibilities groups records by purpose.
• Concept relationships explains how money and context connect.
• Financial functions explains the controlled write boundary.
• Database changes covers forward migration discipline.
• Generated types explains typed callers.

Ledger and context

Transactions contain entries against accounts. Amounts balance at stored precision separately in each currency. People, plans, categories, tags and matters explain those movements without becoming additional money.

A dated balance observation is a financial basis, not a fabricated transaction that pretends to reconstruct missing history.

Client boundary

Application and integration clients use the API. Direct financial table writes bypass validation, atomicity and audit behavior. A table existing in the schema does not make it a public client resource.

Before changing the schema

Inspect the target’s actual version and migration history. Review the affected RPC, ownership policies and read model before adding a forward migration. Align generated types and service callers with the verified runtime shape.

Continue with financial semantics to interpret what the structure means.