The Hiranyakeshi Shrauta Sutra
The Vedic ritual runbook: 3,000-year-old procedures for fire rites - spill repairs, resurrection rites, absence protocols, declared desire. No complete English translation found in the checked inventory.
Concepts
Inherit the Template
This is atideśa as engineering discipline.
Never write the same procedure twice. Define the archetype once, then point every variant at it by reference — the manual stays small because procedure is declared once and reused by pointer. "The procedure has been set forth by means of the whisper-offering." (praśna 7)
Why it matters
This is atideśa as engineering discipline. Duplication is where rituals (and codebases) rot; reference is how they stay consistent.
Use when: Use when you're documenting the Nth variant of a process and rewriting the shared steps. Stop. Name the template, describe only the delta.
Rebuild, Don't Improvise
The system distinguishes failure from novelty.
When the sacred fires are lost, there is no improvised recovery rite. The answer is punarādheya — re-establishment — and the whole procedure is one line: re-run the founding rite. "We shall explain the re-establishment of the fires. Its procedure has been set forth by the establishment-of-the-fires rite." (praśna 3)
Why it matters
The system distinguishes failure from novelty. Recovery procedures that invent new steps under stress produce a second, worse failure.
Use when: Use when a system goes down and the room starts designing a bespoke resurrection plan. Run the founding procedure again instead.
The Spill Protocol
Vague recovery instructions fail under pressure.
Every named failure gets a named repair, scripted in advance. If the speckled ghee spills mid-rite: take fresh ghee, speak the repair formula — "a drop has spilled; may mind enjoy the light" — offer one oblation with the two ladles, continue. Spills are priced in. (praśna 15)
Why it matters
Vague recovery instructions fail under pressure. A system that can't name its repairs can't survive its operators.
Use when: Use when writing runbooks. Write the exact recovery words now, while calm, so nobody composes them while the ghee is on the floor.
Pay What You Can
Flat fees filter by wealth; proportional fees filter by commitment.
The sacrificial fee is not flat. At the fee-giving, the sacrificer gives according to his ability. The most expensive ritual technology in the ancient world prices itself in proportion to means. (praśna 2)
Why it matters
Flat fees filter by wealth; proportional fees filter by commitment.
Use when: Use when setting dues for something meant to include everyone. Scale with ability and watch the participation problem dissolve.
Right Season for the Role
The cheapest variable to differentiate on is often timing, not procedure.
One rite, three schedules. Initiation in spring for the priest, summer for the warrior, autumn for the merchant. Same ritual, stratified calendar — differentiate on when, not what. (praśna 26)
Why it matters
The cheapest variable to differentiate on is often timing, not procedure.
Use when: Use when one program serves segments with different rhythms. Don't fork the program — stagger the calendar.
Darkness to Darkness
Any credentialing system that punishes only the failed student while ignoring the unqualified teacher has the liability backwards.
The ignorant man who initiates a pupil, and the pupil who gets initiated while ignorant — both go from darkness into darkness. Bad teaching is framed as a two-way injury, stated as cosmology in the section on who may teach. (praśna 26)
Why it matters
Any credentialing system that punishes only the failed student while ignoring the unqualified teacher has the liability backwards.
Use when: Use when deciding whether someone is ready to teach — or be taught. If either answer is no, wait.
Rules for Being Away
Most systems are designed for everyone present.
The manual has a full protocol for the sacrificer's absence — pravāsa, dwelling outside the village. What may lapse, what must not. Even the operator's absence is proceduralized, not left to improvisation. "Apart from the household, we shall explain the sojourn abroad." (praśna 3)
Why it matters
Most systems are designed for everyone present. This one answers "what breaks when the key person leaves?" in advance, in writing.
Use when: Use when writing the "while I'm away" doc. Specify which duties travel, which pause, which must never pause.
The Framework First
The manual has a technical term for "don't loop what you can unify."
Tantra — the shared framework, executed once. The three upasad days aren't three rituals; they're declared a single framework and run as one. Factor the common structure out, run it once. (praśna 7)
Why it matters
The manual has a technical term for "don't loop what you can unify."
Use when: Use when you catch yourself running the same setup N times for N items. Declare the tantra.
Design for the Doubtful Case
Edge cases designed last get the worst design.
The funerary manual doesn't start with the clear case — it starts with the ambiguous one: when there is doubt whether the fire-establisher has died, mark out the cremation ground. Maybe-dead gets a procedure before certainly-dead does. (praśna 28)
Why it matters
Edge cases designed last get the worst design. Hesitation itself becomes procedural.
Use when: Use when spec'ing a process with a fuzzy trigger. Write the maybe-case first, not as an appendix.
Declare Your Desire
Rituals drift into maintenance mode, performed because scheduled, wanted by no one.
Every rite names its goal upfront. The new- and full-moon offerings are specified as the instrument of one who desires heaven. The desire (kāma) is part of the specification — procedure bound to purpose. (praśna 2)
Why it matters
Rituals drift into maintenance mode, performed because scheduled, wanted by no one. A process that can't name what it's for is already dead.
Use when: Use when reviewing recurring meetings or reports. Ask each one: who desires what from this?