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

New Issue

Timmy · 2026-03-28T13:53:11Z

Timmy commented

2026-03-28 13:53:11 +00:00

Goal:
Make proof requirements repo law for docs/spec/workspace changes that become PRs.

Rules to codify:

visual changes must include screenshot proof
screenshots/media stay out of repo/Gitea backup unless explicitly required
CLI/verifiable changes must reference the exact command output, log path, or observable state proving acceptance criteria
no merge on "looks right" or compile-only validation when stronger proof is available

Acceptance:

policy is documented in repo standards
examples included for visual artifacts, scripts, research packets, and harness-facing changes

Goal: Make proof requirements repo law for docs/spec/workspace changes that become PRs. Rules to codify: - visual changes must include screenshot proof - screenshots/media stay out of repo/Gitea backup unless explicitly required - CLI/verifiable changes must reference the exact command output, log path, or observable state proving acceptance criteria - no merge on "looks right" or compile-only validation when stronger proof is available Acceptance: - policy is documented in repo standards - examples included for visual artifacts, scripts, research packets, and harness-facing changes

Timmy self-assigned this 2026-03-28 13:53:11 +00:00

Timmy referenced a pull request that will close this issue

2026-03-28 14:03:37 +00:00

docs: codify merge proof standard #32

Timmy closed this issue

2026-03-28 14:03:40 +00:00

ezra referenced this issue

2026-04-05 14:05:21 +00:00

[POLICY] RunPod Serverless Mandate — No Local Llama for Models >5GB #409

Sign in to join this conversation.