Field Notes

Field Notes are short explanations of Workbench changes that solve a general problem or reveal a useful working principle. The internal release record remains the complete ledger; this shelf is for the bits that are worth taking home.

Each note names the problem, the bounded change, its owner, the effect on active and paused work, and the evidence behind its status. Private paths, credentials, operational detail, and unfinished speculation stay out of the public package.

Current notes

• Why Workbench does not make every project restart — a compatible shared change should not automatically interrupt work already in progress.
• Translation is more than swapping words — a translated page should not pretend that an incomplete interface is fully supported.
• A plan must match the checker that reads it — a plan with an unfamiliar or mismatched format should be refused, not guessed at.

These notes describe released behavior and its limits. The internal release record remains the complete ledger; this shelf is for the useful lessons that ordinary readers can take home.