Decoding the Panji of Mithila · Volume II · Chapter 26

How to Decode a Marriage Entry

Chapter                                                        26
How to Decode a Marriage Entry
    1. Why a Marriage Entry Needs Worked Decoding
  The preceding chapter showed how to decode a मातृक चक्र. A
marriage entry requires another method. A विवाह record is not
simply a note that two persons married. It is a structured event
in which houses, villages, titles, numbers, dates, issue, and
maternal consequences meet. A short विवाह phrase may contain
the social explanation for an entire branch, a later daughter-
line, a second marriage, or a maternal cycle.
 Because marriage was one of the practical reasons for
maintaining the Panji, a विवाह entry must be decoded with
special caution. The entry may identify the principal person,
his title, his house, the spouse-side village, the date of the event,
the order of marriage, later issue, and related affinal links. If
the decoder reads only the word विवाह and ignores the
surrounding data, the record loses its social force.
   This chapter demonstrates how to decode a marriage entry
step by step.

                   2. The Marriage Formula
  A marriage entry is usually marked by विवाह, प्रथम विवाह, द्वितीय
विवाह, or a related phrase such as विवाह प्रकरणम्. The word may
appear after the name or title of the principal person. It may be
followed by a date phrase, number, spouse-side clues, issue-list,
or अपरा subunit.

  The formula itself must be preserved exactly. If the source
writes विवाह:।।, विवाह:, विवाह।, प्रथम विवाह, or द्वितीय विवाह, the
punctuation and wording should remain in the source layer.

                 Decoding the Panji of Mithila - Volume II

Different forms may later help identify register habits or
subtypes of entries.
  Data rule: every विवाह formula should receive a marriage-
event row.
  Critical caution: do not treat विवाह as a casual biographical
word. It is a formal social marker.

   3. Step One: Preserve the Original Marriage Phrase
  The first task is to copy the marriage phrase exactly. Include
the title before it, the name before it, the punctuation after it,
and any number or date phrase immediately following it. The
original line is the only secure evidence.
  For example, a phrase may include a title marker such as ठo,
an identity qualifier such as प्रo, a personal name, the word
विवाह, punctuation, and then a date. These elements must
remain together until segmentation is complete.
  Data rule: make an “Original Marriage Phrase” field before
expansion or translation.
  Critical caution: do not modernize the date phrase or
remove title abbreviations in the first layer.

         4. Step Two: Identify the Principal Person
  The principal person is usually the person whose marriage is
being recorded. Often he appears immediately before विवाह. But
in dense passages, names, titles, and qualifiers may precede the
formula, and the nearest name may need to be checked against
the surrounding structure.
  If the source gives ठo छोटकू प्रo वेदमणि विवाह, the first-pass
principal person is the titled person or named person in that
phrase, but the exact relation between छोटकू , वेदमणि, and प्रo must

                  Decoding the Panji of Mithila - Volume II

be preserved for later analysis. If another phrase gives ठo तेजपति
प्रo गंगाधर विवाह, the same caution applies.

   Data rule: mark the principal person and the confidence
level.
  Critical caution: the name before विवाह is usually important,
but its exact role should be checked before final charting.

   5. Step Three: Preserve Titles and Identity Qualifiers
  Titles and qualifiers in marriage entries are essential. ठo,
ठाकु र, प्रo, बाबू, महाराज, वैयाकरण, पण्डित, कविराज, and similar forms can
distinguish persons and houses. They may also show the social
rank or learned status of the alliance.
   A marriage entry involving a titled person should be entered
in the title index as well as the marriage table. If the title is
abbreviated, preserve the abbreviation in the source field and
give the expansion only in the analysis field if confident.
  Data rule: title, abbreviation, and qualifier should have
separate fields.
 Critical caution: do not delete titles from marriage entries to
make the prose smoother.

            6. Step Four: Identify Marriage Order
  Some entries state प्रथम विवाह or द्वितीय विवाह. These words
establish relative sequence. A first marriage and a second
marriage must become separate marriage-event records. If
only विवाह appears, mark the marriage order as unspecified.

  When द्वितीय विवाह appears, the decoder should expect a
separate affinal link and possibly a separate issue group. The
second marriage may introduce a new village, a new maternal
cycle, or a different daughter-line.

                Decoding the Panji of Mithila - Volume II

  Data rule: every marriage row should include marriage
order: first, second, later, unspecified, or uncertain.
   Critical caution: do not merge first and second marriages
into one household line.

           7. Step Five: Identify the Date Phrase
   Some marriage entries include a date phrase. This may
contain month, fortnight, tithi, weekday, year, or modern-
looking date. The date phrase must be copied exactly and kept
separate from numbers in parentheses.
   A phrase such as Phalguna Krishna Chaturdashi on
Wednesday gives traditional calendar information. A modern-
looking date gives a different kind of time evidence. Both are
valuable, but they must not be mixed with register numbers.
  Data rule: create separate fields for traditional date, modern
