संस्कृतव्याकरणम् · A6 of 24 Home
Aṣṭādhyāyī · A2–A5, on one word · प्रक्रिया

One word.
Forty-nine rules.

A2 showed what a sūtra silently inherits. A3 showed what governs it from above. A4 showed what makes a whole stretch of rules invisible to the rest. A5 showed what happens when two rules both want the same word. Those were each shown once, cleanly, separately. Here they run at once, on कृ + णिच् + सन् → चिकारयिषति — a causative built on a desiderative, the one place in this series two सनादि affixes stack on the same root.

→
·
rules fired, per the live engine
which rule fired, and what kind what it inherited (अनुवृत्तिः) what governed it (अधिकारः) and what it beat

The payoff, not another mechanism

Orientation

Nothing below is a new idea. Every device this page uses was taught on an earlier page in this tier — this one only asks what a reader actually needs once real Sanskrit shows up: not one mechanism at a time, but all four, at every single step, on a word worth the trouble.

कृ + णिच् + सन्Why this word

Page 14 already named this stack — STACK['nic_then_san'] — as the one place in the whole series two सनादि affixes pile onto the same root, and moved on once it had the form: . That page's job was cataloguing what the seven सनादि affixes do; it was never going to stop and explain why the rules that build चिकारयिषति fire in the order they do. This page is that unpacking, and the word earns it for a specific reason: stacking the second सनादि affix does not just add rules on top — it changes which rules the first affix's own neighbourhood is even allowed to see. Run सन् directly on कृ and it takes one path; run it on कारि (कृ+णिच्'s own output) and it takes a genuinely different one, for reasons the corpus's own commentary states outright. §5 below walks that fork in full.

The live derivation tool already exists — this page does not rebuild it. Grammar/site/prakriya.html derives any tiṅanta form with every rule linked into the reading view, and every citation on this page traces back to a session driving exactly that engine. What it does not do is stop at any one step and ask what that step inherited, what governed it, or what it beat — that is the question this page adds.

Four questions, asked of every step below

A1–A5, in one place

Each column below is a page you have already read, turned into a question a reader can ask of a single rule as it fires.

ColumnThe questionWhere it was taught
1 · which ruleWhich sūतra fired, and which of the five kinds of statement it is — संज्ञा, विधि, अधिकार, अतिदेश, परिभाषा A1 · सूत्रशैली
2 · what it inheritedWhich words it did not state itself, carried in from an earlier sūत्र by अनुवृत्तिA2 · अनुवृत्तिः
3 · what governed itWhich of the 73 अधिकार domains were still open, silently supplying a word or a modeA3 · अधिकारः
4 · what it beat, and whyThe rival rule that also applied and lost — to परत्व, नित्यत्व, अन्तरङ्गत्व or अपवादत्व — or the असिद्धत्व wall that made a whole stretch invisible to itA4 · A5

Column four is the hard one, and the honest answer is often "none." Most of the 49 rules below have no named rival at all — they are simply the next mandatory step, and inventing a conflict for a rule that has none would be worse than leaving the column blank. Where a rival is named below, it is named because the corpus's own commentary layer names it, not because this page went looking for a fight.

चिकारयिषति, sixteen steps of forty-nine

Interactive

Step through. Sixteen of the real forty-nine are shown — the rest repeat one of two mechanical patterns already visible below (it-letter deletion, अभ्यास purification) with nothing new to say. Toggle to just the forms to see what a textbook prints instead.

1 · which rule
2 · what it inherited
3 · what governed it
4 · what it beat

Same affix, two rule-paths — because णिच् ran first

The ordering effect

Run सन् directly on कृ (desiderative alone: , rules) and it takes one path. Run it on कारि — कृ+णिच्'s own output, inside चिकारयिषति — and the same affix, at the same point in the derivation, takes a different one. Neither path is wrong; they answer to different rules because a different stem is standing in front of सन् by the time it attaches.

stage
The Kāśikā already knew this rule had to reach further than one literal shape. — its own gloss on , which governs सन् on कृ directly. Read past "धातोः" (of a root) and it adds, unprompted: it applies "so that it works for चिकीर्षति too" — the very word on this page's own hero. The Kāśikā's gloss on is equally direct about column four for that path:

What the tradition wrote down, and what running the rules gives

Two accounts

There is no independently-stored derivation chain for a verb the way C.sandhi() ships one for a sandhi pair or shabda/prakriya/ ships one for a nominal cell — both of those are subanta machinery, and the engine this series drives derives only tiṅanta forms. What the commentary layers do leave behind, for this exact stack, is their own worked examples — quoted below in full, not paraphrased.

sūत्रthe Kāśikā's own exampleengine's full account
Nobody wrote out चिकारयिषति itself. The Kāśikā cites चिकीर्षति twice and कारयति once — the two ingredients — but never their sum. Once 3.1.32 सनाद्यन्ता धातवः is understood, the stacked form follows automatically, so nobody needed to spell it out by hand. The -step account in §6 below is what spelling it out looks like once nobody has to do it by hand.

All , in order

How many steps a real derivation takes

A textbook says three: root, causative affix, desiderative affix. The engine's own rule history says . Every row below is one firing, in the order the engine returned it — including the ones that repeat.

#सूत्रtextkindform after
Where every number on this page comes from. All four rule histories (करोति, कारयति, चिकीर्षति, चिकारयिषति) were captured once, live, driving AD.engine.call('deriveTinantas', …) on Grammar/site/prakriya.html over CDP, with dhatu.sanadi set to each of [], ['Ric'], ['san'] and ['Ric','san'] — the same shape that page's own engine.js builds, extended with the sanādi list its UI does not expose a control for (page 14 drove the same engine the same way for the same reason). The four transcripts are frozen in A6-prakriya.engine.json so this build does not depend on a running WASM engine, but nothing in them was retyped: every rule reference is resolved through C.sutra() / C.sutra_rec() at build time, which fail the build on a wrong number. The four-column breakdown in §3 — which अनुवृत्ति words, which अधिकार stack, which rival — is sutra_rec() read fresh for each of the sixteen curated steps; the rival named at each step is either a fact the corpus's own commentary states about that exact rule (marked as such) or, honestly, none.

Check yourself

अभ्यासः

Six questions, each about one of the four columns.