Creative
Creative

Kriyā-Śakti Is Publishing — The Hands and Legs of Devi

Creative Practice

Kriyā-Śakti Is Publishing — The Hands and Legs of Devi

Fourteen drafts. Three of them are genuinely finished — you know they are, because you finished them, twice each.
developing·concept·1 source··Aug 3, 2026

Kriyā-Śakti Is Publishing — The Hands and Legs of Devi

The Folder Nobody Has Seen

Open the folder. Count them.

Fourteen drafts. Three of them are genuinely finished — you know they are, because you finished them, twice each. One has been "nearly ready" since February. There's a video you shot in one take that you watched back and never uploaded. There's an essay you'd defend in an argument tomorrow, sitting in a file, being defended by nobody.

Now the honest question: what would change if all fourteen went out this week?

Not would they do well. Would anything actually break?

Pashupati's translation of the second Śakti is one line, and it lands on this folder like a dropped weight:

For a creator, Kriyā-Śakti is publishing.1

Not creating. Not producing. Not the work. Publishing — the part where it leaves you.

Hands and Legs

The anatomy continues from the first cluster. Icchā was Devi's face. Kriyā is her hands and legs — the parts that move, that get you up, that do something.2

The division is exact and worth holding. A face without limbs is a position nobody can act on. Limbs without a face is motion with no orientation. You need the clarity to know where you stand and the limbs to get it out of the building.

And notice which body parts got assigned. Not the heart, not the voice, not the mind. The extremities — the parts furthest from the centre, the parts that make contact with the world. Publishing is where the work stops being yours.

What Actually Stops You

His diagnosis of the fourteen drafts is unsentimental.

If you sit in the so-called perfectionism and try to get it perfect before you publish — doing research for your content — for a creator, Kriyā-Śakti is publishing.3

The phrase so-called perfectionism is doing the work. He isn't granting it the status of a high standard that happens to be inconvenient. He's saying it's a different thing wearing that name.

And then the substitution, which is the actual mechanism and belongs to the next page: what gets you to publish isn't discipline or courage. It's karuṇā — care for the people who don't get the thing if you don't send it. Without it you'll never publish, because you're thinking I'm not perfect and failing to think so many people are going to lose out on this knowledge that I know.4

That's a genuinely different account of the blockage than the usual one. The standard story says perfectionism is fear of judgement, and the cure is courage or lowered standards. His says perfectionism is attention pointed the wrong way — at yourself and your standing — and the cure isn't bravery, it's redirecting attention onto someone who needs the thing.

You don't get braver. You get less interested in yourself.

Your First Ones Will Be Atrocious

He's blunt about the quality question, and he doesn't soften it into your early work has its own charm.

Obviously the first videos you make will be really bad. They'll be atrocious.5

Then the reframe that makes it survivable: whatever level of practice you have, that's the level of finesse you're going to see. Don't expect finesse without practice.6 You pick up a guitar — are you going to start playing like Clapton? It's going to take years before your content reaches the level of people who've been creating for years.7

And crucially, the care runs inward too. You have to care for yourself enough to say wow, I took my first step — instead of I don't look like that guy who's been creating for ten years. Where do you think he started?8

That last move is what separates this from ordinary ship-it advice. The instruction isn't to tolerate bad early work. It's to extend the same karuṇā to yourself that you'd extend to the audience — which, if you take it seriously, means the self-criticism blocking publication is itself a failure of the cluster's base rasa.

Implementation Workflow

Friday, and the essay has been done for nine days.

You open it to "check one thing" and forty minutes later you've rewritten a paragraph that was fine, and you know it was fine because you rewrote it back to almost exactly what it was.

So you stop and ask the question you've been avoiding: who is not getting this while I sit here?

Not rhetorically. Specifically. And you can name her — the woman who emailed in March describing the exact problem this essay solves, who you replied to with two paragraphs when you had four thousand words about it sitting in a folder.

That's the whole intervention. The essay doesn't get better in the next nine days. She just doesn't get it.

You set a timer for twenty minutes. Not to improve it — to do the last honest pass: typos, the one link you never checked, the sentence in the fourth section you've known was flabby since the first draft and kept not fixing because fixing it would mean the piece was finished.

Timer goes. You publish.

