An AI model must always list the full paths of all changed files. The user needs to know exactly which files were updated. This helps the user verify the changes.
By Pawan Nayar · from the LLOS AI Learning record
An AI model must always list the full paths of all changed files.
The user needs to know exactly which files were updated. This helps the user verify the changes.
When an AI model changes files, it must list them. The list should include the full path for each file. This means showing the complete location of the file on the computer. The user can then easily find and check the updated files.
A developer asks an AI model to update a code file. The AI model makes the changes. After finishing, the AI model lists the full path to the updated file. For example, it might show: `/home/user/project/src/main.py`. This helps the developer quickly find the file and review the changes.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
An AI model must show full file paths after every major update. A major update is any change that modifies one or more files.
Before a developer makes the first edit in any work session, a backup copy of the file must be made. The backup file name should include the date.
A developer must create a new backup right before editing a file. An old backup, even from the same day, can lead to lost work.
A developer should put all Markdown backup copies in the `llos/tools/` folder. This folder is a single, expected place for these files.
An AI model must always list the full paths of all changed files. The user needs to know exactly which files were updated. This helps the user verify the changes.