BPHS Field Manual¶
A personal, growing reference of distilled practical knowledge — not a copy of verses, not a lesson summary. This is what's worth remembering before sitting down to actually read a chart. Updated by the tutor after each completed module, reflecting what that module actually earned, not what might be useful someday.
Every entry carries: the module it came from, its BPHS source, why it matters in practice, and links to related entries or future chapters worth revisiting it against.
Semester 1¶
From Module 1 — Foundations of Creation (Ch. 1–2)¶
1. A planet's significance is an argued claim, not an assumption to import from outside. - Developed in: S1-M1-L1 - Source: Ch. 1, v.21–24 - Why it matters: BPHS does not simply assert that planets matter — it argues for it, via the paramātmā-aṁśa claim. Every later technique (karakas, yogas, dashas) is downstream of this argument. Reading a chart "mechanically," without holding this premise, is explicitly what the course's own source material warns against. - Cross-references: Karakas (Ch. 34, not yet studied); this entry is the foundation every later entry in this manual ultimately rests on.
2. Distinguish verse from translator's Notes before citing anything. - Developed in: S1-M1-L1, S1-M1-L2 - Source: Ch. 1's two Notes blocks (after v.1–4 and after v.21–24) vs. its 24 numbered verses; confirmed by contrast when Ch. 2 turned out to have no Notes block at all. - Why it matters: Translator commentary (Girish Chand Sharma's own explanatory additions) is useful context but a different authority level than Parashara's verse text. Treating the two as interchangeable risks attributing a claim to "BPHS" that is really one translator's 20th-century synthesis. - Cross-references: the course's own source-labeling and citation standards — this entry is why that system exists in the first place.
3. A mythological or doctrinal classification is not automatically a technical strength rule. - Developed in: S1-M1-L2, tested directly in the Module 1 Test's 8-part reasoning exercise - Source: Ch. 2, v.2 (the Pūrṇāvatāra classification) — caution drawn against confusing this with Ch. 29's Shadbala (planetary strength), not yet studied - Why it matters: BPHS's language invites plausible-sounding overreach — "Mars is a complete avatāra, so Mars must be stronger" feels like a reasonable extension but is not a claim the text actually makes. The discipline required: before applying an idea from one domain (mythology/doctrine) to another (technical chart strength), check whether the source actually makes that specific bridge. - Cross-references: Revisit this entry once Ch. 29 (Shadbala) is studied — confirm the caution holds, or correct it if BPHS itself ever does draw such a connection.
4. When BPHS states a fact twice in different forms, treat the second statement as a consistency check, not a new fact. - Developed in: S1-M1-L2 — v.2 names the four Pūrṇāvatāras directly; v.5–7 (the full nine-graha list) independently yields the same four. - Source: Ch. 2, v.2 and v.5–7 - Why it matters: A general reading habit worth carrying through the whole 100-chapter text: internal cross-checks catch a misreading before further conclusions get built on top of it. If two passages that should agree don't, the error is almost always in the reading, not the source. - Cross-references: general reading discipline — applies to every future chapter, especially the longer technical ones (Ch. 3 onward) where cross-checkable claims recur often. Confirmed again in Module 2, entry 5 below.
From Module 2 — Planetary Characters and Description (Ch. 3)¶
5. An approximate cross-reference is worth verifying directly, even when it turns out correct. - Developed in: S1-M2-L2 — the existing Ch. 1 workbook approximated "Ch. 3, shlokas ~20 and ~22"; direct reading confirmed both exactly (v.20 = primordial elements, v.22 = guna classification). - Source: Ch. 3, v.20 and v.22, cross-checked against Ch. 1's own Notes. - Why it matters: the value wasn't in discovering an error — there wasn't one — it was in not assuming the approximation was safe to build on before checking. The habit of verifying rather than trusting generalizes to every future cross-reference in this course, including ones that will eventually turn out wrong. - Cross-references: entry 4 above (internal consistency checks); this course's citation-discipline standards.
6. The same name can mean two different things in BPHS — track context, not just vocabulary. - Developed in: S1-M2-L6 — the fifth point in the Dhuma-Upagraha chain is called "Ketu" in the verse (v.63–64), but is a differently-computed shadow point, not the graha Ketu (the lunar node) taught in Lesson 1. - Source: Ch. 3, v.63–64 vs. v.10 (graha Ketu). - Why it matters: a 100-chapter text spanning centuries of commentary layers will reuse terms across different technical systems. Assuming a familiar word always means the same thing is a real source of misreading — always check which system a term belongs to before applying a rule from a different one. - Cross-references: watch for this again with "Mandi" vs. "Gulika" (same lesson) and any future repeated terminology.
7. Relationships in the classical system are not guaranteed to be mutual. - Developed in: S1-M2-L5 — the Moon lists Mercury as a natural friend; Mercury lists the Moon as an enemy. Both are correct simultaneously. - Source: Ch. 3, v.55 (natural relationship, computed independently per planet from its own Mooltrikona sign). - Why it matters: it's tempting to assume "A likes B" implies "B likes A" — BPHS's own computation method doesn't guarantee this, since each planet's relationships are derived from its own reference point. Never assume symmetry without checking both directions explicitly. - Cross-references: entry 5's verification discipline — this is exactly the kind of assumption worth checking rather than trusting.
8. When a rule seems to combine two factors, check whether it's actually an ordered priority, not a sum. - Developed in: S1-M2-L5 — the Ratio of Effects table (v.59–60) looks like it combines dignity and relationship, but it's really a single ordered hierarchy: check exaltation, then Mooltrikona, then own sign; only fall back to relationship-based scoring if none of those apply. - Source: Ch. 3, v.59–60. - Why it matters: misreading a priority ladder as an additive combination would produce wrong strength assessments as soon as real chart-judgment work begins (Semester 2 onward) — worth re-checking this distinction whenever a later chapter appears to "combine" multiple factors. - Cross-references: Ch. 29 (Shadbala, not yet studied) — confirm whether its more elaborate strength system uses a similar priority structure or a genuine weighted sum, once reached.
(A note on format: from Module 3 onward, new Field Manual entries use the fuller Rule/Observation/Evidence/Practical Advice/Limitations/Related Concepts/Developed In structure below, per your updated instructions. Entries 1–8 above are preserved in their original format rather than retroactively rewritten, consistent with this course's standing rule to preserve valid existing content rather than rewrite it for uniformity.)
From Module 3 — Zodiacal Signs Described (Ch. 4)¶
A term shared between a sign-level and planet-level system does not imply one combined system¶
Rule: When BPHS classifies both a planet and a sign with the same term (e.g., Krūra/Saumya), treat these as two independent systems that happen to share vocabulary — never assume they combine into one score unless BPHS states the bridge explicitly.
Observation: Ch. 4 v.5 classifies all 12 signs as Krūra or Saumya, using the identical terms Ch. 3 v.11 uses to classify planets. Neither chapter states a rule for merging the two — they are applied to different objects and never combined into a single formula anywhere in Ch. 3 or Ch. 4.
Evidence: Ch. 3, v.11 (planet-level); Ch. 4, v.5 (sign-level).
Practical Advice: Before combining a sign-level fact and a planet-level fact into one interpretive conclusion, check explicitly whether BPHS itself states the bridge — or whether the combination is my own inference, which should then be labeled "Interpretation inferred," not presented as a direct BPHS rule.
Limitations: This does not mean sign and planet facts never genuinely interact in a real reading (a planet's dignity is itself sign-dependent, for instance) — only that shared vocabulary between two classification systems is not evidence of a stated combination rule.
Related Concepts: Entry 3 above (Pūrṇa-avatāra ≠ Shadbala strength) — the same pattern of "don't bridge two systems without textual support," recurring in a new context.
Developed In: S1-M3-L1.
A single exception in an otherwise-universal pattern deserves more scrutiny than scattered incomplete data¶
Rule: When auditing source completeness, an attribute that is stated for every instance except exactly one is a stronger signal of a transcription/rendering gap than several unrelated, scattered missing details — weigh it accordingly when deciding whether something merits a Decision Journal entry.
Observation: Every one of the 12 signs in Ch. 4 v.6–24 has an explicitly stated rising type (Prishthodaya/Shirshodaya/Ubhayodaya) — except Scorpio, the sole exception. By contrast, Gemini's missing caste/guna and Capricorn's missing caste are scattered, non-uniquely-exceptional gaps.
Evidence: Ch. 4, v.6–24 (all 12 sign-description verses, cross-referenced against each other).
Practical Advice: When the source appears incomplete, check whether the gap is systematic (one clear exception to an otherwise-universal pattern) or scattered (several unrelated missing details) — the former is worth a dedicated Decision Journal entry; the latter is usually adequately handled with a simple "not stated" note in the lesson itself.
Limitations: This is a study-discipline heuristic, not a BPHS-stated principle — it describes how to triage source gaps, not a fact about the source's content.
Related Concepts: the logged, unresolved source gap around Scorpio's rising type.
Developed In: S1-M3-L2.
A calculation from an earlier module can become a required input later — treat that as a real retention test¶
Rule: When a later lesson's technique requires a number computed in an earlier lesson, recompute it rather than trusting memory — this is a genuine test of whether the earlier method was actually retained, not just cited.
Observation: Nisheka Lagna (Ch. 4 v.25–30, Module 3) requires Gulika's exact position as a direct numerical input — Gulika itself was computed via an entirely separate multi-step procedure taught in Module 2 (Ch. 3 v.66–70).
Evidence: Ch. 3, v.66–70 (Gulika); Ch. 4, v.25–30 (Nisheka Lagna, using Gulika as an input).
Practical Advice: Whenever a new technique cites an earlier computed value, redo that earlier computation from scratch rather than assuming a remembered or previously-recorded value is still correct — this catches both memory drift and any arithmetic slips that went unnoticed the first time.
Limitations: None identified — this is a general verification habit, applicable well beyond these two specific techniques.
Related Concepts: Entry 5 above (verify approximate cross-references directly) — the same discipline, applied to numerical results instead of textual claims.
Developed In: S1-M3-L3.
From Module 4 — Locating Planets and the Ascendant (Ch. 5)¶
A translator's own worked example can contain internal arithmetic inconsistencies — verify reused figures before trusting them as a template¶
Rule: Before treating a worked numerical example in this translation as a reliable calculation template, check whether any figure derived early in the example is reused, unchanged, later in the same example — if so, confirm the reused figure actually matches its own first derivation before building further arithmetic on it.
Observation: Chapter 5's Hapur worked example derives the Sun's corrected position as "1s18°8′12″" at one point (Ch. 5 v.2–4's Notes) but reuses it as "1s18°8′22″" — a 10″ difference — in three later, independent stages of the same example (the Ascendant calculation via two routes, and the 10th House calculation). This pattern recurred twice more in Module 5 (Ch. 6's Hora Lagna intermediate arithmetic; Ch. 8's Vimshopaka Bala worked example grading an own-sign placement with the wrong friendship grade).
Evidence: Ch. 5 (Decision Journal Entry 5); Ch. 6 v.4–5 (Decision Journal Entry 6); Ch. 6 v.13–16 (Decision Journal Entry 7); Ch. 8 v.25–27 (Decision Journal Entry 8) — four independent instances across two modules.
Practical Advice: When a lesson or exercise needs a worked example, prefer BPHS's own stated final result over reproducing intermediate arithmetic steps that aren't independently verifiable — and when assigning new-number practice problems, choose inputs whose arithmetic can be checked cleanly (e.g., no remainder, no ambiguous rounding) rather than mirroring a source example's exact numbers, which may themselves carry unresolved errors.
Limitations: This is a study-discipline heuristic about this translation's reliability, not a claim about Parashara's original verse text, which is not directly reachable without the Sanskrit or a second edition.
Related Concepts: the logged worked-example inconsistencies noted across Modules 4–8; the entry above (S1-M3-L2, single-exception scrutiny) — a related but distinct triage heuristic for source gaps versus source arithmetic errors.
Developed In: S1-M4-L1, confirmed again in S1-M5-L1, L2, L4.
From Module 5 — Special Ascendants, Varnada Dasha, and the Sixteen Vargas (Ch. 6–8)¶
A significator planet can be treated as its own Ascendant for questions specific to its own domain¶
Rule: For a question tied to a specific significator (father → Sun; mother → Moon; younger sibling → Mars; spouse → Venus; progeny → Jupiter; death/longevity → Saturn), count the relevant house from that planet's own position, not only from the natal Ascendant — and weigh both readings together rather than treating one as a replacement for the other.
Observation: Ch. 8 v.39–43 gives an explicit table pairing six planets with the house(s) that should be examined from their own position for a specific topic (e.g., the 9th house from the Sun for father, the 7th house from Venus for spouse) — generalizing the same "alternate Ascendant" logic Ch. 6 already established for Bhava/Hora/Ghati Lagna.
Evidence: Ch. 8, v.39–43.
Practical Advice: When a chart-judgment question is specifically about one of these six domains, always compute the relevant house from both the natal Ascendant and the paired significator planet before concluding — a single-source reading risks missing a factor BPHS itself treats as load-bearing for that specific topic.
Limitations: BPHS's own table only names six planets/topics explicitly (father/Sun, generic 10th–11th/Sun, five houses/Moon, sibling/Mars, 6th-house matters/Mercury, progeny/Jupiter, spouse/Venus, death-and-expenditure/Saturn) — this course does not extend the technique to untested planet/topic pairings without a textual basis.
Related Concepts: Ch. 6 v.1–9 (Bhava/Hora/Ghati Lagna, S1-M5-L1) — the same alternate-Ascendant logic in its original, time-based form; Ch. 34 (Karakas, S2-M18, not yet studied) — likely to extend or formalize this significator-based reasoning further.
Developed In: S1-M5-L4.
From Module 6 — Aspects of Signs and Planets (Ch. 9)¶
Saturn, Jupiter, and Mars's "special aspects" are graduated, not binary — they still aspect every house on the list, just at varying strength¶
Rule: When applying Saturn's, Jupiter's, or Mars's special aspects, do not treat their non-"full" listed houses as unaspected — BPHS's own graduated (paada) table assigns every one of the four listed houses some strength (¼, ½, ¾, or full), never zero, for these three planets.
Observation: Popular summaries of "special aspects" often reduce to a binary rule (e.g., "Mars aspects the 4th, 7th, and 8th houses fully, nothing else") — but BPHS's own v.11–15 assigns Mars a full aspect only to the 4th/8th, with the 7th at ¼ strength and 3rd/10th and 5th/9th at ½ and ¾ respectively. The same graduation applies to Saturn (full on 3rd/10th) and Jupiter (full on 5th/9th).
Evidence: Ch. 9, v.11–15.
Practical Advice: When judging a house's aspects in any future lesson, check the full graduated table (Lesson §5.3), not just which house each planet is "known for" — a house receiving a ¼-strength aspect is still aspected, just weakly, and this distinction may matter once Ch. 28 (Semester 2) teaches how to weigh aspect strength in real judgment.
Limitations: This course has not yet reached Ch. 28, so how much practical weight a ¼-strength aspect should carry (versus a full one) is not yet established — only that it is non-zero.
Related Concepts: Ch. 28 (Evaluation of Planetary Aspects, Semester 2, not yet studied) — the natural place this graduation is put to practical use.
Developed In: S1-M6-L1.
From Module 8 — Yoga Karakas (Ch. 36, Semester 1 Capstone)¶
Natural benefic/malefic is only a starting point — functional (house-lordship) classification can override it entirely, and must always be re-derived per ascendant¶
Rule: Before judging any planet's likely effect in a specific chart, determine its functional nature for that specific ascendant (which houses it rules, and which of the four tiers — Kendra, Trikona, Trishadaya, Parashraya — those houses fall into) before leaning on its natural benefic/malefic status (Module 2). The functional classification is chart-specific and must be re-derived for every new ascendant — it is never safe to carry a planet's classification over from one ascendant to another.
Observation: Ch. 36 shows the same planet receiving opposite functional classifications across different ascendants purely from house lordship — e.g., Mars (a natural malefic) is a full Yoga Karaka for Cancer and Leo Ascendants but a Maraka (killer) for Taurus and Virgo Ascendants; Jupiter (a natural benefic) is the single most inauspicious planet for Taurus Ascendant. Trikona (5th/9th) lordship overrides natural nature entirely and unconditionally (v.2); Kendra (angular) lordship only neutralizes it.
Evidence: Ch. 36, v.2–7 (the four-tier framework) and v.19–44 (the full 12-ascendant demonstration).
Practical Advice: When starting any chart analysis, the first practical step after identifying the Ascendant should be building that specific chart's functional benefic/malefic/Yoga Karaka/Maraka table from house lordship — never assume a planet's reputation (natural benefic or malefic) predicts its actual role until this derivation is done.
Limitations: This module's classifications don't yet account for a planet's dignity (exaltation/debilitation, Module 2) or placement (which house it actually occupies) — both modify the base functional classification further, as the Gemini illustrative chart (Jupiter-Saturn conjunct, Saturn debilitated, in a Trishadaya house) demonstrates. Functional classification is the starting frame, not the complete picture.
Related Concepts: Ch. 3 v.11 (Module 2, natural benefic/malefic) — the baseline this entry says not to over-rely on; Ch. 26 (Bhava Lords, Semester 2) — extends this same house-lordship logic into a full 144-combination system; Ch. 46 (Marakas, Semester 2) — will formalize the killer-planet identifications made here.
Developed In: S1-M8-L1, S1-M8-L2.
A single-planet dual Kendra+Trikona lordship is the strongest, cleanest Yoga Karaka signal — check for it first¶
Rule: Before evaluating more complex angle-trine relationships (exchange, conjunction, mutual aspect between two different planets), first check whether any single planet simultaneously rules one Kendra house and one Trikona house for the ascendant in question — this is BPHS's own stated strongest case (v.13), and produces a Yoga Karaka regardless of where the planet is actually placed in the chart.
Observation: Across all twelve ascendants in Ch. 36's reference table, nearly every "sole, superior Yoga Karaka" (Saturn for Taurus and Libra; Venus for Capricorn and Aquarius; Mars for Cancer) is exactly this single-planet dual-lordship case — the two-planet relationship-based Yoga Karaka (v.11–12) is the secondary, more complex pattern, used when no single planet holds this dual role cleanly (e.g., Virgo's Mercury-Venus pair; and, per BPHS's own Notes, even Libra's Moon-Mercury pair exists alongside Saturn's single-planet case there, not instead of it — some astrologers regard Saturn as the stronger of the two).
Evidence: Ch. 36, v.13 (the rule) cross-checked against all twelve ascendants' actual classifications in v.19–44.
Practical Advice: When first learning a new ascendant's Yoga Karaka landscape, compute each planet's house lordships and scan for the single-planet Kendra+Trikona case before working through the more involved two-planet relationship checks — it resolves the question faster and is the pattern BPHS itself treats as strongest.
Limitations: Not every ascendant has a clean single-planet case (Gemini, Leo, Virgo, Scorpio, Sagittarius, Pisces in this course's reading do not, or have a more conditional version) — the two-planet relationship rule (v.11–12) remains necessary for those.
Related Concepts: the entry above (functional classification generally); Ch. 26 (Bhava Lords, Semester 2).
Developed In: S1-M8-L2.