Decoding the Panji of Mithila · Volume IV · Chapter 18

Khangur to Yamsam, Kakraud, Saurath, and the Noane-Gopinath Continuation

Chapter 18
Khangur to Yamsam, Kakraud, Saurath, and the
Noane-Gopinath Continuation
   This chapter continues the Khangur sequence from entry
(41) through entry (48). It is intentionally limited to this block
alone. The previous chapter closed with the Kailakh-Kakraud
and Adinath-Nand material. The present chapter resumes
with Khangur to Yamsam, then moves through the
continuation     entries,      the     Noane-Gopinath-Kamdev-
Devkinandan-Rudai/Sadanand-Bhagirath-Kakraud grouping,
the    Khangur-to-Kakraud         branch,    the    unnumbered
continuation in entry (46), Khangur to Saurath, and the
suspended Khangur heading in entry (48).
   The whole block belongs to the same broad Sarisab-
Khangur frame that the Genome Mapping index treats as a
key Nagram control point. The index explicitly records
Khangur under the Sarisab system and also gives a specific
Nagram branch reference in which Khangur-Sarisab is tied to
Vishram, son of Kariye Jha. That index reference is important
because it confirms that Khangur is not an accidental village-
name in this section; it is one of the organizing moolgram
markers through which the Nagram Panji remembers several
lines.
   The block is also important because it shows how a single
Khangur heading can hold several different kinds of material:
ordinary sonship chains, named learned persons, village-route
links, blank or incomplete entries, and later extensions
through modern personal names. It should therefore be read
neither as one family alone nor as a loose list of unrelated
names. It is a cluster of interlinked genealogical routes under
the Khangur archive-frame.

18.1 Entry (41): Khangur to Yamsam
   Entry (41) opens with the formula Khangur to Yamsam. The
first movement after the heading continues from the
preceding Adinath-Nand material, but it quickly forms its own
Yamsam-linked cluster. The entry names Jyotishi Mukund and
connects him through Hariamb to Machal, son of Yogi, while
also linking him to Soderpur through Lal. This double
connection is typical of Panji writing: one person is located
through more than one relational route.
   The next named branch introduces Badhan, whose sons
include Mohanlal, Ramlal, and Vishweshwar. This line is
connected through Hariamb to Dayanath, son of Modnath, and
through Narun to Bhairavdatt. The Hariamb and Narun
markers are not incidental. In the Genome Mapping logic,
Hariamb and Narun belong to established moolgram
networks, and the Panji uses them to identify where a branch
stands in the larger marriage and lineage geography.
   The Ramlal line then gives Shrikrishna, connected through
Khoa l to Bhutinath, son of Apuchh, and through Budhwal to
Durgapati. This part of the entry shows the movement from a
Khangur-Yamsam heading into Khoa l and Budhwal networks.
Since Khoa l and Budhwal are both major mool identifiers, the
entry must be treated as a cross-linked genealogical unit, not
as a purely local Yamsam record.
   Another important sub-line begins with Panchkamal and
Rohinidatt, also styled Hibharan, along with Dharbharan. The
entry connects them through Mandar to Shobhakar and
through Budhwal to Bhaiyan. Dharbharan’s sons, Janardan
and Banmali, are then linked through Budhwal to Dullah, son
of Shripati or Thitharu, and through Belounch to Raman. This
repeated Budhwal presence gives the branch a strong
indexable marker.

  Janardan’s sons Lakshmikant and Umakant continue the
chain. Lakshmikant leads to Gorikant and Yaddu, with Alay
and Baliyas connections. Umakant leads to Madhukant and
Nunu, with Pali, Darihara, Soderpur, Narun, and Jajival links.
The many village markers should not be flattened into
migration alone. They record the branch’s relational reach
across several recognized moolgram fields.
  The final part of entry (41) names Banmali’s sons:
Chhakauri, Kantir, Khushar, and Gokulnath. The Phanandah,
Khoa l, Satlakha, Panichobh, Gangouli, and other markers
show that this Khangur-to-Yamsam entry is a dense crossroad.
The practical decoding rule is that Yamsam is the heading,
Khangur is the source-frame, and the internal names carry the
branch into multiple indexable moolgram systems.

18.2 Entry (42): Kantir, Gokulnath, and the
Harnath Line
   Entry (42) continues the previous branch rather than
beginning a fully independent village-route. It opens with
Kantir, whose line is connected through Alay and Baliyas. The
text then names Begu, also known through Gokulnath, and
gives sons Khadganath, Dayanath, Triveninath, and Badrinath.
These names are attached to Alay and Baliyas again, showing
continuity with the closing part of entry (41).
   Khadganath’s sons include Promod, Subodh, Kumudnath,
