SITREP Signal System
Current signal foundation for future per-fund intelligence.Hugo now uses fund_signals as a simple mutation signal stream. A signal records that a fund-scoped mutation happened; it does not compute derived effects or trigger synthesis inline.
Current Shape
| Layer | Current responsibility | Status |
|---|---|---|
recordFundSignal |
Append one signal row after a successful mutation | Current |
fund_signals |
Store signal type, subject, payload, actor, and timestamp | Current |
| SITREP synthesis | Future consumer of signals, not part of mutation handling | Planned |
| Email/notifications | Future outbox/queue consumer of signals | Planned |
fund_signals schema
| Column | Type | Description |
|---|---|---|
id | TEXT PK | Signal id |
fund_id | TEXT FK | Fund this signal belongs to |
signal_type | TEXT | Closed enum value |
subject_type | TEXT | Primary changed entity type |
subject_id | TEXT | Primary changed entity id, nullable for bulk actions |
payload_json | TEXT | Structured JSON payload |
actor_user_id | TEXT | Acting user when available |
created_at | TEXT | Append timestamp |
Removed Design
The previous event wrapper, event table, provenance columns, and MFN eligibility cascades have been removed from the current architecture. Derived work should be implemented later as separate consumers of fund_signals.