Decoding the Panji of Mithila · Volume II · Chapter 24

How to Decode a Village Cluster

Chapter                                                         24
 How to Decode a Village Cluster
     1. Why a Village Cluster Needs Worked Decoding
   A single entry teaches the reader how the Panji compresses
data. A village cluster teaches the reader how that compression
expands across a larger unit. A cluster may contain an opening
formula, several branch statements, included localities,
residence markers, repeated place names, title-bearing
persons, and a closure formula. It is one of the most important
structures in Prachin Panji.
   The village cluster is also one of the places where error
multiplies. If the opening is missed, the frame is lost. If the
closure is ignored, the boundary is lost. If all place names are
treated as simple villages of origin, residence, branch-seat, and
affinal links are confused. If all names are forced into a family
tree, the geographical structure disappears.
  This chapter demonstrates how to decode a cluster, using the
type of passage that begins with an अथ + ग्राम formula and ends
with an एते + ग्राम closure.

          2. The Cluster Chosen for Demonstration
   The demonstration uses the pattern visible in the early
village sections of the source: a cluster opened by a formula
such as अथ गंगोलीग्राम and later closed by एते गंगोली ग्राम. Inside the
cluster appear several branch statements, persons, places,
connectors, and local associations. The same method applies to
clusters such as सरिसब, जजिबाल, खण्डबला, दरिहरा, माण्डर, and other
village frames.
  The goal is not to settle every person-place identification in
one pass. The goal is to show how the cluster should be
preserved, segmented, and tabled before interpretation.

                 Decoding the Panji of Mithila - Volume II

  Data rule: choose one cluster and decode its boundary
before extracting isolated names.
    Critical caution: a village cluster is not a paragraph of prose.
It is a structured register unit.

               3. Step One: Identify the Opener
  The first task is to identify the opening marker. In the Panji,
अथ often signals that a new unit is beginning. When अथ is
followed by a village name and ग्राम, the decoder should open a
new cluster record.
    The opener should be copied exactly. If the source writes
गंगोलीग्राम without a space, preserve that. If it writes ग्राम after a
dash or joined form, preserve the source form first and
normalize only in the analysis layer.
  Data rule: every cluster table begins with an opener field.
  Critical caution: do not begin extraction from the first
personal name. Begin from the village frame.

               4. Step Two: Identify the Closure
  The closure may appear as एते + village-name + ग्राम. This
formula gathers the preceding material into the cluster. The
closure is as important as the opener because it tells the editor
where the register unit ends.
  If the closure says एते गंगोली ग्राम, the reader should work
backward to find the matching opener or probable beginning.
If another अथ appears before the closure, the boundary may be
more complex and must be checked.
  Data rule: enter the closure phrase exactly as written and
record the probable line-range of the cluster.
  Critical caution: do not leave एते unanalysed. It is a boundary
marker.

                   Decoding the Panji of Mithila - Volume II

        5. Step Three: Establish the Cluster Boundary
   Once opener and closure are identified, the editor must
establish the boundary. The strict boundary runs from the
opener to the closure. A wider boundary may include
immediately adjacent continuation material if the source
layout or syntax supports it. Both should be recorded if
uncertain.
  Boundary work is necessary because long passages may
contain internal shifts. A cluster may include sub-branches,
another locality, or an अपरा unit. These do not always end the
cluster. They may exist inside it.
  Data rule: record strict boundary and possible wider
boundary separately.
  Critical caution: cluster boundary must be argued, not
assumed.

         6. Step Four: Segment the Cluster into Units
   After establishing the boundary, segment the cluster. Break
at major structural signs: double danda, अथ, एते, सन्तति, अपत्य, वासी,
डीह, मूलग्राम, पाली, समेत, तत्रैव, dash, ओ, and major title markers.

   The purpose of segmentation is to prevent the cluster from
becoming an undifferentiated stream. Each unit should be
small enough to table: one ancestor-line, one branch-place
formula, one residence marker, one included-place statement,
or one title-bearing person.
  Data rule: every segment receives a segment number inside
the cluster.
  Critical caution: do not translate the whole cluster before
segmenting it.

                  Decoding the Panji of Mithila - Volume II

    7. Step Five: Separate Frame Village from Attached
                           Places
   A cluster has a frame village, but it may also contain several
attached places. The frame village organizes the cluster.
Attached places may be branch-seats, included settlements,
residences, डीह markers, affinal places, or repeated localities.

   This distinction is essential. If every attached place is treated
as a new frame village, the cluster breaks apart. If every
attached place is treated as the same as the frame village, the
internal geography is erased.
   Data rule: use separate columns for frame village and
attached place.
  Critical caution: the governing village and the linked places
are not the same data field.

            8. Step Six: Identify Branch Formulae
   Many cluster segments are branch formulae. These may use
सन्तति, अपत्य, dash, or a sequence of names followed by place
attachment. A branch formula usually connects a remembered
ancestor or line with one or more localities.
   The decoder should first ask: is this a direct generational
statement or a branch-continuity statement? If the segment
uses सन्तति or अपत्य without direct सुत / पुत्र markers, the safer first
reading is branch continuity.
    Data rule: classify each segment as direct descent, branch
continuity, place association, residence, marriage, maternal,
title, or uncertain.
   Critical caution: do not make every branch formula into a
father-son chain.

                 Decoding the Panji of Mithila - Volume II

              9. Step Seven: Read Included Places
  समेत indicates inclusion. In a cluster, it often expands the
geographical range of a branch or locality. A phrase ending
with समेत must be preserved with all included elements.

   Included places should be stored as subordinate but linked
elements. They belong to the segment and should not be lost in
the gazetteer.
  Data rule: create an included-place field for every समेत
occurrence.
  Critical caution: indexing only the first place and omitting
the included place produces a false cluster.

               10. Step Eight: Read Joined Places
  The connector ओ joins names or places. In a cluster, ओ-
linked places should be stored as pairs or groups before
analysis. They may represent two associated settlements, two
branch-seats, or two localities attached to the same line.
  The order of the pair matters. The source order should be
preserved even if the normalized gazetteer later alphabetizes
names for search.
  Data rule: store ओ-linked places as linked forms and
separately as searchable normalized places.
  Critical caution: do not break ओ-linked names into unrelated
rows without recording the original link.

          11. Step Nine: Read Residence Markers
  वासी inside a cluster identifies residence or recognized local
belonging. It may show that a branch under the frame village
was known as resident elsewhere or that a person from
another locality belonged to the cluster through residence.

                  Decoding the Panji of Mithila - Volume II

  The decoder should compare every वासी marker with the
frame village. If the वासी place differs from the frame, record
the difference. This may later support branch dispersal or
settlement analysis, but it should not be called migration until
other evidence confirms it.
  Data rule: every वासी phrase must have a residence field.

  Critical caution: वासी is evidence of residence or belonging,
not automatic origin.

              12. Step Ten: Read डीह and मूलग्राम

  डीह and मूलग्राम are special local identity markers. A डीह may
identify a house-site, settlement seat, or old habitation
memory. मूलग्राम identifies a root village. These markers are
stronger and more specific than ordinary place names.
   Inside a cluster, these terms can explain why a branch is
attached to one place while still organized under another. They
can also distinguish root from residence.
  Data rule: classify डीह and मूलग्राम separately in the local-
identity table.
  Critical caution: do not translate both as simply “village.”

        13. Step Eleven: Read पाली and Sub-Locality

  पाली may function as a locality, sub-settlement, or part of a
place-name. In a cluster, repeated पाली references may show
internal geography. They may also help distinguish branches
that otherwise appear under the same broad village frame.
   The exact form must be preserved. If a place appears as
राजखंड पाली or जलकौर पाली, the पाली element belongs to the source
identity.

                   Decoding the Panji of Mithila - Volume II

  Data rule: include पाली in original place form and in locality-
marker indexing.
  Critical caution: do not normalize पाली away.

      14. Step Twelve: Locate Titles Inside the Cluster
   A village cluster may contain title-bearing persons:
महामहोपाध्याय, म. म., कविराज, वैयाकरण, पण्डित, ठाकु र, बाबू, or other forms.
Such titles may show scholarly or status clustering within the
village frame.
   When titles appear, the cluster becomes evidence for
intellectual and social geography. A title must be attached to its
person, relation word, place, and number.
  Data rule: cluster tables should include title-bearing entries.
  Critical caution: do not extract titles into a separate list
without preserving their village context.

             15. Step Thirteen: Preserve Numbers
    Numbers inside clusters may appear beside names, places,
titles, marriage entries, or notes. Their exact function may
vary, but they must be preserved. In cluster analysis, numbers
may help distinguish repeated names or compare related
entries across the source.
   The number should be recorded with position: before name,
after name, after place, after title, after relation word, or after
note.
   Data rule: include number-as-written and number-position
fields in the cluster table.
  Critical caution: do not convert numbers into dates unless
the source clearly supports that reading.

          16. Step Fourteen: Build the Cluster Table
   A full cluster table should contain: cluster identifier; opener;
closure; strict boundary; wider boundary; segment number;

                Decoding the Panji of Mithila - Volume II

original segment; frame village; person or ancestor; relation
word; attached place; connector; included place; joined place;
residence marker; डीह; मूलग्राम; पाली; title; number; probable
function; confidence level; and critical note.
  This table becomes the bridge between the original source
and later analysis.
  Data rule: build the cluster table before building narrative
history.
  Critical caution: a narrative without a table will hide
uncertainty.

           17. Step Fifteen: Build the Cluster Map
   The cluster map should not be a simple family tree. It should
