You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Executive read: Strong acceptance rate (100%) with zero waste, but 15 unknown outcomes (43% of total) and 8 pending items represent signal gaps. PR Sous Chef dominates volume (60% of outcomes) with unresolved unknowns in create_issue actions; these likely indicate safe-output failures. Contribution Check and Daily workflows are underdefined with mostly unknown or unresolved items.
References: one linked item per status emoji, in the same order as the Status column
🔴 Action Items
Unknown outcome signal is critical: 15 items (43% of total) show outcome_status: unknown, dominated by PR Sous Chef's unresolved create_issue actions with empty URLs. This indicates safe-output failures; verify that issue creation is working and IDs are being captured correctly.
High fallback evaluation rate: 7 items (20% of total) were evaluated using only generic existence checks (target_exists_only). These contribute to inflated acceptance numbers. The daily report workflows (Sentrux, Observability, Regulatory, etc.) all land in this category—lacking dedicated evaluators.
Pending items aging without resolution: 8 items are pending, several without any observed follow-up. Contribution Check has 2 pending comments (both >3h old); PR Sous Chef has 4 pending (oldest >2h old).
Zero-touch acceptance: All 12 accepted items show zero visible human follow-up (zero_touch_rate: 0%). This is a data quality issue—check whether reactions, approvals, or merges are being counted. No accepted item had any measured engagement.
Underdefined Daily workflows: 6 workflows produce only single outcomes each, all in unknown status. These are single discussion/issue creation workflows with no clear acceptance/rejection logic. Each needs either: (a) dedicated evaluators tracking engagement metrics or (b) removal if not actionable.
PR Sous Chef unknowns: 6 of 7 unknown items in PR Sous Chef are failed create_issue actions (empty URL). These are likely safe-output failures where issue creation succeeded but the issue number was not captured. Check recent runs' safe-output logs.
Detailed metrics, evidence quality, workflow counts, and trends
Outcome Scorecard — 2026-07-13
Metric
Value
Status
Acceptance rate
100%
🟢 >80%
Zero-touch rate
0%
🔴 <25%
Waste rate
0%
🟢 <10%
Median time to resolution
23h
—
Accepted
12 / 35
—
— strong evidence
1
closed issue
— medium evidence
11
comments acted upon
— weak evidence
0
—
Rejected
0
—
Ignored
0
—
Unknown
15
no terminal state
Zero-touch
0 / 12
—
Pending
8
—
Runs checked
18
—
Per-Workflow Breakdown
Workflow
Accepted
Rejected
Pending
Unknown
Acceptance
Zero-touch
PR Sous Chef
10
0
4
7
100%
0%
Contribution Check
1
0
2
1
100%
0%
Semantic Function Refactoring
1
0
1
0
100%
0%
Daily Model Inventory Checker
0
0
1
0
N/A
N/A
Agentic Workflow Audit Agent
0
0
0
1
N/A
N/A
Lockfile Statistics Analysis Agent
0
0
0
1
N/A
N/A
Daily Team Evolution Insights
0
0
0
1
N/A
N/A
Daily Sentrux Report
0
0
0
1
N/A
N/A
Daily Regulatory Report Generator
0
0
0
1
N/A
N/A
Daily Observability Report for AWF Firewall and MCP Gateway
0
0
0
1
N/A
N/A
Copilot PR Prompt Pattern Analysis
0
0
0
1
N/A
N/A
Evidence Quality
⚠️7 items were evaluated using only a generic existence check (signal: target_exists_only). These contribute to inflated weak-signal counts and may not represent true acceptance. Dedicated evaluators for create_discussion and close_discussion outcomes are needed. Additionally, 6 items failed with outcome_status: unknown and empty URLs, indicating safe-output issue creation failures.
Key signal: Acceptance rate remains perfect, but unknown outcomes are accumulating. Combined with zero-touch rate at 0%, this suggests the evaluation model is struggling to capture engagement and failures simultaneously.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpg
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
Workflow Health — 2026-07-13
Executive read: Strong acceptance rate (100%) with zero waste, but 15 unknown outcomes (43% of total) and 8 pending items represent signal gaps. PR Sous Chef dominates volume (60% of outcomes) with unresolved unknowns in
create_issueactions; these likely indicate safe-output failures. Contribution Check and Daily workflows are underdefined with mostly unknown or unresolved items.Legend:
🔴 Action Items
Unknown outcome signal is critical: 15 items (43% of total) show
outcome_status: unknown, dominated by PR Sous Chef's unresolvedcreate_issueactions with empty URLs. This indicates safe-output failures; verify that issue creation is working and IDs are being captured correctly.High fallback evaluation rate: 7 items (20% of total) were evaluated using only generic existence checks (
target_exists_only). These contribute to inflated acceptance numbers. The daily report workflows (Sentrux, Observability, Regulatory, etc.) all land in this category—lacking dedicated evaluators.Pending items aging without resolution: 8 items are pending, several without any observed follow-up. Contribution Check has 2 pending comments (both >3h old); PR Sous Chef has 4 pending (oldest >2h old).
Zero-touch acceptance: All 12 accepted items show zero visible human follow-up (
zero_touch_rate: 0%). This is a data quality issue—check whether reactions, approvals, or merges are being counted. No accepted item had any measured engagement.Underdefined Daily workflows: 6 workflows produce only single outcomes each, all in unknown status. These are single discussion/issue creation workflows with no clear acceptance/rejection logic. Each needs either: (a) dedicated evaluators tracking engagement metrics or (b) removal if not actionable.
PR Sous Chef unknowns: 6 of 7 unknown items in PR Sous Chef are failed
create_issueactions (empty URL). These are likely safe-output failures where issue creation succeeded but the issue number was not captured. Check recent runs' safe-output logs.Detailed metrics, evidence quality, workflow counts, and trends
Outcome Scorecard — 2026-07-13
Per-Workflow Breakdown
Evidence Quality
target_exists_only). These contribute to inflated weak-signal counts and may not represent true acceptance. Dedicated evaluators forcreate_discussionandclose_discussionoutcomes are needed. Additionally, 6 items failed withoutcome_status: unknownand empty URLs, indicating safe-output issue creation failures.Trend Signal
Comparison with 2026-07-10 baseline:
Key signal: Acceptance rate remains perfect, but unknown outcomes are accumulating. Combined with zero-touch rate at 0%, this suggests the evaluation model is struggling to capture engagement and failures simultaneously.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.