| Raw sources | The system reads meetings, emails, Teams, documents, and project records. | Packet quality starts with real evidence, not prompt creativity. |
| Attribution | Sources are linked to the right project and intelligence target. | Wrong-project evidence is one of the fastest ways to destroy trust. |
| Signal extraction | Communications compilers extract decisions, risks, tasks, flags, and exposures. | This converts messy text into reviewable operating signals. |
| Insight cards | High-confidence signals promote into insight_cards with linked evidence. | Cards are the durable evidence layer, not just temporary model output. |
| Rolling synthesis | The packet writer loads the prior packet, reads only the new source delta, and adds deterministic project facts. | This creates one current read instead of recomputing disconnected fragments every time. |
| Packet output | The packet writes the exact sections the product renders. | The UI needs a stable strategic shape, not free-form prose. |
| Feedback loop | Users mark output stale, wrong, or useful and the system can refresh again. | A packet that cannot be corrected will drift. |
