Decoding the Panji of Mithila · Volume IV · Chapter 29

Mahishi to Dath and the Mangrauni-Madari Continuation: Entries (221)-(229)

Source-derived chapter text. Source: DECODING_PANJI_4.pdf, PDF pp. 323-328. The web page preserves one formal book chapter as one HTML document; book-level appendices and front/back matter are not promoted to separate chapter pages.
Chapter 29
  Mahishi to Dath and the Mangrauni-Madari Continuation:
                     Entries (221)-(229)
29.1 Scope and Point of Resumption
    This chapter begins at entry (221), exactly where Chapter 28
stopped. It covers entries (221)-(229) only. Entries (221)-(223)
close the present Mahishi-Pali sequence; entries (224)-(229) move
into the Mangrauni-Pali continuation, including the split across
the source-file boundary between Vol-3Final03-a and
Vol-3Final03-b. The chapter deliberately stops before entry (230),
where a new Nagram/Hati-Pali sequence opens.
    The chief control for this chapter is the Pali framework.
Mahishi, Mangrauni, and Jamdauli are all held by the index
under Pali, so the shift from Mahishi to Mangrauni is not a
change of the underlying Pali register. It is a shift from one Pali-
controlled gram line to another. The repeated place names such
as Dath, Basanhi, Tharhi, Madari, Virsayar, and Babhanigam are
read as route, settlement, or local continuation labels unless a
separate index rule elevates them.
29.2 Entry (221): Mahishi to Dath
     Entry (221), Mahishi to Dath, resumes from the Ramanath
branch left open at the end of the preceding chapter. The opening
movement names Bhangi through the Belauch-Bhavanath-Juraun
connection and then introduces another line through Pabauli-
Machal-Narayan Datt, Ghusa ut-Sanphool, and the Bacha group.
Bacha’s sons Tejnath, Ganesh, Kantir also styled Vishwanath,
Babuji, and Bhagirath create a thick collateral cluster. This is a
good example of a Panji entry that does not read as linear prose;
it is a register of parallel descent and sambandha references.
    Tejnath’s line is especially important. It first gives Bhular,
then Ravi and Gangadhar. Bhular is associated with Darihara and
Karmaha references, while Ravi and Gangadhar carry further
links through Baliyas, Jajival, Darihara, Budhwal, and related
nodes. The entry then closes with the Ratnath branch and the

later Vijay Nath, Upendra, and Mahendra group connected
through Parhat-Sakararhi. The Dath label is therefore the
destination field of the entry, while Mahishi-Pali remains the
governing source identity.
29.3 Entry (222): Mahishi to Basanhi in Madhepura
    Entry (222) carries the Mahishi line toward Basanhi in the
Madhepura region. It begins with Kantir or Vishwanath, then
moves to Lakshminarayan and the Ramashankar/Lallu line. The
Badhiyam-Pabauli link through Chandramani and Suryamani is
inserted inside this entry, followed by Manbodh, Khelpati, and
Chandramani again, so the source is preserving an interlocked
chain rather than a simple father-son list.
    Lakshminarayan’s son Kumarnath receives a Soderpur-
Ramdatt-Sadhu connection. Ramashankar gives Bindhyanath,
and Bindhyanath is attached through Khaual-Janakinath-
Indranath and Sarisab-Mahamahopadhyaya Santgopal. The same
entry then moves to Govind’s son Kuli, Parasmani’s son
Badrinath, Grihimani, Muni, Ishdatt, Bhikhi, and Shatrughan. The
pattern is a closing Mahishi branch with several named sub-lines
and a dense spread of Soderpur, Sarisab, Darihara, Pali, Khaual,
Khanda-bala, Karmaha, and Ghusa ut controls.
29.4 Entry (223): Mahishi to Mangrauni-Tharhi
    Entry (223), Mahishi to Mangrauni-Tharhi, is the hinge
