managed-setting is one of chock's eight compile surfaces and it reaches no agent in
practice: only claude credits it, and nothing installs it.
The README and docs/enforcement-surfaces.md already say so, and the generated surfaces figure
draws it in neutral grey rather than on the enforcement ramp — the honesty is in place. What is
missing is the work.
What to do: find out what it would take to make this surface real, and either do it or write
down why it should not exist. Both are valid outcomes, and the second is a real contribution: a
Surface member that will never be reachable is better deleted than left implying future support.
If you do implement it, credit only what actually works, and add the pinning-test coverage that
stops the credit drifting from the code.
Start by reading src/chock/compile/surfaces.py and docs/enforcement-surfaces.md. Larger than
an afternoon — take it if you want to understand chock's compile model properly.
managed-settingis one of chock's eight compile surfaces and it reaches no agent inpractice: only
claudecredits it, and nothing installs it.The README and
docs/enforcement-surfaces.mdalready say so, and the generated surfaces figuredraws it in neutral grey rather than on the enforcement ramp — the honesty is in place. What is
missing is the work.
What to do: find out what it would take to make this surface real, and either do it or write
down why it should not exist. Both are valid outcomes, and the second is a real contribution: a
Surface member that will never be reachable is better deleted than left implying future support.
If you do implement it, credit only what actually works, and add the pinning-test coverage that
stops the credit drifting from the code.
Start by reading
src/chock/compile/surfaces.pyanddocs/enforcement-surfaces.md. Larger thanan afternoon — take it if you want to understand chock's compile model properly.