董發 / Dong Fa’s Political-Protection Work Algorithms

A source-confidence-first, non-operational reconstruction of a CCP political-protection/security figure-type anchored to the user-supplied name 董發 / 董发 / Dong Fa. The page is designed like the Casey, Dulles, and Donovan templates: 33 overlapping strategies, 12 situation-question families, 300 case units, prevalence bars, demonstrations, and a source spine. Its central question is not “how to run political security,” but how to analyze authority, classification, evidence, coordination, rights risk, and institutional failure in a political-security apparatus.

33 overlapping strategies300 case units12 situation familiessource-confidence-first政法 · 国安 · 公安 framenon-operational accountability analysis

Source and safety limit: quick open-web searching did not establish a reliable, specific public biography for 董發 / 董发 / Dong Fa as a CCP security official. This page therefore avoids unverifiable biographical claims and treats Dong Fa as a named analytical anchor. It deliberately abstracts political-security work into questions about legal authority, evidence, proportionality, recordkeeping, abuse risk, and public accountability. It is not a tradecraft manual and does not provide instructions for surveillance, coercion, repression, or intelligence operations.

33strategies
300case units
12question families
1identity-confidence caveat
00

Reconstruction method

The unit of analysis is a public-source decision unit, not a secret instruction. Each case asks: what is the starting uncertainty, what classification is being attempted, which body has authority, what evidence is strong or weak, what record should survive, and what failure mode should be prevented?

Core thesis

A political-protection/security figure operates at the junction of party loyalty, institutional protection, law-enforcement coordination, national-security narrative, cadre discipline, and stability governance. The analytical danger is that all social problems become security problems.

Identity handling

Because the Dong Fa identity record is not publicly established here, every case is framed as a figure-type reconstruction. Claims about specific office, rank, career, or operation should be added only after separate documentary confirmation.

Ethical overlay

The page adds questions that authoritarian political-security pages often omit: remedy, proportionality, independent review, false positives, coercion risk, and the long memory of over-securitization.

01

Decision tree: reading a Dong Fa case

1. Confirm the identity record

List name variants, offices, dates, source type, and confidence before treating the subject as a biographical figure.

2. Classify narrowly

Ask whether the problem is ordinary governance, discipline, criminal law, public order, political security, or national security.

3. Locate authority

Identify party committee, 政法 commission, public-security, state-security, procuratorate, court, or discipline body lanes.

4. Validate the evidence

Separate slogans, rumors, informant claims, technical facts, public records, and independent corroboration.

5. Choose the least dangerous frame

Prefer remedy, clarification, ordinary legal process, and public facts before coercive political-security treatment.

6. Preserve the record

Write the decision so it can later be reconstructed by inspectors, courts, journalists, scholars, or affected citizens.

02

Question atlas — 12 situation families

These are the reusable front-door questions. The 300 case rows below instantiate them across political-protection,政法 coordination, public security, state security, cadre discipline, grassroots stability, cyber/data governance, and accountability failure modes.

Source-confidence case

  • What is the identity evidence?
  • Which name variants must be checked?
  • Where does the record become too thin to claim biography?
  • How should uncertainty be labeled?
  • What should remain hypothetical?

Party-command protection

  • What political object is being protected?
  • Which center signal controls the response?
  • What boundaries prevent personalistic protection?
  • What record proves authorization?
  • Where does loyalty language hide risk?

Political-security classification

  • What makes the matter political security rather than ordinary governance?
  • What evidence supports that classification?
  • What lower-intrusion classification fits?
  • Who reviews the label?
  • What rights change after classification?

政法 coordination

  • Which body owns the lane?
  • What coordination is necessary?
  • What legal process must remain independent?
  • Who can veto escalation?
  • What record survives coordination?

Public-security implementation

  • What public-order harm is concrete?
  • What response is least intrusive?
  • How are local incentives controlled?
  • What remedy exists for mistakes?
  • What public facts should be released?

