Reference Entities

Not all entities are equally complex. These are the best references when extending the system.

finance/single-cashflow

Use this when you need:

• delete behavior that can transform into another action
• blocked delete states
• field-level editability
• mutation-time enforcement for both update and delete

It demonstrates the difference between:

• interaction policy in workflows
• hard integrity protection in mutation hooks

finance/recurring-cashflow

Use this when you need:

• branching update flows
• selection-based workflows
• change categorization
• editability that depends on time state

This is the strongest example of a workflow returning more than direct or confirmation.

work/time-entry

Use this when you need:

• a consolidated evaluation model
• blocked delete, update, and select rules coming from one source
• field-level locking derived from one evaluation function
• mutation-time protection for paid or payout-linked records

This is the clearest example of “evaluate once, derive many decisions”.

work/project

Use this when you need:

• warning-only delete workflows
• query-derived delete inputs
• field-level editability tied to related data
• action hooks that derive both delete and edit inputs from live query state

Simple-entity references

For simple entities that still follow the full contract, look at:

• work/folder
• work/time-tracker
• system/notification
• system/profile
• system/settings

These show how to keep the architecture consistent without inventing fake complexity.