Extraction Complete
Total Entities: 21
Actions: 5
Events: 2
Causal Chains: 5
Allen Relations: 8
Timeline: 7
Timeline Overview
Note: The timeline includes only actions and events with clear temporal markers that could be sequenced chronologically.
Timeline Elements: 7
Actions on Timeline: 5 (of 5 extracted)
Events on Timeline: 2 (of 2 extracted)
Temporal Markers
  • After discovery of design errors during first tower construction 1 elements
  • Initial engagement with Engineer B 1 elements
  • Upon initial engagement by Owner 1 elements
  • After Engineer B's objection 1 elements
  • After being notified of proposed peer review 1 elements
  • During construction of first tower 1 elements
  • After Owner agrees to notify Engineer A 1 elements
Temporal Consistency Check
Valid
Extracted Actions (5)
Volitional professional decisions with intentions and ethical context

Description: Owner decides to retain Engineer B to conduct peer review of Engineer A's plans for the second tower after discovering design errors in the first tower.

Temporal Marker: After discovery of design errors during first tower construction

Mental State: deliberate

Intended Outcome: Prevent design errors in second tower

Fulfills Obligations:
  • Due diligence
  • Risk management
Guided By Principles:
  • Public safety
  • Quality assurance
Required Capabilities:
Project management Risk assessment
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Owner seeks to prevent similar costly design errors in the second tower after discovering significant problems in the first tower construction

Ethical Tension: Due diligence and risk management vs potential damage to existing professional relationship

Learning Significance: Demonstrates the importance of quality assurance and the right to seek independent professional review when safety concerns arise

Stakes: Public safety, financial losses, professional liability, and potential structural failures in the second tower

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Continue with Engineer A despite errors
  • Terminate Engineer A and hire new engineer
  • Require Engineer A to self-review with additional oversight

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/15#Action_Seek_Peer_Review_Services",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Continue with Engineer A despite errors",
    "Terminate Engineer A and hire new engineer",
    "Require Engineer A to self-review with additional oversight"
  ],
  "proeth-scenario:characterMotivation": "Owner seeks to prevent similar costly design errors in the second tower after discovering significant problems in the first tower construction",
  "proeth-scenario:consequencesIfAlternative": [
    "Risk repeating same errors",
    "Legal complications and project delays",
    "May not catch all issues without independent perspective"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates the importance of quality assurance and the right to seek independent professional review when safety concerns arise",
  "proeth-scenario:ethicalTension": "Due diligence and risk management vs potential damage to existing professional relationship",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public safety, financial losses, professional liability, and potential structural failures in the second tower",
  "proeth:description": "Owner decides to retain Engineer B to conduct peer review of Engineer A\u0027s plans for the second tower after discovering design errors in the first tower.",
  "proeth:foreseenUnintendedEffects": [
    "Potential conflict with Engineer A"
  ],
  "proeth:fulfillsObligation": [
    "Due diligence",
    "Risk management"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety",
    "Quality assurance"
  ],
  "proeth:hasAgent": "Owner (Client)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Engineer relationship vs Safety",
    "proeth:resolutionReasoning": "Safety concerns outweighed relationship preservation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Prevent design errors in second tower",
  "proeth:requiresCapability": [
    "Project management",
    "Risk assessment"
  ],
  "proeth:temporalMarker": "After discovery of design errors during first tower construction",
  "proeth:withinCompetence": true,
  "rdfs:label": "Seek Peer Review Services"
}

Description: Owner initially instructs Engineer B to conduct the peer review without Engineer A's knowledge or consent.

Temporal Marker: Initial engagement with Engineer B

Mental State: deliberate

Intended Outcome: Obtain unbiased review while avoiding confrontation

Guided By Principles:
  • Efficiency
  • Conflict avoidance
Required Capabilities:
Understanding of professional ethics
Within Competence: No
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Owner wants to avoid confrontation with Engineer A and potential legal complications while still ensuring design quality

Ethical Tension: Practical risk management vs professional transparency and Engineer A's right to know about review of their work

Learning Significance: Highlights the ethical problems with secret peer reviews and the importance of transparency in professional relationships