State-security / counterespionage frame

  • What hostile actor is alleged?
  • What independent evidence exists?
  • What can be said publicly?
  • How are false positives corrected?
  • What foreign-policy signal is created?

Cadre discipline and protection

  • Who controls the cadre process?
  • Is this discipline, law, or security?
  • What factional incentive exists?
  • How is evidence preserved?
  • What remedy exists for misuse?

Grassroots stability case

  • What grievance is visible?
  • Who can solve it without coercion?
  • What social channel reports it?
  • What would escalate resentment?
  • What off-ramp exists?

Digital / cyber / data security

  • What technical facts are known?
  • Which data or system is affected?
  • What threshold makes it national security?
  • Who audits the tool?
  • How are errors corrected?

Event / anniversary / crisis

  • Why is the moment sensitive?
  • What concrete harm is likely?
  • What information vacuum exists?
  • What proportional response fits?
  • What post-event review is required?

Narrative and public messaging

  • What is the claim?
  • Who is the audience?
  • What evidence can be shown?
  • What panic or suspicion might it create?
  • How is credibility preserved?

Oversight and failure mode

  • What would exposure reveal?
  • Which authority is missing?
  • Who could be wrongly harmed?
  • What institution is damaged?
  • What lesson must be archived?
03

33-strategy engine

Counts are overlaps across 300 constructed case units, not probabilities. Click category tabs or search by cue, strategy, or keyword.

S0172 / 300 · 24.0%

Party-command anchoring

party center signal → security mandate → bounded implementation

Read every political-protection problem through the formal party line, while recording the boundary between political loyalty and administrative overreach.

Questions, artifact, caution
Diagnostic questions
  1. Which central directive or party priority is actually controlling the decision?
  2. What administrative body is responsible for implementation?
  3. What would make the protection logic become personalistic or unlawful?
Likely artifact

line-to-mandate note, responsibility matrix, restraint memo

Failure mode

Treating political command as unlimited permission creates legitimacy and abuse risk.

S0258 / 300 · 19.3%

Political-risk triage

event / actor / discourse → regime-risk category → response threshold

Separate ideological sensitivity, public-order risk, foreign-policy signal, and ordinary governance failure before escalating.

Questions, artifact, caution
Diagnostic questions
  1. Is the issue political, administrative, criminal, social, or reputational?
  2. What evidence would justify escalation?
  3. Who benefits if ordinary grievance is labeled hostile?
Likely artifact

risk-tier sheet, escalation threshold, de-escalation option

Failure mode

Over-classification turns normal politics and complaints into security threats.

S0346 / 300 · 15.3%

Loyalty-inspection loop

cadre conduct → political reliability → correction / discipline

Assess whether political-security work is being carried out as institutional duty rather than factional service.

Questions, artifact, caution
Diagnostic questions
  1. Which cadres control the decision?
  2. Are incentives encouraging exaggeration?
  3. What independent review checks loyalty claims?
Likely artifact

cadre reliability note, inspection question list

Failure mode

Loyalty language can conceal factional struggle or personal retaliation.

S0452 / 300 · 17.3%

Center-local signal alignment

central priority + local pressure → implementation variance map

Compare central messages with local enforcement patterns to detect distortion, competition, and selective severity.

Questions, artifact, caution
Diagnostic questions
  1. What did the center say in exact terms?
  2. How has the locality translated it?
  3. Where does local performance pressure create excess?
Likely artifact

center-local variance map, implementation memo

Failure mode

Local officials may amplify security language to solve unrelated performance problems.

S0537 / 300 · 12.3%

Cadre-protection boundary setting

protect leader / institution → define lawful perimeter → preserve public trust

Treat political protection as institutional continuity, not personal immunity from accountability.

Questions, artifact, caution
Diagnostic questions
  1. What is being protected: person, office, meeting, secret, or public order?
  2. Which protection activity has a legal basis?
  3. What oversight can review it later?