Then the part that matters more than publishing: you don't look at it. No refresh, no analytics, nothing until Monday. Because the thing that's actually been running you isn't the standard of the work — it's the wanting to know how it went, and if you let that back in at the moment of publishing, you've just moved the self-attention downstream instead of dropping it.

Monday, there are four replies. One of them is from her.

Analytical Case Study — The Cows

The best worked example he gives is about sculpture, and it's the one that keeps the page from collapsing into just ship it.

His first cow sculpture looked like a pig. A pig with a somewhat horse-cow face, he says.9

The obvious response is more attempts, more volume. That's not what he did, and this is where the page earns its keep.

He went and lived with cows. Stood in the heat drawing them live in a sketchbook, because what he was copying from the internet wasn't cutting it — he was missing the life force and the nature of the animal, which you can feel in its form and can't feel in a sculpture of it. He got chased. He got poked. It was all a pleasure to him.10

Why was the sculpture bad? Because the artist hasn't spent enough time. He'd already decided he knew everything about cows.11

Then the sculptures sold out. And his account of why is not "I got better technically" — it's that they had life in them, that people could feel something in the actual bronze that doesn't survive a photograph, and that he could charge accordingly because the work had that much energy in it.12

So the Kriyā doctrine is not publish anything, fast, forever. It's:

Publish before you're ready — the first cows go out, badly. And go to the source — living with the subject, not researching it.

Those two together are the actual instruction. Volume alone produces a thousand pigs. Volume plus contact produces something that sells out.

What Kriyā Is Not

Worth marking the boundary, because "action" is a broad word and he means something narrow.

Kriyā is not busyness. He's scathing elsewhere about people who chase trends, make an opinion video every time a scandal breaks, and let the SEO tool decide what they think about.13 All of that is action. None of it is Kriyā-Śakti, because none of it originates in care for a particular person.

Kriyā is also not production. You can produce continuously and publish nothing — the fourteen drafts are the evidence. Production is comfortable, because nothing has left you yet.

What Kriyā requires is the specific irreversible moment where the work becomes available to be received badly. That's the whole of it. And the reason he anchors it in karuṇā rather than discipline is that nothing else reliably gets a person through that moment.

The Fear That Produces the Movement

There's a second engine under Kriyā besides care, and it's the one people find harder to accept.

When you are afraid of not taking action, you take action. That is how Kriyā-Śakti is created.14

Both of the cluster's non-base rasas resolve into motion — both bhayānaka and bībhatsa lead to action15 — but only through karuṇā. Fear of the consequences of staying where you are, and disgust at where you are, are the two things that actually get a body up.

Which means the cluster is not a gentle one. Its base rasa is care, and its working rasas are terror and revulsion, and the design is deliberate: care is what keeps the other two from being cruelty.

The uncomfortable implication for a creator is that comfort does not publish. Nothing in this cluster suggests you'll ship because you feel good and ready. You ship because the alternative has become intolerable — either you can't stand the version of yourself who's sitting on it, or you can't stand what happens to the person who doesn't get it.

And one more thing worth naming, which he says in passing and doesn't develop.

When you're creating content, you're transferring energy, not information.16

If that's true, publishing isn't distribution. Distribution is what happens to information — it goes out, copies are made, nothing leaves you. Energy transfer means something is actually spent.

That reframes the reluctance in the folder. Part of what makes the moment before publishing feel costly may not be fear of judgement at all. It may be an accurate read that something is about to leave and not come back — which is a reasonable thing to hesitate over, and a reason the cluster needs two rasas' worth of force to get past it.

Evidence, Tensions, Open Questions

Evidence. The strongest support is the reframe itself: locating the blockage in self-attention rather than in courage explains why courage-based interventions ("just be brave," "feel the fear and do it anyway") have such a poor record against perfectionism, and why thinking about a specific person works so reliably.

Tension — publish-fast against go-to-the-source. These pull in opposite directions and he never says how to hold both. Living with cows takes months. The instruction to publish atrocious early work says don't wait. A creator following both gets whiplash, and the source offers no sequencing.

Tension — the Gurukulam trust-flag. "Publish before you're ready" is convenient doctrine for someone selling a publishing programme, and the 84-day challenge sits directly downstream of it.