Stakes: Professional trust, legal liability, and the integrity of the peer review process

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Immediately inform Engineer A of peer review plans
  • Request Engineer A to participate collaboratively in the review

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/15#Action_Request_Secret_Peer_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Immediately inform Engineer A of peer review plans",
    "Request Engineer A to participate collaboratively in the review"
  ],
  "proeth-scenario:characterMotivation": "Owner wants to avoid confrontation with Engineer A and potential legal complications while still ensuring design quality",
  "proeth-scenario:consequencesIfAlternative": [
    "Potential conflict but maintains transparency",
    "Could improve designs through collaboration but may face resistance"
  ],
  "proeth-scenario:decisionSignificance": "Highlights the ethical problems with secret peer reviews and the importance of transparency in professional relationships",
  "proeth-scenario:ethicalTension": "Practical risk management vs professional transparency and Engineer A\u0027s right to know about review of their work",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Professional trust, legal liability, and the integrity of the peer review process",
  "proeth:description": "Owner initially instructs Engineer B to conduct the peer review without Engineer A\u0027s knowledge or consent.",
  "proeth:foreseenUnintendedEffects": [
    "Potential ethical violations",
    "Professional relationship damage"
  ],
  "proeth:guidedByPrinciple": [
    "Efficiency",
    "Conflict avoidance"
  ],
  "proeth:hasAgent": "Owner (Client)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Confidentiality vs Professional courtesy",
    "proeth:resolutionReasoning": "Initially prioritized review objectivity over transparency"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Obtain unbiased review while avoiding confrontation",
  "proeth:requiresCapability": [
    "Understanding of professional ethics"
  ],
  "proeth:temporalMarker": "Initial engagement with Engineer B",
  "proeth:violatesObligation": [
    "Professional courtesy",
    "Transparency"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Request Secret Peer Review"
}

Description: Engineer B objects to conducting the peer review without Engineer A's knowledge and insists on transparency.

Temporal Marker: Upon initial engagement by Owner

Mental State: deliberate

Intended Outcome: Maintain professional ethics and transparency

Fulfills Obligations:
  • Professional courtesy
  • Transparency
  • Collegiality
Guided By Principles:
  • Professional integrity
  • Ethical practice
Required Capabilities:
Ethical judgment Professional knowledge
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer B upholds professional ethics requiring transparency and respect for fellow engineers' professional standing

Ethical Tension: Client service and business interests vs professional integrity and collegial respect

Learning Significance: Demonstrates the ethical obligation to refuse unethical requests even when it may cost business opportunities

Stakes: Professional reputation, ethical standards, and the integrity of the engineering profession

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Accept secret review to secure the contract
  • Withdraw from consideration entirely

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/15#Action_Refuse_Secret_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept secret review to secure the contract",
    "Withdraw from consideration entirely"
  ],
  "proeth-scenario:characterMotivation": "Engineer B upholds professional ethics requiring transparency and respect for fellow engineers\u0027 professional standing",
  "proeth-scenario:consequencesIfAlternative": [
    "Violate professional ethics and potentially face disciplinary action",
    "Lose business opportunity but avoid ethical compromise"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates the ethical obligation to refuse unethical requests even when it may cost business opportunities",
  "proeth-scenario:ethicalTension": "Client service and business interests vs professional integrity and collegial respect",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Professional reputation, ethical standards, and the integrity of the engineering profession",
  "proeth:description": "Engineer B objects to conducting the peer review without Engineer A\u0027s knowledge and insists on transparency.",
  "proeth:foreseenUnintendedEffects": [
    "Potential loss of work",
    "Client dissatisfaction"
  ],
  "proeth:fulfillsObligation": [
    "Professional courtesy",
    "Transparency",
    "Collegiality"
  ],
  "proeth:guidedByPrinciple": [
    "Professional integrity",
    "Ethical practice"
  ],
  "proeth:hasAgent": "Engineer B (Reviewing Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client wishes vs Professional ethics",
    "proeth:resolutionReasoning": "Professional ethics superseded client preferences"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Maintain professional ethics and transparency",
  "proeth:requiresCapability": [
    "Ethical judgment",
    "Professional knowledge"
  ],
  "proeth:temporalMarker": "Upon initial engagement by Owner",
  "proeth:withinCompetence": true,
  "rdfs:label": "Refuse Secret Review"
}

Description: Owner reluctantly consents to notifying Engineer A about the peer review after Engineer B's objection to secrecy.

Temporal Marker: After Engineer B's objection

Mental State: reluctant

Intended Outcome: Proceed with peer review while maintaining Engineer B's cooperation

