| name | no-compat-paths |
|---|---|
| description | Use for ANY software project, language, or codebase when a change touches a data format, schema, field, storage layout, serialization, API, or config — or whenever you think "compat path", "backward compatibility", "legacy support", "migration shim", "dual format", "deprecation alias". Default stance: convert old data once and delete the old machinery; breaking churn is fine. |
A default engineering stance for all software work — any project, language, repo, file, or folder. Treat it as the rule unless an explicit external contract says otherwise, and even then, surface the decision to the owner instead of silently adding compat code.