#75 audit: governance propagation across execution surfaces

[Anonymous]

Originally created by: TheoV823

Goal

Audit the current automation surfaces and identify where repository conventions are not propagating correctly.

This should be framed as governance propagation across execution surfaces, not just repo cleanup.

Focus areas

• Auto-generated branch naming / worktree naming
• PR title generation
• Commit message conventions
• Generated asset validation
• CI-generated metadata / artifacts
• Deployment / release naming consistency
• Any other automation-emitted public artifacts

For each surface, document

1. Current behavior
2. Intended governance rule
3. Where the drift occurs
4. Recommended enforcement point
5. Enforcement mode:
6. preventive
7. validation-based
8. advisory / warn-mode

Context

Recent dogfooding surfaced two useful examples:

• Worktree/session tooling can emit public branch names that bypass the repo taxonomy, even when CLAUDE.md documents the intended convention.
• OG image generation can technically succeed while producing semantically invalid artifacts, so generated visual assets need validation before commit/deploy.

These are site/repo automation hygiene issues, not product incidents, but the pattern is strategically important: governance needs to propagate into automation-emitted artifacts, not only source code.