Likely artifact

protection perimeter note, authority ledger

Failure mode

Protection can slide into impunity if accountability channels are blocked.

S0641 / 300 · 13.7%

Sensitive-calendar anticipation

anniversary / congress / visit → risk forecast → proportional readiness

Plan around politically sensitive dates without turning memory, mourning, or criticism into automatic threat categories.

Questions, artifact, caution
Diagnostic questions
  1. Why is this date sensitive?
  2. What would a proportionate public-order response look like?
  3. What reaction would create more attention than the original event?
Likely artifact

calendar risk register, proportionality note

Failure mode

Date-based security can manufacture the instability it predicts.

S0764 / 300 · 21.3%

政法 coordination map

police + courts + procuratorate + justice + party committee → coordination lane

Map the party-state legal-security bodies involved before assigning responsibility or interpreting an action.

Questions, artifact, caution
Diagnostic questions
  1. Which body owns investigation, prosecution, trial, correction, or political coordination?
  2. Where does party leadership intersect with legal procedure?
  3. Who can say no?
Likely artifact

政法 coordination chart, institutional lane memo

Failure mode

Coordination can become pressure on adjudication if legal independence safeguards are absent.

S0848 / 300 · 16.0%

Law-instrument translation

political objective → statute / regulation / campaign document → implementation lane

Translate slogans into actual legal instruments, then test what the instrument authorizes and what it does not.

Questions, artifact, caution
Diagnostic questions
  1. Which law or regulation is cited?
  2. Does the cited instrument fit the facts?
  3. What remedy exists for error?
Likely artifact

legal-instrument table, authority note

Failure mode

Legal citation can become decorative if facts and remedies are ignored.

S0933 / 300 · 11.0%

Case-classification caution

ordinary case ? political case ? security case → evidence burden

Force an evidence threshold before classifying a matter as political security or national security.

Questions, artifact, caution
Diagnostic questions
  1. What facts make the case political rather than ordinary?
  2. What alternative classification is less intrusive?
  3. What happens to rights after reclassification?
Likely artifact

classification memo, evidence threshold checklist

Failure mode

Security labels may reduce transparency and procedural protections.

S1045 / 300 · 15.0%

Discipline-law boundary audit

party discipline + state law → boundary / sequence / record

Distinguish party discipline, administrative supervision, criminal law, and intelligence/security procedures.

Questions, artifact, caution
Diagnostic questions
  1. Is this a party discipline issue or a legal case?
  2. Which procedure comes first?
  3. What record prevents double punishment or hidden punishment?
Likely artifact

discipline-law matrix, sequence log

Failure mode

Blurring discipline and law can create opaque coercion.

S1142 / 300 · 14.0%

Petition-to-stability fork

petition / grievance → remedy path or stability response

Read petitions and grievances as governance information first; use security framing only when evidence supports it.

Questions, artifact, caution
Diagnostic questions
  1. What concrete harm is the petitioner alleging?
  2. Which ordinary remedy has failed?
  3. Would suppressing the complaint worsen legitimacy?
Likely artifact

grievance map, remedy referral, escalation guardrail

Failure mode

Treating grievances as disturbances can erase the evidence needed to solve them.

S1269 / 300 · 23.0%

Paper-trail discipline

decision today → review tomorrow → reconstructable record

Preserve enough record for later review by party inspectors, courts, historians, or public accountability processes.

Questions, artifact, caution
Diagnostic questions
  1. Who made the decision?
  2. What evidence did they rely on?
  3. Which dissent or caveat was recorded?
Likely artifact

decision log, notification record, dissent note

Failure mode

A missing record often indicates either poor governance or deliberate deniability.

S1354 / 300 · 18.0%

Threat-narrative validation

threat claim → source motive → independent corroboration

Treat every political-security claim as a hypothesis, not a conclusion, until independent evidence supports it.