Shambhunath, and Sudhir. Their connections through
Darihara and Khandbala place them in two major index
systems. Dayanath’s sons Adityanath and Gitanath are linked
with Kujouli and Khandbala. Triveninath’s sons Ashok Kumar
and Mulu are connected through Khoa l and Budhwal. The
structure is therefore not random; each son-line is given a
relational coordinate.

   The second half of entry (42) introduces Narayandatt and
Kanhai. Kanhai is connected with Beherarhi and Belounch.
Other sons and branches include Bhailal, Parshi, Bahoran,
Panchanand, Gopal, Govind, Thithar, and Yogadhar. These are
attached to Pali, Khoa l, Mandar, Soderpur, Hariamb,
Darihara, and Katayi. Such layering demonstrates one of the
main features of the Nagram Panji: a single entry can cross
many villages while still belonging to one genealogical
continuation.
   For index logic, entry (42) is especially useful because it
turns a Khangur heading into a practical demonstration of
how gotra-mool identity and village affiliation are recorded
together. The names are not enough by themselves. The
village-route after each son-line is what makes the entry
usable for matching, cross-checking, and later indexing.

18.3 Entry (43): The Short Khangur Continuation
   Entry (43) is headed Khangur with a reference number. It
begins from Sanath and Bhavi and then moves to Jalpadatt
and Enipal Narayan. The entry is shorter than the preceding
two, but it is not less important. Short Panji entries often
function as connective tissue, carrying forward a branch from
a larger entry and anchoring it to a new reference number.
   The Kanhai line brings in Budhwal, Sakararhi, Pali,
Karmaha, Mandar, Hariamb, Darihara, and Ghusaut
connections. Thithar’s son Markandeya is linked through
Hariamb and Darihara; Parshi’s son Mannulal is linked
through Mandar and Ghusaut. These markers show that even
a compact entry can preserve a wide relational geography.
  The most important editorial decision here is not to expand
the entry beyond what it says. Some portions are clear; other
portions are abbreviated or incomplete. The decoding
therefore records the visible structure, identifies the main

names and route markers, and preserves the incomplete
character of the source where the Panji itself does not provide
more detail.

18.4 Entry (44): Noane, Gopinath, Kamdev,
Devkinandan, Rudai/Sadanand, Bhagirath, and
Kakraud
    Entry (44) is one of the most crowded headings in this
chapter. It names Khangur and then gives a string of
identifiers: Noane, Gopinath, Kamdev, Devkinandan, Rudai or
Sadanand, Bhagirath, and Kakraud. This type of heading
should be read as a clustered label. It is not simply one person.
It is a heading that gathers several remembered nodes into the
Khangur-Kakraud field.
   The Bhagirath branch begins with sons Machal,
Hridyanandan, and Yadunandan. Machal is linked through
Pali and Sakararhi; Chhavan, Buda, and Shivandan are linked
through Sakararhi and Beherarhi. Ankhi is linked through
Sakararhi and Babhaniyam. These repeated Sakararhi and
Babhaniyam markers are significant because both belong to
established moolgram mapping systems in the Genome
Mapping framework.
  Machal’s sons include Fakiran and Nanu. Fakiran’s line
produces Jhumkalal, Nandalal, Banshidhar, and Manohar,
connected through Karmaha and Soderpur. Fakiran’s other
sons include Nand Kishor and Yugal Kishor, with Urduni,
Enipal Narayan, Pali, and Madhunand connections. The entry
thus moves from a named ancestor to multiple son-lines and
then into recognized village-route markers.
  The ending part of entry (44) keeps several Babhaniyam
and Belounch connections. This matters for index checking:
where a future index lists Babhaniyam, Belounch, Karmaha,

Soderpur, or Sakararhi under the Khangur-Kakraud cluster,
this entry must be included.

18.5 Entries (45) and (46): Khangur to Kakraud
and Its Continuation
  Entry (45) is explicitly headed Khangur to Kakraud. The
opening names Nandalal and gives his sons Ramchandra,
Krishnachandra, and Bauku. This branch is connected
through Baliyas and Pabouli, and then Nanu is linked through
Baliyas and Babhaniyam. Nand Kishor leads to Tantranath
and Bangat or Nehnath, with Dadari, Panichobh, and
Belounch links.
   The Tejnath branch gives Markandeya, Mukund, and
Keshav, connected through Nahas-Khoa l and Pali.
Markandeya produces Madhusudan and Umesh, linked with
Hariamb and Alay. The later modern forms Satish Chandra,
Sudhir Chandra, Abhay Chandra, and Subhash Chandra show
that the Panji continues to receive recent family memory
alongside older formulae.
   Entry (46) is not separately headed by a new village-route