date, event date, record date, and date confidence.
 Critical caution: do not convert a traditional date into a
modern date unless the calendar basis and year are known.

   8. Step Six: Separate Register Numbers from Dates
   Parenthetical numbers near marriage entries are not
automatically dates. They may be register numbers, person
identifiers, branch references, note markers, or internal
anchors. A marriage entry may contain both a date phrase and
a parenthetical number. These must be separated.
  The number should be recorded exactly, including slash,
double slash, zero, and position. If the number follows the date,
record that. If it precedes the spouse-side statement, record
that. If it belongs to the next unit, mark uncertainty.
  Data rule: every marriage table should include number-as-
written and number-position.
  Critical caution: false dating from parenthetical numbers
can damage the chronology.

                 Decoding the Panji of Mithila - Volume II

           9. Step Seven: Locate the Spouse-Side Clue
   A marriage record may not always name the spouse directly.
It may indicate the spouse’s house through village, father, title,
or later issue. The spouse-side clue may appear after the
marriage phrase, after a date, after a number, or inside an अपरा
subunit.
   The decoder should not invent a bride’s name if the source
does not supply one. Instead, record the spouse-side house or
village as named, probable, possible, or unknown.
  Data rule: every marriage record should have spouse-side
person, spouse-side village, and spouse-side confidence fields.
  Critical caution: unnamed spouse does not mean missing
data; the house may still be structurally visible.

      10. Step Eight: Read सँ in the Marriage Context

  The connector सँ is especially important after विवाह. In
marriage context it may identify the spouse-side village, the
affinal house, or a related settlement. It may also mark
residence or branch association. The first-pass reading should
be neutral: “linked with.”
  Only after the principal person, spouse-side clue, issue-list,
and nearby maternal material are analyzed should सँ be
classified as affinal, residence, origin, maternal, or uncertain.
  Data rule: every सँ near a विवाह entry should receive a
connector-function field.
  Critical caution: translating सँ as simple “from” can place the
marriage in the wrong house.

      11. Step Nine: Read सुता After a Marriage Entry

  A सुता list after a marriage entry may contain issue of the
marriage, issue of a related person, or a new branch. In

                 Decoding the Panji of Mithila - Volume II

multiple-marriage passages, this is especially delicate. A child
listed after a second marriage may belong to that marriage, but
structural proof is needed.
  The safe method is to record the सुता list exactly and assign
issue only with confidence levels. If the source is ambiguous,
the chart should show the issue group as probable or
uncertain.
  Data rule: every issue-list after विवाह should have marriage-
event attachment and confidence.
  Critical caution: do not assign all following children to the
nearest marriage automatically.

      12. Step Ten: Read अपरा After a Marriage Entry

  अपरा may introduce another branch, another spouse-line,
another issue group, or another marriage-related subunit.
When it appears after विवाह, प्रथम विवाह, or द्वितीय विवाह, it must be
treated as a structural shift.
  Open a sub-entry for अपरा. Then decide whether it belongs to
the same marriage, a second marriage, another spouse-line, or
a related branch. If uncertain, preserve the uncertainty.
  Data rule: अपरा near विवाह creates a provisional subunit.

  Critical caution: ignoring अपरा may merge separate marriage
consequences.

13. Step Eleven: Connect the Marriage Entry to मातृक चक्र

  A marriage entry may explain a later मातृक चक्र. The marriage
joins two houses; the maternal cycle preserves the
consequences of that joining. If a मातृक चक्र appears near the
marriage entry, compare names, villages, titles, and numbers.

                 Decoding the Panji of Mithila - Volume II

   A first marriage and second marriage may each create
different maternal circuits. Therefore the marriage event
number must be linked to any related cycle.
  Data rule: every विवाह row should have related मातृक चक्र fields.

  Critical caution: do not interpret maternal cycles without
checking marriage entries.

  14. Step Twelve: Connect the Marriage Entry to दौहित्र

   A daughter’s-son entry may be the later effect of a marriage.
If दौहित्र appears near the marriage entry or in a related cluster,
the daughter-line should be reconstructed. The daughter may
be unnamed, but her structural position must be recorded.
  The daughter’s son should not be placed directly into the
paternal line of the maternal grandfather. He should be
charted as a bridge between houses.
  Data rule: every विवाह table should include a related-दौहित्र field
where applicable.
  Critical caution: do not erase the daughter through whom
the relation passes.

15. Step Thirteen: Classify Villages in the Marriage Entry
  A marriage entry may contain several villages. One may
belong to the principal house, another to the spouse-side house,
another to issue residence, and another to maternal or
daughter-line relation. Classify each separately.
  The same village may be root for one branch and affinal for
another. Therefore the place function must be local to the
entry, not assumed globally.
  Data rule: every village in a विवाह entry should have a place-