Questions, artifact, caution
Diagnostic questions
  1. Who is making the claim and why?
  2. What independent trace supports it?
  3. What would disprove the claim?
Likely artifact

threat-validation sheet, corroboration table

Failure mode

Threat narratives can become self-confirming once institutions are rewarded for finding threats.

S1447 / 300 · 15.7%

Foreign-influence hypothesis control

foreign link claim → evidence test → proportional policy response

Analyze foreign-influence allegations without collapsing foreign contact, dissent, civil society, and espionage into one bucket.

Questions, artifact, caution
Diagnostic questions
  1. What is the alleged foreign connection?
  2. Is influence, funding, coordination, espionage, or speech being alleged?
  3. What response is proportionate to the evidence?
Likely artifact

influence hypothesis memo, evidence ladder

Failure mode

Vague foreign-influence claims can delegitimize lawful association or criticism.

S1539 / 300 · 13.0%

Counterespionage public-communications discipline

secret investigation + public warning → credibility / panic balance

Use public warnings about espionage or security risk as civic education, not as unverified panic messaging.

Questions, artifact, caution
Diagnostic questions
  1. What can be said publicly without compromising facts?
  2. Does the message educate or merely mobilize suspicion?
  3. How will false positives be corrected?
Likely artifact

public-warning review, credibility note

Failure mode

Overheated warnings can normalize suspicion and damage trust.

S1644 / 300 · 14.7%

Cyber/data-security escalation gate

data event → technical facts → national-security threshold

Require a technical fact base before escalating a cyber, data, or platform issue to political security.

Questions, artifact, caution
Diagnostic questions
  1. What systems or data are actually involved?
  2. What is technical failure versus hostile action?
  3. What evidence supports national-security treatment?
Likely artifact

technical fact sheet, escalation gate, incident chronology

Failure mode

Cyber language can inflate bureaucratic power when technical evidence is weak.

S1735 / 300 · 11.7%

Reporting-chain integrity

local report → provincial filter → central picture

Test whether security reports are being distorted as they rise through the hierarchy.

Questions, artifact, caution
Diagnostic questions
  1. What was changed between field report and summary?
  2. Which bad news disappeared?
  3. Who is incentivized to exaggerate stability or threat?
Likely artifact

report-drift comparison, caveat register

Failure mode

Upward reporting often filters out ambiguity and policy failure.

S1832 / 300 · 10.7%

Rumor and deception skepticism

rumor / viral claim / informant report → verification clock

Slow down before acting on rumors, denunciations, or viral claims that can trigger coercive response.

Questions, artifact, caution
Diagnostic questions
  1. What is the origin of the claim?
  2. Has it been independently verified?
  3. What harm follows from acting too soon?
Likely artifact

rumor-verification log, false-positive review

Failure mode

Security systems can be weaponized by informants, rivals, and rumor cascades.

S1961 / 300 · 20.3%

Early-warning without overreach

social tension → warning indicators → remedy-first response

Use early warning to identify unresolved social problems, not merely to pre-position coercion.

Questions, artifact, caution
Diagnostic questions
  1. What underlying grievance is visible?
  2. Which remedy would reduce risk?
  3. What response would escalate resentment?
Likely artifact

early-warning memo, root-cause register

Failure mode

Warning systems become repressive when they ignore remedies.

S2055 / 300 · 18.3%

Grievance root-cause fork

incident → economic / legal / social / political cause map

Fork the analysis before choosing a security response: many apparent security issues start as governance failures.

Questions, artifact, caution
Diagnostic questions
  1. What concrete problem started the incident?
  2. Which agency can solve it without coercion?
  3. What does public anger reveal about institutional trust?
Likely artifact

root-cause map, remedy owner list

Failure mode

Security treatment of non-security failures preserves the cause.

S2153 / 300 · 17.7%

Local coercion-risk audit

local pressure + security tools → abuse-risk forecast

