TVK vs DMK after TN 2026: social justice and fair community distribution

Data-grounded party comparison (TN 2026)

Indicator	TVK	DMK	Delta (TVK - DMK)
Tickets fielded	0	0	0
Seats won	0	0	0
Win conversion %	0.0%	0.0%	0.0 pp
Near-miss count (rank 2 losses)	0	0	0
Near-misses under 5,000 votes	0	0	0
Average winner margin	0	0	0
Median winner margin	0	0	0
Average winner vote share	0.00%	0.00%	0.00 pp
Average criminal cases per candidate	0.00	0.00	0.00
Zero-criminal-case candidate share	0.0%	0.0%	0.0 pp
Average declared assets (crore INR)	0.00	0.00	0.00
Graduate-and-above share	0.0%	0.0%	0.0 pp
Incumbent ticket share	0.0%	0.0%	0.0 pp
Turncoat ticket share	0.0%	0.0%	0.0 pp

Total votes perspective (TVK vs DMK)

Indicator	TVK	DMK
Total votes (all candidates)	0	0
Two-party vote share (TVK + DMK pool)	0.00%	0.00%
Average votes per candidate	0	0
Average votes per winner	0	0
Rows with non-null votes (candidate/winner)	0/0	0/0

Age segregation (status)

Age field exists but current API rows are null/unknown for this election payload, so age segmentation is shown as not currently measurable.

Social justice lens: what data is ready now

We can already compare structural fairness proxies with hard data: ticket opportunity, conversion quality, near-miss pressure, criminal-case burden, incumbent dependence, and turncoat dependence.

Community-percentage readiness: Community tags are not present in current candidate payloads, so direct community-share percentages cannot yet be computed from this API.

Age-segregation readiness: Age field exists but current API rows are null/unknown for this election payload, so age segmentation is shown as not currently measurable.

Gender-segregation readiness: Gender field is not exposed in current election/candidate API payloads for this route, so gender segregation cannot yet be computed here.

Consistent party-comparison protocol

Protocol version: party-compare-v1

1. Fix election scope and candidate universe before comparing parties.
2. Use the same metric definitions and formulas for both parties.
3. Separate raw scale metrics (tickets, votes, seats) from conversion metrics (win rate, near misses).
4. Publish data-readiness status for community, age, and gender segmentation before drawing fairness conclusions.
5. Attach methodology, transparency, and uncertainty notes in every comparison page.

Community-percentage audit model (next layer to operationalize)

1. Candidate Share %: (community candidates / total party candidates) x 100.
2. Winner Share %: (community winners / total party winners) x 100.
3. Community Conversion %: (community winners / community candidates) x 100.
4. Representation Balance Ratio: candidate share % / community population benchmark %.
5. Women-within-community %: women candidates in each community bucket / that community total.

Standard metric dictionary (used across party-pair pages)

Metric	Formula	Interpretation
Tickets fielded	Count of candidates fielded by party in election scope	Opportunity surface and coalition strategy footprint
Seats won	Count of candidates with outcome = WON	Raw outcome power
Win conversion %	(seats won / tickets fielded) x 100	Conversion efficiency independent of raw ticket volume
Two-party vote share %	(party total votes / sum of two compared parties total votes) x 100	Relative voter pull within the compared pair
Near-miss pressure	Count of rank-2 losses (plus subset under 5,000 margin)	Expandable frontier for next-cycle conversion
Winner margin profile	Average and median winning margin	Victory depth and stability
Integrity and candidate profile mix	Avg criminal cases, zero-criminal share, assets, education, incumbent %, turncoat %	Candidate quality and risk distribution
Demography readiness	Availability of community/age/gender fields in payloads	Determines whether social-justice segmentation can be measured directly

What this comparison already shows

This page now uses the same election backend as winner and near-miss pages, so conclusions are tied to the live TN 2026 candidate/result tables rather than generic narrative. The strongest party-level fairness reading today is: ticket distribution strategy, conversion quality, and pressure zones where each party repeatedly loses narrowly.

Community-tag comparisons should be enabled as soon as normalized community fields are available in candidate payloads.

Transparency and guardrails

Do not treat any single indicator as moral proof. Use this page as a public audit board: verify sources, compare with constituency-level evidence, and record uncertainty where tags are missing.

Use this page with Transparency, Editorial Policy, and Methodology for full context.