function tag.
  Critical caution: do not put all marriage-entry villages into
the origin column.

                 Decoding the Panji of Mithila - Volume II

        16. Step Fourteen: Build the Marriage Table
   A full marriage table should include: original phrase; source
location; principal person; title; qualifier; marriage marker;
marriage order; date phrase; modern date if supplied;
parenthetical number; number position; principal village;
spouse-side person; spouse-side village; connector; issue-list;
issue-confidence; अपरा subunit; related मातृक चक्र; related दौहित्र;
related titles; and critical note.
    This table should link to the person index, village gazetteer,
title index, number table, maternal-cycle table, and daughter’s-
son table.
  Data rule: create one row per marriage event.
  Critical caution: do not store several marriages in one
undifferentiated note.

         17. Step Fifteen: Draw the Marriage Chart
  A marriage chart should contain a marriage node. The
principal person or house should connect to the node. The
spouse-side house should connect to the same node. Issue
should descend from the node only when the source supports
that attachment.
   If there is a second marriage, create a second node. If issue
assignment is uncertain, place the issue in a provisional box. If
a daughter’s son appears, show the daughter-line bridge.
  Data rule: chart marriages as event nodes, not merely as
notes beside a name.
   Critical caution: a clean chart with wrong issue attachment
is worse than a cautious chart.

    18. Step Sixteen: Write a Cautious Prose Decoding
  Only after table and chart should the editor write the prose
explanation. A safe explanation may say:

                 Decoding the Panji of Mithila - Volume II

   “The source records a marriage of the named titled person.
The marriage formula is followed by a date phrase and a
parenthetical number. The following village and person
sequence likely identifies the spouse-side or affinal house, but
the exact attachment should be marked with confidence. Any
सुता list after the formula must be tested before assigning issue.
Nearby मातृक चक्र or दौहित्र entries should be cross-linked.”

  Data rule: prose must state both what is clear and what
remains uncertain.
   Critical caution: do not write a full marriage narrative from
a compressed formula unless the source supplies the links.

         19. Step Seventeen: Write the Critical Note
  A critical note should end every marriage decoding. It
should identify the marriage marker, principal person, title,
date evidence, number evidence, spouse-side clue, issue-
confidence, and related maternal or daughter-line links.
  The note should also warn if the entry contains द्वितीय विवाह,
अपरा, or uncertain सुता assignment. These are the places where
mistakes most often enter.
  Data rule: every marriage entry needs a critical note.
  Critical caution: the critical note protects the editor from
overclaiming.

 20. Critical Analysis: What Marriage Decoding Reveals
   A marriage entry reveals the Panji as a working social
register. The marriage is not simply an event in a person’s life.
It is a connection between houses, a basis for maternal
memory, a possible source of daughter-line links, and a fact
relevant to future marriage regulation.
  The presence of first and second marriage markers shows
that the register recognized complexity. The presence of date
phrases shows that some marriages were temporally anchored.

                 Decoding the Panji of Mithila - Volume II

The presence of titles shows social rank. The presence of
villages shows alliance geography. The presence of numbers
shows archival organization.
  A decoded marriage entry therefore becomes a social
document.

    21. Common Errors in Decoding a Marriage Entry
  The common errors are: treating विवाह as a minor note;
failing to separate first and second marriages; removing titles;
confusing date phrases with register numbers; translating सँ
too narrowly; inventing a spouse’s name; assigning all
following सुता to the marriage; ignoring अपरा; failing to connect
the entry to मातृक चक्र; failing to connect it to दौहित्र; and drawing
one spouse line where the source gives multiple events.

             22. Rules for Decoding विवाह Entries

  First, preserve the exact marriage formula.
  Second, identify the principal person and title.
  Third, classify marriage order.
  Fourth, preserve date phrases exactly.
  Fifth, keep numbers separate from dates.
  Sixth, identify spouse-side clues without inventing names.
  Seventh, read सँ neutrally until its function is clear.

  Eighth, assign issue with confidence levels.
  Ninth, open subunits for अपरा.

  Tenth, cross-link with मातृक चक्र and दौहित्र.

        23. Conclusion: Marriage as Decoded Event
  A विवाह entry is a decoded event, not merely a translated
word. It joins people, houses, villages, dates, titles, numbers,
issue, and maternal consequences. The editor’s task is to

               Decoding the Panji of Mithila - Volume II

preserve all these layers without forcing them into a simple
modern marriage sentence.
   When decoded properly, the marriage entry becomes one of
the strongest bridges between genealogy, social structure,
geography, and time. It shows why the Panji was necessary:
because marriage required memory, and memory required
disciplined record.
  Chapter 27 will continue the worked-decoding section by
examining a long dense passage. It will show how to divide a
complex sequence into manageable units without losing data.

                Decoding the Panji of Mithila - Volume II

Illustrated research apparatus

Mithila · Vajji · Anga