between the Mahishi and Mangrauni materials. It begins with
Phalgun and his sons Bacha, Kanhai, Gopi, and Govind. Bacha
runs through a Darihara-Bhoranath-Manik route; Kanhai
produces Srishtidhar and Krishnadhar; Krishnadhar, also styled
Krishna, gives Babuji or Gangadhar; and Gangadhar then gives
Chandradhar. The source also records Gopi and Govind branches,
with Govind’s son Ganesh followed by Tarakant and
Saraswatikant.
     The later part of entry (223) is structurally important because
it introduces Arjun, Mannu, Lotan, and Jhotan. Mannu’s Mukund-
Balli line and Lotan’s Baidyanath line lead toward Soderpur and

Baliyas connections. Jhotan’s sons Giridhari and Gumani
continue into Muktinath, Shivdatt, and Haldhar. The quoted
Muktinath sambandha formula is retained in the register,
showing that the compiler was preserving a specific received
variant rather than smoothing it into a single normalized
genealogy. The entry ends by bringing the line toward
Mangrauni, so it prepares the next Pali gram opening.
29.5 Entries (224)-(225): The Mangrauni-Pali Opening and Its
First Extension
    Entry (224), Mangrauni to Babhania, opens the Mangrauni-
Pali gram register. The entry begins from Manbodh and then lists
Bhavadatt and many alternate branches: Jivan, Hridaynath,
Durlabh, Mangani, Shivan, Mani, Shobhnath, Shrinath, Bhanjan,
Bacha, Dayanath, Kalanath, Sanphool, Modnath, Lakshminath,
Janaki, and others. The numbering of many “apara” branches is
significant. It shows that the source is not merely narrating
succession; it is separating remembered collateral streams under
a single Mangrauni-Pali framework.
    Bhavadatt’s son Sonma and Chanda form an important sub-
division. Sonma gives Kulmani and Nityanand; Kulmani gives
Ayodhyanath; Ayodhyanath gives Mahadev and Basudev.
Nityanand gives Baidyanath and Meghanath. The entry thus sets
up a wide family map under the Mangrauni heading. The
repeated links to Satlakha, Soderpur, Pali, Khaual, Jajival, Baliyas,
Karmaha, Sarisab, Babhania, Mandar, and Belauch should be
treated as sambandha and route controls, not as replacements
for the Mangrauni-Pali heading.
   Entry (225), Mangrauni to Babhanigam-Madari, continues
Chanda and Jivan. Chanda’s line gives Babunandan, Phalgun,
Arjun, and Chhedi; Babunandan is connected through Narun-
Bhikhiya-Dhirnath and Sarisab-Govind. Phalgun gives
Shiveshwar or Chichan, and Shiveshwar is tied through Baliyas-
Lanha-Yashodhar and Pali-Gharbharan. Jivan’s son Mangani then
creates another stream through Babue, Manne, Kun-kun,
Nityanand, Pachkaudi, Vishweshwar, Jageshwar, Hari, and

Durlabh. The line at the end of the source-file segment is visibly
unfinished, ending in the middle of the Dayashankar-related
chain; the continuation appears at the start of the next source
file.
29.6 Entries (226)-(229): Mangrauni Continues Across the
Source-File Boundary
    Entry (226), Mangrauni to Madari, begins in Vol-3Final03-b
and continues the end of the preceding Mangrauni material. The
opening preserves Devkinandan and the Yatashankar-
Dayashankar sequence, then gives Lootan’s son Ramanath, also
styled Khataru. Ramanath’s sons include Durganath, Premnath,
Sahityacharya-Principal Dinanath, and Bhagwanji. The entry also
brings in Bhaskar, engineer Pushkar, Sanjay, Vinay, and other
later or status-marked names. This shows a modern layer
entering the Panji formula without breaking the older structure
of suta, sambandha, and route.
    The same entry continues through Chhotu, Mahavir,
