What this replaces
Instead of one-off recap docs that disappear into Drive, the post-event recap becomes a tracked, reusable artifact tied to the workspace.
Back to workflows
Post-event recap
Most events lose institutional memory the moment they end. CT Networks treats the post-event recap as a structured workflow tied to the workspace history, not a one-off doc.
Workflow shape
1
Event workspace history is closed with attributable artifacts
2
Insight Strategist drafts a structured recap from workspace state
3
Operators review, edit, and approve the recap
4
Recap is stored as an artifact and referenced from the next event
What this requires
The system needs an Insight Strategist coworker, a post-event recap playbook, and an artifact store inside the workspace.