Viraha-jvara

What the controlled programme establishes

In Bhuvaneśvaranātha Miśra “Mādhava”, Rāmabhakti-sāhitya meṃ Madhura Upāsanā (Bihar Rāṣṭrabhāṣā Pariṣad, Patna, 1957), scan 304 / printed page 277 explicitly begins विरह-ज्वर. The quotation window continues across scans 305 and 306 and through two visual groups at the top of scan 307 / printed page 280, where the explicit अष्टयाम-भावना heading begins the next section.

The local window contains 9 + 15 + 15 + 2 = 41 visually separated groups. These are editorial observations used only to describe the programme boundary. They are not canonical numbers, not a verified complete-work extent, and not prepared text units. Repeated language, signature forms, page crossings, and source lineation remain quarantined in the controlled images without transcription or normalization.

Checked image identity

• Scan 304 / printed page 277 · 9 visual groups in the bounded window
  5fef15318919391a942e3110afde3208d203d818895f6c92dafa8ade8500a2a9
• Scan 305 / printed page 278 · 15 visual groups in the bounded window
  51d7bc599cd71400a34fd4e4aee9f278cba353608770549f0afae6d78e43b75c
• Scan 306 / printed page 279 · 15 visual groups in the bounded window
  79035fadaf5ae001f37f04bc48d60b507bfd4cf86dcce75aafe1c1d8fcf6c2af
• Scan 307 / printed page 280 · 2 visual groups in the bounded window
  99e776ad30f118646c186315c4ebbf3865d06131931dafa6203127ce17fee06f

All four hashes match the preceding scripture-50 manifest. That shared source control preserves adjacent evidence while keeping scripture 50 and scripture 51 as separate registry identities.

Attribution and role boundary

Chapter Eight separately registers Viraha-jvara under Lavakuśa Śaraṇa “Līlābihārī”. The programme's surrounding prose, however, discusses sections in a collection and examples from Yugalānanya Śaraṇa's writings; some groups contain Yugalānanya signature language. Neither fact alone settles exact-work authorship.

Yugalānanya signature lines do not prove that every quoted group constitutes a separate Yugalānanya work. A collection, compiler, collector, publisher, or guru-lineage notice likewise does not prove primary authorship by Lavakuśa Śaraṇa. The registry attribution is preserved without presenting the unresolved role as verified.

Secondary bibliography and bounded search

Church Mission Press, Gorakhpur, 22 November 1916 is the settled reading of the neighbouring secondary programme notice. No primary Viraha-jvara title leaf or colophon currently proves that imprint for this separately attributed identity.

Ten Internet Archive query families, nine bounded public query strings, saved catalogue searches, and controlled local-corpus searches produced 0 independent exact-work candidates. The only broad Archive result, a 2014 Krishna separation-mantra audio item, was rejected by title, attribution, genre, date, and format. Generic “separation fever” phrases in unrelated texts are not title evidence. Search absence does not prove loss.

The inspected programme title page identifies the 1957 secondary study. Its final content leaf is an index and its final scan is a blank rear cover; neither supplies an exact-work ending or colophon.

Precise gaps

• No independent witness securely links the bounded programme quotation window to the separately catalogued Viraha-jvara attributed to Lavakuśa Śaraṇa “Līlābihārī”.
• Primary author, compiler, collector, publisher, and lineage-successor roles for the exact work remain unresolved.
• No exact-work primary title leaf, author statement, opening, ending, colophon, imprint, pagination, or continuous ordered witness is controlled.
• Canonical unit type, count, numbering, order, repetition pattern, and total extent are unknown.
• It is unverified whether material before or after the programme window belongs to the same exact work.
• Church Mission Press, Gorakhpur, 22 November 1916 is secondary contextual evidence from the neighbouring programme notice, not verified primary-imprint evidence for this separately attributed identity.
• No original text, English translation, textual note, reader, unit route, print view, PDF, facsimile, binary asset, or download is released.