Shashivir, Gudar, Kamlu, Lala, Bhairavi, and Gauridatt. Gudar’s
sons Kamlu and Lala link to Sarisab, Pali, and Satlakha lines;
Bhairavi and Gauridatt supply additional sambandha paths.
Entry (226) is therefore not a new gram beginning but a
continuation that completes the Mangrauni-Madari material
after the manuscript or file break.
   Entry (227), Mangrauni to Virsayar, begins with Shivan’s sons
Vanshmani and Grihimani, and then moves through Manik,
Shobhnath, Brahmadatt, Dharmadatt, Babu, Gopal, Jagmohan,
Rudramani, Shrinath, Jayanath, Fakiran, Deonath, Babunath,
Gopinath, Babua, Ram, Manmohini, Lakshminarayan, and
Madhusudan. The Virsayar label is a route marker, while the
descent logic remains Mangrauni-Pali. The entry is rich in
Sarisab, Darihara, Pabauli, Baliyas, Belauch, Gangoli, Hariamb,
Soderpur, Karmaha, and Khaual controls.
   Entry (228), Mangrauni continued, begins with Bhanjan’s son
Anand and Bacha’s son Shyamnath. It then develops Dayanath’s
sons Adinath and Premnath, the Shyamnath and Kalanath lines,

Sanphool, the Hanumandatt-Bhagwandatt-Shankardatt-
Chandidatt-Ishwaridatt group, and the Modnath-Babunath-Jhotan
group. Later, Janaki and Bawunath extend the record through
Kanhai, Babunath, and additional Baliyas, Pabauli, Pali, Satlakha,
Karmaha, and Soderpur references. This entry is a consolidation
of collateral material before the Mangrauni sequence closes.
    Entry (229) is marked rikta. In this chapter it functions as a
formal closure marker: it confirms that the Mangrauni segment
has a numbered place in the source sequence even though no
genealogical matter has been supplied for that entry.
Immediately after it, the source writes “Nagram” and then entry
(230), Hati to Satlakha. That new Hati-Pali sequence belongs to
the next chapter.
29.7 Index Logic Applied
    The index control is decisive here. Mahishi and Mangrauni
are both under Pali, and Jamdauli also belongs to the same Pali
group. Therefore the chapter should be read as a Pali-register
transition from Mahishi into Mangrauni, not as a movement into
a wholly separate gotra-mool structure. The Pali control explains
why the same network of Sarisab, Soderpur, Baliyas, Khaual,
Darihara, Karmaha, Pabauli, Jajival, Mandar, Belauch, Budhwal,
and related nodes recurs throughout the chapter.
    The file boundary between entries (225) and (226) does not
create a conceptual break. Entry (225) ends mid-flow, and entry
(226) continues the same Mangrauni-Madari material. The
interpretation therefore keeps the source-file transition visible
while preserving the genealogy as a continuous register.
   Entry (229) is treated as a true rikta entry. It is not omitted,
and it is not filled from inference. Its presence matters because it
separates the Mangrauni sequence from the following Hati
sequence. This prevents the next chapter’s Hati material from
being mistakenly absorbed into Mangrauni.
29.8 Coverage Ledger for Chapter 29

 • Entries (221)-(223): Mahishi to Dath, Mahishi to Basanhi in
    Madhepura, and Mahishi to Mangrauni-Tharhi.
 • Entries (224)-(225): Mangrauni-Pali opening to Babhania and
    Babhanigam-Madari, including the unfinished continuation at
    the end of Vol-3Final03-a.
 • Entries (226)-(228): Mangrauni to Madari, Mangrauni to
    Virsayar, and the final Mangrauni continuation preserved at
    the beginning of Vol-3Final03-b.
 • Entry (229): rikta, preserved as a formal source entry.
 • Reserved for Chapter 30: entry (230), Nagram/Hati to Satlakha,
    and the subsequent Hati-Pali sequence.