Fulfills Obligations:
  • Transparency
  • Professional courtesy
Guided By Principles:
  • Ethical compliance
  • Professional cooperation
Required Capabilities:
Negotiation Adaptability
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Owner balances need for design review with Engineer B's ethical requirements and desire to maintain professional relationships

Ethical Tension: Expedient problem-solving vs transparent professional practices

Learning Significance: Shows how ethical pressure from professionals can guide clients toward more ethical practices

Stakes: Maintaining professional relationships while ensuring adequate design review and project safety

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Abandon peer review plans entirely
  • Find different engineer willing to do secret review

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/15#Action_Agree_to_Notify_Engineer",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Abandon peer review plans entirely",
    "Find different engineer willing to do secret review"
  ],
  "proeth-scenario:characterMotivation": "Owner balances need for design review with Engineer B\u0027s ethical requirements and desire to maintain professional relationships",
  "proeth-scenario:consequencesIfAlternative": [
    "Accept higher risk of design errors",
    "Undermine professional ethics and potentially face exposure later"
  ],
  "proeth-scenario:decisionSignificance": "Shows how ethical pressure from professionals can guide clients toward more ethical practices",
  "proeth-scenario:ethicalTension": "Expedient problem-solving vs transparent professional practices",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Maintaining professional relationships while ensuring adequate design review and project safety",
  "proeth:description": "Owner reluctantly consents to notifying Engineer A about the peer review after Engineer B\u0027s objection to secrecy.",
  "proeth:foreseenUnintendedEffects": [
    "Engineer A\u0027s potential objection",
    "Project complications"
  ],
  "proeth:fulfillsObligation": [
    "Transparency",
    "Professional courtesy"
  ],
  "proeth:guidedByPrinciple": [
    "Ethical compliance",
    "Professional cooperation"
  ],
  "proeth:hasAgent": "Owner (Client)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Secrecy preference vs Service acquisition",
    "proeth:resolutionReasoning": "Adapted to professional requirements to secure necessary services"
  },
  "proeth:hasMentalState": "reluctant",
  "proeth:intendedOutcome": "Proceed with peer review while maintaining Engineer B\u0027s cooperation",
  "proeth:requiresCapability": [
    "Negotiation",
    "Adaptability"
  ],
  "proeth:temporalMarker": "After Engineer B\u0027s objection",
  "proeth:withinCompetence": true,
  "rdfs:label": "Agree to Notify Engineer"
}

Description: Engineer A objects to and refuses to consent to the peer review of their plans for the second tower.

Temporal Marker: After being notified of proposed peer review

Mental State: defensive

Intended Outcome: Prevent external review and protect professional standing

Guided By Principles:
  • Self-protection
  • Professional autonomy
Required Capabilities:
Professional accountability Error acknowledgment
Within Competence: No
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A protects professional reputation and resists external validation of their work, possibly due to pride or fear of further error discovery

Ethical Tension: Professional autonomy and reputation vs public safety and quality assurance

Learning Significance: Illustrates the tension between professional ego and the broader obligation to ensure safe, quality engineering work

Stakes: Engineer A's professional standing, project safety, Owner's ability to ensure quality, and precedent for future peer reviews

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Agree to peer review with conditions
  • Propose collaborative review process
  • Offer to conduct additional self-review

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/15#Action_Refuse_Peer_Review_Consent",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Agree to peer review with conditions",
    "Propose collaborative review process",
    "Offer to conduct additional self-review"
  ],
  "proeth-scenario:characterMotivation": "Engineer A protects professional reputation and resists external validation of their work, possibly due to pride or fear of further error discovery",
  "proeth-scenario:consequencesIfAlternative": [
    "Maintain some control over process while allowing review",
    "Potentially improve designs through cooperation",
    "May not provide independent validation Owner seeks"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the tension between professional ego and the broader obligation to ensure safe, quality engineering work",
  "proeth-scenario:ethicalTension": "Professional autonomy and reputation vs public safety and quality assurance",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A\u0027s professional standing, project safety, Owner\u0027s ability to ensure quality, and precedent for future peer reviews",
  "proeth:description": "Engineer A objects to and refuses to consent to the peer review of their plans for the second tower.",
  "proeth:foreseenUnintendedEffects": [
    "Project delays",
    "Client relationship damage",
    "Safety concerns"
  ],
  "proeth:guidedByPrinciple": [
    "Self-protection",
    "Professional autonomy"
  ],
  "proeth:hasAgent": "Engineer A (Original Design Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional reputation vs Public safety",
    "proeth:resolutionReasoning": "Self-interest prioritized over professional responsibility and safety"
  },
  "proeth:hasMentalState": "defensive",
  "proeth:intendedOutcome": "Prevent external review and protect professional standing",
  "proeth:requiresCapability": [
    "Professional accountability",
    "Error acknowledgment"
  ],
  "proeth:temporalMarker": "After being notified of proposed peer review",
  "proeth:violatesObligation": [
    "Professional responsibility",
    "Public safety",
    "Cooperation",
    "Accountability"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Refuse Peer Review Consent"
}
Extracted Events (2)
Occurrences that trigger ethical considerations and state changes

