Project development analytics: balance map, KPIs, and the escaped-defect rate (spec) - #8
Conversation
OpenSpec change proposal (no implementation). Adds a project-analytics capability to the governance dashboard: a two-state summary (submitted = to-be, merged = current-state), a topic read against the project goal and invariants, a six-dimension radar balance map overlaying current-state and to-be, governance KPI ratios, and the escaped-defect (green-then-bug) KPI for building bug-free software. Signed-off-by: Christoph <awchristoph@gmail.com>
- score the current-state from merged PRs; measure over an explicit, paginated window instead of only the most-recent page - spec-conformance reads its own intake signal and excludes spec-exempt lanes; the review emits a machine-readable per-lens result so categories, malicious, and impact-core are queryable without scraping the comment - to-be excludes changes-requested PRs; Verification and Documentation exclude non-applicable PRs from their denominators - escaped-defect framed as the review false-negative rate, linkable from a bug PR or a bug-labelled issue; add a temporal trend; a minimum-signal note per metric so a new project shows a note and an existing repo scores from history - add the builtin-format spec mirror and a worked HTML design example Signed-off-by: Christoph <awchristoph@gmail.com>
|
ASDD review - advisory (recommendation:
This change is 2317 lines, over the 2000-line review cap, so the model lenses did not run. That cap exists because a model call costs money and an unbounded diff would let one pull request drain the budget. Split it into reviewable pieces, or raise review.max_diff_lines if the project wants to pay for changes this size. The deterministic security checks below still ran. Security scan (deterministic + SAST): no new issues. Impact scan: 1 finding(s), 0 block. CODE - skippedNo findings. SECURITY - okNo findings. SPEC - skippedNo findings. QUALITY - skippedNo findings. IMPACT - concerns
Generated by the ASDD advisory review. Mode: |
…gn example Remove the worked HTML example from the change so the diff stays under the review cost cap and the model review runs on the proposal itself. The example remains available as a design reference; the proposal, tasks, and mirror now describe it without an in-repo path. Signed-off-by: Christoph <awchristoph@gmail.com>
|
ASDD review - advisory (recommendation:
This change is 2060 lines, over the 2000-line review cap, so the model lenses did not run. That cap exists because a model call costs money and an unbounded diff would let one pull request drain the budget. Split it into reviewable pieces, or raise review.max_diff_lines if the project wants to pay for changes this size. The deterministic security checks below still ran. Security scan (deterministic + SAST): no new issues. Impact scan: 1 finding(s), 0 block. CODE - skippedNo findings. SECURITY - okNo findings. SPEC - skippedNo findings. QUALITY - skippedNo findings. IMPACT - concerns
Generated by the ASDD advisory review. Mode: |
|
ASDD review - advisory (recommendation:
The review runtime returned invalid output; a human should review manually. Security scan (deterministic + SAST): no new issues. Impact scan: 1 finding(s), 0 block. SECURITY - okNo findings. IMPACT - ok
Generated by the ASDD advisory review. Mode: |
1 participant
Summary
A spec proposal (OpenSpec change
project-development-analytics) for a project-analytics section on the governance dashboard. No implementation in this PR.It adds, on top of the existing stage buckets: a two-state summary (submitted PRs = the to-be state, merged PRs = the current-state); a read of what the work is about against the declared project goal and invariants; a six-dimension radar balance map (0 centre to 5 point) overlaying current-state and to-be; governance KPI ratios; an escaped-defect KPI framed as the review agent's false-negative rate; a temporal trend; and a minimum-signal note so a new project shows a note while a repo with history scores from it.
Two producer changes it depends on (specified here, built later): intake exposes the spec result as its own signal, and the review emits a machine-readable per-lens result so categories, malicious, and impact-core are queryable without scraping the rendered comment.
A worked HTML example of the whole view ships under
design/analytics-example.html.Contents: the OpenSpec change (
proposal.md,tasks.md,specs/project-analytics/spec.md) and its builtin-format mirror atdocs/specs/project-development-analytics.md.Disclosure (required - ASDD)
Agent identity:
asdd-agentInstructed by (human handle):
welsbachImpact
Checklist
git commit -s)