show a frame village at the center or top, with branch units
attached to it. Each branch unit can then connect to places,
included localities, residence markers, titles, or numbers.
  If direct descent appears, it can be charted separately inside
the branch. If the cluster gives only सन्तति or अपत्य statements,
the chart should show branch continuity rather than exact
generations.
  Data rule: choose a cluster map, branch map, or family tree
according to evidence.
  Critical caution: do not force a geographical cluster into a
vertical genealogy.

            18. Step Sixteen: Test for Migration
 A cluster may contain migration evidence, but migration
must be tested. Look for मूलग्राम plus later वासी, repeated branch
names across several places, डीह plus residence elsewhere, or
multi-generation sequence with changing place markers.
  If the evidence is not sufficient, use cautious language:
“associated with,” “recorded under,” “resident at,” “linked

                 Decoding the Panji of Mithila - Volume II

with,” or “branch appears in.” Use “migrated” only when
multiple markers support movement.
  Data rule: all migration statements require evidence type
and confidence level.
  Critical caution: do not mistake cluster complexity for
migration.

19. Step Seventeen: Connect the Cluster to Marriage and
                   Maternal Records
 A village cluster may later become important because of
marriage entries, मातृक चक्र, or दौहित्र. A place that looks like a
branch-seat in one segment may be affinal in another.
Therefore the cluster should be cross-linked to marriage and
maternal tables.
  If a village appears in a विवाह entry, it may be the spouse’s
house. If it appears in a दौहित्र entry, it may be maternal-affinal.
If it appears in मातृक चक्र, it may belong to a cycle rather than a
paternal branch.
 Data rule: every cluster place should be checked against
marriage, maternal, and daughter’s-son records.
  Critical caution: do not assign one fixed function to a village
across all contexts.

     20. Step Eighteen: Write the Cluster Explanation
  Only after the table and map are prepared should the editor
write prose. A cautious explanation may say:
  “The cluster opens with a village frame and closes with an एते
formula. Within the boundary, several branch-continuity
statements are attached to places by dash, समेत, and ओ. Some
entries indicate residence through वासी, and some local markers
require separate treatment. The cluster should be read as a
geographical-social unit, not as a single linear genealogy.

                Decoding the Panji of Mithila - Volume II

Migration is possible only where root, residence, or repeated
branch evidence supports it.”
  Data rule: prose explanation must cite the table structure.
  Critical caution: avoid turning a cluster into a story before
the evidence is classified.

  21. Critical Analysis: What Cluster Decoding Reveals
   A village cluster reveals the Panji’s method of social
mapping. It does not merely list families in villages. It records
houses in relation to frame villages, branch localities, included
settlements, residence markers, titles, and sometimes affinal or
maternal links.
   The cluster form shows that Mithila’s social memory was
organized geographically. Families were remembered as part
of places, and places were remembered through families. The
cluster also shows why simple extraction is dangerous. A list of
names loses geography; a list of villages loses descent; a family
tree loses cluster structure.
   The correct decoding preserves all three: person, place, and
relation.

    22. Common Errors in Decoding a Village Cluster
   The common errors are: beginning with the first personal
name instead of the opener; ignoring the closure; treating all
attached places as frame villages; omitting समेत places; breaking
ओ-linked places without recording the link; reading वासी as
origin; reading डीह as ordinary village; erasing पाली; dropping
titles and numbers; claiming migration without evidence; and
writing a linear genealogy where the source gives a cluster.

          23. Rules for Decoding a Village Cluster
  First, identify the opener.
  Second, identify the closure.

                 Decoding the Panji of Mithila - Volume II

  Third, establish the strict and wider boundary.
  Fourth, segment the cluster.
  Fifth, separate frame village from attached places.
  Sixth, classify सन्तति and अपत्य as branch-continuity unless
direct generation markers appear.
  Seventh, preserve समेत, ओ, वासी, डीह, मूलग्राम, and पाली.

  Eighth, keep titles and numbers attached.
  Ninth, build a cluster table and map before writing prose.
  Tenth, test migration cautiously.

     24. Conclusion: The Village Cluster as Social Map
  A village cluster is a miniature map of society. It contains
descent, place, settlement, branch, title, and sometimes
marriage or maternal connection. To decode it is to recover
how a house was placed inside Mithila’s remembered
geography.
  The method is simple but disciplined: opener, closure,
boundary, segmentation, classification, table, map, and
cautious explanation. Once a cluster is decoded in this way, it
can be linked to other clusters and used for wider
reconstruction.
  Chapter 25 will continue the worked-decoding section by
turning to मातृक चक्र. It will show how to decode a maternal cycle
without confusing daughter-line, marriage, and paternal
descent.

                 Decoding the Panji of Mithila - Volume II

Illustrated research apparatus

Mithila · Vajji · Anga