Description: Significant design errors by Engineer A are discovered during construction of the first tower. This discovery reveals serious flaws that could affect the mirror-image second tower.

Temporal Marker: During construction of first tower

Activates Constraints:
  • PublicSafety_Paramount_Constraint
  • Professional_Competence_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Alarm and embarrassment for Engineer A; concern and frustration for Owner; anxiety about professional reputation and safety; urgency to prevent similar problems in second tower

Stakeholder Consequences:
  • engineer_a: Professional reputation damaged, competence questioned, potential liability exposure
  • owner: Construction delays, cost overruns, uncertainty about second tower project
  • public: Safety concerns for both towers, potential structural risks
  • construction_workers: Immediate safety concerns, work disruption

Learning Moment: Shows how design errors can have cascading effects across multiple projects; demonstrates importance of quality control and peer review

Ethical Implications: Reveals tension between professional loyalty and public safety; demonstrates consequences of inadequate design review; highlights duty to learn from and prevent repetition of errors

Discussion Prompts:
  • What obligations does this discovery create for all parties involved?
  • How should the engineering profession balance protecting colleagues versus ensuring public safety?
  • What systemic changes could prevent similar errors from going undetected?
Crisis / Turning Point Tension: high Pacing: crisis
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/15#Event_Design_Errors_Discovery",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What obligations does this discovery create for all parties involved?",
    "How should the engineering profession balance protecting colleagues versus ensuring public safety?",
    "What systemic changes could prevent similar errors from going undetected?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Alarm and embarrassment for Engineer A; concern and frustration for Owner; anxiety about professional reputation and safety; urgency to prevent similar problems in second tower",
  "proeth-scenario:ethicalImplications": "Reveals tension between professional loyalty and public safety; demonstrates consequences of inadequate design review; highlights duty to learn from and prevent repetition of errors",
  "proeth-scenario:learningMoment": "Shows how design errors can have cascading effects across multiple projects; demonstrates importance of quality control and peer review",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "construction_workers": "Immediate safety concerns, work disruption",
    "engineer_a": "Professional reputation damaged, competence questioned, potential liability exposure",
    "owner": "Construction delays, cost overruns, uncertainty about second tower project",
    "public": "Safety concerns for both towers, potential structural risks"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Professional_Competence_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/15#Action_Original_Design_Work__by_Engineer_A_",
  "proeth:causesStateChange": "First tower construction compromised; second tower design validity questioned; professional competence under scrutiny",
  "proeth:createsObligation": [
    "Correct_Design_Errors",
    "Review_Related_Projects",
    "Ensure_Second_Tower_Safety",
    "Professional_Accountability"
  ],
  "proeth:description": "Significant design errors by Engineer A are discovered during construction of the first tower. This discovery reveals serious flaws that could affect the mirror-image second tower.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During construction of first tower",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Design Errors Discovery"
}

Description: Engineer A's refusal to consent to peer review creates a deadlock situation where the second tower's safety cannot be independently verified despite known risks from the first tower's design errors.

Temporal Marker: After Owner agrees to notify Engineer A

Activates Constraints:
  • Professional_Autonomy_Respect
  • Safety_Verification_Blocked
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Frustration for Owner unable to get safety verification; professional defensiveness from Engineer A; ethical concern from Engineer B about blocked safety review

Stakeholder Consequences:
  • owner: Cannot proceed with confidence on second tower, may face regulatory scrutiny
  • engineer_a: Professional autonomy protected but reputation further damaged by appearing obstructionist
  • engineer_b: Ethical position validated but unable to provide needed safety service
  • public: Safety verification blocked, potential continued exposure to design risks

