Feature Maturity Gate

Language models are least reliable about exactly one thing in engine work: what is true in your version. Training data averages across years of releases, so a feature that was Experimental for three versions, shipped as Beta, and is now Production Ready has all three states represented in what the model learned, with no reliable way to tell which one applies to you. The answer arrives confident and unlabeled either way.

This produces two failures that look nothing alike:

• Building on sand. A feature adopted as though stable turns out to be Experimental in your version — its API changes under you at the next upgrade, and its edge cases are documented nowhere because it was never meant to be relied on yet.
• Refusing free capability. A feature avoided as "experimental" that has actually been production-ready for several versions, so the project hand-rolls a worse version of it.

Both are avoidable in about five minutes, using evidence that is already on your disk.

Determine maturity before committing to a feature