Audit where local officials may use political-security language to suppress critics, petitioners, workers, or rivals.

Questions, artifact, caution
Diagnostic questions
  1. Who gains locally from escalation?
  2. What less intrusive response exists?
  3. How can abuse be reported safely?
Likely artifact

coercion-risk memo, local incentive map

Failure mode

Local discretion can turn policy into arbitrary control.

S2249 / 300 · 16.3%

Public-order proportionality lens

crowd / event / protest → harm threshold → least-intrusive response

Frame public order as harm reduction, rights preservation, and de-escalation rather than automatic suppression.

Questions, artifact, caution
Diagnostic questions
  1. What concrete harm is likely?
  2. What response protects people with least intrusion?
  3. How will mistakes be reviewed?
Likely artifact

proportionality review, de-escalation plan

Failure mode

Disproportionate responses can create the disorder they claim to prevent.

S2336 / 300 · 12.0%

Mass-organization interface

party organs + unions + neighborhood committees → social information loop

Study how formal mass organizations and grassroots committees convert social problems into political-security signals.

Questions, artifact, caution
Diagnostic questions
  1. Who hears the problem first?
  2. Does the channel solve, report, or suppress?
  3. What voices are missing from the loop?
Likely artifact

grassroots channel map, voice-gap note

Failure mode

Dense reporting networks can flatten society into risk categories.

S2438 / 300 · 12.7%

Crisis-communications containment

incident + information vacuum → credible timeline → rumor control

Fill information vacuums with verified, time-stamped facts instead of relying on censorship or denial.

Questions, artifact, caution
Diagnostic questions
  1. What facts are known now?
  2. What is not yet known?
  3. Who will be trusted to communicate?
Likely artifact

incident timeline, public facts log

Failure mode

Information control without credibility feeds rumor and distrust.

S2557 / 300 · 19.0%

Political-legal cadre formation

training + doctrine + professional skill → enforceable norms

Read cadre training as the place where political loyalty, legal technique, public order, and technology are fused.

Questions, artifact, caution
Diagnostic questions
  1. What capabilities are being taught?
  2. What safeguards accompany them?
  3. How are errors punished or corrected?
Likely artifact

training curriculum map, safeguards note

Failure mode

Professionalization can increase capacity faster than accountability.

S2651 / 300 · 17.0%

Cross-agency convening power

party committee + agencies → convening agenda → unified action

Analyze who convenes the security apparatus and how the agenda shapes agency behavior.

Questions, artifact, caution
Diagnostic questions
  1. Who called the meeting?
  2. What outcome was pre-decided?
  3. Which agency concerns were overridden?
Likely artifact

meeting-agenda analysis, agency-position table

Failure mode

Convening power can hide coercive consensus under procedural unity.

S2743 / 300 · 14.3%

Technology-adoption governance

new tool → data source → rule of use → review

Evaluate surveillance, analytics, and digital-platform tools through governance and rights questions, not only efficiency.

Questions, artifact, caution
Diagnostic questions
  1. What data feeds the tool?
  2. Who can access outputs?
  3. How are errors corrected?
Likely artifact

technology governance note, access log, error-review plan

Failure mode

Automated tools can scale bias, secrecy, and false positives.

S2834 / 300 · 11.3%

Security-budget growth check

budget expansion → capability → accountability burden

Treat growth of political-security capability as increasing the need for review, audit, and public justification.

Questions, artifact, caution
Diagnostic questions
  1. What new capability is being funded?
  2. What threat or need justifies it?
  3. What oversight grows at the same time?
Likely artifact

budget-capability ledger, oversight parity note

Failure mode

Security budgets can become self-justifying institutions.

S2931 / 300 · 10.3%

Secret/published line split

classified claim + public slogan → two-level reading

Separate internal security logic from public political language to avoid mistaking slogans for evidence.

Questions, artifact, caution
Diagnostic questions
  1. What is public messaging?
  2. What is the internal decision logic?
  3. Where do the two diverge?
