notes-history

Generic, host-agnostic, append-only note history for any entity. Owns one event-sourced entity, note-entry (read_note_entries), keyed by (entityType, entityId) — so attaching notes adds NO column to the host entity and needs no relational pivot or JOIN. Provides a create write-handler (author stamped server-side from the caller, never client-supplied) and a list query filterable on entityId. Deliberately append-only: no update or delete handler is registered — a correction is a new entry, not an edit, so who-said-what-when stays reconstructable. Every path uses one access rule — adopt the host’s model with createNotesHistoryFeature({ access: { openToAll: { reason } } }) or pin roles with createNotesHistoryFeature({ roles }).

How it fits

The write commands this feature provides (Provides).

flowchart TB
  n_notes_history["notes-history"]
  subgraph how_provides["Provides"]
    n_cmd_notes_history_write_add_note(["add-note"])
  end
  n_notes_history --> n_cmd_notes_history_write_add_note

Provides — write commands this feature registers (dispatch them through the command bus):

• notes-history:write:add-note

Dependencies

• Requires: none
• Activation: always on (not toggleable)