video1.0<iframe src="https://www.loom.com/embed/cc47ae6ac2ae4501ace60612a7c779f0" frameborder="0" width="1152" height="864" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>8641152Loomhttps://www.loom.com8641152https://cdn.loom.com/sessions/thumbnails/cc47ae6ac2ae4501ace60612a7c779f0-92c0ff556b1d4c51.gif246.158This is a live walkthrough of the Decision Capture Pipeline, a 14-node n8n automation that turns Slack emoji reactions into structured, searchable decision records in Notion. The problem: In remote teams, decisions get made in Slack threads and disappear. Nobody remembers what was decided, who decided it, or why. The fix: React with a ✅ emoji in the #decisions channel. The pipeline captures the message, thread context, and rationale, deduplicates against existing entries, creates a structured draft in the Notion Decision Log, writes to the Automation Audit Log for traceability, and confirms back in Slack. All in about 4 seconds. Five execution paths handle success, duplicate prevention, validation failure, error recovery, and Slack confirmation. Every path produces an audit trail. Nothing fails silently. The automation handles capture and structure. Humans handle judgment and context. No AI is making decisions here. It just makes sure decisions don't get lost. This pipeline is part of the Remote OS Architecture, a full operating system for remote-first, async teams: https://www.notion.so/Remote-OS-Architecture-30fbcd9cf5a181f5bec9e8a10f2ffed6