Step 1: Contextual Framework Pass (Facts)
Extract roles, states, and resources from the facts section
Pipeline Steps
Overview Step 1: Contextual Framework Step 2: Normative Requirements Step 3: Temporal Dynamics Step 4: Whole-Case Synthesis
Generate Scenario (Coming Soon)
Post-Public Employment - City Engineer Transitioning to Consultant
Step 1 of 3
Facts Section
Section Content:
Facts: Engineer D, a licensed professional engineer, works as the City Engineer in a mid-sized municipality that has been experiencing rapid growth along with rapid infrastructure growth. Engineer D has been one of the City's main points of contact for AE firms and contractors in the area, both with respect to contract negotiation and award (consultant and construction) and senior-level review of major project issues that arise from time to time. Engineer D announces plans to step down as the City Engineer and indicates that they accepted a position at an unnamed engineering firm in the City. Of significance is that the City does not include “revolving door” provisions in employment contracts for its senior-level employees. Shortly after Engineer D's announcement, Firm AE&R announces Engineer D as a newly hired associate. AE&R completed many projects for the City during Engineer D's tenure as City Engineer, and the firm plans to continue submitting proposals and performing consulting work for the City.
Roles Extraction
LLM Prompt
DUAL ROLE EXTRACTION - Professional Roles Analysis
EXISTING ROLE CLASSES IN ONTOLOGY:
- Employer Relationship Role: Organizational relationship balancing loyalty and independence
- Engineer Role: A professional role involving engineering practice and responsibilities
- Participant Role: A role of an involved party or stakeholder that does not itself establish professional obligations (
- Professional Peer Role: Collegial relationship with mentoring and review obligations
- Professional Role: A role within a profession that entails recognized ends/goals of practice (e.g., safeguarding public
- ProfessionalRole: Ontology class for Role
- Provider-Client Role: Service delivery relationship with duties of competence and care
- Public Responsibility Role: Societal obligation that can override other professional duties
- Role: A role that can be realized by processes involving professional duties and ethical obligations. This
- Stakeholder Role: A participant role borne by stakeholders such as Clients, Employers, and the Public. Typically not t
=== TASK ===
From the following case text (facts section), extract information at TWO levels:
LEVEL 1 - NEW ROLE CLASSES: Identify professional roles that appear to be NEW types not covered by existing classes above. Look for:
- Specialized professional functions
- Emerging role types in engineering/technology
- Domain-specific professional positions
- Roles with unique qualifications or responsibilities
For each NEW role class, provide:
- label: Clear professional role name
- definition: Detailed description of role function and scope
- distinguishing_features: What makes this role unique/different
- professional_scope: Areas of responsibility and authority
- typical_qualifications: Required education, licensing, experience
- generated_obligations: What specific duties does this role create?
- associated_virtues: What virtues/qualities are expected (integrity, competence, etc.)?
- relationship_type: Provider-Client, Professional Peer, Employer, Public Responsibility
- domain_context: Engineering/Medical/Legal/etc.
- examples_from_case: How this role appears in the case text
LEVEL 2 - ROLE INDIVIDUALS: Identify specific people mentioned who fulfill professional roles. For each person:
- name: EXACT name or identifier as it appears in the text (e.g., "Engineer A", "Client B", "Dr. Smith")
- role_classification: Which role class they fulfill (use existing classes when possible, or new class label if discovered)
- attributes: Specific qualifications, experience, titles, licenses mentioned in the text
- relationships: Employment, reporting, collaboration relationships explicitly stated
- Each relationship should specify: type (employs, reports_to, collaborates_with, serves_client, etc.) and target (person/org name)
- active_obligations: What specific duties is this person fulfilling in the case?
- ethical_tensions: Any conflicts between role obligations and personal/other obligations?
- case_involvement: How they participate in this case
IMPORTANT: Use ONLY the actual names/identifiers found in the case text. DO NOT create realistic names or make up details not explicitly stated.
CASE TEXT:
Facts:
Engineer D, a licensed professional engineer, works as the City Engineer in a mid-sized municipality that has been experiencing rapid growth along with rapid infrastructure growth.
Engineer D has been one of the City's main points of contact for AE firms and contractors in the area, both with respect to contract negotiation and award (consultant and construction) and senior-level review of major project issues that arise from time to time.
Engineer D announces plans to step down as the City Engineer and indicates that they accepted a position at an unnamed engineering firm in the City.
Of significance is that the City does not include “revolving door” provisions in employment contracts for its senior-level employees.
Shortly after Engineer D's announcement, Firm AE&R announces Engineer D as a newly hired associate.
AE&R completed many projects for the City during Engineer D's tenure as City Engineer, and the firm plans to continue submitting proposals and performing consulting work for the City.
Respond with valid JSON in this format:
{
"new_role_classes": [
{
"label": "Environmental Compliance Specialist",
"definition": "Professional responsible for ensuring projects meet environmental regulations and standards",
"distinguishing_features": ["Environmental regulation expertise", "Compliance assessment capabilities", "EPA standards knowledge"],
"professional_scope": "Environmental impact assessment, regulatory compliance review, permit coordination",
"typical_qualifications": ["Environmental engineering degree", "Regulatory compliance experience", "Knowledge of EPA standards"],
"generated_obligations": ["Ensure regulatory compliance", "Report violations", "Maintain environmental standards"],
"associated_virtues": ["Environmental stewardship", "Regulatory integrity", "Technical competence"],
"relationship_type": "Provider-Client",
"domain_context": "Engineering",
"examples_from_case": ["Engineer A was retained to prepare environmental assessment", "specialist reviewed compliance requirements"]
}
],
"role_individuals": [
{
"name": "Engineer A",
"role_classification": "Environmental Compliance Specialist",
"attributes": {
"title": "Engineer",
"license": "professional engineering license",
"specialization": "environmental engineer",
"experience": "several years of experience"
},
"relationships": [
{"type": "retained_by", "target": "Client W"}
],
"case_involvement": "Retained to prepare comprehensive report addressing organic compound characteristics"
}
]
}
Saved: 2025-10-13 13:39
LLM Response
```json
{
"new_role_classes": [
{
"label": "City Engineer Role",
"definition": "Senior municipal engineering professional responsible for overseeing city infrastructure development, managing engineering contracts, and serving as primary liaison between the city and engineering firms/contractors",
"distinguishing_features": ["Municipal government position", "Contract negotiation authority", "Infrastructure oversight responsibility", "Senior-level project review authority"],
"professional_scope": "Municipal infrastructure planning and oversight, contract negotiation and award for consulting and construction projects, senior-level review of major project issues, liaison between city government and private engineering firms",
"typical_qualifications": ["Professional engineering license", "Extensive municipal engineering experience", "Knowledge of public contracting", "Infrastructure development expertise"],
"generated_obligations": ["Serve public interest in infrastructure development", "Ensure fair and transparent contracting processes", "Maintain impartiality in vendor selection", "Protect municipal interests", "Avoid conflicts of interest post-employment"],
"associated_virtues": ["Public service commitment", "Impartiality", "Transparency", "Professional integrity", "Stewardship of public resources"],
"relationship_type": "Public Responsibility",
"domain_context": "Engineering",
"examples_from_case": ["Engineer D works as the City Engineer", "main points of contact for AE firms and contractors", "contract negotiation and award", "senior-level review of major project issues"]
}
],
"role_individuals": [
{
"name": "Engineer D",
"role_classification": "City Engineer Role",
"attributes": {
"title": "City Engineer",
"license": "licensed professional engineer",
"position": "senior municipal engineering position",
"tenure": "served during period of rapid growth and infrastructure development"
},
"relationships": [
{"type": "employed_by", "target": "mid-sized municipality"},
{"type": "main_contact_for", "target": "AE firms and contractors"},
{"type": "future_employment", "target": "Firm AE&R"}
],
"active_obligations": ["Oversee city infrastructure growth", "Manage contract negotiations and awards", "Review major project issues"],
"ethical_tensions": "Potential conflict between past role overseeing contracts with AE&R and future employment with same firm; absence of 'revolving door' provisions creates appearance of conflict",
"case_involvement": "Central figure transitioning from City Engineer position to employment with engineering firm that has received city contracts during their tenure"
},
{
"name": "Firm AE&R",
"role_classification": "Provider-Client Role",
"attributes": {
"type": "engineering firm",
"location": "in the City",
"history": "completed many projects for the City during Engineer D's tenure"
},
"relationships": [
{"type": "contractor_for", "target": "the City"},
{"type": "hiring", "target": "Engineer D"}
],
"active_obligations": ["Provide engineering consulting services", "Submit proposals for city work"],
"ethical_tensions": "Hiring former City Engineer who previously oversaw their contracts",
"case_involvement": "Engineering firm hiring Engineer D as associate after their tenure overseeing the firm's city contracts"
}
]
}
```
States Extraction
LLM Prompt
EXISTING STATE CLASSES IN ONTOLOGY (DO NOT RE-EXTRACT THESE):
STATE STATES:
- Certification Required State: Checkpoint state requiring formal validation processes
- Competing Duties State: State requiring ethical prioritization between conflicting obligations
- Conflict of Interest State: Professional situation where personal and professional interests compete
- Make Objective Truthful Statements: Requirement for honesty in professional communications
- Non-Compliant State: State requiring compliance remediation
- Non-Compliant State: Problematic state requiring immediate corrective action
- Objective and Truthful Statements: Requirement for honesty in professional communications
- Provide Objective Statements: Professional communication standard
- Public Statements: Requirement for honesty and objectivity in all public communications and professional statements
- Regulatory Compliance State: Legal compliance context constraining actions
- State: A quality representing conditions that affect ethical decisions and professional conduct. This is the S component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs).
IMPORTANT: Only extract NEW state types not listed above!
You are analyzing a professional ethics case to extract both STATE CLASSES and STATE INSTANCES.
DEFINITIONS:
- STATE CLASS: A type of situational condition (e.g., "Conflict of Interest", "Emergency Situation", "Resource Constraint")
- STATE INDIVIDUAL: A specific instance of a state active in this case attached to specific people/organizations
CRITICAL REQUIREMENT: Every STATE CLASS you identify MUST be based on at least one specific STATE INDIVIDUAL instance in the case.
You cannot propose a state class without providing the concrete instance(s) that demonstrate it.
KEY INSIGHT FROM LITERATURE:
States are not abstract - they are concrete conditions affecting specific actors at specific times.
Each state has a subject (WHO is in the state), temporal boundaries (WHEN), and causal relationships (WHY).
YOUR TASK - Extract two LINKED types of entities:
1. NEW STATE CLASSES (types not in the existing ontology above):
- Novel types of situational states discovered in this case
- Must be sufficiently general to apply to other cases
- Should represent distinct environmental or contextual conditions
- Consider both inertial (persistent) and non-inertial (momentary) fluents
2. STATE INDIVIDUALS (specific instances in this case):
- Specific states active in this case narrative
- MUST be attached to specific individuals or organizations in the case
- Include temporal properties (when initiated, when terminated)
- Include causal relationships (triggered by what event, affects which obligations)
- Map to existing classes where possible, or to new classes you discover
EXTRACTION GUIDELINES:
For NEW STATE CLASSES, identify:
- Label: Clear, professional name for the state type
- Definition: What this state represents
- Activation conditions: What events/conditions trigger this state
- Termination conditions: What events/conditions end this state
- Persistence type: "inertial" (persists until terminated) or "non-inertial" (momentary)
- Affected obligations: Which professional duties does this state affect?
- Temporal properties: How does this state evolve over time?
- Domain context: Medical/Engineering/Legal/etc.
- Examples from case: Specific instances showing this state type
For STATE INDIVIDUALS, identify:
- Identifier: Unique descriptor (e.g., "John_Smith_ConflictOfInterest_ProjectX")
- State class: Which state type it represents (existing or new)
- Subject: WHO is in this state (person/organization name from the case)
- Initiated by: What event triggered this state?
- Initiated at: When did this state begin?
- Terminated by: What event ended this state (if applicable)?
- Terminated at: When did this state end (if applicable)?
- Affects obligations: Which specific obligations were affected?
- Urgency/Intensity: Does this state's urgency change over time?
- Related parties: Who else is affected by this state?
- Case involvement: How this state affected the case outcome
CASE TEXT FROM facts SECTION:
Facts:
Engineer D, a licensed professional engineer, works as the City Engineer in a mid-sized municipality that has been experiencing rapid growth along with rapid infrastructure growth.
Engineer D has been one of the City's main points of contact for AE firms and contractors in the area, both with respect to contract negotiation and award (consultant and construction) and senior-level review of major project issues that arise from time to time.
Engineer D announces plans to step down as the City Engineer and indicates that they accepted a position at an unnamed engineering firm in the City.
Of significance is that the City does not include “revolving door” provisions in employment contracts for its senior-level employees.
Shortly after Engineer D's announcement, Firm AE&R announces Engineer D as a newly hired associate.
AE&R completed many projects for the City during Engineer D's tenure as City Engineer, and the firm plans to continue submitting proposals and performing consulting work for the City.
Respond with a JSON structure. Here's a CONCRETE EXAMPLE showing the required linkage:
EXAMPLE (if the case mentions "Engineer A faced a conflict when discovering his brother worked for the contractor"):
{
"new_state_classes": [
{
"label": "Family Conflict of Interest",
"definition": "A state where a professional's family relationships create potential bias in professional decisions",
"activation_conditions": ["Discovery of family member involvement", "Family member has financial interest"],
"termination_conditions": ["Recusal from decision", "Family member withdraws"],
"persistence_type": "inertial",
"affected_obligations": ["Duty of impartiality", "Disclosure requirements"],
"temporal_properties": "Persists until formally addressed through recusal or disclosure",
"domain_context": "Engineering",
"examples_from_case": ["Engineer A discovered brother worked for ABC Contractors"],
"confidence": 0.85,
"rationale": "Specific type of conflict not covered by general COI in existing ontology"
}
],
"state_individuals": [
{
"identifier": "EngineerA_FamilyConflict_ABCContractors",
"state_class": "Family Conflict of Interest",
"subject": "Engineer A",
"initiated_by": "Discovery that brother is senior manager at ABC Contractors",
"initiated_at": "When bidding process began",
"terminated_by": "Engineer A recused from contractor selection",
"terminated_at": "Two weeks after discovery",
"affects_obligations": ["Maintain impartial contractor selection", "Disclose conflicts to client"],
"urgency_level": "high",
"related_parties": ["Client B", "ABC Contractors", "Engineer A's brother"],
"case_involvement": "Led to Engineer A's recusal from contractor selection process",
"is_existing_class": false,
"confidence": 0.9
}
]
}
YOUR RESPONSE FORMAT (use the same structure with YOUR case's specific details):
{
"new_state_classes": [
// For each new state type you discover
],
"state_individuals": [
// For each specific instance in the case (MUST have at least one per new class)
]
}
EXTRACTION RULES:
1. For EVERY new state class you identify, you MUST provide at least one corresponding state individual
2. State individuals MUST have a clear subject (specific person/organization from the case)
3. If you cannot identify a specific instance, do not create the state class
4. States without subjects are invalid (e.g., cannot have "general emergency" - must be "City M's water emergency")
5. Each state individual should clearly demonstrate why its state class is needed
Focus on states that:
1. Are attached to specific individuals or organizations mentioned in the case
2. Have clear temporal boundaries (when initiated, when terminated)
3. Affect specific ethical obligations or professional duties
4. Show causal relationships with events in the case
5. Demonstrate the context-dependent nature of professional ethics
EXAMPLE OF CORRECT EXTRACTION:
State Class: "Public Health Risk State"
State Individual: "City_M_PublicHealthRisk_2023" with subject="City M", initiated_by="Decision to change water source", affects_obligations=["Ensure public safety", "Provide clean water"]
EXAMPLE OF INCORRECT EXTRACTION:
State Class: "Emergency Situation" with NO corresponding individual (INVALID - no specific instance)
Saved: 2025-10-13 13:39
LLM Response
```json
{
"new_state_classes": [
{
"label": "Post-Employment Transition State",
"definition": "A transitional state where a professional has announced departure from a public position but continues to hold decision-making authority before officially leaving",
"activation_conditions": ["Announcement of resignation", "Acceptance of future position", "Continued employment in current role"],
"termination_conditions": ["Official departure from position", "Recusal from relevant decisions"],
"persistence_type": "inertial",
"affected_obligations": ["Duty of loyalty to current employer", "Avoidance of self-dealing", "Maintenance of public trust"],
"temporal_properties": "Persists from announcement until official departure date",
"domain_context": "Engineering/Public Service",
"examples_from_case": ["Engineer D announced departure while still serving as City Engineer"],
"confidence": 0.9,
"rationale": "Captures the specific ethical challenges during the transition period between announcement and departure"
},
{
"label": "Revolving Door Vulnerability State",
"definition": "An organizational state where the absence of post-employment restrictions creates potential for conflicts of interest in senior-level hiring and contracting decisions",
"activation_conditions": ["Absence of revolving door provisions", "Senior employee with contracting authority", "Active relationships with private firms"],
"termination_conditions": ["Implementation of revolving door policies", "Removal of contracting authority"],
"persistence_type": "inertial",
"affected_obligations": ["Ensure fair contracting processes", "Protect public interest", "Maintain competitive bidding integrity"],
"temporal_properties": "Persists as long as policy gap exists",
"domain_context": "Public Administration/Engineering",
"examples_from_case": ["City's lack of revolving door provisions for senior employees"],
"confidence": 0.85,
"rationale": "Identifies systemic vulnerability in organizational ethics infrastructure"
}
],
"state_individuals": [
{
"identifier": "EngineerD_PostEmploymentTransition_CityEngineer",
"state_class": "Post-Employment Transition State",
"subject": "Engineer D",
"initiated_by": "Engineer D's announcement of plans to step down and acceptance of position at unnamed engineering firm",
"initiated_at": "Time of announcement to step down",
"terminated_by": "Official departure from City Engineer position",
"terminated_at": "Not specified in case",
"affects_obligations": ["Maintain loyalty to City during remaining tenure", "Avoid favoritism toward future employer", "Ensure fair treatment of all contractors"],
"urgency_level": "high",
"related_parties": ["City", "AE&R", "Other engineering firms"],
"case_involvement": "Created potential conflict as Engineer D could influence decisions affecting future employer",
"is_existing_class": false,
"confidence": 0.9
},
{
"identifier": "City_RevolvingDoorVulnerability_SeniorEmployees",
"state_class": "Revolving Door Vulnerability State",
"subject": "City",
"initiated_by": "City's policy decision not to include revolving door provisions in employment contracts",
"initiated_at": "Prior to Engineer D's tenure (ongoing policy)",
"terminated_by": "Not terminated in case narrative",
"terminated_at": "Not applicable",
"affects_obligations": ["City's duty to ensure fair contracting", "Protection of public resources", "Prevention of conflicts of interest"],
"urgency_level": "medium",
"related_parties": ["Engineer D", "AE&R", "All contractors working with City"],
"case_involvement": "Enabled Engineer D to immediately join firm that had contracts with City",
"is_existing_class": false,
"confidence": 0.85
},
{
"identifier": "AER_ConflictOfInterest_HiringCityEngineer",
"state_class": "Conflict of Interest State",
"subject": "AE&R",
"initiated_by": "AE&R's hiring of Engineer D who was City Engineer overseeing their contracts",
"initiated_at": "When AE&R announced Engineer D as newly hired associate",
"terminated_by": "Not specified in case",
"terminated_at": "Not applicable",
"affects_obligations": ["Fair competition in bidding", "Avoiding appearance of impropriety", "Maintaining professional integrity"],
"urgency_level": "high",
"related_parties": ["Engineer D", "City", "Competing engineering firms"],
"case_involvement": "AE&R gains potential unfair advantage through hiring of former City Engineer",
"is_existing_class": true,
"confidence": 0.95
}
]
}
```
Resources Extraction
LLM Prompt
EXISTING RESOURCE CLASSES IN ONTOLOGY (DO NOT RE-EXTRACT THESE):
- Legal Resource: Legal framework constraining professional practice
- Resource: An independent continuant entity that serves as input or reference for professional activities. This is the Rs component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs).
- Resource Constrained: Resource limitation affecting available actions
- Resource Constraint: Limitations on available time, budget, materials, or human resources (Ganascia 2007)
- Resource Type: Meta-class for specific resource types recognized by the ProEthica system
- Resources Available: Resource sufficiency enabling full options
IMPORTANT: Only extract NEW resource types not listed above!
You are analyzing a professional ethics case to extract both RESOURCE CLASSES and RESOURCE INSTANCES.
DEFINITIONS:
- RESOURCE CLASS: A type of document, tool, standard, or knowledge source (e.g., "Emergency Response Protocol", "Technical Specification", "Ethics Code")
- RESOURCE INDIVIDUAL: A specific instance of a resource used in this case (e.g., "NSPE Code of Ethics 2023", "City M Water Quality Standards")
CRITICAL REQUIREMENT: Every RESOURCE CLASS you identify MUST be based on at least one specific RESOURCE INDIVIDUAL instance in the case.
You cannot propose a resource class without providing the concrete instance(s) that demonstrate it.
YOUR TASK - Extract two LINKED types of entities:
1. NEW RESOURCE CLASSES (types not in the existing ontology above):
- Novel types of resources discovered in this case
- Must be sufficiently general to apply to other cases
- Should represent distinct categories of decision-making resources
- Consider documents, tools, standards, guidelines, databases, etc.
2. RESOURCE INDIVIDUALS (specific instances in this case):
- Specific documents, tools, or knowledge sources mentioned
- MUST have identifiable titles or descriptions
- Include metadata (creator, date, version) where available
- Map to existing classes where possible, or to new classes you discover
EXTRACTION GUIDELINES:
For NEW RESOURCE CLASSES, identify:
- Label: Clear, professional name for the resource type
- Definition: What this resource type represents
- Resource type: document, tool, standard, guideline, database, etc.
- Accessibility: public, restricted, proprietary, etc.
- Authority source: Who typically creates/maintains these resources
- Typical usage: How these resources are typically used
- Domain context: Medical/Engineering/Legal/etc.
- Examples from case: Specific instances showing this resource type
For RESOURCE INDIVIDUALS, identify:
- Identifier: Unique descriptor (e.g., "NSPE_CodeOfEthics_2023")
- Resource class: Which resource type it represents (existing or new)
- Document title: Official name or description
- Created by: Organization or authority that created it
- Created at: When it was created (if mentioned)
- Version: Edition or version information
- URL or location: Where to find it (if mentioned)
- Used by: Who used this resource in the case
- Used in context: How this resource was applied
- Case involvement: How this resource affected decisions
CASE TEXT FROM facts SECTION:
Facts:
Engineer D, a licensed professional engineer, works as the City Engineer in a mid-sized municipality that has been experiencing rapid growth along with rapid infrastructure growth.
Engineer D has been one of the City's main points of contact for AE firms and contractors in the area, both with respect to contract negotiation and award (consultant and construction) and senior-level review of major project issues that arise from time to time.
Engineer D announces plans to step down as the City Engineer and indicates that they accepted a position at an unnamed engineering firm in the City.
Of significance is that the City does not include “revolving door” provisions in employment contracts for its senior-level employees.
Shortly after Engineer D's announcement, Firm AE&R announces Engineer D as a newly hired associate.
AE&R completed many projects for the City during Engineer D's tenure as City Engineer, and the firm plans to continue submitting proposals and performing consulting work for the City.
Respond with a JSON structure. Here's an EXAMPLE:
EXAMPLE (if the case mentions "Engineer A consulted the NSPE Code of Ethics and the state's engineering regulations"):
{
"new_resource_classes": [
{
"label": "State Engineering Regulations",
"definition": "Legal requirements and regulations governing engineering practice at the state level",
"resource_type": "regulatory_document",
"accessibility": ["public", "official"],
"authority_source": "State Engineering Board",
"typical_usage": "Legal compliance and professional practice guidance",
"domain_context": "Engineering",
"examples_from_case": ["State engineering regulations consulted by Engineer A"],
"confidence": 0.85,
"rationale": "Specific type of regulatory resource not in existing ontology"
}
],
"resource_individuals": [
{
"identifier": "NSPE_CodeOfEthics_Current",
"resource_class": "Professional Ethics Code",
"document_title": "NSPE Code of Ethics",
"created_by": "National Society of Professional Engineers",
"created_at": "Current version",
"version": "Current",
"used_by": "Engineer A",
"used_in_context": "Consulted for ethical guidance on conflict of interest",
"case_involvement": "Provided framework for ethical decision-making",
"is_existing_class": true,
"confidence": 0.95
},
{
"identifier": "State_Engineering_Regulations_Current",
"resource_class": "State Engineering Regulations",
"document_title": "State Engineering Practice Act and Regulations",
"created_by": "State Engineering Board",
"used_by": "Engineer A",
"used_in_context": "Referenced for legal requirements",
"case_involvement": "Defined legal obligations for professional practice",
"is_existing_class": false,
"confidence": 0.9
}
]
}
EXTRACTION RULES:
1. For EVERY new resource class you identify, you MUST provide at least one corresponding resource individual
2. Resource individuals MUST have identifiable titles or descriptions
3. If you cannot identify a specific instance, do not create the resource class
4. Focus on resources that directly influence decision-making in the case
5. Each resource individual should clearly demonstrate why its resource class is needed
Focus on resources that:
1. Are explicitly mentioned or referenced in the case
2. Guide professional decisions or actions
3. Provide standards, requirements, or frameworks
4. Serve as knowledge sources for the professionals involved
Saved: 2025-10-13 13:39
LLM Response
```json
{
"new_resource_classes": [
{
"label": "Municipal Employment Contract",
"definition": "Legal agreement defining terms of employment, obligations, and restrictions for municipal employees, including post-employment provisions",
"resource_type": "legal_document",
"accessibility": ["restricted", "internal"],
"authority_source": "Municipal Government/City Administration",
"typical_usage": "Defining employment terms, obligations, and post-employment restrictions for public sector employees",
"domain_context": "Public Administration/Engineering",
"examples_from_case": ["City's employment contracts for senior-level employees (noted as lacking revolving door provisions)"],
"confidence": 0.9,
"rationale": "Specific type of employment agreement that governs public sector employment relationships and post-employment restrictions"
},
{
"label": "Revolving Door Policy",
"definition": "Regulatory provision or policy that restricts former government employees from immediately working for entities they previously regulated or contracted with",
"resource_type": "policy_document",
"accessibility": ["public", "regulatory"],
"authority_source": "Government Ethics Office/Municipal Administration",
"typical_usage": "Preventing conflicts of interest and maintaining public trust in government contracting processes",
"domain_context": "Public Administration/Ethics",
"examples_from_case": ["Revolving door provisions (noted as absent from City employment contracts)"],
"confidence": 0.85,
"rationale": "Specific type of ethics policy that addresses post-employment restrictions, explicitly mentioned as absent in this case"
}
],
"resource_individuals": [
{
"identifier": "City_Senior_Employment_Contract_Current",
"resource_class": "Municipal Employment Contract",
"document_title": "City Employment Contract for Senior-Level Employees",
"created_by": "City Administration",
"created_at": "Current version during Engineer D's tenure",
"version": "Current",
"used_by": "Engineer D",
"used_in_context": "Governing Engineer D's employment terms as City Engineer",
"case_involvement": "Notably lacks revolving door provisions, allowing Engineer D to immediately join AE&R after leaving City position",
"is_existing_class": false,
"confidence": 0.95
},
{
"identifier": "Absent_Revolving_Door_Provisions",
"resource_class": "Revolving Door Policy",
"document_title": "Revolving Door Provisions (Absent from City Contracts)",
"created_by": "Not applicable - noted as absent",
"used_by": "City Administration",
"used_in_context": "Absence of such provisions in employment contracts",
"case_involvement": "The absence of these provisions enabled Engineer D to immediately join a firm that had contracts with the City",
"is_existing_class": false,
"confidence": 0.85
}
]
}
```