Three things a workspace should be able to prove about itself

A folder without a CONTEXT.md is a folder the agent has to guess about, and it will.

Loose files in the root are where structure goes to die. They arrive one at a time, so there is never a day you notice it happening.

Every relative link resolving is the one worth having. Rename a file and every reference to it keeps pointing at nothing. No error, no crash, nothing turns red. The model reads around the gap and answers you anyway. It is the only failure of the three that leaves no trace.

Attached is a shell script that checks all three. No dependencies, any Mac or Linux, run it from the workspace root. It exits 0 or tells you what is wrong.

One thing before you trust it: break it on purpose. Delete a CONTEXT.md, run it, watch it fail, put the file back. A check you have never seen reject anything and a check that quietly stopped matching look identical from where you are standing.

What else would you want it to catch?

0 comments

Three things a workspace should be able to prove about itself