5.7 Signal-driven task generation
5.7 Signal-driven task generation
signals from both proactive sources (scheduled security scans, UI regression runs, mutation testing, health checks) and reactive sources (user reviews, support tickets, app store ratings, meeting notes, production metrics) flow through automated triage into typed task creation. Both sources contribute; neither is manually gated. The proactive-source path depends on an agent-invokable scheduling primitive — scored here rather than as its own criterion, but load-bearing for `PL2-test-quality`, `PL2-ui-test-coverage`, `PL2-load-stress-testing`, `PL4-release-strategy`, `PL5-pipeline-reliability`, `PL5-outcome-input-loop` as well
Levels
Level 0
Neither source creates tasks; signals are lost or read by humans only
Level 1
Partial coverage — some scheduled jobs produce reports *or* external signals are manually triaged into tickets, but not both automated
Level 2
Comprehensive across both sources: scheduled runs (scans, regression, mutation tests, health checks) **and** external signals (reviews, tickets, metrics, meeting notes) flow through automated triage into typed task creation; sanitization applied at ingestion per `PL4-prompt-injection-defence`. **The proactive-source path requires an agent-invokable scheduler — the agent can create, edit, and cancel scheduled jobs through the project's own tool surface, not merely observe jobs ops configured out-of-band. Without this primitive the criterion caps at level 1 regardless of reactive-source coverage.**
Level 3
Signal classification improves from past triage decisions; scan cadence and scope auto-tuned from finding-rate trends; new scan types added from observed incident classes; signal-to-task conversion quality measured and improves over time