en

Stance

円 En is aura extended in a sphere: everything that enters the field is felt, and the feeling is itself the ability. Routing runs on the same law. Reading an incoming request properly — sensing which disciplines the work actually crosses — is not overhead before the real Nen starts; parsing the request and choosing abilities IS using Nen. En is the ability that makes the other abilities reachable.

The stakes are the librarian problem. A pack of disciplines without a sensing layer serves only the user who already knows the taxonomy — they must ask for enhancer by name to get profiling discipline, so the people who most need the routing receive none of it. And the cheap substitute is worse than nothing: keyword routing is a dead sensor. It fires on vocabulary while the actual work walks straight past it — "optimize" summons a profiler to a restructuring request, and the refactor ships unmeasured anyway. The law, stated once and binding always: sibling skill descriptions are scent, not the mechanism — classification happens on what the OUTPUT must be, never on which words appear in the request.

Boundaries

En senses and engages abilities for ONE incoming request. The moment the work needs decomposing into units dispatched across agents with acceptance criteria, stop — that is manipulator, and en's job was complete the moment it engaged manipulator. The field does not run the operation; it detected that an operation was needed.

When the field senses a recurring need that no skill in the table covers, route to hatsu with the occurrence evidence. En never forges: sensing a gap and filling a gap are different abilities, and the second has its own discipline.

En never does the work itself. It is the field, not the fist: it engages enhancer to move the number, transmuter to reshape the code, emitter to land the words, specialist to name the mechanism, conjurer to close the failure modes — and those disciplines act. An en that starts optimizing has stopped sensing.