29.9 Transition to the Next Chapter
    The next chapter should begin with entry (230), Hati to
Satlakha. That heading follows a clear “Nagram” marker and
opens a new Hati-Pali run. Keeping it outside Chapter 29 protects
the boundary between the Mangrauni continuation and the next
Hati sequence.

Source structure and verification apparatus

Editorial source apparatus. This apparatus is descriptive, not interpretive. It records the source-controlled structure used to verify that this page corresponds to formal Chapter 29 of Decoding the Panji of Mithila — Volume IV. The chapter text above is preserved from PDF pp. 323-328; formal Chapter 29 in the commit-pinned authoritative source. It is not merged with a neighboring chapter, appendix, annexure, or independent front/back-matter unit. The internal headings below come from the repository’s source-heading inventory and are retained as navigational and audit evidence; showing them here does not turn those headings into separate publications or add claims that are absent from the source.

Internal source headings

No subordinate heading was separately encoded in the repository source-heading inventory for this chapter.

Source-text concordance

Mahishi · Dath · Mangrauni-Madari · Continuation · Entries · Scope · Point · Resumption · begins · entry · exactly · stopped · covers · close · present · Mahishi-Pali · sequence · move · Mangrauni-Pali · including · split · across · source-file · boundary · Vol-3Final03-a · Vol-3Final03-b · deliberately · stops · Nagram · Hati-Pali · opens · chief · control · Pali · framework · Mangrauni · Jamdauli · held · index · shift · change · underlying · register · controlled · gram · line · another · repeated · place · names · Basanhi · Tharhi · Madari · Virsayar · Babhanigam · read · route · settlement · local · labels · unless · separate · rule · elevates · resumes · Ramanath · branch · left · open · preceding · opening · movement · Bhangi · Belauch-Bhavanath-Juraun · connection · introduces · Pabauli · Machal-Narayan · Datt · Ghusa

Boundary verification. In the formal sequence this chapter follows Volume IV Chapter 28, “Jamdauli to Dath and the Mahishi-Pali Register: Entries (207)- (220)” and precedes Volume IV Chapter 30, “Hati-Pali and Samauli-Pali: From Satlakha and Pilkhwar to Sanha, Jhanjharpur and Bagahi”. The chapter extractor begins at the verified formal Chapter 29 marker and stops at the next verified formal chapter marker; for a final chapter it stops before recognized book-level back matter. The concordance above is generated only from distinct terms already present in this chapter’s preserved source text. It is provided for discovery, comparison, and audit, not as an automated judgment about persons, lineages, status, kinship, marriage eligibility, or historical truth.

Illustrated research apparatus

Mithila · Vajji · Anga

Decoding the Panji publication artwork
Figure 1 · Asset Art 1. Decoding the Panji publication artwork retained as series-level visual context.
Synthetic illustrated Panji folio reconstruction PANJI · SYNTHETIC Synthetic genealogical network for editorial explanation AnchorBranch ABranch BA1A2B1B2
Figure 4 · Synthetic reconstruction plate. Left: a synthetic Panji folio. Right: a synthetic genealogical network used only to explain record relationships. Synthetic illustrated reconstruction for editorial use. This is not a photograph or facsimile of a historical manuscript. Human review required. This prototype encodes relationships and tags; it does not decide marriage eligibility or kinship status.

Chapter-specific source notes

  1. Primary chapter witness. Gajendra Thakur, Decoding the Panji of Mithila — Volume IV, formal Chapter 29, PDF pp. 323-328; formal Chapter 29. The HTML transcription is generated from the commit-pinned source PDF and retains the chapter boundary recorded in this edition.
  2. Internal structure. The repository source-heading inventory records no separately encoded subordinate heading for this chapter.
  3. Digital editorial method. The page keeps the preserved source text distinct from generated navigational, concordance, visual, and provenance apparatus. The synthetic reconstruction is explanatory only and is not evidence for an individual lineage or a determination of social or marital status.