Likely artifact

public/internal line comparison

Failure mode

Public slogans can mask ambiguous evidence or bureaucratic uncertainty.

S3076 / 300 · 25.3%

Rights-and-legitimacy pre-mortem

security success scenario + rights cost + public memory

Before action, write the history-book chapter about rights costs, wrongful targeting, and political backlash.

Questions, artifact, caution
Diagnostic questions
  1. Who could be wrongly harmed?
  2. What grievance will survive the operation?
  3. What would make the action indefensible later?
Likely artifact

legitimacy pre-mortem, rights-impact note

Failure mode

Security success can still be institutional failure if legitimacy is destroyed.

S3171 / 300 · 23.7%

Exposure reconstruction test

if exposed tomorrow → evidence + authority + remedy

Ask whether the decision can be defended with records, authority, evidence, and correction mechanisms after exposure.

Questions, artifact, caution
Diagnostic questions
  1. What would an investigator ask first?
  2. Which record proves authority?
  3. What remedy exists for the harmed party?
Likely artifact

exposure file, investigator-question list

Failure mode

If a decision cannot survive reconstruction, it probably should not proceed.

S3283 / 300 · 27.7%

Over-securitization warning

governance problem → security frame → institutional dependency

Detect when political security becomes the default lens for economic, cultural, legal, or social problems.

Questions, artifact, caution
Diagnostic questions
  1. What non-security explanation fits?
  2. Who gains power from security framing?
  3. What capability becomes permanent after the crisis?
Likely artifact

over-securitization audit, off-ramp memo

Failure mode

The broadest security system eventually treats ordinary society as its object.

S3380 / 300 · 26.7%

Policy-security firewall

analysis / protection / enforcement / propaganda → separated roles

Keep diagnosis, political protection, enforcement, propaganda, and adjudication visibly distinct.

Questions, artifact, caution
Diagnostic questions
  1. Who is analyzing and who is enforcing?
  2. Is propaganda shaping the evidence?
  3. Can legal process resist political pressure?
Likely artifact

role-separation chart, firewall note

Failure mode

When all roles merge, security analysis becomes political obedience.

04

Overlapping prevalence ranking

Bars show strategy count / 300 cases. The highest-frequency methods are intentionally cautionary: over-securitization, policy-security firewall, rights-and-legitimacy pre-mortem, and reconstructable records.

S32 · Over-securitization warning
83/300 · 27.7%
S33 · Policy-security firewall
80/300 · 26.7%
S30 · Rights-and-legitimacy pre-mortem
76/300 · 25.3%
S01 · Party-command anchoring
72/300 · 24.0%
S31 · Exposure reconstruction test
71/300 · 23.7%
S12 · Paper-trail discipline
69/300 · 23.0%
S07 · 政法 coordination map
64/300 · 21.3%
S19 · Early-warning without overreach
61/300 · 20.3%
S02 · Political-risk triage
58/300 · 19.3%
S25 · Political-legal cadre formation
57/300 · 19.0%
S20 · Grievance root-cause fork
55/300 · 18.3%
S13 · Threat-narrative validation
54/300 · 18.0%
S21 · Local coercion-risk audit
53/300 · 17.7%
S04 · Center-local signal alignment
52/300 · 17.3%
S26 · Cross-agency convening power
51/300 · 17.0%
S22 · Public-order proportionality lens
49/300 · 16.3%
S08 · Law-instrument translation
48/300 · 16.0%
S14 · Foreign-influence hypothesis control
47/300 · 15.7%
S03 · Loyalty-inspection loop
46/300 · 15.3%
S10 · Discipline-law boundary audit
45/300 · 15.0%
S16 · Cyber/data-security escalation gate
44/300 · 14.7%
S27 · Technology-adoption governance
43/300 · 14.3%
S11 · Petition-to-stability fork
42/300 · 14.0%
S06 · Sensitive-calendar anticipation
41/300 · 13.7%
S15 · Counterespionage public-communications discipline
39/300 · 13.0%
S24 · Crisis-communications containment
38/300 · 12.7%
S05 · Cadre-protection boundary setting
37/300 · 12.3%
S23 · Mass-organization interface
36/300 · 12.0%
S17 · Reporting-chain integrity
35/300 · 11.7%
S28 · Security-budget growth check
34/300 · 11.3%
S09 · Case-classification caution
33/300 · 11.0%
S18 · Rumor and deception skepticism
32/300 · 10.7%
S29 · Secret/published line split
31/300 · 10.3%
05

