A 30‑day‑old note was obeyed exactly as hard as a 7‑year‑old one

Описание и применение

Модель ИИ продолжает соблюдать устаревшие ограничения из репозитория, игнорируя изменения навыков команды. Решение – хранить отклонённые решения в Markdown‑файлах с датой истечения, чтобы после истечения они становились невидимыми для модели.

Задача

AI agents keep following stale repository constraints, ignoring that team skills may have changed.

Результат

The experiment showed that models obey stale constraints regardless of age; hiding expired notes restores correct behavior. The whynot tool provides a lightweight, audit‑friendly way to manage such constraints.

Рабочий процесс

• 1. Create a note in the repo with a creation date and an expiry date. 2. Run the model to choose a stack. 3. Observe that the model obeys the note regardless of age. 4. Hide the note after its expiry date. 5. Re‑run the model and see it recommends TypeScript.
• 6. Build the "whynot" tool to store rejected decisions as Markdown files with expiry metadata.
• 7. Install via npx whynot-cli init and audit existing agent configs with npx whynot-cli audit.
• 8. Use the tool to manage future constraints.
• 9. Monitor agent behavior over time to assess impact.

Доказательства

Every single response refused TypeScript.

Источник

A one-month-old note was obeyed exactly as hard as a seven-year-old one.

Источник

Make the expired entry invisible. Not annotated. Not warned about. Absent.

Источник

whynot is a folder of Markdown files in your repository that records what you ruled out and why — especially rejected entries, which are the only kind of knowledge that cannot be recovered from the code.

Источник