but continues the same branch. It includes Raghudev, Bhooli,
Suryanarayan, Sudisht Narayan, Udisht Narayan, and several
later branches. The presence of repeated sons and partially
blank portions shows that this is a continuation of a living
line, not a polished narrative genealogy. Some names are
secure, some links are partial, and some marriage or
affiliation points are left incomplete.
   The later part of entry (46) includes Ramkrishna, Dular,
Chiranjeev, Basudev, Lakshyeshwar, Vighneshwar, Ayodhya,
Jadab, Khuni, and Sachchidanand. These names connect
through Baliyas, Soderpur, Sakararhi, Pali, Babhaniyam,
Belounch, Budhwal, and Khandbala. From an index point of
view, this is one of the main reasons the Khangur-to-Kakraud

section cannot be summarized too briefly. It touches too many
classified villages.

18.6 Entry (47): Khangur to Saurath
   Entry (47) carries the Khangur sequence to Saurath. The
entry begins with Khuni’s further branch and includes
Ishwaridatt, Kumarkant, Ratneshwar, Kranti, and later
connections through Khoa l, Pabouli, Hariamb, Mahua-Khoa l,
Belounch, and Khoa l again. Saurath here is not merely a
place-name. It is a major Maithil institutional memory-site,
and its occurrence in a Khangur route deserves careful
attention.
   The Shivnandan or Khushi line includes Hridyanath and
Jayan. Hridyanath gives Vaiju, Amritnath, and Gudar, with
Baliyas and Narun links. Jayan gives Goshain, connected
through Darihara and Pabouli. Ankhi gives Chakradhar and
Shridatt, with Tisaut, Baliyas, Pali, and Darihara links.
Chakradhar leads to Pritinath and Nand Kishor, carrying the
line through Pali, Ekhara, Ghusaut, and Soderpur.
  This entry is important because it shows how a Khangur
branch can enter the Saurath orbit while retaining several
older moolgram markers. It should therefore be indexed
under Khangur, Saurath, Khoa l, Pabouli, Hariamb, Baliyas,
Narun, Darihara, Tisaut, Pali, Ekhara, Ghusaut, and Soderpur
wherever the final index allows such granularity.

18.7 Entry (48): Suspended Khangur Heading and
the Sadashiv-Sahab-Manbodh Branch
  Entry (48) returns to a suspended Khangur heading. It
names Sadashiv and his sons Sahab and Manbodh, then links
the branch through Baliyas and Karmaha. Sadashiv also has
the son Bhanjan, connected through Karmaha and Darihara.
Sahab’s branch includes Mana, Chitru, Dullah, Datti,

Bachharan, Jivan, and several further children and marriage
links.
   The entry is dense because it repeatedly uses the formula
‘apara suta’ or ‘other son/branch’, moving from one son-line to
another. Mana leads to Ishwardatt and later to Parshmani,
Kulanand, and Indramani. Kulanand leads to Pan Bamhboli
and Pan Kashinath, with Ghusaut, Darihara, Hariamb, and
Pali links. These markers preserve the network even where
some personal details are abbreviated.
   Entry (48) also illustrates a recurring feature of the Khangur
block: the Panji does not always close a branch neatly before
beginning the next one. Instead, it accumulates relational
evidence. The decoder must therefore identify the principal
branch, list the son-lines, preserve the village-route evidence,
and avoid imposing artificial order where the source keeps a
looser archival structure.

18.8 Index Logic and Coverage Note for Chapter
   For the Genome Mapping cross-check, this chapter must be
tied first to the Sarisab-Khangur framework. The index
records Khangur under Sarisab and also supplies a Nagram
branch reference for Khangur-Sarisab tied to Vishram and
Kariye Jha. This validates the continuing use of Khangur as the
governing archive-marker for the present chapter.
  The chapter also touches many index-relevant moolgram
markers: Yamsam, Kakraud, Saurath, Khoa l, Budhwal,
Mandar, Baliyas, Alay, Darihara, Khandbala, Kujouli, Pali,
Sakararhi, Babhaniyam, Belounch, Soderpur, Ghusaut, Narun,
Hariamb, Tisaut, Ekhara, Pabouli, and Panichobh. Each of
these names must be checked again during the final index
audit.

  The most important interpretive point is that entries (41) to
(48) do not merely extend the Khangur list. They show
Khangur as a branching platform from which the Panji moves
to Yamsam, Dihiya continuations, Kakraud, Saurath, and
several learned or titled lines. This is why the chapter has
been kept exclusive rather than absorbed into a broad
summary of the Khangur section.
  Coverage for this chapter is therefore limited to entries (41),
(42), (43), (44), (45), (46), (47), and (48). The next chapter should
begin only after entry (48), with the following numbered or
headed source section, so that the cumulative reconstruction
remains sequential and auditable.

Illustrated research apparatus

Mithila · Vajji · Anga