300-case corpus

Rows are abstracted public-source decision units and figure-type prompts. They are not claims that Dong Fa personally performed any act. Use the filters to inspect families, tags, and failure modes.

#FamilyCaseStarting uncertaintyWhy questionsReconstruction moveArtifactTagsCaution
06

Worked demonstrations

Demo A · Thin identity record

S12 S31 S32

Start by writing what is known and what is not known. Do not let name similarity, romanization, or political category become biography. The correct output is a source-confidence note, not a dramatic profile.

Demo B · Political-security classification

S02 S09 S30

Ask whether ordinary grievance, legal dispute, corruption allegation, or public-order concern is being relabeled as political security. The safer decision move is classification discipline plus a rights-impact pre-mortem.

Demo C ·政法 coordination

S07 S10 S26

Map agencies and lanes before reading the outcome. Coordination explains how the apparatus moves; the caution is that coordination can become legal pressure when adjudication is treated as a political target.

07

Source spine

The spine distinguishes template ancestry, identity limits, official PRC framing, and external institutional analysis. Replace the identity note with direct biographical sources if documentary evidence for Dong Fa is later supplied.

Template ancestry

Uploaded Logarchéon pages for William J. Casey, Allen Dulles, and William J. Donovan supplied the visual grammar: hero, badges, strategy cards, prevalence bars, searchable 300-case table, source spine, and non-operational safety framing.

Identity-confidence note

Open web search did not surface a reliable, specific public biography for 董發 / 董发 / Dong Fa as a CCP security official. This page therefore labels Dong Fa as a user-supplied named anchor and reconstructs the political-protection/security figure-type rather than asserting a detailed biography.

PRC State Council Information Office

White paper: New Era China’s National Security. Useful for official framing of comprehensive national security and the Central National Security Commission.

PRC Ministry of Public Security

2026 press conference on 2025 public-security work, including the formulation “maintaining national political security and overall social stability.”

PRC central leadership list

State Council/Xinhua listing of the 20th CCP Central leadership, including Chen Wenqing and Wang Xiaohong in the Secretariat list.

Central政法 work meeting

2026 central political-legal work meeting report, useful for public language on party leadership, national security, safe China, rule of law, grassroots work, digitization, and cadre building.

PRC Leader / Neil Thomas

Analytic background on the Central Political and Legal Affairs Commission as a domestic-security coordinating body.

Supreme People’s Court English site

English summary of the 2026 Central Conference on Work Relating to Political and Legal Affairs, confirming Chen Wenqing’s role and policy language.

08

Limits & ethics

This page is intentionally non-operational. It avoids surveillance instructions, enforcement procedures, recruitment or informant handling, evasion, coercive tactics, or practical advice for political repression. Its reusable value is critical analysis: source confidence, authority, classification, evidence, proportionality, recordkeeping, remedy, and accountability.

What may be added later

Verified office history, archival citations, dates, appointments, speeches, obituaries, memoir references, or reliable secondary scholarship about 董發 / Dong Fa.

What should not be added

Unverified allegations, tactical political-security procedures, personal data about private people, or instructions that would facilitate coercion or surveillance.

Best use

Use it as a critical reading instrument for CCP security-politics source material: identify the frame, test the evidence, and foreground the accountability questions.