Chinese source (authoritative): ../../skills/structured-element-extraction/SKILL.md
07 Structured Element Checklist
I. Overview Table
| Item |
Content |
| Capability name |
Structured Element Checklist |
| Capability type |
Pre-analysis / Quality gate |
| Core function |
Decompose a legal question into a complete, mutually exclusive, verifiable element checklist |
| Upstream input |
Case facts, legal provisions, user questions, contract text, and other raw materials |
| Downstream output |
Verified structured element checklist for legal reasoning, application of law, risk assessment, etc. |
| Key principles |
Completeness first (prefer over-listing to omission); exhaust then prune; status-label each item |
| Quality standard |
Enter the next stage only after passing the "triple completeness check" |
II. Legal Disclaimer
Important: This skill file is an operational guide for an AI agent and does not constitute legal advice. Extraction of a structured element checklist depends on accurate understanding of the constituent elements of the relevant legal field. In actual legal services, the checklist should be reviewed and confirmed by a licensed legal professional. When outputting an element checklist, the AI agent should clearly label confidence and prompt the user to manually review key elements.
III. Core Concepts
3.1 What Are "Structured Elements"
Structured elements are the result of breaking a legal question into minimal decidable units. Each element should satisfy:
- Atomicity: Cannot be further meaningfully subdivided
- Decidability: Can receive a clear judgment of "satisfied / not satisfied / to be verified"
- Independence: Elements do not logically contain one another (MECE)
- Traceability: Each element can be traced to a specific legal provision or doctrinal basis
3.2 Three Sources of Elements
| Source type |
Explanation |
Example |
| Statutory elements |
Constituent requirements expressly provided in law |
Four elements of tort under Civil Code Art. 1165 |
| Judicial-interpretation elements |
Refinement or supplementation of statutory elements in judicial interpretations |
SPC standards for recognizing "经营场所" (business premises) |
| Doctrinal / practice elements |
Judgment standards formed in prevailing doctrine or adjudicative practice |
Factors for judging "substantial modification" of a contract |
3.3 Element Status Labeling System
Each extracted element must be labeled with one of the following statuses:
| Status |
Symbol |
Meaning |
| Satisfied |
✅ |
Existing materials sufficiently prove the element |
| Not satisfied |
❌ |
Existing materials clearly show the element is not established |
| To be verified |
⚠️ |
Existing materials insufficient to judge; information needed |
| Not applicable |
➖ |
The element need not be examined on these facts |
| Disputed |
🔶 |
Whether the element is satisfied admits different interpretations |
3.4 MECE in Legal Element Extraction
MECE = Mutually Exclusive, Collectively Exhaustive
- Mutually exclusive: No containment or overlap between any two elements at the same level
- Collectively exhaustive: Together, the elements cover all judgment dimensions of the legal question
Typical MECE violations:
- Listing "fault" and "intent" as same-level elements (containment)
- Omitting "causation" (not exhaustive)
- Mixing "questions of fact" and "questions of law" at the same level (inconsistent classification)
IV. Complete Workflow
Phase 1: Identify Problem Type and Fix the Element Framework
Step 1.1 → Identify the type of legal question
├── Contract disputes (formation, validity, performance, breach, termination)
├── Tort liability (general tort, special tort, product liability, etc.)
├── Crime composition (four-element / three-stratum systems)
├── Administrative acts (five elements of legality review)
├── Procedural matters (jurisdiction, limitation, standing)
└── Other types (by specific field)
Step 1.2 → Retrieve the corresponding standard element framework
- Prefer statutory constituent elements
- If statutory elements unclear, refer to judicial interpretations
- If neither is clear, refer to prevailing doctrine
Step 1.3 → Confirm hierarchical structure of the framework
- Level-1 elements: statutory constituent elements (must all be covered)
- Level-2 elements: refinements of level-1 elements
- Level-3 elements: concrete factual judgment points (optional, by complexity)
Phase 2: Extract and Fill Elements Item by Item
Step 2.1 → Against the framework, extract corresponding facts from raw materials
- Extract each element independently; do not skip
- Quote key sentences from raw materials directly
- Mark unextractable elements as "to be verified"
Step 2.2 → Label status for each element (✅/❌/⚠️/➖/🔶)
Step 2.3 → Record evidence / basis source for each element
- Fact elements: which part of which material
- Legal elements: corresponding article numbers
Phase 3: Completeness Check (Triple Check)
First check: Framework completeness
→ Ask: Any level-1 element in the standard framework omitted?
→ Method: Compare extraction result with the standard framework item by item
→ If omitted: Supplement and label status
Second check: Fact coverage
→ Ask: Are there important facts in the raw materials not yet "digested" by any element?
→ Method: Re-read raw materials; mark uncited fact fragments
→ If omitted: Assign to an element, or add a new element if needed
Third check: Logical coherence
→ Ask: Are there logical contradictions among elements?
→ Method: Check logical relations (e.g., consistency of causation and damage elements)
→ If contradiction: Label conflict points and note need for further analysis
Phase 4: Output and Handoff
Step 4.1 → Output structured element checklist per standard template
Step 4.2 → Attach completeness declaration (passed / failed triple check)
Step 4.3 → Label overall confidence
Step 4.4 → List items to be verified (if any)
Step 4.5 → Confirm ready for next stage / need more information before continuing
V. Common Fields and Legal Sources
5.1 Contract Dispute Element Framework
| Level-1 element |
Legal source |
Level-2 elements |
| Proper contractual parties |
Civil Code Art. 143 |
Capacity for civil acts, agency authority, subject qualification |
| Genuine expression of intent |
Civil Code Art. 143 |
No fraud, duress, major misunderstanding, or obvious unfairness |
| Lawful content |
Civil Code Arts. 143, 153 |
No violation of mandatory provisions; no breach of public order and good morals |
| Contract formation |
Civil Code Arts. 471–495 |
Offer, acceptance, meeting of minds, form requirements |
| Contract performance |
Civil Code Arts. 509–534 |
Performing party, content, manner, time, place |
| Breach facts |
Civil Code Art. 577 |
Non-performance, incomplete performance, delayed performance, defective performance |
| Breach remedies |
Civil Code Arts. 577–594 |
Specific performance, remedial measures, damages, liquidated damages |
| Exemptions |
Civil Code Art. 590 etc. |
Force majeure, exemption clauses, counterparty fault |
5.2 General Tort Liability Element Framework
| Level-1 element |
Legal source |
Level-2 elements |
| Injurious act |
Civil Code Art. 1165 |
Act / omission; unlawfulness of conduct |
| Damage |
Civil Code Art. 1165 |
Personal, property, mental harm; certainty of damage |
| Causation |
Civil Code Art. 1165 |
Factual causation (condition theory); legal causation (adequate causation) |
| Subjective fault |
Civil Code Art. 1165 |
Intent / negligence; degree of fault; standard of care |
5.3 Crime Composition Framework (Four-Element System)
| Level-1 element |
Level-2 elements |
| Object of the crime |
Direct object, indirect object, object of the act |
| Objective aspect |
Harmful act, harmful result, causation, time/place/method (for specific crimes) |
| Subject |
Age of criminal responsibility, capacity, special identity |
| Subjective aspect |
Intent (direct/indirect), negligence (carelessness/overconfidence), purpose, motive |
5.4 Administrative-Act Legality Review Framework
| Level-1 element |
Legal source |
Explanation |
| Authority basis |
Administrative Litigation Law Art. 70 |
Whether there is statutory authority |
| Fact-finding |
Administrative Litigation Law Art. 70 |
Whether primary evidence is sufficient |
| Application of law |
Administrative Litigation Law Art. 70 |
Whether laws and regulations are correctly applied |
| Procedural legality |
Administrative Litigation Law Art. 70 |
Whether statutory procedure is followed |
| Reasonable discretion |
Administrative Litigation Law Art. 70 |
Abuse of power or manifest inappropriateness |
5.5 Labor Dispute Element Framework
| Level-1 element |
Legal source |
Level-2 elements |
| Establishment of labor relationship |
MOLSS Fa [2005] No. 12 |
Proper parties; personal, economic, and organizational subordination |
| Facts of employment |
Labor Contract Law Art. 7 |
Actual start date, work content, work location |
| Written contract |
Labor Contract Law Art. 10 |
Whether signed, signing time, term, mandatory clauses |
| Wages and remuneration |
Labor Contract Law Art. 30 |
Wage standard, payment method, cycle, whether below minimum wage |
| Termination |
Labor Contract Law Arts. 36–50 |
Type of termination, grounds, procedure, economic compensation |
VI. Verification and Screening Rules
6.1 Five Verification Rules for Element Extraction
| Rule ID |
Name |
Content |
Consequence of failure |
| V-01 |
Legal-source anchoring |
Each level-1 element must have a clear statutory or doctrinal basis |
May not serve as analysis basis; must reconfirm |
| V-02 |
Atomicity test |
Lowest-level elements cannot be further meaningfully subdivided |
Continue subdividing to atomic level |
| V-03 |
MECE test |
Same-level elements: no overlap, no omission |
Adjust element structure |
| V-04 |
Status labeling |
Each element must have exactly one status label |
Supplement labels before continuing |
| V-05 |
Source tracing |
Each "satisfied" element must cite a fact source |
Downgrade to "to be verified" |
6.2 Priority Rules for Element Screening
When raw materials are insufficient, proceed by priority:
- Must elements: Every statutory constituent element — must be listed even if marked "to be verified"
- Should elements: Elements affecting severity of legal consequences — should be listed
- May elements: Auxiliary but not essential — may be listed
- Exclude elements: Irrelevant to the case — do not list, but briefly record exclusion reasons
VII. Output Format Templates
Template A: Standard Element Checklist
## Structured Element Checklist
**Legal question:** [brief description]
**Question type:** [contract / tort / crime composition / administrative act / other]
**Applicable framework:** [framework name and legal source]
**Extraction date:** [YYYY-MM-DD]
### Element Checklist
| No. | Level | Element name | Status | Fact summary | Source / basis | Notes |
|------|------|----------|------|----------|-----------|------|
| 1 | L1 | [Level-1 element 1] | ✅/❌/⚠️/➖/🔶 | [corresponding facts] | [article] | [notes] |
| 1.1 | L2 | [Level-2 element 1.1] | ✅/❌/⚠️/➖/🔶 | [corresponding facts] | [article] | [notes] |
| ... | ... | ... | ... | ... | ... | ... |
### Completeness Check Results
| Check item | Result | Explanation |
|--------|------|------|
| Framework completeness | ✅ Pass / ❌ Fail | [explanation] |
| Fact coverage | ✅ Pass / ❌ Fail | [explanation] |
| Logical coherence | ✅ Pass / ❌ Fail | [explanation] |
### Items to Be Verified
1. [Element X]: Need to supplement [specific information]
2. [Element Y]: Need to confirm [specific issue]
### Overall confidence: [High/Medium/Low] — [brief reason]
### Conclusion: [May enter next stage / Need more information before continuing]
Template B: Concise Element Checklist (Quick Verification)
## Element Checklist — [brief legal question]
**Framework:** [name] | **Legal source:** [core articles]
- [ ] Element 1: [name] — [status] — [one-sentence note]
- [ ] Element 2: [name] — [status] — [one-sentence note]
- [ ] Element 3: [name] — [status] — [one-sentence note]
- [ ] Element 4: [name] — [status] — [one-sentence note]
**Omission check:** ✅ None / ⚠️ Omissions: [explanation]
**May continue:** ✅ Yes / ❌ No, reason: [explanation]
VIII. Confidence Labeling System
8.1 Single-Element Confidence
| Confidence |
Standard |
Labeling |
| High |
Facts clear + legal source clear + no dispute |
Status ✅ or ❌ |
| Medium |
Facts basically clear but details fuzzy, or legal source admits multiple readings |
Status 🔶 |
| Low |
Facts unclear or legal source unclear |
Status ⚠️ |
8.2 Overall Checklist Confidence
| Overall confidence |
Criteria |
| High |
All level-1 elements ✅ or ❌, no ⚠️, triple check all passed |
| Medium |
1–2 ⚠️ or 🔶 elements that do not affect core judgment; triple check basically passed |
| Low |
3+ ⚠️ elements, or core element is ⚠️, or triple check failed |
8.3 Confidence and Next Actions
| Overall confidence |
Allowed next action |
| High |
Proceed directly to legal reasoning / application of law |
| Medium |
May proceed, but must clearly label uncertainties in the analysis |
| Low |
Must not enter next stage; first supplement information or request user confirmation |
IX. Common Errors and Prevention
9.1 Fatal Error Table
| Error ID |
Name |
Description |
Severity |
Prevention |
| F-01 |
Omitting statutory elements |
Failure to list a statutory constituent element |
⭐⭐⭐⭐⭐ Fatal |
Fix complete statutory framework first; compare item by item |
| F-02 |
Confused element levels |
Listing level-2 elements alongside level-1 |
⭐⭐⭐⭐ Serious |
Strict hierarchy; same level uses same classification standard |
| F-03 |
Skipping check before output |
Delivering without triple completeness check |
⭐⭐⭐⭐⭐ Fatal |
Make check mandatory; results must appear in output |
| F-04 |
Missing status labels |
Elements listed without satisfaction status |
⭐⭐⭐⭐ Serious |
Exactly one status per element |
| F-05 |
Fact–element mismatch |
Assigning a fact to the wrong element |
⭐⭐⭐⭐ Serious |
After extraction, back-check: does this fact prove this element? |
| F-06 |
Forcing ahead on low confidence |
Entering reasoning when overall confidence is "Low" |
⭐⭐⭐⭐⭐ Fatal |
Strictly follow confidence–action table |
9.2 Common Traps
| Trap |
Manifestation |
Correct approach |
| Conclusion instead of elements |
Writing "constitutes tort" without splitting four elements |
Split into each independent element |
| Omitting negative elements |
Focusing only on "establishment," ignoring exemptions/defenses |
Exemptions and defenses are also necessary elements |
| Mixing fact and legal evaluation |
Putting legal conclusions in the fact-summary column |
Fact summary records objective facts only; legal evaluation goes in notes |
| Over-splitting |
Splitting a simple element into a dozen sub-items |
Split to "independently decidable"; do not pursue extreme granularity |
| Rigid frameworks |
Applying one framework to all cases |
Choose framework by question type |
| Ignoring time dimension |
Ignoring element changes from statutory amendments |
Confirm applicable law version; label time nodes |
| Omitting procedural elements |
Focusing only on substantive elements; ignoring limitation, jurisdiction |
List procedural elements as a separate group |
X. Special Scenario Handling
10.1 Intersecting Legal Relationships
Scenario: Same facts involve multiple legal relationships (e.g., concurrent contract breach and tort)
Handling:
- Build an independent element checklist for each legal relationship
- Cross-reference shared fact elements between checklists
- Explicitly state "This case involves N legal relationships; separate checklists established"
- If claim concurrence exists, note the concurrence relationship
10.2 Vague or Blank Law
Scenario: Legal standard for an element is unclear; no direct provision to cite
Handling:
- Label legal source as "prevailing doctrine" or "similar-case adjudicative rules"
- List at least two reference cases or scholarly views
- Mark element confidence as Medium or Low
- Note the specific source of uncertainty
10.3 Severely Insufficient Facts
Scenario: User information extremely limited; many elements cannot be judged
Handling:
- Still list the complete element framework (do not omit for lack of information)
- Mark all undecidable elements as ⚠️
- Generate an "information supplementation request list" by priority
- Overall confidence Low; expressly state next stage must not begin
10.4 Multiple Time Nodes for Applicable Law
Scenario: Facts span before and after a statutory amendment
Handling:
- Fix the time of each fact element
- Fix the effective law version for each time point
- If different versions apply at different times, build separate checklists
- Clearly label the temporal dividing line for applicable law
10.5 Party Dispute Focus Not Fully Aligned with Framework
Scenario: Parties dispute something outside the core elements of the standard framework
Handling:
- Still complete full extraction under the standard framework (no omission)
- Add a "dispute-focus elements" section for issues actually disputed
- Note the relationship between dispute focus and standard elements
XI. Quality Checklist
Before outputting a structured element checklist, the AI agent must complete:
Pre-extraction Checks
Extraction Process Checks
Pre-output Checks
XII. Complete Examples
Example 1: Simple Scenario — General Tort Element Extraction
Raw materials:
On 15 March 2024, while reversing in a shopping-mall parking lot, Zhang San failed to observe behind and knocked down Li Si who was walking through. Li Si was taken to hospital, diagnosed with a right-leg fracture, hospitalized 20 days, medical expenses RMB 32,000. Traffic police issued an accident determination finding Zhang San fully liable. Li Si lost RMB 15,000 in wages during hospitalization.
Structured Element Checklist
Legal question: Zhang San reversed into Li Si; can Li Si require Zhang San to bear tort damages?
Question type: Tort liability (general tort — fault liability)
Applicable framework: Four elements of general tort (Civil Code Art. 1165(1))
Extraction date: 2024-03-20
Element Checklist
| No. |
Level |
Element name |
Status |
Fact summary |
Source / basis |
Notes |
| 1 |
L1 |
Injurious act |
✅ |
Zhang San knocked down Li Si while reversing |
Civil Code Art. 1165 |
Injurious act in form of commission |
| 1.1 |
L2 |
Manner of act |
✅ |
Driving in reverse (commission) |
— |
— |
| 1.2 |
L2 |
Unlawfulness |
✅ |
Failed to observe behind; breached safe-driving duty |
Road Traffic Safety Law Art. 22 |
Police found Zhang San fully liable |
| 2 |
L1 |
Damage |
✅ |
Li Si right-leg fracture; 20 days hospitalization |
Civil Code Art. 1165 |
— |
| 2.1 |
L2 |
Personal injury |
✅ |
Right-leg fracture |
Civil Code Art. 1179 |
— |
| 2.2 |
L2 |
Property damage |
✅ |
Medical RMB 32,000 + lost wages RMB 15,000 |
Civil Code Art. 1179 |
Total RMB 47,000 |
| 2.3 |
L2 |
Mental harm |
⚠️ |
Materials do not mention mental harm |
Civil Code Art. 1183 |
Fracture may support mental damages claim; to verify |
| 3 |
L1 |
Causation |
✅ |
Reverse collision directly caused fracture |
Civil Code Art. 1165 |
Factual causation clear; police determination corroborates |
| 3.1 |
L2 |
Factual causation |
✅ |
Collision was direct cause of fracture |
— |
Condition theory: no collision, no fracture |
| 3.2 |
L2 |
Legal causation |
✅ |
Fracture from reverse collision is ordinarily foreseeable |
— |
Adequate causation established |
| 4 |
L1 |
Subjective fault |
✅ |
Failed to observe behind; negligence |
Civil Code Art. 1165 |
Police full liability |
| 4.1 |
L2 |
Type of fault |
✅ |
Negligence (carelessness) |
— |
Ought to have foreseen but did not |
| 4.2 |
L2 |
Degree of fault |
✅ |
Full fault (police full liability) |
Accident determination |
— |
| 5 |
L1 |
Exemptions |
❌ |
No exemption shown |
Civil Code Arts. 1174–1177 |
— |
| 5.1 |
L2 |
Victim fault |
❌ |
Materials do not show Li Si at fault |
Civil Code Art. 1173 |
Police found Zhang San fully liable |
| 5.2 |
L2 |
Third-party cause |
❌ |
No third-party intervention shown |
Civil Code Art. 1175 |
— |
| 5.3 |
L2 |
Force majeure |
❌ |
None |
Civil Code Art. 180 |
— |
| 5.4 |
L2 |
Self-defense / necessity |
➖ |
Not involved |
— |
— |
| 6 |
L1 |
Procedural elements |
— |
— |
— |
— |
| 6.1 |
L2 |
Limitation |
✅ |
Accident 15 March 2024; within 3-year limitation |
Civil Code Art. 188 |
Expires 14 March 2027 |
| 6.2 |
L2 |
Jurisdiction |
⚠️ |
Materials do not name a court |
Civil Procedure Law Art. 29 |
Court of place of tort or defendant’s domicile |
Completeness Check Results
| Check item |
Result |
Explanation |
| Framework completeness |
✅ Pass |
Four elements + exemptions + procedural elements covered |
| Fact coverage |
✅ Pass |
All facts in raw materials assigned to elements |
| Logical coherence |
✅ Pass |
No logical contradiction among elements |
Items to Be Verified
- Mental harm (element 2.3): Confirm whether Li Si claims mental damages; disability rating from fracture
- Forum (element 6.2): Confirm place of accident and defendant’s domicile for jurisdiction
Overall confidence: High
Core four elements (injurious act, damage, causation, subjective fault) all "satisfied"; facts clear; legal sources clear. Items to verify do not affect the basic judgment that tort liability is established.
Conclusion: ✅ May enter next stage (application of law and liability determination)
Example 2: Complex Scenario — Labor Relationship Confirmation + Unlawful Termination
Raw materials:
Wang joined a tech company on 1 June 2022 as a software engineer, monthly salary RMB 20,000; the company did not sign a written labor contract. Wang worked at the company office during company hours (9:00–18:00), used company computer and workstation, and accepted project-manager assignments and appraisals. Wages paid monthly by bank transfer.
On 10 August 2023, the company orally told Wang "due to business adjustment, no need to come tomorrow," without stating specific termination grounds, without 30 days’ advance notice, and without any economic compensation. Wang asked for a written termination notice; the company refused.
Wang had no disciplinary record; performance appraisals were all "合格" (合格) or above. The company did not pay social insurance for Wang.
On 1 September 2023 Wang applied to the local labor arbitration commission seeking: (1) confirmation of labor relationship; (2) double-wage differential for failure to sign a written contract; (3) compensation for unlawful termination; (4) make-up of social insurance.
Structured Element Checklist
Legal question: Is there a labor relationship between Wang and the tech company? Was termination unlawful? Can Wang’s claims be supported?
Question type: Labor dispute (relationship confirmation + unlawful termination + multiple claims)
Applicable framework: Labor-relationship confirmation elements + legality of labor-contract termination
Extraction date: 2024-03-20
Note: Multiple legal issues; separate element checklists established.
Checklist 1: Labor Relationship Confirmation
Applicable framework: MOLSS Fa [2005] No. 12, Art. 1
| No. |
Level |
Element name |
Status |
Fact summary |
Source / basis |
Notes |
| 1 |
L1 |
Proper parties |
✅ |
— |
MOLSS Fa [2005] No. 12 Art. 1(1) |
— |
| 1.1 |
L2 |
Employer qualification |
✅ |
"A tech company" has employer capacity |
— |
Company form to confirm further (LLC / sole prop., etc.) |
| 1.2 |
L2 |
Worker qualification |
✅ |
Wang natural person, software engineer |
— |
Age not stated; presumed statutory working age |
| 2 |
L1 |
Personal subordination |
✅ |
— |
MOLSS Fa [2005] No. 12 Art. 1(2) |
— |
| 2.1 |
L2 |
Observe rules |
✅ |
Worked company hours (9:00–18:00) |
— |
Fixed hours |
| 2.2 |
L2 |
Accept management |
✅ |
Accepted project-manager assignments and appraisals |
— |
Clear managerial hierarchy |
| 2.3 |
L2 |
Designated workplace |
✅ |
Worked at company office |
— |
— |
| 3 |
L1 |
Economic subordination |
✅ |
— |
MOLSS Fa [2005] No. 12 Art. 1(3) |
— |
| 3.1 |
L2 |
Remuneration |
✅ |
RMB 20,000/month by bank transfer |
— |
Fixed salary, not project settlement |
| 3.2 |
L2 |
Means of production |
✅ |
Company provided computer and workstation |
— |
Tools provided by employer |
| 4 |
L1 |
Organizational subordination |
✅ |
Wang’s work part of company business |
MOLSS Fa [2005] No. 12 Art. 1(3) |
Software engineer is core business role for a tech company |
Checklist 2: Double Wages for Unsigned Written Contract
Applicable framework: Labor Contract Law Arts. 10, 82; Implementing Regulations Arts. 6, 7
| No. |
Level |
Element name |
Status |
Fact summary |
Source / basis |
Notes |
| 1 |
L1 |
Labor relationship established |
✅ |
See Checklist 1 |
— |
Prerequisite confirmed |
| 2 |
L1 |
No written contract |
✅ |
"Company did not sign a written labor contract" |
Labor Contract Law Art. 10 |
— |
| 3 |
L1 |
Beyond statutory signing period |
✅ |
Hired 1 June 2022 to termination 10 Aug 2023; over one month |
Labor Contract Law Art. 82 |
Over one month from start of employment |
| 4 |
L1 |
Double-wage calculation period |
🔶 |
1 July 2022 to 31 May 2023 (11 months) |
Labor Contract Law Arts. 82, 14(3) |
After one year deemed open-ended; double wage max 11 months |
| 5 |
L1 |
Arbitration limitation |
🔶 |
Arbitration filed 1 Sept 2023 |
Labor Dispute Mediation and Arbitration Law Art. 27 |
Whether double-wage claims subject to 1-year arbitration limitation is disputed; July 2022 portion may be time-barred; depend on local adjudicative practice |
| 6 |
L1 |
Fault for non-signing |
⚠️ |
Materials do not say whether company failed to offer or Wang refused |
— |
Usually employer bears signing duty; different if worker refused |
Checklist 3: Unlawful Termination
Applicable framework: Labor Contract Law Arts. 36–43, 48, 87
| No. |
Level |
Element name |
Status |
Fact summary |
Source / basis |
Notes |
| 1 |
L1 |
Fact of termination |
✅ |
10 Aug 2023 oral notice "no need to come tomorrow" |
— |
Unilateral employer termination |
| 2 |
L1 |
Lawfulness of termination grounds |
❌ |
Only "business adjustment"; no specific statutory ground |
Labor Contract Law Arts. 39–41 |
— |
| 2.1 |
L2 |
Fault-based dismissal (Art. 39) |
❌ |
No disciplinary record; performance合格 or above |
Labor Contract Law Art. 39 |
Fits none |
| 2.2 |
L2 |
Non-fault dismissal (Art. 40) |
❌ |
No proof of incompetence / major change of objective circumstances, etc. |
Labor Contract Law Art. 40 |
"Business adjustment" may relate to objective change, but no evidence |
| 2.3 |
L2 |
Economic layoff (Art. 41) |
⚠️ |
Only oral "business adjustment"; no layoff plan, etc. |
Labor Contract Law Art. 41 |
Even if layoff, statutory procedure not followed |
| 3 |
L1 |
Lawfulness of termination procedure |
❌ |
— |
— |
— |
| 3.1 |
L2 |
Advance notice |
❌ |
No 30 days’ written notice or payment in lieu |
Labor Contract Law Art. 40 |
— |
| 3.2 |
L2 |
Written form |
❌ |
Oral notice; refused written termination notice |
Labor Contract Law Art. 50 |
— |
| 3.3 |
L2 |
Union procedure |
⚠️ |
Materials silent on whether union exists / was notified |
Labor Contract Law Art. 43 |
To verify |
| 4 |
L1 |
Economic compensation / damages |
— |
— |
— |
— |
| 4.1 |
L2 |
Length of service |
✅ |
1 June 2022 to 10 Aug 2023 ≈ 1 year 2 months |
Labor Contract Law Art. 47 |
Count as 1.5 months (≥6 months <1 year counts as 1 year) |
| 4.2 |
L2 |
Monthly wage standard |
✅ |
RMB 20,000/month |
Labor Contract Law Art. 47 |
Confirm whether includes overtime, bonuses, etc. |
| 4.3 |
L2 |
Unlawful-termination damages |
✅ |
Twice economic compensation standard |
Labor Contract Law Art. 87 |
2 × 1.5 × 20000 = RMB 60,000 |
| 5 |
L1 |
Prohibited-termination situations |
⚠️ |
Materials silent on medical period, pregnancy, etc. |
Labor Contract Law Art. 42 |
To verify; if present, further aggravates unlawfulness |
Checklist 4: Social Insurance Make-up
| No. |
Level |
Element name |
Status |
Fact summary |
Source / basis |
Notes |
| 1 |
L1 |
Period of labor relationship |
✅ |
1 June 2022 to 10 Aug 2023 |
— |
— |
| 2 |
L1 |
Non-payment of social insurance |
✅ |
"Company did not pay social insurance for Wang" |
Social Insurance Law Art. 58 |
— |
| 3 |
L1 |
Arbitration acceptance scope |
🔶 |
Whether social-insurance make-up is within labor arbitration acceptance |
— |
Most localities treat make-up as administrative; complain to social-insurance authority; some localities’ arbitration may accept |
Completeness Check Results
| Check item |
Result |
Explanation |
| Framework completeness |
✅ Pass |
Four legal issues each have independent complete checklists |
| Fact coverage |
✅ Pass |
All facts assigned; performance records under Checklist 3 item 2.1 |
| Logical coherence |
✅ Pass |
Checklists consistent; Checklist 1 conclusions are prerequisites for 2–4 |
Items to Be Verified (by priority)
- [High] Fault for non-signing (Checklist 2–element 6): Confirm whether company failed to offer or Wang refused
- [High] Union procedure (Checklist 3–element 3.3): Confirm whether company has a union
- [Medium] Prohibited-termination situations (Checklist 3–element 5): Medical period, pregnancy, etc.
- [Medium] Double-wage arbitration limitation (Checklist 2–element 5): Local arbitration practice on double-wage limitation
- [Medium] Social-insurance make-up acceptance (Checklist 4–element 3): Whether local arbitration accepts make-up claims
- [Low] Employer form (Checklist 1–element 1.1): Specific organizational form
- [Low] Monthly wage composition (Checklist 3–element 4.2): Whether RMB 20,000 is all remuneration
Overall confidence: Medium
Reasons: Checklist 1 (relationship confirmation) high confidence; all four elements satisfied. Checklist 3 (unlawful termination) core judgment high confidence (grounds and procedure both unlawful). But double-wage limitation and social-insurance acceptance vary by locality and need confirmation. Overall, core claims (confirm relationship + unlawful-termination damages) have a sufficient analytical basis to enter the next stage, with uncertainties labeled.
Conclusion: ✅ May enter next stage (application of law and claim assessment), but keep the 7 items to be verified labeled, and recommend the user supplement high-priority information.
1---2name: structured-element-extraction-23description: When the AI agent must systematically analyze a legal question, case facts, legal provision, or legal relationship, it must first decompose it into a structured element checklist. Trigger this skill when: - A description of case facts is received and all legal elements must be extracted before analysis - Determining whether a legal relationship is established (e.g., contract formation, tort composition, crime composition) - Comparing similarities and differences among two or more legal facts or provisions - As a pre-quality gate before downstream tasks such as legal reasoning, application of law, or legal advice - The user expressly asks to "list elements," "analyze item by item," or "check for omissions" Core goal: ensure element extraction is complete and without omission, forming a traceable, verifiable structured checklist before allowing the next stage of reasoning. It is the "quality gate" in the legal analysis chain.4---56> **Chinese source (authoritative):** [`../../skills/structured-element-extraction/SKILL.md`](../../skills/structured-element-extraction/SKILL.md)78# 07 Structured Element Checklist910## I. Overview Table1112| Item | Content |13|---|---|14| **Capability name** | Structured Element Checklist |15| **Capability type** | Pre-analysis / Quality gate |16| **Core function** | Decompose a legal question into a complete, mutually exclusive, verifiable element checklist |17| **Upstream input** | Case facts, legal provisions, user questions, contract text, and other raw materials |18| **Downstream output** | Verified structured element checklist for legal reasoning, application of law, risk assessment, etc. |19| **Key principles** | Completeness first (prefer over-listing to omission); exhaust then prune; status-label each item |20| **Quality standard** | Enter the next stage only after passing the "triple completeness check" |2122## II. Legal Disclaimer2324> **Important:** This skill file is an operational guide for an AI agent and does not constitute legal advice. Extraction of a structured element checklist depends on accurate understanding of the constituent elements of the relevant legal field. In actual legal services, the checklist should be reviewed and confirmed by a licensed legal professional. When outputting an element checklist, the AI agent should clearly label confidence and prompt the user to manually review key elements.2526## III. Core Concepts2728### 3.1 What Are "Structured Elements"2930Structured elements are the result of breaking a legal question into **minimal decidable units**. Each element should satisfy:3132- **Atomicity**: Cannot be further meaningfully subdivided33- **Decidability**: Can receive a clear judgment of "satisfied / not satisfied / to be verified"34- **Independence**: Elements do not logically contain one another (MECE)35- **Traceability**: Each element can be traced to a specific legal provision or doctrinal basis3637### 3.2 Three Sources of Elements3839| Source type | Explanation | Example |40|---|---|---|41| **Statutory elements** | Constituent requirements expressly provided in law | Four elements of tort under Civil Code Art. 1165 |42| **Judicial-interpretation elements** | Refinement or supplementation of statutory elements in judicial interpretations | SPC standards for recognizing "经营场所" (business premises) |43| **Doctrinal / practice elements** | Judgment standards formed in prevailing doctrine or adjudicative practice | Factors for judging "substantial modification" of a contract |4445### 3.3 Element Status Labeling System4647Each extracted element must be labeled with one of the following statuses:4849| Status | Symbol | Meaning |50|---|---|---|51| **Satisfied** | ✅ | Existing materials sufficiently prove the element |52| **Not satisfied** | ❌ | Existing materials clearly show the element is not established |53| **To be verified** | ⚠️ | Existing materials insufficient to judge; information needed |54| **Not applicable** | ➖ | The element need not be examined on these facts |55| **Disputed** | 🔶 | Whether the element is satisfied admits different interpretations |5657### 3.4 MECE in Legal Element Extraction5859**MECE = Mutually Exclusive, Collectively Exhaustive**6061- **Mutually exclusive**: No containment or overlap between any two elements at the same level62- **Collectively exhaustive**: Together, the elements cover all judgment dimensions of the legal question6364Typical MECE violations:65- Listing "fault" and "intent" as same-level elements (containment)66- Omitting "causation" (not exhaustive)67- Mixing "questions of fact" and "questions of law" at the same level (inconsistent classification)6869## IV. Complete Workflow7071### Phase 1: Identify Problem Type and Fix the Element Framework7273```74Step 1.1 → Identify the type of legal question75 ├── Contract disputes (formation, validity, performance, breach, termination)76 ├── Tort liability (general tort, special tort, product liability, etc.)77 ├── Crime composition (four-element / three-stratum systems)78 ├── Administrative acts (five elements of legality review)79 ├── Procedural matters (jurisdiction, limitation, standing)80 └── Other types (by specific field)8182Step 1.2 → Retrieve the corresponding standard element framework83 - Prefer statutory constituent elements84 - If statutory elements unclear, refer to judicial interpretations85 - If neither is clear, refer to prevailing doctrine8687Step 1.3 → Confirm hierarchical structure of the framework88 - Level-1 elements: statutory constituent elements (must all be covered)89 - Level-2 elements: refinements of level-1 elements90 - Level-3 elements: concrete factual judgment points (optional, by complexity)91```9293### Phase 2: Extract and Fill Elements Item by Item9495```96Step 2.1 → Against the framework, extract corresponding facts from raw materials97 - Extract each element independently; do not skip98 - Quote key sentences from raw materials directly99 - Mark unextractable elements as "to be verified"100101Step 2.2 → Label status for each element (✅/❌/⚠️/➖/🔶)102103Step 2.3 → Record evidence / basis source for each element104 - Fact elements: which part of which material105 - Legal elements: corresponding article numbers106```107108### Phase 3: Completeness Check (Triple Check)109110```111First check: Framework completeness112 → Ask: Any level-1 element in the standard framework omitted?113 → Method: Compare extraction result with the standard framework item by item114 → If omitted: Supplement and label status115116Second check: Fact coverage117 → Ask: Are there important facts in the raw materials not yet "digested" by any element?118 → Method: Re-read raw materials; mark uncited fact fragments119 → If omitted: Assign to an element, or add a new element if needed120121Third check: Logical coherence122 → Ask: Are there logical contradictions among elements?123 → Method: Check logical relations (e.g., consistency of causation and damage elements)124 → If contradiction: Label conflict points and note need for further analysis125```126127### Phase 4: Output and Handoff128129```130Step 4.1 → Output structured element checklist per standard template131Step 4.2 → Attach completeness declaration (passed / failed triple check)132Step 4.3 → Label overall confidence133Step 4.4 → List items to be verified (if any)134Step 4.5 → Confirm ready for next stage / need more information before continuing135```136137## V. Common Fields and Legal Sources138139### 5.1 Contract Dispute Element Framework140141| Level-1 element | Legal source | Level-2 elements |142|---|---|---|143| Proper contractual parties | Civil Code Art. 143 | Capacity for civil acts, agency authority, subject qualification |144| Genuine expression of intent | Civil Code Art. 143 | No fraud, duress, major misunderstanding, or obvious unfairness |145| Lawful content | Civil Code Arts. 143, 153 | No violation of mandatory provisions; no breach of public order and good morals |146| Contract formation | Civil Code Arts. 471–495 | Offer, acceptance, meeting of minds, form requirements |147| Contract performance | Civil Code Arts. 509–534 | Performing party, content, manner, time, place |148| Breach facts | Civil Code Art. 577 | Non-performance, incomplete performance, delayed performance, defective performance |149| Breach remedies | Civil Code Arts. 577–594 | Specific performance, remedial measures, damages, liquidated damages |150| Exemptions | Civil Code Art. 590 etc. | Force majeure, exemption clauses, counterparty fault |151152### 5.2 General Tort Liability Element Framework153154| Level-1 element | Legal source | Level-2 elements |155|---|---|---|156| Injurious act | Civil Code Art. 1165 | Act / omission; unlawfulness of conduct |157| Damage | Civil Code Art. 1165 | Personal, property, mental harm; certainty of damage |158| Causation | Civil Code Art. 1165 | Factual causation (condition theory); legal causation (adequate causation) |159| Subjective fault | Civil Code Art. 1165 | Intent / negligence; degree of fault; standard of care |160161### 5.3 Crime Composition Framework (Four-Element System)162163| Level-1 element | Level-2 elements |164|---|---|165| Object of the crime | Direct object, indirect object, object of the act |166| Objective aspect | Harmful act, harmful result, causation, time/place/method (for specific crimes) |167| Subject | Age of criminal responsibility, capacity, special identity |168| Subjective aspect | Intent (direct/indirect), negligence (carelessness/overconfidence), purpose, motive |169170### 5.4 Administrative-Act Legality Review Framework171172| Level-1 element | Legal source | Explanation |173|---|---|---|174| Authority basis | Administrative Litigation Law Art. 70 | Whether there is statutory authority |175| Fact-finding | Administrative Litigation Law Art. 70 | Whether primary evidence is sufficient |176| Application of law | Administrative Litigation Law Art. 70 | Whether laws and regulations are correctly applied |177| Procedural legality | Administrative Litigation Law Art. 70 | Whether statutory procedure is followed |178| Reasonable discretion | Administrative Litigation Law Art. 70 | Abuse of power or manifest inappropriateness |179180### 5.5 Labor Dispute Element Framework181182| Level-1 element | Legal source | Level-2 elements |183|---|---|---|184| Establishment of labor relationship | MOLSS Fa [2005] No. 12 | Proper parties; personal, economic, and organizational subordination |185| Facts of employment | Labor Contract Law Art. 7 | Actual start date, work content, work location |186| Written contract | Labor Contract Law Art. 10 | Whether signed, signing time, term, mandatory clauses |187| Wages and remuneration | Labor Contract Law Art. 30 | Wage standard, payment method, cycle, whether below minimum wage |188| Termination | Labor Contract Law Arts. 36–50 | Type of termination, grounds, procedure, economic compensation |189190## VI. Verification and Screening Rules191192### 6.1 Five Verification Rules for Element Extraction193194| Rule ID | Name | Content | Consequence of failure |195|---|---|---|---|196| V-01 | Legal-source anchoring | Each level-1 element must have a clear statutory or doctrinal basis | May not serve as analysis basis; must reconfirm |197| V-02 | Atomicity test | Lowest-level elements cannot be further meaningfully subdivided | Continue subdividing to atomic level |198| V-03 | MECE test | Same-level elements: no overlap, no omission | Adjust element structure |199| V-04 | Status labeling | Each element must have exactly one status label | Supplement labels before continuing |200| V-05 | Source tracing | Each "satisfied" element must cite a fact source | Downgrade to "to be verified" |201202### 6.2 Priority Rules for Element Screening203204When raw materials are insufficient, proceed by priority:2052061. **Must elements**: Every statutory constituent element — must be listed even if marked "to be verified"2072. **Should elements**: Elements affecting severity of legal consequences — should be listed2083. **May elements**: Auxiliary but not essential — may be listed2094. **Exclude elements**: Irrelevant to the case — do not list, but briefly record exclusion reasons210211## VII. Output Format Templates212213### Template A: Standard Element Checklist214215```markdown216## Structured Element Checklist217218**Legal question:** [brief description]219**Question type:** [contract / tort / crime composition / administrative act / other]220**Applicable framework:** [framework name and legal source]221**Extraction date:** [YYYY-MM-DD]222223### Element Checklist224225| No. | Level | Element name | Status | Fact summary | Source / basis | Notes |226|------|------|----------|------|----------|-----------|------|227| 1 | L1 | [Level-1 element 1] | ✅/❌/⚠️/➖/🔶 | [corresponding facts] | [article] | [notes] |228| 1.1 | L2 | [Level-2 element 1.1] | ✅/❌/⚠️/➖/🔶 | [corresponding facts] | [article] | [notes] |229| ... | ... | ... | ... | ... | ... | ... |230231### Completeness Check Results232233| Check item | Result | Explanation |234|--------|------|------|235| Framework completeness | ✅ Pass / ❌ Fail | [explanation] |236| Fact coverage | ✅ Pass / ❌ Fail | [explanation] |237| Logical coherence | ✅ Pass / ❌ Fail | [explanation] |238239### Items to Be Verified2402411. [Element X]: Need to supplement [specific information]2422. [Element Y]: Need to confirm [specific issue]243244### Overall confidence: [High/Medium/Low] — [brief reason]245246### Conclusion: [May enter next stage / Need more information before continuing]247```248249### Template B: Concise Element Checklist (Quick Verification)250251```markdown252## Element Checklist — [brief legal question]253254**Framework:** [name] | **Legal source:** [core articles]255256- [ ] Element 1: [name] — [status] — [one-sentence note]257- [ ] Element 2: [name] — [status] — [one-sentence note]258- [ ] Element 3: [name] — [status] — [one-sentence note]259- [ ] Element 4: [name] — [status] — [one-sentence note]260261**Omission check:** ✅ None / ⚠️ Omissions: [explanation]262**May continue:** ✅ Yes / ❌ No, reason: [explanation]263```264265## VIII. Confidence Labeling System266267### 8.1 Single-Element Confidence268269| Confidence | Standard | Labeling |270|---|---|---|271| **High** | Facts clear + legal source clear + no dispute | Status ✅ or ❌ |272| **Medium** | Facts basically clear but details fuzzy, or legal source admits multiple readings | Status 🔶 |273| **Low** | Facts unclear or legal source unclear | Status ⚠️ |274275### 8.2 Overall Checklist Confidence276277| Overall confidence | Criteria |278|---|---|279| **High** | All level-1 elements ✅ or ❌, no ⚠️, triple check all passed |280| **Medium** | 1–2 ⚠️ or 🔶 elements that do not affect core judgment; triple check basically passed |281| **Low** | 3+ ⚠️ elements, or core element is ⚠️, or triple check failed |282283### 8.3 Confidence and Next Actions284285| Overall confidence | Allowed next action |286|---|---|287| **High** | Proceed directly to legal reasoning / application of law |288| **Medium** | May proceed, but must clearly label uncertainties in the analysis |289| **Low** | **Must not enter next stage**; first supplement information or request user confirmation |290291## IX. Common Errors and Prevention292293### 9.1 Fatal Error Table294295| Error ID | Name | Description | Severity | Prevention |296|---|---|---|---|---|297| F-01 | **Omitting statutory elements** | Failure to list a statutory constituent element | ⭐⭐⭐⭐⭐ Fatal | Fix complete statutory framework first; compare item by item |298| F-02 | **Confused element levels** | Listing level-2 elements alongside level-1 | ⭐⭐⭐⭐ Serious | Strict hierarchy; same level uses same classification standard |299| F-03 | **Skipping check before output** | Delivering without triple completeness check | ⭐⭐⭐⭐⭐ Fatal | Make check mandatory; results must appear in output |300| F-04 | **Missing status labels** | Elements listed without satisfaction status | ⭐⭐⭐⭐ Serious | Exactly one status per element |301| F-05 | **Fact–element mismatch** | Assigning a fact to the wrong element | ⭐⭐⭐⭐ Serious | After extraction, back-check: does this fact prove this element? |302| F-06 | **Forcing ahead on low confidence** | Entering reasoning when overall confidence is "Low" | ⭐⭐⭐⭐⭐ Fatal | Strictly follow confidence–action table |303304### 9.2 Common Traps305306| Trap | Manifestation | Correct approach |307|---|---|---|308| **Conclusion instead of elements** | Writing "constitutes tort" without splitting four elements | Split into each independent element |309| **Omitting negative elements** | Focusing only on "establishment," ignoring exemptions/defenses | Exemptions and defenses are also necessary elements |310| **Mixing fact and legal evaluation** | Putting legal conclusions in the fact-summary column | Fact summary records objective facts only; legal evaluation goes in notes |311| **Over-splitting** | Splitting a simple element into a dozen sub-items | Split to "independently decidable"; do not pursue extreme granularity |312| **Rigid frameworks** | Applying one framework to all cases | Choose framework by question type |313| **Ignoring time dimension** | Ignoring element changes from statutory amendments | Confirm applicable law version; label time nodes |314| **Omitting procedural elements** | Focusing only on substantive elements; ignoring limitation, jurisdiction | List procedural elements as a separate group |315316## X. Special Scenario Handling317318### 10.1 Intersecting Legal Relationships319320**Scenario:** Same facts involve multiple legal relationships (e.g., concurrent contract breach and tort)321322**Handling:**3231. Build an independent element checklist for each legal relationship3242. Cross-reference shared fact elements between checklists3253. Explicitly state "This case involves N legal relationships; separate checklists established"3264. If claim concurrence exists, note the concurrence relationship327328### 10.2 Vague or Blank Law329330**Scenario:** Legal standard for an element is unclear; no direct provision to cite331332**Handling:**3331. Label legal source as "prevailing doctrine" or "similar-case adjudicative rules"3342. List at least two reference cases or scholarly views3353. Mark element confidence as Medium or Low3364. Note the specific source of uncertainty337338### 10.3 Severely Insufficient Facts339340**Scenario:** User information extremely limited; many elements cannot be judged341342**Handling:**3431. Still list the complete element framework (do not omit for lack of information)3442. Mark all undecidable elements as ⚠️3453. Generate an "information supplementation request list" by priority3464. Overall confidence Low; expressly state next stage must not begin347348### 10.4 Multiple Time Nodes for Applicable Law349350**Scenario:** Facts span before and after a statutory amendment351352**Handling:**3531. Fix the time of each fact element3542. Fix the effective law version for each time point3553. If different versions apply at different times, build separate checklists3564. Clearly label the temporal dividing line for applicable law357358### 10.5 Party Dispute Focus Not Fully Aligned with Framework359360**Scenario:** Parties dispute something outside the core elements of the standard framework361362**Handling:**3631. Still complete full extraction under the standard framework (no omission)3642. Add a "dispute-focus elements" section for issues actually disputed3653. Note the relationship between dispute focus and standard elements366367## XI. Quality Checklist368369Before outputting a structured element checklist, the AI agent must complete:370371### Pre-extraction Checks372373- [ ] Legal question type clearly identified374- [ ] Correct element framework selected375- [ ] Applicable law version (time node) confirmed376- [ ] All raw materials read at least once377378### Extraction Process Checks379380- [ ] Every level-1 element listed (no omission)381- [ ] Every element status-labeled (✅/❌/⚠️/➖/🔶)382- [ ] Every "satisfied" element has fact summary and source citation383- [ ] Same-level elements have no overlap (MECE–exclusive)384- [ ] All level-1 elements together cover all judgment dimensions (MECE–exhaustive)385- [ ] Exemptions / defenses and other negative elements considered386- [ ] Procedural elements considered (limitation, jurisdiction, etc., if applicable)387388### Pre-output Checks389390- [ ] Triple completeness check executed and results recorded391- [ ] Overall confidence labeled392- [ ] Items to be verified listed (if any)393- [ ] Explicitly labeled "may enter next stage" or "need more information"394- [ ] Output format matches standard template395- [ ] Fact summaries do not mix in legal conclusions396397## XII. Complete Examples398399### Example 1: Simple Scenario — General Tort Element Extraction400401**Raw materials:**402403> On 15 March 2024, while reversing in a shopping-mall parking lot, Zhang San failed to observe behind and knocked down Li Si who was walking through. Li Si was taken to hospital, diagnosed with a right-leg fracture, hospitalized 20 days, medical expenses RMB 32,000. Traffic police issued an accident determination finding Zhang San fully liable. Li Si lost RMB 15,000 in wages during hospitalization.404405---406407## Structured Element Checklist408409**Legal question:** Zhang San reversed into Li Si; can Li Si require Zhang San to bear tort damages?410**Question type:** Tort liability (general tort — fault liability)411**Applicable framework:** Four elements of general tort (Civil Code Art. 1165(1))412**Extraction date:** 2024-03-20413414### Element Checklist415416| No. | Level | Element name | Status | Fact summary | Source / basis | Notes |417|------|------|----------|------|----------|-----------|------|418| 1 | L1 | Injurious act | ✅ | Zhang San knocked down Li Si while reversing | Civil Code Art. 1165 | Injurious act in form of commission |419| 1.1 | L2 | Manner of act | ✅ | Driving in reverse (commission) | — | — |420| 1.2 | L2 | Unlawfulness | ✅ | Failed to observe behind; breached safe-driving duty | Road Traffic Safety Law Art. 22 | Police found Zhang San fully liable |421| 2 | L1 | Damage | ✅ | Li Si right-leg fracture; 20 days hospitalization | Civil Code Art. 1165 | — |422| 2.1 | L2 | Personal injury | ✅ | Right-leg fracture | Civil Code Art. 1179 | — |423| 2.2 | L2 | Property damage | ✅ | Medical RMB 32,000 + lost wages RMB 15,000 | Civil Code Art. 1179 | Total RMB 47,000 |424| 2.3 | L2 | Mental harm | ⚠️ | Materials do not mention mental harm | Civil Code Art. 1183 | Fracture may support mental damages claim; to verify |425| 3 | L1 | Causation | ✅ | Reverse collision directly caused fracture | Civil Code Art. 1165 | Factual causation clear; police determination corroborates |426| 3.1 | L2 | Factual causation | ✅ | Collision was direct cause of fracture | — | Condition theory: no collision, no fracture |427| 3.2 | L2 | Legal causation | ✅ | Fracture from reverse collision is ordinarily foreseeable | — | Adequate causation established |428| 4 | L1 | Subjective fault | ✅ | Failed to observe behind; negligence | Civil Code Art. 1165 | Police full liability |429| 4.1 | L2 | Type of fault | ✅ | Negligence (carelessness) | — | Ought to have foreseen but did not |430| 4.2 | L2 | Degree of fault | ✅ | Full fault (police full liability) | Accident determination | — |431| 5 | L1 | Exemptions | ❌ | No exemption shown | Civil Code Arts. 1174–1177 | — |432| 5.1 | L2 | Victim fault | ❌ | Materials do not show Li Si at fault | Civil Code Art. 1173 | Police found Zhang San fully liable |433| 5.2 | L2 | Third-party cause | ❌ | No third-party intervention shown | Civil Code Art. 1175 | — |434| 5.3 | L2 | Force majeure | ❌ | None | Civil Code Art. 180 | — |435| 5.4 | L2 | Self-defense / necessity | ➖ | Not involved | — | — |436| 6 | L1 | Procedural elements | — | — | — | — |437| 6.1 | L2 | Limitation | ✅ | Accident 15 March 2024; within 3-year limitation | Civil Code Art. 188 | Expires 14 March 2027 |438| 6.2 | L2 | Jurisdiction | ⚠️ | Materials do not name a court | Civil Procedure Law Art. 29 | Court of place of tort or defendant’s domicile |439440### Completeness Check Results441442| Check item | Result | Explanation |443|--------|------|------|444| Framework completeness | ✅ Pass | Four elements + exemptions + procedural elements covered |445| Fact coverage | ✅ Pass | All facts in raw materials assigned to elements |446| Logical coherence | ✅ Pass | No logical contradiction among elements |447448### Items to Be Verified4494501. **Mental harm (element 2.3):** Confirm whether Li Si claims mental damages; disability rating from fracture4512. **Forum (element 6.2):** Confirm place of accident and defendant’s domicile for jurisdiction452453### Overall confidence: High454455Core four elements (injurious act, damage, causation, subjective fault) all "satisfied"; facts clear; legal sources clear. Items to verify do not affect the basic judgment that tort liability is established.456457### Conclusion: ✅ May enter next stage (application of law and liability determination)458459---460461### Example 2: Complex Scenario — Labor Relationship Confirmation + Unlawful Termination462463**Raw materials:**464465> Wang joined a tech company on 1 June 2022 as a software engineer, monthly salary RMB 20,000; the company did not sign a written labor contract. Wang worked at the company office during company hours (9:00–18:00), used company computer and workstation, and accepted project-manager assignments and appraisals. Wages paid monthly by bank transfer.466>467> On 10 August 2023, the company orally told Wang "due to business adjustment, no need to come tomorrow," without stating specific termination grounds, without 30 days’ advance notice, and without any economic compensation. Wang asked for a written termination notice; the company refused.468>469> Wang had no disciplinary record; performance appraisals were all "合格" (合格) or above. The company did not pay social insurance for Wang.470>471> On 1 September 2023 Wang applied to the local labor arbitration commission seeking: (1) confirmation of labor relationship; (2) double-wage differential for failure to sign a written contract; (3) compensation for unlawful termination; (4) make-up of social insurance.472473---474475## Structured Element Checklist476477**Legal question:** Is there a labor relationship between Wang and the tech company? Was termination unlawful? Can Wang’s claims be supported?478**Question type:** Labor dispute (relationship confirmation + unlawful termination + multiple claims)479**Applicable framework:** Labor-relationship confirmation elements + legality of labor-contract termination480**Extraction date:** 2024-03-20481482> **Note:** Multiple legal issues; separate element checklists established.483484---485486### Checklist 1: Labor Relationship Confirmation487488**Applicable framework:** MOLSS Fa [2005] No. 12, Art. 1489490| No. | Level | Element name | Status | Fact summary | Source / basis | Notes |491|------|------|----------|------|----------|-----------|------|492| 1 | L1 | Proper parties | ✅ | — | MOLSS Fa [2005] No. 12 Art. 1(1) | — |493| 1.1 | L2 | Employer qualification | ✅ | "A tech company" has employer capacity | — | Company form to confirm further (LLC / sole prop., etc.) |494| 1.2 | L2 | Worker qualification | ✅ | Wang natural person, software engineer | — | Age not stated; presumed statutory working age |495| 2 | L1 | Personal subordination | ✅ | — | MOLSS Fa [2005] No. 12 Art. 1(2) | — |496| 2.1 | L2 | Observe rules | ✅ | Worked company hours (9:00–18:00) | — | Fixed hours |497| 2.2 | L2 | Accept management | ✅ | Accepted project-manager assignments and appraisals | — | Clear managerial hierarchy |498| 2.3 | L2 | Designated workplace | ✅ | Worked at company office | — | — |499| 3 | L1 | Economic subordination | ✅ | — | MOLSS Fa [2005] No. 12 Art. 1(3) | — |500| 3.1 | L2 | Remuneration | ✅ | RMB 20,000/month by bank transfer | — | Fixed salary, not project settlement |501| 3.2 | L2 | Means of production | ✅ | Company provided computer and workstation | — | Tools provided by employer |502| 4 | L1 | Organizational subordination | ✅ | Wang’s work part of company business | MOLSS Fa [2005] No. 12 Art. 1(3) | Software engineer is core business role for a tech company |503504---505506### Checklist 2: Double Wages for Unsigned Written Contract507508**Applicable framework:** Labor Contract Law Arts. 10, 82; Implementing Regulations Arts. 6, 7509510| No. | Level | Element name | Status | Fact summary | Source / basis | Notes |511|------|------|----------|------|----------|-----------|------|512| 1 | L1 | Labor relationship established | ✅ | See Checklist 1 | — | Prerequisite confirmed |513| 2 | L1 | No written contract | ✅ | "Company did not sign a written labor contract" | Labor Contract Law Art. 10 | — |514| 3 | L1 | Beyond statutory signing period | ✅ | Hired 1 June 2022 to termination 10 Aug 2023; over one month | Labor Contract Law Art. 82 | Over one month from start of employment |515| 4 | L1 | Double-wage calculation period | 🔶 | 1 July 2022 to 31 May 2023 (11 months) | Labor Contract Law Arts. 82, 14(3) | After one year deemed open-ended; double wage max 11 months |516| 5 | L1 | Arbitration limitation | 🔶 | Arbitration filed 1 Sept 2023 | Labor Dispute Mediation and Arbitration Law Art. 27 | Whether double-wage claims subject to 1-year arbitration limitation is disputed; July 2022 portion may be time-barred; depend on local adjudicative practice |517| 6 | L1 | Fault for non-signing | ⚠️ | Materials do not say whether company failed to offer or Wang refused | — | Usually employer bears signing duty; different if worker refused |518519---520521### Checklist 3: Unlawful Termination522523**Applicable framework:** Labor Contract Law Arts. 36–43, 48, 87524525| No. | Level | Element name | Status | Fact summary | Source / basis | Notes |526|------|------|----------|------|----------|-----------|------|527| 1 | L1 | Fact of termination | ✅ | 10 Aug 2023 oral notice "no need to come tomorrow" | — | Unilateral employer termination |528| 2 | L1 | Lawfulness of termination grounds | ❌ | Only "business adjustment"; no specific statutory ground | Labor Contract Law Arts. 39–41 | — |529| 2.1 | L2 | Fault-based dismissal (Art. 39) | ❌ | No disciplinary record; performance合格 or above | Labor Contract Law Art. 39 | Fits none |530| 2.2 | L2 | Non-fault dismissal (Art. 40) | ❌ | No proof of incompetence / major change of objective circumstances, etc. | Labor Contract Law Art. 40 | "Business adjustment" may relate to objective change, but no evidence |531| 2.3 | L2 | Economic layoff (Art. 41) | ⚠️ | Only oral "business adjustment"; no layoff plan, etc. | Labor Contract Law Art. 41 | Even if layoff, statutory procedure not followed |532| 3 | L1 | Lawfulness of termination procedure | ❌ | — | — | — |533| 3.1 | L2 | Advance notice | ❌ | No 30 days’ written notice or payment in lieu | Labor Contract Law Art. 40 | — |534| 3.2 | L2 | Written form | ❌ | Oral notice; refused written termination notice | Labor Contract Law Art. 50 | — |535| 3.3 | L2 | Union procedure | ⚠️ | Materials silent on whether union exists / was notified | Labor Contract Law Art. 43 | To verify |536| 4 | L1 | Economic compensation / damages | — | — | — | — |537| 4.1 | L2 | Length of service | ✅ | 1 June 2022 to 10 Aug 2023 ≈ 1 year 2 months | Labor Contract Law Art. 47 | Count as 1.5 months (≥6 months <1 year counts as 1 year) |538| 4.2 | L2 | Monthly wage standard | ✅ | RMB 20,000/month | Labor Contract Law Art. 47 | Confirm whether includes overtime, bonuses, etc. |539| 4.3 | L2 | Unlawful-termination damages | ✅ | Twice economic compensation standard | Labor Contract Law Art. 87 | 2 × 1.5 × 20000 = RMB 60,000 |540| 5 | L1 | Prohibited-termination situations | ⚠️ | Materials silent on medical period, pregnancy, etc. | Labor Contract Law Art. 42 | To verify; if present, further aggravates unlawfulness |541542---543544### Checklist 4: Social Insurance Make-up545546| No. | Level | Element name | Status | Fact summary | Source / basis | Notes |547|------|------|----------|------|----------|-----------|------|548| 1 | L1 | Period of labor relationship | ✅ | 1 June 2022 to 10 Aug 2023 | — | — |549| 2 | L1 | Non-payment of social insurance | ✅ | "Company did not pay social insurance for Wang" | Social Insurance Law Art. 58 | — |550| 3 | L1 | Arbitration acceptance scope | 🔶 | Whether social-insurance make-up is within labor arbitration acceptance | — | Most localities treat make-up as administrative; complain to social-insurance authority; some localities’ arbitration may accept |551552---553554### Completeness Check Results555556| Check item | Result | Explanation |557|--------|------|------|558| Framework completeness | ✅ Pass | Four legal issues each have independent complete checklists |559| Fact coverage | ✅ Pass | All facts assigned; performance records under Checklist 3 item 2.1 |560| Logical coherence | ✅ Pass | Checklists consistent; Checklist 1 conclusions are prerequisites for 2–4 |561562### Items to Be Verified (by priority)5635641. **[High] Fault for non-signing (Checklist 2–element 6):** Confirm whether company failed to offer or Wang refused5652. **[High] Union procedure (Checklist 3–element 3.3):** Confirm whether company has a union5663. **[Medium] Prohibited-termination situations (Checklist 3–element 5):** Medical period, pregnancy, etc.5674. **[Medium] Double-wage arbitration limitation (Checklist 2–element 5):** Local arbitration practice on double-wage limitation5685. **[Medium] Social-insurance make-up acceptance (Checklist 4–element 3):** Whether local arbitration accepts make-up claims5696. **[Low] Employer form (Checklist 1–element 1.1):** Specific organizational form5707. **[Low] Monthly wage composition (Checklist 3–element 4.2):** Whether RMB 20,000 is all remuneration571572### Overall confidence: Medium573574**Reasons:** Checklist 1 (relationship confirmation) high confidence; all four elements satisfied. Checklist 3 (unlawful termination) core judgment high confidence (grounds and procedure both unlawful). But double-wage limitation and social-insurance acceptance vary by locality and need confirmation. Overall, core claims (confirm relationship + unlawful-termination damages) have a sufficient analytical basis to enter the next stage, with uncertainties labeled.575576### Conclusion: ✅ May enter next stage (application of law and claim assessment), but keep the 7 items to be verified labeled, and recommend the user supplement high-priority information.
thuyran