heartbeat

A system reflection scan identifies active threads, emergent signals, and recurring patterns across sessions and backlogs. It performs a lightweight cross-silo scan to surface what is alive and connecting, routing categorized insights to appropriate system docs.

Run a system reflection scan at session starts, pauses, or transitions to maintain context and alignment. Applying the scan at these timely moments surfaces what is alive and emerging, ensuring you act on meaningful signals rather than chasing noise.

Routing insights works by categorizing scan findings and directing them to appropriate system docs or task backlogs. A frontmatter-guided workflow reads entry metadata, performs the reflective scan, and outputs categorized insights with specific routing guidelines.

The best way to identify emergent signals without chasing noise is to apply a lightweight, structured reflection that scans across silos. This process filters system data to surface active threads and connecting patterns, routing actionable insights to appropriate docs.

A system reflection scan requires no external dependencies or specific components. It operates as a standalone frontmatter-guided workflow, reading the entry name and description to perform the scan and output categorized insights with routing guidelines.

Yes, you can use a system scan to route findings to existing task backlogs. The scan categorizes emergent signals and active threads, providing routing guidelines that direct these actionable insights to the appropriate system docs or task backlogs.