Decoding the Panji of Mithila · Volume II · Chapter 28
Creating a Panji Family Tree
Chapter 28
Creating a Panji Family Tree
1. Why a Panji Family Tree Is Not an Ordinary Family
Tree
A modern family tree usually begins with individuals and
draws lines of descent from parent to child. A Panji family tree
must do more. It must preserve descent, branch continuity,
village identity, marriage nodes, maternal cycles, daughter’s-
son bridges, titles, numbers, and uncertainty. If the tree
records only father and son, it will be visually simple but
historically incomplete.
The Panji does not always give every generation in direct
sequence. Sometimes it gives सुत or पुत्र. Sometimes it gives पौत्र or
प्रपौत्र. Sometimes it gives सन्तति or अपत्य, which may show a
branch rather than immediate sonship. Sometimes a विवाह entry
interrupts the line. Sometimes a दौहित्र belongs to a daughter-line
rather than to the paternal tree. A good Panji family tree must
respect all these differences.
This chapter explains how to create a family tree from
decoded Panji data without flattening the source.
2. Begin with the Source, Not the Chart
The first rule is simple: do not begin by drawing. Begin by
preserving the source phrase. A chart is only an interpretation
of the source. If the chart comes first, the editor may force the
Panji into modern visual habits.
Every family-tree line should be traceable back to an
original phrase. The original phrase should remain available in
the data table. If later research corrects the chart, the editor
must be able to return to the exact wording that caused the
first decision.
Decoding the Panji of Mithila - Volume II
Data rule: every chart line must have a source-reference
field.
Critical caution: a tree without source phrases becomes
genealogy by assertion.
3. Build the Paternal Spine First
The paternal spine is the direct descent line supported by
words such as सुत, पुत्र, पौत्र, प्रपौत्र, and related markers. Begin here
because the paternal line often gives the strongest vertical
structure.
But the paternal spine should include only supported links.
If the source says सुत, draw a father-son link. If it says पौत्र, draw
a grandson link and mark the missing intermediate generation
if unnamed. If it says प्रपौत्र, draw a great-grandson relation with
the correct generational distance. If the source only says सन्तति
or अपत्य, do not draw an immediate father-son line.
Data rule: each line in the paternal spine should indicate the
relationship word that supports it.
Critical caution: never use name order alone as proof of
descent.
4. Represent सन्तति and अपत्य as Branch Continuity
सन्तति and अपत्य are not always direct generation markers.
They often show branch continuity or offspring-line
attachment. In a family tree, these should be represented
differently from सुत.
A useful method is to create a branch box. The ancestor or
line-holder appears above; the सन्तति or अपत्य group appears
below or beside it as a branch-continuity unit. If later direct
descent links appear inside that branch, they can be drawn
within it.
Decoding the Panji of Mithila - Volume II
Data rule: use branch boxes or dotted continuity lines for
सन्तति and अपत्य unless direct generational evidence appears.
Critical caution: turning every सन्तति into “son of” creates
false genealogy.
5. Handling पौत्र, प्रपौत्र, and Missing Generations
When the source gives पौत्र or प्रपौत्र, the chart must preserve
generational distance. A पौत्र is not merely “descendant.” A प्रपौत्र
is not merely “later descendant.” These words indicate levels.
If the intermediate name is missing, draw an unnamed
generation node. For example, if C is marked as पौत्र of A, then
the chart should show A, an unnamed child of A, and C as
grandson, unless another named generation is supplied. This
protects the generational structure without inventing a person.
Data rule: use unnamed nodes for implied but unnamed
generations.
Critical caution: do not shorten पौत्र and प्रपौत्र into direct
sonship.
6. Record Women Even When Unnamed
A Panji family tree must include women structurally even
when they are not personally named. Marriage, मातृक चक्र, दौहित्र,
and affinal links often require an unnamed daughter, wife, or
mother. If the woman is omitted, the relation becomes false.
For a दौहित्र, the daughter through whom the relation passes
must be represented. If her name is not supplied, create a node
labelled “unnamed daughter” or “female link unnamed in
source.” If a maternal cycle requires a mother’s natal house,
represent that house even if the mother’s name is not known.
Data rule: create unnamed female-link nodes when the
structure requires them.
Decoding the Panji of Mithila - Volume II
Critical caution: absence of a name is not absence of a
person in the structure.
7. Use Marriage Nodes
A marriage should not be drawn as a mere line between two
individuals when the source gives detailed marriage evidence.
Use a marriage node. Connect the principal person and spouse-
side house to that node. Attach date phrase, number, title, and
village data to the node.
If the spouse is unnamed but the spouse-side village is
known, connect the node to the spouse-side house or village
with uncertainty. If the marriage is प्रथम विवाह or द्वितीय विवाह, label
the node accordingly.
Data rule: every विवाह entry becomes a marriage node in the
family tree system.
Critical caution: do not hide marriage evidence inside a note
attached to a man’s name.
8. Separate First and Second Marriages
First and second marriages must be charted separately. A
second marriage may create a different spouse-side house,
different issue, different maternal cycle, and different
daughter-line. If both marriages are merged, issue assignment
becomes unreliable.
The chart should show Marriage 1 and Marriage 2 as
separate nodes. Children should be placed under a specific
marriage only when the source supports the attachment. If
uncertain, place them in a provisional issue box connected by
dotted lines.
Data rule: create separate nodes for प्रथम विवाह and द्वितीय विवाह.
Critical caution: do not assign all children to one wife for
visual neatness.
Decoding the Panji of Mithila - Volume II
9. Attach Villages by Function
A Panji family tree should show villages, but not all village
names mean the same thing. A village may be a frame village,
मूलग्राम, वासी-place, डीह, पाली, branch-seat, spouse-side village,
maternal village, or daughter-line place.
Attach the village to the correct person, branch, marriage
node, maternal link, or house. Use labels such as “root village,”
“resident at,” “डीह,” “affinal village,” or “maternal link.” This
keeps geography from misleading the chart.
Data rule: every village attached to the tree must carry a
place-function label.
Critical caution: do not attach all villages to the nearest male
ancestor.
10. Attach Titles to Persons and Houses
Titles should appear in the family tree because they identify
social and intellectual role. A title may belong to an individual,
but repeated titles may identify a house. महामहोपाध्याय, कविराज,
वैयाकरण, पण्डित, ठाकु र, बाबू, and other forms should be shown in a
title field.
If the title is uncertain or abbreviated, preserve the
abbreviation. If the title clearly belongs to a person, attach it to
the person. If the title characterizes a branch or house, attach it
to the branch box with a note.
Data rule: include title-as-written and normalized-title fields
in the tree data.
Critical caution: do not remove titles from charts because
they make names longer.
11. Attach Numbers Without Interpreting Too Much
Parenthetical numbers should appear in the family-tree
data, but the chart should not treat them as dates unless
Decoding the Panji of Mithila - Volume II
proven. They may function as register anchors, branch
numbers, person numbers, marriage references, or note
markers.
In a visual chart, numbers can be shown in small text beside
the person, branch, or marriage node. In the underlying table,
preserve number-as-written and number-position.
Data rule: every number used in the chart must be tied to its
original position.
Critical caution: do not convert numbers into dates inside
the family tree.
12. Chart मातृक चक्र as Network
A मातृक चक्र should not be forced into the paternal spine. It
should be charted as a network crossing between houses. Show
the principal house, the maternal or affinal house, the female
link, and the persons connected through that link.
If the cycle includes दौहित्र, draw the daughter-line bridge. If it
includes villages through सँ, attach them as maternal or affinal
where supported. If the boundary is uncertain, mark the
boundary with a note.
Data rule: draw मातृक चक्र as a side-network linked to the
relevant person or branch.
Critical caution: a maternal cycle is not a decorative
appendix to the male line. It is structural.
13. Chart दौहित्र Correctly
A दौहित्र must be charted through a daughter. The daughter’s
son belongs to his father’s paternal line, but he also preserves
the maternal relation of his mother’s house. Therefore he
should not be placed as the direct son of his maternal
grandfather.
Decoding the Panji of Mithila - Volume II
Use a bridge: maternal house -> daughter -> daughter’s son,
with the father’s house shown where known. If the daughter is
unnamed, create an unnamed daughter node. If the father is
unknown, mark father unknown rather than inventing him.
Data rule: every दौहित्र chart must contain the female-link
path.
Critical caution: incorrect placement of दौहित्र is one of the
most serious family-tree errors.
14. Use Confidence Levels in the Visual System
A Panji family tree should show uncertainty. Use solid lines
for certain direct relations, dotted lines for probable or
possible links, bracketed labels for implied persons, and notes
for uncertain boundaries. A scholarly tree does not hide
uncertainty.
The chart should visually distinguish certain, probable,
possible, and uncertain. This can be done by line style, labels,
or footnotes.
Data rule: every relationship in the tree must have a
confidence value.
Critical caution: a clean chart without uncertainty may be
less accurate than a complex chart with honest markers.
15. The Family-Tree Data Table
Before drawing the final tree, create a family-tree data table.
The table should include: node identifier; source phrase;
person name; normalized name; title; relationship word;
linked parent; linked child; branch marker; marriage node;
spouse-side clue; female-link node; दौहित्र link; village function;
number; source location; confidence level; and critical note.
The table is more important than the drawing because it
preserves the decisions behind the drawing. The drawing can
change; the table records why.
Decoding the Panji of Mithila - Volume II
Data rule: every visual node must correspond to a table row.
Critical caution: never draw a person who does not exist in
the data table.
16. Choosing the Chart Type
Not every Panji passage needs the same chart. A direct
descent passage may use a vertical family tree. A सन्तति cluster
may need a branch map. A village passage may need a cluster
map. A marriage passage may need marriage nodes. A मातृक चक्र
requires a network diagram.
The editor should choose the chart type after decoding the
source, not before. A passage may require more than one
chart: paternal spine, marriage network, maternal cycle, and
village attachment.
Data rule: chart type should follow evidence type.
Critical caution: forcing every passage into a vertical tree
damages the Panji’s structure.
17. Versioning and Corrections
Family trees created from Panji data will change as more
entries are decoded. Therefore each chart should have a
version number, date of preparation, source range, and note of
unresolved issues. Corrections should not erase earlier
uncertainty; they should record how the interpretation
changed.
A later discovery may show that a person belongs to a
different marriage, a different branch, or a maternal rather
than paternal line. Versioning makes correction possible
without confusion.
Data rule: every family tree should have a revision log.
Critical caution: do not present an early reconstruction as
final.
Decoding the Panji of Mithila - Volume II
18. Critical Analysis: What a Panji Family Tree Reveals
A properly built Panji family tree reveals more than
ancestry. It shows how a house exists socially: through descent,
branch continuity, marriage, maternal connection, residence,
village identity, title, and archival numbering. It shows that
family in the Panji is not only biological. It is social,
geographical, intellectual, and ritual.
A good tree also reveals what the source does not say. It
shows unnamed women, missing generations, uncertain
spouse-side links, and probable rather than certain issue
assignment. This honesty is part of the tree’s value.
The Panji family tree should therefore be understood as a
critical reconstruction, not a decorative genealogy.
19. Common Errors in Creating a Panji Family Tree
The common errors are: drawing before preserving the
source; treating सन्तति and अपत्य as direct sonship; collapsing पौत्र
and प्रपौत्र into son; omitting unnamed women; placing दौहित्र in
the paternal line; merging first and second marriages; ignoring
maternal cycles; attaching all villages as origins; deleting titles
and numbers; hiding uncertainty; and presenting one chart as
final when the source remains layered.
20. Rules for Creating a Panji Family Tree
First, preserve the original phrase.
Second, build a data table before drawing.
Third, draw the paternal spine only from direct evidence.
Fourth, represent सन्तति and अपत्य as branch continuity unless
direct links appear.
Fifth, use marriage nodes.
Sixth, separate first and second marriages.
Seventh, represent unnamed women when required.
Decoding the Panji of Mithila - Volume II
Eighth, chart मातृक चक्र as a network.
Ninth, place दौहित्र through the daughter-line.
Tenth, attach villages, titles, and numbers with function
labels.
Eleventh, show uncertainty visually.
Twelfth, keep a revision log.
21. Conclusion: A Tree That Preserves the Forest
A Panji family tree must not reduce the Panji to a simple line
of men. It must preserve the forest of relations: fathers, sons,
daughters, wives, daughter’s sons, villages, root houses,
residences, titles, numbers, marriages, and maternal cycles.
The correct family tree is therefore both a chart and an
argument. It shows what the source supports, what is probable,
what is uncertain, and what must remain open. Such a tree
does not merely decorate the Panji. It decodes it.
Chapter 29 will turn from family trees to the village index. It
will show how to build a place-based reference system that
preserves original spellings, normalized forms, local functions,
clusters, and uncertainty.
Decoding the Panji of Mithila - Volume IISource 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 28 of Decoding the Panji of Mithila — Volume II. The chapter text above is preserved from PDF pp. 315-325; formal Chapter 28 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
Creating · Family · Tree · Ordinary · modern · usually · begins · individuals · draws · lines · descent · parent · child · must · preserve · branch · continuity · village · identity · marriage · nodes · maternal · cycles · daughter’s · bridges · titles · numbers · uncertainty · records · father · visually · simple · historically · incomplete · always · give · every · generation · direct · sequence · Sometimes · gives · show · rather · immediate · sonship · entry · interrupts · line · belongs · daughter-line · paternal · good · respect · differences · explains · create · decoded · data · without · flattening · Begin · Chart · first · rule · drawing · preserving · phrase · interpretation · comes · editor · force · visual · habits · family-tree · traceable · back · original · remain · available
Boundary verification. In the formal sequence this chapter follows Volume II Chapter 27, “How to Decode a Long Dense Passage” and precedes Volume II Chapter 29, “Creating a Village Index”. The chapter extractor begins at the verified formal Chapter 28 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
Chapter-specific source notes
- Primary chapter witness. Gajendra Thakur, Decoding the Panji of Mithila — Volume II, formal Chapter 28, PDF pp. 315-325; formal Chapter 28. The HTML transcription is generated from the commit-pinned source PDF and retains the chapter boundary recorded in this edition.
- Internal structure. The repository source-heading inventory records no separately encoded subordinate heading for this chapter.
- 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.