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
Copy file name to clipboardExpand all lines: .github/workflows/objective-impact-report.md
+40-11Lines changed: 40 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
emoji: 📊
3
-
description: Impact efficiency report from workflow outcomes and linked objectives.
3
+
description: Executive impact efficiency report from workflow outcomes tied to tracked objectives.
4
4
on:
5
5
workflow_dispatch:
6
6
permissions:
@@ -19,9 +19,9 @@ safe-outputs:
19
19
20
20
## Goal
21
21
22
-
POC: Test whether Impact Efficiency is a more meaningful signal than accepted outcome counts alone.
22
+
Produce a comprehensive executive report on what work was performed, what AIC tokens were spent on, and which outcomes delivered the highest impact. The report must clearly answer: *What did we build, fix, and ship — and was it worth the cost?*
23
23
24
-
Focus only on **pull request outcomes** and **safe output outcomes** (issues created or closed via the safe-output mechanism). Other outcome types are excluded from this POC because their acceptance criteria are not yet well-defined and most remain pending.
24
+
Focus only on **pull request outcomes** and **safe output outcomes** (issues created or closed via the safe-output mechanism). Other outcome types are excluded because their acceptance criteria are not yet well-defined and most remain pending.
25
25
26
26
Use this model:
27
27
@@ -59,7 +59,7 @@ If a run's `aic` field is missing or null, treat it as `0` and count it as missi
59
59
60
60
Analyze only the following outcome types from the last 180 days:
61
61
62
-
-**Pull request outcomes**: PRs created by GitHub Agentic Workflow runs. Accepted = merged. Rejected = closed without merge. Skip open (pending) PRs.
62
+
-**Pull request outcomes**: PRs created by GitHub Agentic Workflow runs**that have a linked closing issue** (`Closes #N`). Accepted = merged. Rejected = closed without merge. Skip open (pending) PRs. **Exclude entirely** any PR without a traceable linked issue — do not fall back to PR labels.
63
63
-**Safe output outcomes**: issues created or closed by workflow runs via the safe-output mechanism. Accepted = issue successfully created/closed. Skip any with unresolved state.
64
64
65
65
Exclude all other outcome types (direct issue outcomes, comments, discussions, etc.). These are omitted because their acceptance criteria are incomplete and most are left pending, which would distort the metric.
@@ -91,11 +91,11 @@ If a traced root object has no labels that exist in the mapping, mark the outcom
91
91
92
92
For each in-scope outcome, follow the implemented root-tracing behavior:
93
93
94
-
1. For pull-request outcomes, trace the PR to its linked closing issue and use that root issue's labels.
95
-
2. If PR root tracing fails, use labels on the PR itself.
94
+
1. For pull-request outcomes, trace the PR to its linked closing issue (`Closes #N`) and use that root issue's labels.
95
+
2. If PR root tracing fails (no linked closing issue found), **exclude the PR from analysis entirely**. Do not fall back to PR labels. Count it in the "PRs excluded (no linked issue)" total.
96
96
3. For safe-output issue outcomes, use labels on the safe-output issue itself.
97
97
4. Record the traced root URL when one is found so the report preserves an audit trail.
98
-
5. If no mapped objective labels can be found, mark the outcome as `unmapped`, exclude it from `Σ Outcome Value`, and report it separately.
98
+
5. If no mapped objective labels can be found after tracing, mark the outcome as `unmapped`, exclude it from `Σ Outcome Value`, and report it separately.
Write 2–4 sentences that directly answer: *What did we work on, what was the highest-impact work, and how efficiently were AIC tokens spent?* Highlight the most impactful objective categories and call out any significant gaps (e.g., large AIC spend with no mapped objective value).
Group all **accepted, mapped** outcomes by objective category (the highest-value objective label from the mapping). For each category, list:
168
+
169
+
- Objective category name and its mapping value
170
+
- Number of accepted outcomes in this category
171
+
- Total outcome value contributed
172
+
- AIC consumed by outcomes in this category
173
+
- Impact Efficiency for this category (total outcome value / AIC consumed)
174
+
- Representative examples (up to 3 linked outcomes)
175
+
176
+
Sort categories by total outcome value descending. Also call out separately which category consumed the **most AIC** (highest denominator cost), so readers can see where budget was spent regardless of value delivered.
177
+
155
178
### Top outcomes by outcome value
156
179
157
-
| Outcome | Type | Associated objective| Objective Value | Outcome Value |
180
+
| Outcome | Type |Root / Associated Objective| Objective Value | Outcome Value |
158
181
|---|---|---|---:|---:|
159
182
183
+
List the top 15 outcomes with highest Outcome Value. Include a link to the PR or issue.
184
+
160
185
### Unmapped outcomes
161
186
162
187
| Outcome | Type | Reason objective was not mapped |
163
188
|---|---|---|
164
189
190
+
Only include outcomes that were in scope (linked-issue PRs and safe-output issues) but had no matching label in the objective mapping. Do not include PRs that were excluded for lacking a linked issue — those are already counted in "PRs excluded".
191
+
165
192
### Interpretation
166
193
167
194
Compare:
@@ -171,11 +198,13 @@ Compare:
171
198
172
199
Explain which one better reflects meaningful delivered value relative to cost.
173
200
201
+
Call out the most significant finding: which objective category delivered the most value per AIC? Which categories consumed AIC with little or no mapped value?
202
+
174
203
### Data quality
175
204
176
205
Mention missing or weak links in:
177
206
178
-
- PR root tracing and linked-closing-issue coverage
207
+
- PR root tracing and linked-closing-issue coverage (count of PRs excluded for lacking a linked issue)
179
208
- safe-output issue label mapping coverage in `.github/objective-mapping.json`
0 commit comments