Open question. If perfectionism is misdirected attention rather than fear, what about the creator whose care for the audience is exactly why they won't publish something unfinished? He treats karuṇā as always pro-publication. It isn't obviously so.

Author Tensions & Convergences

Set this beside Krisang's Kriyā as the Only Path to Gyāna and you find teacher and student using the same word for two stages of one process.

Krisang's Kriyā is epistemic. Action is how knowledge gets made — you cannot get real knowing from consuming information, only from doing the thing. His concern is the person who has watched forty videos and understands nothing, and his cure is to act so that understanding can form.

Pashupati's Kriyā is transactional. Action means the work leaves the building. His concern isn't the person who hasn't learned; it's the person who has learned and is sitting on it.

Follow Krisang and you act in order to know. Follow Pashupati and you publish in order to serve. And the two produce genuinely different daily practices — the student's version is satisfied by private work that teaches you something, and the teacher's version isn't satisfied by anything that stays private.

They also stack, which neither of them says. Krisang's kriyā generates the knowledge; Pashupati's kriyā delivers it. A creator running only the first learns continuously and publishes nothing. A creator running only the second ships constantly and has nothing to say, because they never did anything long enough to know something.

Against The Content Monk Archetype the tension is sharper. The Monk's whole posture is patience, creating from silence, work as prayer, editorial cadence as ritual — and there is nothing in that posture that treats the unpublished as a failure. The Monk can sit with something for a year. This page says the year is a person not being served.

Cross-Domain Handshakes

To Creator Economy Hubbusiness

The creator-economy corpus is emphatic and near-unanimous on shipping: publish daily, volume beats deliberation, the algorithm rewards consistency, your first hundred pieces are tuition. The warrant is statistical and platform-shaped — you can't predict what lands, and the distribution machine feeds on frequency.

Pashupati arrives at the same instruction from care for a specific person.

What holding them together produces is a prediction about what each doctrine does to a creator over years, and they diverge completely despite identical weekly behaviour. Volume doctrine trains you to optimise against a distribution system, which means your attention during production is on the system — its formats, its rewards, its rhythms. Karuṇā doctrine trains you to optimise against a person, which means your attention is on her. Both produce a piece on Tuesday. Only one of them produces a creator who still knows who they're talking to in year five, and the burnout the creator-economy literature documents so thoroughly may be exactly what it looks like when the first kind of attention runs long enough. You cannot sustain attention on a machine.

To Somatic Trauma Theory Hubpsychology

The psychology corpus has a well-developed account of perfectionism, and it does not read it as high standards. It reads it as shame-avoidance — the work is held back because release exposes the self to evaluation, and evaluation is intolerable for reasons that predate the work entirely. The clinical marker is that finishing is fine and releasing is not, which is exactly the fourteen-drafts pattern.

Pashupati's cure is redirection: stop attending to yourself, attend to the person who needs it.

The insight the pairing produces is a real caution about that cure. The clinical literature would say redirection can be a genuine reorientation, or it can be avoidance wearing a nobler coat — the person still cannot tolerate exposure, and has simply found a frame in which they don't have to notice. The tell is what happens after publishing: genuine reorientation leaves you interested in whether it helped her, and avoidance leaves you refreshing metrics with your stomach in a knot. Which is why the workflow above puts the don't-look instruction where it does, and why "publish more" prescribed to a shame-driven creator can increase output and increase the underlying damage at the same time. Volume is not evidence the block has resolved.

The Live Edge

Sharpest implication. Perfectionism is not a standards problem and not a courage problem — it is attention pointed at yourself, and the cure is not to become braver but to become less interesting to yourself than the person waiting for the thing. Which reframes every unpublished draft: the question isn't whether it's good enough, it's who is currently not being served by your self-regard.

Generative questions.

  1. Krisang's kriyā makes knowledge, Pashupati's delivers it, and they stack. Why does each teacher only hold one half — and is a lineage where the student teaches the private half and the teacher the public half a coincidence?
  2. If karuṇā can also be a reason not to publish something unfinished, what distinguishes protective withholding from perfectionism, from inside?
  3. Volume can rise while the shame-block stays intact. What would count as evidence that a creator's publishing problem had actually resolved rather than been routed around?

Connected Concepts

Footnotes

domainCreative Practice
developing
sources1
complexity
createdAug 3, 2026
inbound links4