workflow-reflect

You can filter sigil telemetry by name, mode, date range, and minimum signal count to prepare observability signals for analysis. This filtering clusters signals by type, severity, and drift to reveal recurring patterns and threshold-driven insights.

Generating evidence-backed proposals requires grouping accumulated observability signals to detect recurring gaps. You produce concrete proposals preserving the sigil contract unless telemetry evidence justifies changes, culminating in a final reflection report.

Yes, you can apply filters by sigil name, mode, date range, and minimum signal count to determine whether to write a full reflection report or produce a dry run. This ensures only relevant observability signals are analyzed.

Reflection report generation aggregates context, patterns, and gap analysis from observability signals to output recommended next steps. It converts clustered telemetry into evidence-backed proposals for lifecycle decisions and maintenance improvements.

You should produce a dry run when evaluating filtered observability signals without committing to final evidence-backed proposals. Use a dry run to validate pattern detection and gap analysis before writing the final reflection report.