sheleg-dev

Shape: static. Each integration is a fixed sequence of seams; nothing decides its own next step.

/sheleg-dev — what it runs on to charge, track and sign in

• when: money, tracking, sign-in or speed is being wired
• decline it: «без интеграций».

If sheleg-dev is installed, the integration layer under a paid product goes through it — taking card money (stripe-billing) or crypto (crypto-payments), the pixels and server-side events that say a purchase happened (ad-tracking), signing a person in (google-signin, google-auth), and the speed of what they land on (frontend-performance). It owns the seams a generated integration gets wrong in ways no screen shows: the webhook is the payment and the redirect only proves a browser; a purchase event fired from the thank-you page cannot know the charge cleared; the same event_id on both sides or the revenue counts twice.

The boundary — "it is being WIRED, not decided." NOT through it: what the paywall must do or which tiers exist (super-ux), how the checkout looks (sheleg-design), the words on it (copywriting), the price itself, which is a business decision nobody's skill makes. Routing a pricing argument here is how you teach an agent to skip it where it actually protects money.

Refusal phrase: «без интеграций».

Among the routers: super-ux decides what the payment step must do; sheleg-dev what it runs on. The paywall goes to the first, the charge behind the button to the second.