A path that hands your work to another skill is fixed, not configurable, and the reference now says which paths those are.workspace-status' layout page documented a shaping key nothing reads and left out output_dir, the one every consumer does read. It now describes the real key, explains that the shaping folder is composed under it rather than configured beside it, and states plainly that your briefs and intents folders are hand-offs — redirect them and the artifact stops being found.
A new intent now gets a readable name, not just a slug. An intent admitted through work-intake at a recognized altitude lands as CAP-0004-external-tracker-projection.md rather than external-tracker-projection.md, so you can say which one you mean out loud. The number is per altitude, so a capability and a feature can both be 0001.
Admission never stops because a number was unavailable. If the altitude has no prefix, or the allocator cannot be sure of its answer, the intent is still written and registered under its plain name and records why — so nothing you were doing is lost, and the number can be added later. The slug is the identity; the number is a label for humans.
Nothing is renamed. An intent already on disk keeps its filename whatever its altitude, so existing links and registry entries keep resolving.
The layout reference answers your question instead of citing ours. Where it used to say that two of our internal proposals disagree about whether a skill offers the default path before asking you, it now tells you what to do: do not rely on either order, and set output_dir explicitly if the distinction matters.