[POLICY] Merge proof standard — screenshot for visual changes, logs/output for CLI changes #83

Closed
opened 2026-03-28 13:53:11 +00:00 by Timmy · 0 comments
Owner

Goal:
Make proof requirements repo law.

Rules to codify:

  • visual changes must include screenshot proof
  • screenshots/media should not be committed to Gitea backup unless explicitly required
  • CLI/verifiable changes must cite the exact command output, log path, or world-state proof showing acceptance criteria were met
  • config-only changes are not fully accepted until live behavior is proven where applicable

Acceptance:

  • policy is documented in the repo
  • PR template or contribution docs require proof sections
  • examples included for visual vs CLI/harness changes
Goal: Make proof requirements repo law. Rules to codify: - visual changes must include screenshot proof - screenshots/media should not be committed to Gitea backup unless explicitly required - CLI/verifiable changes must cite the exact command output, log path, or world-state proof showing acceptance criteria were met - config-only changes are not fully accepted until live behavior is proven where applicable Acceptance: - policy is documented in the repo - PR template or contribution docs require proof sections - examples included for visual vs CLI/harness changes
Timmy self-assigned this 2026-03-28 13:53:11 +00:00
Timmy closed this issue 2026-03-28 14:03:36 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#83