Definition #
The supply-side actors who run the consultancy-face instance of [Transactional Arbitrage]. The operators-of-the-arbitrage in the consultancy domain. Named instance under the parent — not a new mechanic, the actors-running-the-mechanic.
Family #
NEEDS WORKSHOP
Why Behind the Thinking #
NEEDS WORKSHOP
Pairs With #
[Transactional Arbitrage] (parent), [Hacksterism] (worldview), [Hack Funnel] (operating form), [Transactional Fix] (product), [Static Decline] (what their product produces). * Layer: Actor layer under [Transactional Arbitrage] consultancy face. * Origin language (user verbatim, prior session): “i call them drug pushers. the addiction is the crak they sell operators that need a solution bad.” Why “Pushers” over “Dealers”: Pushers carries active behavior — push the product, push the close, push the next tier. Dealers reads passive — set up shop, take orders. The consultancy-face actor pushes; doesn’t wait. Active verb fits the actor. * Lead-term compliance: Leads with “Transactional” per the locked Transactional family lead-term rule. Not a character claim about any individual consultant. Role-claim, not a character claim — names the actor running the role, not any specific actor by name. * Open: 1. Test against [Hacksterism] / [Hack Funnel] — does naming the actor add diagnostic value beyond worldview and operating form? Initial read: yes. * Open: Test for character-claim risk — process-read discipline applies. * Open: Test for vocabulary collision — “pusher” carries drug-trade resonance. User chose this deliberately. Resonance is the asset, not the liability. * Open: Test against [Hacksterism]’s “what it is not” line.
Placement #
Core Architecture
