Technique Masterclasses

Pure Mathematics 1

Deep Dive: Sine and Cosine Rules Ambiguous Case

Provenance: written 2026-09-29. Sources actually read for this document: research/veridian/WMA11-verified-facts.md in full for this topic — §1 (spec 3.1's verbatim wording), §2 (formula-booklet contents), §4.3 ("Sine/cosine rule, including the ambiguous case," Jan 2019 Q7 verbatim M/A/B breakdown and the Alt1(a) cosine-rule note), §7 (June 2022 Q2 flag), and the full "sine-and-cosine-rules-ambiguous-case.ts (spec 3.1)" lesson-audit-log entry; the live lesson file content/veridian/curriculum/wma11/sine-and-cosine-rules-ambiguous-case.ts (all 793 lines, read in full, specifically to avoid duplicating its teach blocks, worked chains, diagram, marked-solution, trap-taxonomy and MCQs); content/veridian/technique-hub/wma11/signal-topic-brief-sine-and-cosine-rules-ambiguous-case.md (in full); content/veridian/technique-hub/wma11/codex-formula-and-method-bank.md §1.3.1 and §2.3.1; and content/veridian/question-bank/wma11.ts (grepped — confirmed to contain no sine/cosine-rule or "ambiguous" content, so there is nothing there to cross-check against or avoid duplicating). No new primary-source PDF was fetched for this pass; every exam citation below is inherited from the facts bank's own already-verified extraction of WMA11_01_1901_QP/MS/ER, re-checked here only for correct attribution and word-count compliance on quotes. Every classification, worked micro-example and algebraic identity in §2–§4 below is original mathematical derivation, not an exam citation — each was checked numerically with Python (math.sin/asin/cos, exact float comparison) before being written in, the same discipline the live lesson's own header describes for its worked numbers. Not affiliated with or endorsed by Pearson Edexcel.

CODEX Deep-Dive — Sine and Cosine Rules: The Ambiguous Case (WMA11, spec 3.1)

0. What this document does not repeat

Spec 3.1 reads, verbatim: "The sine and cosine rules, and the area of a triangle in the form ½ab sin C — including the ambiguous case of the sine rule." The live lesson already builds, correctly and in full: which of the four data shapes (SSS, SAS, ASA/AAS, SSA) each rule actually fits; a from-scratch derivation of ½ab sin C; the exam formula booklet's real P1 contents (cosine rule only — sine rule and area formula must be memorised); a coordinate-geometry construction of where a second triangle geometrically comes from (a circle of radius a meeting a fixed ray at up to two points); a structural injectivity argument for why the cosine rule can never produce this ambiguity; four fully-worked chains/drills covering every rule in its safe form; a complete marked-solution built around the one verified examiner finding on this spec point; six trap-taxonomy items; and three MCQs. None of that is reproduced here.

What the lesson's single worked mechanism example does not do — because one numerical instance can't — is state the general rule for how many triangles a given SSA data set actually determines, or address the mark-scheme's own alternative route for solving SSA data. Both are genuine, spec-required content (the ambiguous case is, precisely, a solution-count question, and spec 3.1 names no single method as the required one). This document supplies both, plus an honest accounting of every real exam angle on record for this exact topic.


1. Definitions, precisely


2. The complete classification: how many triangles does a given SSA data set actually determine?

Fix the data as: angle AA, its opposite side aa, and the other given side bb (adjacent to AA, not opposite it — this is what makes the data SSA rather than SAS). Define h=bsin⁡Ah = b\sin A — the height of the perpendicular dropped from the vertex opposite bb down to the ray carrying the unknown side, in the lesson's own compass-construction picture. This single number, together with a plain comparison of aa against bb, settles the whole question. Both branches below were checked exhaustively across a systematic numerical sweep (a range of AA values on either side of 90°90°, with aa swept finely through every named boundary) before being stated as fact.

Branch 1 — AA acute (0°<A<90°0°<A<90°):

ConditionTrianglesWhy
a<ha<h0sin⁡B=h/a>1\sin B = h/a>1 — no angle has a sine that large.
a=ha=hexactly 1sin⁡B=1\sin B=1, so B=90°B=90° exactly — the ray is tangent to the circle of radius aa; the two candidate positions from the lesson's own construction coincide.
h<a<bh<a<bexactly 2Both candidates, B1B_1 and 180°−B1180°-B_1, keep the angle sum under 180°180° — the circle crosses the ray at two genuinely distinct positive points.
a=ba=bexactly 1The triangle is isosceles (A=B1A=B_1); the supplementary candidate forces the third angle to exactly 0°0° — degenerate, not a real triangle.
a>ba>bexactly 1Only the acute candidate keeps the angle sum under 180°180°; the supplementary candidate always overshoots once aa exceeds bb.

Branch 2 — AA a right angle or obtuse (A≥90°A\geq90°): hh plays no role here at all — a systematic check across A=100°,110°,115°,120°,135°,150°A=100°,110°,115°,120°,135°,150° with aa swept through the region h<a<bh<a<b that produces two triangles in Branch 1 found zero valid triangles there in every case; the only boundary that matters is aa against bb directly:

ConditionTrianglesWhy
a≤ba\leq b0Even where sin⁡−1\sin^{-1} still returns a value, both resulting candidates force the third angle to zero or negative — checked directly at a=ba=b: the only surviving candidate has B=180°−AB=180°-A, giving third angle 180°−A−(180°−A)=0°180°-A-(180°-A)=0° exactly, a degenerate boundary, not a real triangle.
a>ba>bexactly 1Only the acute candidate for BB survives the angle-sum check; the case never produces two.

Verified micro-examples (all five Branch-1 rows, one fixed pair A=40°A=40°, b=12b=12, so h=bsin⁡40°≈7.7135h=b\sin40°\approx7.7135):

Verified micro-examples, Branch 2 (A=115°A=115°, b=12b=12, so h≈10.876h\approx10.876 — shown to confirm it is irrelevant here):

The practical shortcut this classification actually earns. Since h=bsin⁡A<bh=b\sin A<b for every acute AA (with equality only in the limit A→90°A\to90°), the two-triangle window h<a<bh<a<b is always a subset of a<ba<b. So genuine ambiguity — a real fork between two valid triangles, not just two candidates from sin⁡−1\sin^{-1} — is possible only when the side opposite the given angle is strictly shorter than the other given side (a<ba<b), and even then only if aa clears the height threshold hh. If a≥ba\geq b, or if the given angle AA is itself a right angle or obtuse, there is at most one valid triangle regardless of what sin⁡−1\sin^{-1} returns — the supplementary-angle check the lesson's central trap is built around is still the correct method to run (it costs nothing and catches the genuine cases), but its outcome is decided before any arithmetic starts, the moment the two given side lengths are compared.


3. Where this connects back to the lesson's own construction

The lesson's mechanism block places vertex AA at the origin, side AC=bAC=b at angle AA above the ray carrying BB, and finds BB as wherever the circle of radius aa centred on CC crosses that ray. Solving that intersection algebraically — (t−bcos⁡A)2+(bsin⁡A)2=a2(t-b\cos A)^2+(b\sin A)^2=a^2 — gives t=bcos⁡A±a2−h2t=b\cos A\pm\sqrt{a^2-h^2}, exactly the two candidate positions the lesson's own numerical instance (A=30°,a=5,b=9A=30°,a=5,b=9) draws. The "a<ha<h gives none, a=ha=h gives one, a>ha>h gives two candidate crossing points" fact is just this square root turning imaginary, zero, or real — the same discriminant idea the lesson's sibling lessons use for a quadratic's roots, applied here to a circle-meets-line intersection instead. What the lesson's single instance doesn't show is that a candidate crossing point can still fail to count, because it lands on the negative side of the ray (behind AA, not a valid triangle vertex): the nearer crossing point, t=bcos⁡A−a2−h2t=b\cos A-\sqrt{a^2-h^2}, is positive exactly when a2−h2<bcos⁡A\sqrt{a^2-h^2}<b\cos A — which rearranges (squaring, since both sides are positive for acute AA) to a2−b2sin⁡2A<b2cos⁡2Aa^2-b^2\sin^2A<b^2\cos^2A, i.e. a2<b2(sin⁡2A+cos⁡2A)=b2a^2<b^2(\sin^2A+\cos^2A)=b^2, i.e. a<ba<b. That is the same a<ba<b condition §2 reaches from the angle-sum argument — two independent routes to an identical boundary, which is exactly the kind of cross-check this course's own discipline expects before trusting a general claim.


4. A second, mark-scheme-credited route through SSA data: the cosine rule as a quadratic

The facts bank's own record of the one fully-documented exam appearance of this topic (Jan 2019 Q7(a)) notes that the real mark scheme's Alt1(a) route solves the same SSA data with the cosine rule instead of the sine rule — forming a quadratic in the unknown third side, then applying the cosine rule a second time for the angle. The live lesson's own teach block states the sine rule is "the only tool that fits" SSA data; its closing audit log flags this as a real, unresolved tension, left for "whichever pass next touches this lesson's teach block." This section is that pass, scoped narrowly to resolving it here rather than editing the lesson itself.

The method, in general. With AA, opposite side aa, and adjacent side bb known, and cc the unknown third side, the cosine rule a2=b2+c2−2bccos⁡Aa^2=b^2+c^2-2bc\cos A rearranges into a quadratic in cc:

c2−(2bcos⁡A)c+(b2−a2)=0.c^2-(2b\cos A)c+(b^2-a^2)=0.

By the quadratic formula, c=bcos⁡A±b2cos⁡2A−b2+a2=bcos⁡A±a2−h2c=b\cos A\pm\sqrt{b^2\cos^2A-b^2+a^2}=b\cos A\pm\sqrt{a^2-h^2} — the same expression §3 derived geometrically for the crossing point tt, confirming the two methods are the same construction seen algebraically instead of with coordinates. The discriminant is 4(a2−h2)4(a^2-h^2), so it reproduces §2's own aa-vs-hh boundary directly: negative discriminant (a<ha<h) means no real cc, zero discriminant (a=ha=h) means one repeated root, positive discriminant (h<ah<a) means two real roots — of which only the positive ones are valid side lengths. By Vieta's formulas the two roots multiply to b2−a2b^2-a^2: when a<ba<b that product is positive, so both roots share the same sign as their sum (2bcos⁡A2b\cos A, positive for acute AA) and both are valid — two triangles; when a>ba>b the product is negative, so exactly one root is positive and one is negative (an algebraically real but geometrically meaningless "negative length") — exactly one triangle. This is the identical aa-vs-bb test from §2, reached a third, independent way.

Verified micro-example (A=40°A=40°, a=8a=8 opposite AA, b=12b=12 — the same two-triangle regime as §2's row three): the sine rule gives B≈74.62°B\approx74.62° or B≈105.38°B\approx105.38°. The cosine-rule quadratic, c2−(24cos⁡40°)c+(144−64)=0c^2-(24\cos40°)c+(144-64)=0, has discriminant ≈18.01\approx18.01 and roots c≈11.3145c\approx11.3145 and c≈7.0706c\approx7.0706 — both positive, so both are valid third sides. Substituting each back into cos⁡A=b2+c2−a22bc\cos A=\frac{b^2+c^2-a^2}{2bc} recovers A=40.0000°A=40.0000° exactly for both, confirming the two roots correspond to the same two triangles the sine rule found, reached without ever computing sin⁡−1\sin^{-1} of anything.

What this genuinely resolves. The sine rule remains the didactically-intended default for SSA data — it is shorter, and it is what the lesson correctly teaches as the standard route. But "the only tool that fits" overstates the real mark scheme, which credits the cosine-rule quadratic as an equally valid Alt1(a) method for the exact same data shape. The two methods are not just both "valid answers" in the loose sense every alternative method is — they are, as shown above, the same underlying algebra (a2−h2a^2-h^2 under a square root) arrived at from two different starting formulas, which is why they always agree on how many triangles exist and never disagree about which ones.


5. Synthesis: every real exam angle this topic has actually been tested from

This course's own SIGNAL brief for this topic gives the honest count directly: the ambiguous case is confirmed in 2 of 9 series checked — one fully documented, one thinly. Both are real; neither should be over-generalised, and nothing below states a likelihood beyond that count.

Jan 2019 Q7(a) — fully documented. A roof-truss SSA question (3 marks, M1/A1/A1, no dependent marks — the only confirmed mark-tariff shape on record for this topic). The examiner report names two distinct real traps from the same paragraph: candidates who "achieved the correct acute angle" but "failed to find the required obtuse angle," and, separately, candidates who worked "in radians" when the question's own angle (35°) was in degrees. The first is this lesson's central trap; the second is its sixth trap-taxonomy item. Both are already fully taught in the live lesson and are not repeated here beyond this synthesis line. What §2 above adds to this specific appearance: the roof-truss context resolves the ambiguity by diagram/context-embedded validity — a candidate has to reason about which candidate angle the physical shape permits, not compute an aa-vs-bb comparison, because the question's own diagram (rather than a stated inequality) is what fixes it.

June 2022 Q2 — thinly documented. Recorded in the facts bank and the SIGNAL brief only as: a sine-rule ambiguous-case question resolved by a stated side-length comparison, found by a later, narrower content-gap audit rather than a full question-by-question read of that series. No mark tariff, wording, or M/A/B breakdown survives in the research pass for this one — inventing any of that here would be exactly the fabrication this course's discipline exists to prevent, so none is offered. What can honestly be added: a stated comparison of the two given side lengths is, per §2's own classification, a genuinely different — and in one respect more efficient — resolution route than the diagram-based one above. If a question states outright which of the two given sides is longer, that alone can settle whether ambiguity is even mathematically possible before any trigonometry is done: a≥ba\geq b rules out a second triangle immediately (§2, Branch 1's last two rows), while a<ba<b leaves the question open pending the hh comparison. A real exam question resolving the ambiguous case this way is independent confirmation that the aa-vs-bb test in §2 is not merely a tidy theoretical shortcut — it is a genuine, examiner-tested resolution mechanism in its own right, distinct from reading a diagram.

What is not claimed. Seven of the nine series this course's research has touched for WMA11 were never checked question-by-question for this specific topic, so their silence is not evidence the ambiguous case didn't appear in them — only that it hasn't been found there yet. No grade boundary, no percentage of candidates, and no frequency finer than "2 of 9 series checked" is stated anywhere in this document, matching the one mark-tariff data point (3 marks, M1/A1/A1) actually on record. The Alt1(a) cosine-rule route in §4 is mark-scheme-verified for the one fully-documented appearance (Jan 2019 Q7) specifically — it is not separately confirmed for June 2022 Q2, where no method breakdown survives at all.


6. Closing scope note

Everything in §2–§4 is ordinary, checkable trigonometry — a solution-count classification, a coordinate-geometry cross-check, and an algebraic identity connecting two textbook methods — verified here by direct numerical computation across a systematic sweep of cases, exactly the way the live lesson's own header describes verifying its worked numbers. None of it is an empirical claim about how WMA11 candidates actually perform, and none of it should be read as such. The only empirical claims in this document are in §5, and each is traced to the facts bank's own two named findings (Jan 2019 Q7(a), fully documented; June 2022 Q2, thinly documented) — nothing beyond what those two entries actually support.