audit score weights trailer coverage too heavily for greenfield/low-commit-count projects

[stackbilt-admin]

Description

The audit scoring gives 50% weight to governance trailer coverage. For a new project with few commits (e.g., <10), having 0% trailer coverage on historical commits (CI config, initial scaffold, deploy fixes) tanks the score to 50/100 even when patterns and policy are both at 100%.

These early commits are typically low-governance-risk (infrastructure setup, CI wiring) and rarely warrant Governed-By or Resolves-Request trailers.

Example

Score Breakdown
  Trailer coverage:     0/100 (50% weight)    ← historical commits, all CI/infra
  Pattern definitions:  100/100 (30% weight)
  Policy documentation: 100/100 (20% weight)
  Total:                50/100

Suggestion

Consider one or more of:

• A grace period or commit-count threshold (skip trailer scoring when commits_analyzed < N)
• Lower trailer weight for repos under a certain age or commit count
• Exclude commit categories (e.g., chore, ci) from trailer requirements in early lifecycle
• Allow config to set a "governance start" commit so historical commits before adoption aren't penalized

Environment

• Charter v0.9.2
• Project with 5 total commits, all infrastructure/CI

[stackbilt-admin]

Already fixed in 6f921bf — trailer weight scales by commit count (20% at ≤20 commits, ramping to 50% at ≥100). Greenfield projects no longer penalized.