Skip to content

docs: Phase J J4 deprecation policy -- intentional obsolescence for benchmarks, schemas, scripts, CLI commands; agent anti-patterns listed - #905

Merged
cschanhniem merged 1 commit into
mainfrom
feat/j4-deprecation-policy
Jul 10, 2026
Merged

cschanhniem merged 1 commit into
mainfrom
feat/j4-deprecation-policy

Conversation

@cschanhniem

Copy link
Copy Markdown
Collaborator

Implements J4 from NEXT_100_PR_MAP: deprecation policy document.

What

  • docs/DEPRECATION_POLICY.md: 7 sections
  • Scope: benchmark cards, evidence schemas, JSON schemas, scripts, CLI commands, scoring/calibration modules
  • When to deprecate vs delete (+ anti-patterns)
  • How to deprecate each artifact type with code examples
  • Deprecation timeline: deprecated → scheduled removal → removed (minimum one release cycle)
  • Agent rules: MUST NOT silently delete or un-deprecate without review
  • Docs-only PR; no code or test changes

Why

Undocumented deprecations are invisible dependencies. Without policy, agents delete artifacts that old evidence trail entries still reference.

Disconfirming pass

  • No existing benchmarks deprecated here
  • No schema IDs changed
  • No code removed

…enchmarks, schemas, scripts, CLI commands; agent anti-patterns listed (#905)
@cschanhniem
cschanhniem merged commit ad857d6 into main Jul 10, 2026
1 check failed
cschanhniem added a commit that referenced this pull request Jul 10, 2026
…enchmarks, schemas, scripts, CLI commands; agent anti-patterns listed (#905) (#906)

Co-authored-by: OpenCode <opencode@example.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant