Why Cut exists

Some code questions cannot be a pull request.

The person who should answer is on the other side of a boundary: no repository access, no branch, no shared working tree. Cut is the artifact built for that moment, and for the answer that has to come back across it.

Six things have to be true at the same time.

Content-addressed identity, provenance that refuses to lie, a local disclosure airlock, one URL with native representations for people and agents, access that fails uniformly, and an answer path that returns real code.

When you should not use Cut.

Use a pull request when the job is review and merge. Use a gist for a reusable standalone snippet. Use a call for synchronous pairing. Use a context workspace for long-lived project knowledge.