Learning Moment: Demonstrates conflict between professional autonomy and safety verification; shows limitations of consent-based peer review systems

Ethical Implications: Reveals tension between individual professional rights and collective safety responsibilities; shows gaps in voluntary peer review systems; highlights need for mandatory safety verification mechanisms

Discussion Prompts:
  • Should professional autonomy rights override safety verification needs?
  • What alternative mechanisms could ensure design safety when peer review is refused?
  • How can the profession balance protecting members' rights with public safety obligations?
Tension: medium Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/15#Event_Peer_Review_Impasse",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Should professional autonomy rights override safety verification needs?",
    "What alternative mechanisms could ensure design safety when peer review is refused?",
    "How can the profession balance protecting members\u0027 rights with public safety obligations?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Frustration for Owner unable to get safety verification; professional defensiveness from Engineer A; ethical concern from Engineer B about blocked safety review",
  "proeth-scenario:ethicalImplications": "Reveals tension between individual professional rights and collective safety responsibilities; shows gaps in voluntary peer review systems; highlights need for mandatory safety verification mechanisms",
  "proeth-scenario:learningMoment": "Demonstrates conflict between professional autonomy and safety verification; shows limitations of consent-based peer review systems",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Professional autonomy protected but reputation further damaged by appearing obstructionist",
    "engineer_b": "Ethical position validated but unable to provide needed safety service",
    "owner": "Cannot proceed with confidence on second tower, may face regulatory scrutiny",
    "public": "Safety verification blocked, potential continued exposure to design risks"
  },
  "proeth:activatesConstraint": [
    "Professional_Autonomy_Respect",
    "Safety_Verification_Blocked"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/15#Action_Refuse_Peer_Review_Consent__by_Engineer_A_",
  "proeth:causesStateChange": "Safety verification process blocked; alternative review methods must be considered; professional relationship tensions escalated",
  "proeth:createsObligation": [
    "Find_Alternative_Safety_Verification",
    "Respect_Professional_Rights",
    "Resolve_Design_Safety_Questions"
  ],
  "proeth:description": "Engineer A\u0027s refusal to consent to peer review creates a deadlock situation where the second tower\u0027s safety cannot be independently verified despite known risks from the first tower\u0027s design errors.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Owner agrees to notify Engineer A",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Peer Review Impasse"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: Significant design errors by Engineer A are discovered during construction of the first tower. This leads to the Owner's decision to retain Engineer B for peer review of the second tower

Necessary Factors (NESS):
  • Discovery of significant design errors in first tower
  • Owner's awareness of the errors
  • Existence of a second tower requiring review
Sufficient Factors:
  • Combination of discovered errors + Owner's loss of confidence in Engineer A + need to protect second tower project
Counterfactual Test: Without the discovery of design errors in the first tower, Owner would not have sought peer review services
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Design Errors Discovery
    Significant design errors by Engineer A discovered during first tower construction
  2. Owner Loss of Confidence
    Owner realizes Engineer A's work is unreliable
  3. Seek Peer Review Services
    Owner decides to retain Engineer B to review second tower plans
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/15#CausalChain_308632ad",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Significant design errors by Engineer A are discovered during construction of the first tower. This leads to the Owner\u0027s decision to retain Engineer B for peer review of the second tower",
  "proeth:causalSequence": [
    {
      "proeth:description": "Significant design errors by Engineer A discovered during first tower construction",
      "proeth:element": "Design Errors Discovery",
      "proeth:step": 1
    },
    {
      "proeth:description": "Owner realizes Engineer A\u0027s work is unreliable",
      "proeth:element": "Owner Loss of Confidence",
      "proeth:step": 2
    },
    {
      "proeth:description": "Owner decides to retain Engineer B to review second tower plans",
      "proeth:element": "Seek Peer Review Services",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Design Errors Discovery",
  "proeth:counterfactual": "Without the discovery of design errors in the first tower, Owner would not have sought peer review services",
  "proeth:effect": "Seek Peer Review Services",
  "proeth:necessaryFactors": [
    "Discovery of significant design errors in first tower",
    "Owner\u0027s awareness of the errors",
    "Existence of a second tower requiring review"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of discovered errors + Owner\u0027s loss of confidence in Engineer A + need to protect second tower project"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Owner initially instructs Engineer B to conduct the peer review without Engineer A's knowledge. Engineer B objects to conducting the peer review without Engineer A's knowledge

Necessary Factors (NESS):
  • Owner's request for secret review
  • Engineer B's ethical awareness
  • Professional standards requiring transparency
Sufficient Factors:
  • Engineer B's ethical principles + professional standards requiring colleague notification
Counterfactual Test: Without the request for secrecy, Engineer B would not have needed to refuse and insist on transparency
Responsibility Attribution:

Agent: Engineer B
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Request Secret Peer Review
    Owner instructs Engineer B to conduct peer review without Engineer A's knowledge
  2. Refuse Secret Review
    Engineer B objects and insists on transparency with Engineer A
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/15#CausalChain_862f77e1",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Owner initially instructs Engineer B to conduct the peer review without Engineer A\u0027s knowledge. Engineer B objects to conducting the peer review without Engineer A\u0027s knowledge",
  "proeth:causalSequence": [
    {
      "proeth:description": "Owner instructs Engineer B to conduct peer review without Engineer A\u0027s knowledge",
      "proeth:element": "Request Secret Peer Review",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B objects and insists on transparency with Engineer A",
      "proeth:element": "Refuse Secret Review",
      "proeth:step": 2
    }
  ],
  "proeth:cause": "Request Secret Peer Review",
  "proeth:counterfactual": "Without the request for secrecy, Engineer B would not have needed to refuse and insist on transparency",
  "proeth:effect": "Refuse Secret Review",
  "proeth:necessaryFactors": [
    "Owner\u0027s request for secret review",
    "Engineer B\u0027s ethical awareness",
    "Professional standards requiring transparency"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Engineer B\u0027s ethical principles + professional standards requiring colleague notification"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer B objects to conducting the peer review without Engineer A's knowledge and insists on transparency. Owner reluctantly consents to notifying Engineer A after Engineer B's objection

Necessary Factors (NESS):
  • Engineer B's firm refusal to proceed secretly
  • Owner's need for peer review to proceed
  • Owner's willingness to compromise
Sufficient Factors:
  • Engineer B's ethical stance + Owner's project dependency on peer review
Counterfactual Test: Without Engineer B's refusal, Owner would have proceeded with secret review
Responsibility Attribution:

Agent: Engineer B
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Refuse Secret Review
    Engineer B insists on transparency with Engineer A
  2. Owner Pressure vs Ethics
    Owner faces choice between transparency or finding another reviewer
  3. Agree to Notify Engineer
    Owner reluctantly consents to notifying Engineer A
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/15#CausalChain_7b320c64",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B objects to conducting the peer review without Engineer A\u0027s knowledge and insists on transparency. Owner reluctantly consents to notifying Engineer A after Engineer B\u0027s objection",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B insists on transparency with Engineer A",
      "proeth:element": "Refuse Secret Review",
      "proeth:step": 1
    },
    {
      "proeth:description": "Owner faces choice between transparency or finding another reviewer",
      "proeth:element": "Owner Pressure vs Ethics",
      "proeth:step": 2
    },
    {
      "proeth:description": "Owner reluctantly consents to notifying Engineer A",
      "proeth:element": "Agree to Notify Engineer",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Refuse Secret Review",
  "proeth:counterfactual": "Without Engineer B\u0027s refusal, Owner would have proceeded with secret review",
  "proeth:effect": "Agree to Notify Engineer",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s firm refusal to proceed secretly",
    "Owner\u0027s need for peer review to proceed",
    "Owner\u0027s willingness to compromise"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Engineer B\u0027s ethical stance + Owner\u0027s project dependency on peer review"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Owner consents to notifying Engineer A about the peer review. Engineer A objects to and refuses to consent to the peer review of their plans

Necessary Factors (NESS):
  • Engineer A being notified of peer review
  • Engineer A's professional pride/defensiveness
  • Engineer A's authority to refuse consent
Sufficient Factors:
  • Notification + Engineer A's defensive reaction + legal right to refuse
Counterfactual Test: If Engineer A had not been notified, they could not have refused consent
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Agree to Notify Engineer
    Owner consents to transparent peer review process
  2. Engineer A Notification
    Engineer A learns of planned peer review of second tower
  3. Refuse Peer Review Consent
    Engineer A objects to and refuses consent for peer review
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/15#CausalChain_27f978f9",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Owner consents to notifying Engineer A about the peer review. Engineer A objects to and refuses to consent to the peer review of their plans",
  "proeth:causalSequence": [
    {
      "proeth:description": "Owner consents to transparent peer review process",
      "proeth:element": "Agree to Notify Engineer",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A learns of planned peer review of second tower",
      "proeth:element": "Engineer A Notification",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A objects to and refuses consent for peer review",
      "proeth:element": "Refuse Peer Review Consent",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Agree to Notify Engineer",
  "proeth:counterfactual": "If Engineer A had not been notified, they could not have refused consent",
  "proeth:effect": "Refuse Peer Review Consent",
  "proeth:necessaryFactors": [
    "Engineer A being notified of peer review",
    "Engineer A\u0027s professional pride/defensiveness",
    "Engineer A\u0027s authority to refuse consent"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Notification + Engineer A\u0027s defensive reaction + legal right to refuse"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A's refusal to consent to peer review creates a deadlock situation where the second tower's safety cannot be verified

Necessary Factors (NESS):
  • Engineer A's refusal of consent
  • Legal/contractual requirement for Engineer A's consent
  • No alternative review mechanism available
Sufficient Factors:
  • Engineer A's refusal + legal consent requirement + lack of alternative verification path
Counterfactual Test: Without Engineer A's refusal, peer review could proceed and verify second tower safety
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Refuse Peer Review Consent
    Engineer A blocks peer review of second tower plans
  2. Legal Deadlock
    Owner cannot proceed with review due to consent requirement
  3. Peer Review Impasse
    Second tower safety verification becomes impossible
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/15#CausalChain_ab0e5fff",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A\u0027s refusal to consent to peer review creates a deadlock situation where the second tower\u0027s safety cannot be verified",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A blocks peer review of second tower plans",
      "proeth:element": "Refuse Peer Review Consent",
      "proeth:step": 1
    },
    {
      "proeth:description": "Owner cannot proceed with review due to consent requirement",
      "proeth:element": "Legal Deadlock",
      "proeth:step": 2
    },
    {
      "proeth:description": "Second tower safety verification becomes impossible",
      "proeth:element": "Peer Review Impasse",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Refuse Peer Review Consent",
  "proeth:counterfactual": "Without Engineer A\u0027s refusal, peer review could proceed and verify second tower safety",
  "proeth:effect": "Peer Review Impasse",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s refusal of consent",
    "Legal/contractual requirement for Engineer A\u0027s consent",
    "No alternative review mechanism available"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Engineer A\u0027s refusal + legal consent requirement + lack of alternative verification path"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (8)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
Engineer A notification after
Entity1 is after Entity2
Engineer B objection time:after
http://www.w3.org/2006/time#after
Engineer B objects to conducting the peer review without advising Engineer A. When Owner reluctantly...
design errors discovery before
Entity1 is before Entity2
peer review decision time:before
http://www.w3.org/2006/time#before
As the first tower is built, several significant design errors are discovered in the plans and desig...
Engineer B retention after
Entity1 is after Entity2
peer review decision time:after
http://www.w3.org/2006/time#after
Owner decides to obtain a peer review of the plans and design of Engineer A for the second tower and...
first tower construction before
Entity1 is before Entity2
second tower construction time:before
http://www.w3.org/2006/time#before
Owner is developing a site with two mirror-image towers to be built two years apart
design errors discovery during
Entity1 occurs entirely within the duration of Entity2
first tower construction time:intervalDuring
http://www.w3.org/2006/time#intervalDuring
As the first tower is built, several significant design errors are discovered
Engineer A objection after
Entity1 is after Entity2
Engineer A notification time:after
http://www.w3.org/2006/time#after
When Owner reluctantly consents to notifying Engineer A, Engineer A objects and refused to consent t...
independent external review before
Entity1 is before Entity2
joint venture invitation time:before
http://www.w3.org/2006/time#before
Engineer A was the lead engineer on an independent external review of an agency-prepared project... ...
reviewer selection before
Entity1 is before Entity2
confidentiality agreement time:before
http://www.w3.org/2006/time#before
When selected as a reviewer for the program, Engineer A contractually agreed not to disclose confide...
About Allen Relations & OWL-Time

Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.

Each relation includes both a ProEthica custom property and a time:* OWL-Time property for maximum compatibility.