23 entities 5 actions 6 events 5 causal chains 6 temporal relations
Timeline Overview
Action Event 11 sequenced markers
Engineer A Gains Committee Prominence After joining the committee; before the threat from Engineer B
Employer Embarrassment Perceived After Engineer A's public advocacy becomes visible; immediately before Engineer B's threat
Joining Citizens Committee Advocacy Early in the case, prior to any employer warning
Keeping Advocacy Statements General Throughout the advocacy period, concurrent with all public activities
Threatening Discharge for Advocacy After Engineer A's advocacy activities became publicly visible, prior to any discharge
Continuing Advocacy Despite Threat After receiving Engineer B's warning, as an anticipated future decision
Ethics Board Evaluating Engineer B Retrospective analysis in the case discussion section
Product Quality Decline Observed Prior to Engineer A's committee involvement; background condition
Engineer A's Employment Threatened Simultaneous with and immediately following Engineer B's threat
Engineer A's Advocacy Validated During/after NSPE Ethics Board evaluation; retrospective determination
OWL-Time Temporal Structure 6 relations time: = w3.org/2006/time
Case 61-10 ruling time:before Discussion analysis of current case
Engineer A joining the Citizens Committee and becoming a leading spokesman time:before Engineer B's threat of discharge
Engineer A's concern about inferior products time:before Engineer A joining the Citizens Committee
Engineer A's public advocacy (letters, legislative appearances) time:before Engineer B's warning
Engineer B's threat time:before Discussion/ethical analysis of the case
Engineer A's advocacy activities time:intervalOverlaps Engineer A's employment at XYZ Manufacturing
Extracted Actions (5)
Volitional professional decisions with intentions and ethical context

Description: Engineer A and the Citizens Committee deliberately chose to keep all public statements, letters, and legislative testimony general in scope, refraining from naming XYZ Manufacturing or any specific company or product. This was a conscious boundary-setting decision within their advocacy strategy.

Temporal Marker: Throughout the advocacy period, concurrent with all public activities

Mental State: deliberate and strategically cautious

Intended Outcome: Advocate for industry-wide quality standards without directly implicating or embarrassing any specific employer, thereby preserving the legitimacy and reach of the advocacy

Fulfills Obligations:
  • Duty as faithful agent or trustee to employer by not disclosing employer-specific information (Code Section 1)
  • Duty to public welfare through broad advocacy (Code Section 2, 2a, 2b)
  • Integrity in professional relations by not misrepresenting or unfairly targeting employers
Guided By Principles:
  • Integrity in professional conduct
  • Balance between public service and employer loyalty
  • Good faith in advocacy scope
  • Distinction between industry-wide critique and company-specific criticism
Required Capabilities:
Strategic communication and message framing Understanding of ethical boundaries between civic advocacy and employer disclosure Legislative and public testimony skills
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A and the Committee sought to advocate for systemic improvement in product quality without crossing into tortious or professionally improper territory such as defamation, unfair competitive disparagement, or breach of confidentiality obligations. The decision to remain general was both legally prudent and ethically deliberate, protecting the integrity of the advocacy while respecting limits on what engineers may publicly disclose.

Ethical Tension: Maximum public impact of advocacy (which might require naming specific offenders) vs. fairness, legal prudence, and professional restraint; transparency and specificity as virtues vs. the risk of harm to named parties without due process; the duty to inform the public fully vs. the duty to avoid misuse of professional knowledge.

Learning Significance: Demonstrates that ethical advocacy is not unlimited speech — engineers must calibrate how they communicate concerns to remain within professional and legal boundaries. Teaches the concept of responsible whistleblowing and public communication: being truthful and impactful without being reckless or unfair. Also shows that general advocacy can be fully legitimate and effective.

Stakes: If statements had named specific companies or products, Engineer A and the Committee could face defamation claims, professional discipline, or loss of public credibility. By remaining general, they preserve the advocacy's legitimacy but may reduce its immediate corrective force on specific bad actors.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Name specific companies and products in public statements and legislative testimony to maximize accountability pressure
  • Publish detailed technical reports with anonymized but traceable case studies that indirectly identify offenders
  • Limit advocacy entirely to closed professional forums such as engineering society meetings, avoiding all public-facing statements

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Action_Keeping_Advocacy_Statements_General",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Name specific companies and products in public statements and legislative testimony to maximize accountability pressure",
    "Publish detailed technical reports with anonymized but traceable case studies that indirectly identify offenders",
    "Limit advocacy entirely to closed professional forums such as engineering society meetings, avoiding all public-facing statements"
  ],
  "proeth-scenario:characterMotivation": "Engineer A and the Committee sought to advocate for systemic improvement in product quality without crossing into tortious or professionally improper territory such as defamation, unfair competitive disparagement, or breach of confidentiality obligations. The decision to remain general was both legally prudent and ethically deliberate, protecting the integrity of the advocacy while respecting limits on what engineers may publicly disclose.",
  "proeth-scenario:consequencesIfAlternative": [
    "Increased legal exposure to defamation suits; potential professional discipline; possible chilling effect on other engineers willing to advocate; but also potentially greater immediate corrective pressure on specific manufacturers",
    "Partial accountability with some legal protection; risks being decoded by industry insiders and still triggering employer retaliation; may be seen as disingenuous by legislators and the public",
    "Eliminates most employer retaliation risk and legal exposure but drastically reduces public influence; systemic change becomes unlikely; the advocacy fails to fulfill its public welfare purpose"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that ethical advocacy is not unlimited speech \u2014 engineers must calibrate how they communicate concerns to remain within professional and legal boundaries. Teaches the concept of responsible whistleblowing and public communication: being truthful and impactful without being reckless or unfair. Also shows that general advocacy can be fully legitimate and effective.",
  "proeth-scenario:ethicalTension": "Maximum public impact of advocacy (which might require naming specific offenders) vs. fairness, legal prudence, and professional restraint; transparency and specificity as virtues vs. the risk of harm to named parties without due process; the duty to inform the public fully vs. the duty to avoid misuse of professional knowledge.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "If statements had named specific companies or products, Engineer A and the Committee could face defamation claims, professional discipline, or loss of public credibility. By remaining general, they preserve the advocacy\u0027s legitimacy but may reduce its immediate corrective force on specific bad actors.",
  "proeth:description": "Engineer A and the Citizens Committee deliberately chose to keep all public statements, letters, and legislative testimony general in scope, refraining from naming XYZ Manufacturing or any specific company or product. This was a conscious boundary-setting decision within their advocacy strategy.",
  "proeth:foreseenUnintendedEffects": [
    "Employer may still perceive general advocacy as implicitly critical",
    "Limiting specificity may reduce persuasive impact on legislators or public"
  ],
  "proeth:fulfillsObligation": [
    "Duty as faithful agent or trustee to employer by not disclosing employer-specific information (Code Section 1)",
    "Duty to public welfare through broad advocacy (Code Section 2, 2a, 2b)",
    "Integrity in professional relations by not misrepresenting or unfairly targeting employers"
  ],
  "proeth:guidedByPrinciple": [
    "Integrity in professional conduct",
    "Balance between public service and employer loyalty",
    "Good faith in advocacy scope",
    "Distinction between industry-wide critique and company-specific criticism"
  ],
  "proeth:hasAgent": "Engineer A (Staff Engineer, XYZ Manufacturing Company) and Citizens Committee members",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Advocacy effectiveness vs. employer fidelity and professional integrity",
    "proeth:resolutionReasoning": "The committee resolved this by accepting reduced specificity as the cost of maintaining ethical integrity, preserving both their public welfare mission and their obligations as employees"
  },
  "proeth:hasMentalState": "deliberate and strategically cautious",
  "proeth:intendedOutcome": "Advocate for industry-wide quality standards without directly implicating or embarrassing any specific employer, thereby preserving the legitimacy and reach of the advocacy",
  "proeth:requiresCapability": [
    "Strategic communication and message framing",
    "Understanding of ethical boundaries between civic advocacy and employer disclosure",
    "Legislative and public testimony skills"
  ],
  "proeth:temporalMarker": "Throughout the advocacy period, concurrent with all public activities",
  "proeth:withinCompetence": true,
  "rdfs:label": "Keeping Advocacy Statements General"
}

Description: Engineer B, as Engineer A's supervisor, explicitly warned Engineer A that continued participation in the Citizens Committee's activities would result in his discharge, citing embarrassment to the employer. This was a deliberate managerial intervention intended to suppress Engineer A's external advocacy.

Temporal Marker: After Engineer A's advocacy activities became publicly visible, prior to any discharge

Mental State: deliberate and protective of employer interests

Intended Outcome: Protect XYZ Manufacturing Company from perceived public embarrassment by halting Engineer A's external advocacy activities

Fulfills Obligations:
  • Perceived duty as faithful agent to employer by attempting to protect employer reputation (Code Section 1, from employer's perspective)
Guided By Principles:
  • Employer loyalty (as Engineer B construed it)
  • Protection of company reputation
Required Capabilities:
Supervisory and personnel management authority Understanding of employer-employee professional obligations Knowledge of NSPE Code of Ethics provisions applicable to supervisors
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer B acted to protect XYZ Manufacturing's reputation and business interests, likely perceiving Engineer A's public advocacy as a reputational liability even if no specific company was named. Engineer B may also have been responding to pressure from senior management or interpreting his supervisory role as requiring enforcement of organizational loyalty. The threat may have reflected a genuine but ethically mistaken belief that employees owe their employers silence on industry-wide concerns.

Ethical Tension: Managerial authority and organizational loyalty vs. the professional rights and duties of subordinate engineers; the employer's legitimate interest in reputation management vs. the engineer's protected right to public interest advocacy; short-term organizational comfort vs. long-term professional integrity of the field.

Learning Significance: This action is the moral pivot of the case. It illustrates that supervisory authority has ethical limits — managers cannot legitimately use termination threats to suppress conduct that engineers are professionally obligated or entitled to perform. It teaches that coercive suppression of ethical advocacy is itself a Code violation, not merely a management prerogative. Students learn to recognize retaliatory threats as an independent ethical wrong.

Stakes: Engineer A's livelihood and career are directly threatened. The integrity of the engineering profession is at stake if such suppression is normalized. Engineer B's own professional standing and ethical compliance are at risk. XYZ Manufacturing risks fostering a culture that subordinates professional ethics to corporate convenience.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Engineer B meets with Engineer A privately to express the employer's concerns and seek a mutually acceptable boundary for his advocacy without threatening termination
  • Engineer B escalates the matter to XYZ Manufacturing's legal or HR department to assess whether Engineer A's activities constitute a policy violation before taking any action
  • Engineer B does nothing, choosing not to intervene in Engineer A's outside professional activities

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Action_Threatening_Discharge_for_Advocacy",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Engineer B meets with Engineer A privately to express the employer\u0027s concerns and seek a mutually acceptable boundary for his advocacy without threatening termination",
    "Engineer B escalates the matter to XYZ Manufacturing\u0027s legal or HR department to assess whether Engineer A\u0027s activities constitute a policy violation before taking any action",
    "Engineer B does nothing, choosing not to intervene in Engineer A\u0027s outside professional activities"
  ],
  "proeth-scenario:characterMotivation": "Engineer B acted to protect XYZ Manufacturing\u0027s reputation and business interests, likely perceiving Engineer A\u0027s public advocacy as a reputational liability even if no specific company was named. Engineer B may also have been responding to pressure from senior management or interpreting his supervisory role as requiring enforcement of organizational loyalty. The threat may have reflected a genuine but ethically mistaken belief that employees owe their employers silence on industry-wide concerns.",
  "proeth-scenario:consequencesIfAlternative": [
    "Preserves the employment relationship; may result in agreed refinements to Engineer A\u0027s advocacy approach; avoids the Code violation that the threat itself constitutes; models constructive conflict resolution",
    "A formal review might conclude Engineer A\u0027s general advocacy does not violate any policy, leading to no action; it depersonalizes the conflict but may still chill Engineer A\u0027s activities through bureaucratic pressure",
    "Engineer A continues advocacy without interference; XYZ Manufacturing\u0027s reputation concern goes unaddressed internally; no Code violation occurs on Engineer B\u0027s part; the case never escalates to an ethics board"
  ],
  "proeth-scenario:decisionSignificance": "This action is the moral pivot of the case. It illustrates that supervisory authority has ethical limits \u2014 managers cannot legitimately use termination threats to suppress conduct that engineers are professionally obligated or entitled to perform. It teaches that coercive suppression of ethical advocacy is itself a Code violation, not merely a management prerogative. Students learn to recognize retaliatory threats as an independent ethical wrong.",
  "proeth-scenario:ethicalTension": "Managerial authority and organizational loyalty vs. the professional rights and duties of subordinate engineers; the employer\u0027s legitimate interest in reputation management vs. the engineer\u0027s protected right to public interest advocacy; short-term organizational comfort vs. long-term professional integrity of the field.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A\u0027s livelihood and career are directly threatened. The integrity of the engineering profession is at stake if such suppression is normalized. Engineer B\u0027s own professional standing and ethical compliance are at risk. XYZ Manufacturing risks fostering a culture that subordinates professional ethics to corporate convenience.",
  "proeth:description": "Engineer B, as Engineer A\u0027s supervisor, explicitly warned Engineer A that continued participation in the Citizens Committee\u0027s activities would result in his discharge, citing embarrassment to the employer. This was a deliberate managerial intervention intended to suppress Engineer A\u0027s external advocacy.",
  "proeth:foreseenUnintendedEffects": [
    "Suppression of a subordinate engineer\u0027s Code-mandated civic engagement",
    "Potential chilling effect on other engineers\u0027 public welfare activities",
    "Own potential Code violation by threatening to preclude public welfare advocacy"
  ],
  "proeth:fulfillsObligation": [
    "Perceived duty as faithful agent to employer by attempting to protect employer reputation (Code Section 1, from employer\u0027s perspective)"
  ],
  "proeth:guidedByPrinciple": [
    "Employer loyalty (as Engineer B construed it)",
    "Protection of company reputation"
  ],
  "proeth:hasAgent": "Engineer B (Supervisor, XYZ Manufacturing Company)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Employer reputational protection vs. subordinate engineer\u0027s Code-protected civic advocacy",
    "proeth:resolutionReasoning": "Engineer B incorrectly prioritized employer reputational interests over the Code\u0027s hierarchy, which places public welfare as paramount; the ethics board concluded this constituted a Code violation because the threat was designed to preclude Code-consonant conduct by a subordinate engineer"
  },
  "proeth:hasMentalState": "deliberate and protective of employer interests",
  "proeth:intendedOutcome": "Protect XYZ Manufacturing Company from perceived public embarrassment by halting Engineer A\u0027s external advocacy activities",
  "proeth:requiresCapability": [
    "Supervisory and personnel management authority",
    "Understanding of employer-employee professional obligations",
    "Knowledge of NSPE Code of Ethics provisions applicable to supervisors"
  ],
  "proeth:temporalMarker": "After Engineer A\u0027s advocacy activities became publicly visible, prior to any discharge",
  "proeth:violatesObligation": [
    "Duty to have proper regard for public welfare (Code Section 2)",
    "Duty to treat public welfare as paramount (Code Section 2a)",
    "Duty to support constructive civic service by engineers (Code Section 2b)",
    "Integrity in professional relations by using coercive threat to suppress legitimate professional conduct (Code Section 1, applied to Engineer B\u0027s own conduct)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Threatening Discharge for Advocacy"
}

Description: Engineer A faced an implicit but critical decision point to either continue his Citizens Committee activities or cease them in response to Engineer B's discharge threat. The case structure and ethics board analysis treat continued advocacy as the ethically justified course, placing Engineer A's employment at personal risk.

Temporal Marker: After receiving Engineer B's warning, as an anticipated future decision

Mental State: deliberate under duress, values-driven

Intended Outcome: Fulfill Code-mandated public welfare obligations despite personal professional risk, continuing to advocate for industry-wide product quality standards

Fulfills Obligations:
  • Duty to public welfare as paramount (Code Section 2a)
  • Duty to seek constructive civic service opportunities (Code Section 2b)
  • Duty to have proper regard for public safety, health, and welfare (Code Section 2)
  • Integrity and adherence to highest professional standards (Code Section 1)
Guided By Principles:
  • Public welfare paramount over personal professional security
  • Professional integrity requires acting on sincere good-faith beliefs about public interest
  • Civic engagement as a professional duty, not merely a personal choice
Required Capabilities:
Moral courage to act on professional obligations under coercive pressure Continued public communication and legislative advocacy skills Judgment to maintain appropriate boundaries in public statements
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A's continued advocacy reflects his conviction that his professional duty to the public welfare outweighs the personal cost of potential job loss. He may also have been motivated by principle — capitulating to an improper threat would itself be an ethical compromise, validating the suppression of legitimate professional advocacy. His role as a leading spokesman may have heightened his sense of responsibility to the Committee and its mission.

Ethical Tension: Personal financial security and career continuity vs. professional integrity and public duty; the rational self-interest of compliance vs. the ethical imperative of resistance to improper coercion; individual vulnerability vs. collective professional responsibility.

Learning Significance: This is the case's central courage moment — the point at which abstract ethical commitments must be tested against concrete personal cost. It teaches that ethical behavior is not merely intellectual assent to principles but action under pressure. Students learn to evaluate what it means to 'hold the line' professionally and to recognize that the NSPE Code is meant to protect engineers who do so.

Stakes: Engineer A risks termination, loss of income, potential difficulty finding equivalent employment, and reputational harm within XYZ Manufacturing. If he ceases advocacy, the Citizens Committee loses a key voice and the broader public welfare goal is undermined. If he continues, he may become a test case for professional rights — with significant personal cost.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Cease all Citizens Committee activities immediately upon receiving Engineer B's threat, prioritizing job security
  • Resign from XYZ Manufacturing voluntarily before being discharged, to continue advocacy from a position free of employer constraint
  • Seek legal counsel and formally notify Engineer B and XYZ Manufacturing that the termination threat may itself constitute an improper act, without yet deciding whether to continue or cease advocacy

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Action_Continuing_Advocacy_Despite_Threat",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Cease all Citizens Committee activities immediately upon receiving Engineer B\u0027s threat, prioritizing job security",
    "Resign from XYZ Manufacturing voluntarily before being discharged, to continue advocacy from a position free of employer constraint",
    "Seek legal counsel and formally notify Engineer B and XYZ Manufacturing that the termination threat may itself constitute an improper act, without yet deciding whether to continue or cease advocacy"
  ],
  "proeth-scenario:characterMotivation": "Engineer A\u0027s continued advocacy reflects his conviction that his professional duty to the public welfare outweighs the personal cost of potential job loss. He may also have been motivated by principle \u2014 capitulating to an improper threat would itself be an ethical compromise, validating the suppression of legitimate professional advocacy. His role as a leading spokesman may have heightened his sense of responsibility to the Committee and its mission.",
  "proeth-scenario:consequencesIfAlternative": [
    "Engineer A retains his job but abandons a professionally justified activity under coercion; the suppression succeeds and may embolden similar behavior by other employers; Engineer A may experience lasting professional regret",
    "Engineer A gains full freedom to advocate but bears immediate financial hardship; the advocacy continues at personal sacrifice; this action may itself be seen as a principled statement but removes the case\u0027s central employment-rights tension",
    "Introduces a legal and procedural dimension that may deter Engineer B from following through; buys time for Engineer A; may result in a negotiated resolution but also risks escalating the conflict and hardening positions"
  ],
  "proeth-scenario:decisionSignificance": "This is the case\u0027s central courage moment \u2014 the point at which abstract ethical commitments must be tested against concrete personal cost. It teaches that ethical behavior is not merely intellectual assent to principles but action under pressure. Students learn to evaluate what it means to \u0027hold the line\u0027 professionally and to recognize that the NSPE Code is meant to protect engineers who do so.",
  "proeth-scenario:ethicalTension": "Personal financial security and career continuity vs. professional integrity and public duty; the rational self-interest of compliance vs. the ethical imperative of resistance to improper coercion; individual vulnerability vs. collective professional responsibility.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A risks termination, loss of income, potential difficulty finding equivalent employment, and reputational harm within XYZ Manufacturing. If he ceases advocacy, the Citizens Committee loses a key voice and the broader public welfare goal is undermined. If he continues, he may become a test case for professional rights \u2014 with significant personal cost.",
  "proeth:description": "Engineer A faced an implicit but critical decision point to either continue his Citizens Committee activities or cease them in response to Engineer B\u0027s discharge threat. The case structure and ethics board analysis treat continued advocacy as the ethically justified course, placing Engineer A\u0027s employment at personal risk.",
  "proeth:foreseenUnintendedEffects": [
    "Real and acknowledged risk of discharge",
    "Code cannot protect Engineer A from employer punitive action since Code applies only to individual engineers, not companies",
    "Potential to inspire or embolden other engineers in similar advocacy"
  ],
  "proeth:fulfillsObligation": [
    "Duty to public welfare as paramount (Code Section 2a)",
    "Duty to seek constructive civic service opportunities (Code Section 2b)",
    "Duty to have proper regard for public safety, health, and welfare (Code Section 2)",
    "Integrity and adherence to highest professional standards (Code Section 1)"
  ],
  "proeth:guidedByPrinciple": [
    "Public welfare paramount over personal professional security",
    "Professional integrity requires acting on sincere good-faith beliefs about public interest",
    "Civic engagement as a professional duty, not merely a personal choice"
  ],
  "proeth:hasAgent": "Engineer A (Staff Engineer, XYZ Manufacturing Company)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Ethical duty to public welfare vs. personal employment security",
    "proeth:resolutionReasoning": "The ethics board\u0027s analysis implies that the Code-consistent resolution is to continue advocacy, accepting personal risk as the price of professional integrity, while recognizing the Code\u0027s limitation in protecting engineers from corporate retaliation"
  },
  "proeth:hasMentalState": "deliberate under duress, values-driven",
  "proeth:intendedOutcome": "Fulfill Code-mandated public welfare obligations despite personal professional risk, continuing to advocate for industry-wide product quality standards",
  "proeth:requiresCapability": [
    "Moral courage to act on professional obligations under coercive pressure",
    "Continued public communication and legislative advocacy skills",
    "Judgment to maintain appropriate boundaries in public statements"
  ],
  "proeth:temporalMarker": "After receiving Engineer B\u0027s warning, as an anticipated future decision",
  "proeth:violatesObligation": [
    "Potential practical tension with employer loyalty obligation (Code Section 1), though ethics board found advocacy did not constitute a substantive violation given its general, non-company-specific nature"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Continuing Advocacy Despite Threat"
}

Description: The NSPE ethics board made a deliberate analytical decision to evaluate Engineer B's conduct as an independent potential Code violation, rather than limiting its review solely to the question of whether Engineer A's advocacy was permissible. This framing choice broadened the ethical accountability of the case.

Temporal Marker: Retrospective analysis in the case discussion section

Mental State: deliberate and principled institutional judgment

Intended Outcome: Establish that the Code's public welfare obligations bind supervisors and managers as individual engineers, and that using supervisory authority to suppress Code-mandated advocacy is itself a Code violation

Fulfills Obligations:
  • Institutional duty to interpret and apply Code of Ethics comprehensively
  • Duty to protect the integrity of public welfare obligations across all engineering roles
  • Duty to provide guidance that deters Code violations by engineers in supervisory positions
Guided By Principles:
  • Code applies to all individual engineers regardless of managerial role
  • Public welfare obligations cannot be subordinated to employer loyalty even by supervisors
  • Institutional integrity requires addressing all Code violations identified in a case, not only those of the primary subject
Required Capabilities:
Authoritative interpretation of NSPE Code of Ethics Ability to distinguish between employer business decisions and individual engineer ethical obligations Institutional judgment to set precedent through case analysis
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: The NSPE ethics board was motivated by a commitment to comprehensive ethical analysis — recognizing that a case involving potential retaliation against an engineer for ethical conduct necessarily raises questions about the retaliating party's own compliance with the Code. The board may also have been motivated by a desire to send a clear institutional signal that supervisory roles do not exempt engineers from professional ethics obligations.

Ethical Tension: The scope of ethics review (narrow adjudication of the presenting question vs. broader accountability for all parties); the risk of overreach in evaluating conduct not formally submitted for review vs. the risk of moral incompleteness by ignoring an apparent violation; institutional caution vs. professional integrity.

Learning Significance: Teaches students that ethical analysis in professional contexts is not purely reactive or narrowly scoped — reviewers have a responsibility to identify ethical issues that arise from the full facts, even if not explicitly raised by the parties. It also demonstrates that authority figures (supervisors, managers) are fully subject to the same professional codes as those they supervise, and that coercion of ethical conduct is itself a recognized category of Code violation.

Stakes: The board's framing choice determines whether the case produces one or two ethical lessons. A narrow ruling validates Engineer A but leaves Engineer B's conduct unexamined, potentially signaling that supervisory retaliation is a gray area. The broader ruling establishes clear precedent that retaliatory threats violate the Code, protecting future engineers in similar situations.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Limit the ethics opinion solely to whether Engineer A's advocacy was permissible under the Code, declining to evaluate Engineer B's conduct as outside the scope of the submission
  • Refer Engineer B's conduct to a separate disciplinary process rather than addressing it within the same opinion, treating it as a distinct matter requiring its own formal complaint
  • Issue a general advisory opinion about the permissibility of engineer advocacy without addressing the specific conduct of either Engineer A or Engineer B by role

Narrative Role: resolution

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Action_Ethics_Board_Evaluating_Engineer_B",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Limit the ethics opinion solely to whether Engineer A\u0027s advocacy was permissible under the Code, declining to evaluate Engineer B\u0027s conduct as outside the scope of the submission",
    "Refer Engineer B\u0027s conduct to a separate disciplinary process rather than addressing it within the same opinion, treating it as a distinct matter requiring its own formal complaint",
    "Issue a general advisory opinion about the permissibility of engineer advocacy without addressing the specific conduct of either Engineer A or Engineer B by role"
  ],
  "proeth-scenario:characterMotivation": "The NSPE ethics board was motivated by a commitment to comprehensive ethical analysis \u2014 recognizing that a case involving potential retaliation against an engineer for ethical conduct necessarily raises questions about the retaliating party\u0027s own compliance with the Code. The board may also have been motivated by a desire to send a clear institutional signal that supervisory roles do not exempt engineers from professional ethics obligations.",
  "proeth-scenario:consequencesIfAlternative": [
    "The opinion is narrower and less precedentially useful; Engineer B\u0027s conduct escapes formal ethical scrutiny; future engineers facing similar threats receive less institutional protection; the case\u0027s full ethical complexity is underexplored",
    "Engineer B\u0027s accountability is preserved but deferred; the procedural separation may reduce the opinion\u0027s immediate impact; the dual-track approach may be seen as more fair to Engineer B but less efficient as a teaching instrument",
    "The opinion provides useful general guidance but fails to model how ethics analysis applies to concrete conduct; it may be less persuasive to practitioners and less effective as a case study for ethics education"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that ethical analysis in professional contexts is not purely reactive or narrowly scoped \u2014 reviewers have a responsibility to identify ethical issues that arise from the full facts, even if not explicitly raised by the parties. It also demonstrates that authority figures (supervisors, managers) are fully subject to the same professional codes as those they supervise, and that coercion of ethical conduct is itself a recognized category of Code violation.",
  "proeth-scenario:ethicalTension": "The scope of ethics review (narrow adjudication of the presenting question vs. broader accountability for all parties); the risk of overreach in evaluating conduct not formally submitted for review vs. the risk of moral incompleteness by ignoring an apparent violation; institutional caution vs. professional integrity.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "The board\u0027s framing choice determines whether the case produces one or two ethical lessons. A narrow ruling validates Engineer A but leaves Engineer B\u0027s conduct unexamined, potentially signaling that supervisory retaliation is a gray area. The broader ruling establishes clear precedent that retaliatory threats violate the Code, protecting future engineers in similar situations.",
  "proeth:description": "The NSPE ethics board made a deliberate analytical decision to evaluate Engineer B\u0027s conduct as an independent potential Code violation, rather than limiting its review solely to the question of whether Engineer A\u0027s advocacy was permissible. This framing choice broadened the ethical accountability of the case.",
  "proeth:foreseenUnintendedEffects": [
    "Creates precedent that engineering supervisors cannot use managerial authority to suppress subordinates\u0027 public welfare advocacy",
    "May create tension with employer authority structures in engineering workplaces",
    "Clarifies that Code obligations are personal and cannot be subordinated to managerial role"
  ],
  "proeth:fulfillsObligation": [
    "Institutional duty to interpret and apply Code of Ethics comprehensively",
    "Duty to protect the integrity of public welfare obligations across all engineering roles",
    "Duty to provide guidance that deters Code violations by engineers in supervisory positions"
  ],
  "proeth:guidedByPrinciple": [
    "Code applies to all individual engineers regardless of managerial role",
    "Public welfare obligations cannot be subordinated to employer loyalty even by supervisors",
    "Institutional integrity requires addressing all Code violations identified in a case, not only those of the primary subject"
  ],
  "proeth:hasAgent": "NSPE Ethics Board (Institutional deliberative body)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Narrow case resolution vs. comprehensive ethical accountability",
    "proeth:resolutionReasoning": "The board resolved in favor of comprehensive analysis, consistent with its institutional mandate to uphold the Code\u0027s public welfare primacy and to ensure that supervisory authority cannot be weaponized against Code-mandated professional conduct"
  },
  "proeth:hasMentalState": "deliberate and principled institutional judgment",
  "proeth:intendedOutcome": "Establish that the Code\u0027s public welfare obligations bind supervisors and managers as individual engineers, and that using supervisory authority to suppress Code-mandated advocacy is itself a Code violation",
  "proeth:requiresCapability": [
    "Authoritative interpretation of NSPE Code of Ethics",
    "Ability to distinguish between employer business decisions and individual engineer ethical obligations",
    "Institutional judgment to set precedent through case analysis"
  ],
  "proeth:temporalMarker": "Retrospective analysis in the case discussion section",
  "proeth:withinCompetence": true,
  "rdfs:label": "Ethics Board Evaluating Engineer B"
}

Description: Engineer A voluntarily joined a cross-company group of engineers concerned about inferior commercial products and assumed a leading spokesman role for the Citizens Committee for Quality Products. This was a deliberate professional and civic commitment beyond his employment duties.

Temporal Marker: Early in the case, prior to any employer warning

Mental State: deliberate and principled

Intended Outcome: Raise awareness of inadequate engineering in commercial products and advocate for industry-wide quality standards in the public interest

Fulfills Obligations:
  • Duty to public welfare as paramount (Code Section 2a)
  • Duty to seek opportunities for constructive civic service (Code Section 2b)
  • Duty to have proper regard for safety, health, and welfare of the public (Code Section 2)
Guided By Principles:
  • Public welfare paramount
  • Civic engagement as professional duty
  • Integrity in professional relations
  • Good faith advocacy for societal benefit
Required Capabilities:
Engineering judgment regarding product quality and durability Public communication and advocacy skills Ability to distinguish between employer-specific criticism and industry-wide advocacy
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A was driven by genuine professional concern over a systemic decline in product quality across the industry, believing that inadequate engineering practices posed risks to the public. He sought collective civic action as a means of amplifying his concerns beyond what individual complaint within his employer could achieve, and likely felt a professional obligation rooted in the NSPE Code's emphasis on public welfare.

Ethical Tension: Loyalty to employer vs. broader professional duty to public welfare; individual career security vs. collective civic responsibility; staying within the conventional boundaries of employment vs. exercising independent professional judgment in the public interest.

Learning Significance: Illustrates that engineers have professional identities and obligations that extend beyond their employment relationship, and that participation in civic or professional advocacy bodies is a legitimate — and sometimes obligatory — expression of those obligations. Teaches students to distinguish between employee loyalty and abdication of professional responsibility.

Stakes: Engineer A's career standing and relationship with XYZ Manufacturing are placed at latent risk from the outset. The public stands to benefit or lose depending on whether advocacy of this kind is normalized or suppressed. The credibility and influence of the Citizens Committee depends on the quality of its membership.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Raise quality concerns exclusively through internal channels at XYZ Manufacturing and decline external involvement
  • Participate in the Citizens Committee as a passive member without assuming a leadership or spokesman role
  • Report concerns to a professional engineering society or regulatory body rather than a citizen advocacy group

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Action_Joining_Citizens_Committee_Advocacy",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Raise quality concerns exclusively through internal channels at XYZ Manufacturing and decline external involvement",
    "Participate in the Citizens Committee as a passive member without assuming a leadership or spokesman role",
    "Report concerns to a professional engineering society or regulatory body rather than a citizen advocacy group"
  ],
  "proeth-scenario:characterMotivation": "Engineer A was driven by genuine professional concern over a systemic decline in product quality across the industry, believing that inadequate engineering practices posed risks to the public. He sought collective civic action as a means of amplifying his concerns beyond what individual complaint within his employer could achieve, and likely felt a professional obligation rooted in the NSPE Code\u0027s emphasis on public welfare.",
  "proeth-scenario:consequencesIfAlternative": [
    "Internal complaints may be ignored or suppressed by management; the systemic industry-wide problem goes unaddressed; Engineer A avoids immediate employment risk but potentially fails his broader professional duty",
    "The Citizens Committee loses a credible technical voice; Engineer A reduces his personal exposure but diminishes the group\u0027s effectiveness; the ethical tension with his employer may still arise but at lower intensity",
    "Regulatory or professional society channels may move slowly or lack public visibility; the advocacy may be more formally protected but less publicly impactful; Engineer A\u0027s employer may still object"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that engineers have professional identities and obligations that extend beyond their employment relationship, and that participation in civic or professional advocacy bodies is a legitimate \u2014 and sometimes obligatory \u2014 expression of those obligations. Teaches students to distinguish between employee loyalty and abdication of professional responsibility.",
  "proeth-scenario:ethicalTension": "Loyalty to employer vs. broader professional duty to public welfare; individual career security vs. collective civic responsibility; staying within the conventional boundaries of employment vs. exercising independent professional judgment in the public interest.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Engineer A\u0027s career standing and relationship with XYZ Manufacturing are placed at latent risk from the outset. The public stands to benefit or lose depending on whether advocacy of this kind is normalized or suppressed. The credibility and influence of the Citizens Committee depends on the quality of its membership.",
  "proeth:description": "Engineer A voluntarily joined a cross-company group of engineers concerned about inferior commercial products and assumed a leading spokesman role for the Citizens Committee for Quality Products. This was a deliberate professional and civic commitment beyond his employment duties.",
  "proeth:foreseenUnintendedEffects": [
    "Potential perception of disloyalty or embarrassment to employer",
    "Risk of professional retaliation from employer"
  ],
  "proeth:fulfillsObligation": [
    "Duty to public welfare as paramount (Code Section 2a)",
    "Duty to seek opportunities for constructive civic service (Code Section 2b)",
    "Duty to have proper regard for safety, health, and welfare of the public (Code Section 2)"
  ],
  "proeth:guidedByPrinciple": [
    "Public welfare paramount",
    "Civic engagement as professional duty",
    "Integrity in professional relations",
    "Good faith advocacy for societal benefit"
  ],
  "proeth:hasAgent": "Engineer A (Staff Engineer, XYZ Manufacturing Company)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Public welfare advocacy vs. employer loyalty and job security",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by prioritizing public welfare as paramount per the Code, while mitigating employer conflict by keeping advocacy general and not naming specific companies or products"
  },
  "proeth:hasMentalState": "deliberate and principled",
  "proeth:intendedOutcome": "Raise awareness of inadequate engineering in commercial products and advocate for industry-wide quality standards in the public interest",
  "proeth:requiresCapability": [
    "Engineering judgment regarding product quality and durability",
    "Public communication and advocacy skills",
    "Ability to distinguish between employer-specific criticism and industry-wide advocacy"
  ],
  "proeth:temporalMarker": "Early in the case, prior to any employer warning",
  "proeth:violatesObligation": [
    "Potential tension with duty as faithful agent or trustee to employer (Code Section 1), though not a direct violation since no employer-specific information was disclosed"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Joining Citizens Committee Advocacy"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changes

Description: A discernible trend toward inferior commercial products emerges in the manufacturing sector, observable to engineers working within the industry. This decline becomes the foundational condition that motivates Engineer A's subsequent advocacy activities.

Temporal Marker: Prior to Engineer A's committee involvement; background condition

Activates Constraints:
  • PublicWelfare_Protection_Constraint
  • Engineer_Competence_Obligation
  • Professional_Honesty_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A experiences professional frustration and moral unease; colleagues may feel complicit or helpless; management may be indifferent or defensive; consumers are unaware but vulnerable

Stakeholder Consequences:
  • engineer_a: Moral distress and professional dissatisfaction; sense of obligation to act
  • general_public: Exposed to inferior products without knowledge or recourse; safety and economic interests at risk
  • industry: Reputational risk if trend becomes public; potential regulatory scrutiny
  • xyz_manufacturing: Implicitly part of the trend Engineer A observes, creating internal tension

Learning Moment: Illustrates how systemic problems in an industry create ethical obligations for individual engineers; demonstrates that awareness of public harm — even diffuse, gradual harm — can trigger professional duty to act. Students should recognize that engineering ethics is not only about acute crises but also chronic, structural failures.

Ethical Implications: Reveals the tension between loyalty to employer and duty to the public; raises questions about the scope of professional responsibility beyond one's immediate workplace; highlights the NSPE principle that engineers must hold public safety and welfare paramount

Discussion Prompts:
  • At what point does an engineer's awareness of a quality trend become an ethical obligation to act publicly?
  • Is a single engineer responsible for industry-wide failures, or does collective action require collective responsibility?
  • How should engineers weigh the risk of being wrong about a trend against the risk of staying silent?
Tension: low Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Event_Product_Quality_Decline_Observed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what point does an engineer\u0027s awareness of a quality trend become an ethical obligation to act publicly?",
    "Is a single engineer responsible for industry-wide failures, or does collective action require collective responsibility?",
    "How should engineers weigh the risk of being wrong about a trend against the risk of staying silent?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Engineer A experiences professional frustration and moral unease; colleagues may feel complicit or helpless; management may be indifferent or defensive; consumers are unaware but vulnerable",
  "proeth-scenario:ethicalImplications": "Reveals the tension between loyalty to employer and duty to the public; raises questions about the scope of professional responsibility beyond one\u0027s immediate workplace; highlights the NSPE principle that engineers must hold public safety and welfare paramount",
  "proeth-scenario:learningMoment": "Illustrates how systemic problems in an industry create ethical obligations for individual engineers; demonstrates that awareness of public harm \u2014 even diffuse, gradual harm \u2014 can trigger professional duty to act. Students should recognize that engineering ethics is not only about acute crises but also chronic, structural failures.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Moral distress and professional dissatisfaction; sense of obligation to act",
    "general_public": "Exposed to inferior products without knowledge or recourse; safety and economic interests at risk",
    "industry": "Reputational risk if trend becomes public; potential regulatory scrutiny",
    "xyz_manufacturing": "Implicitly part of the trend Engineer A observes, creating internal tension"
  },
  "proeth:activatesConstraint": [
    "PublicWelfare_Protection_Constraint",
    "Engineer_Competence_Obligation",
    "Professional_Honesty_Constraint"
  ],
  "proeth:causesStateChange": "Industry quality baseline degrades; engineers with knowledge of standards become aware of gap between acceptable and actual product quality; conditions for whistleblowing concern are established",
  "proeth:createsObligation": [
    "Engineer_Awareness_Of_Public_Risk",
    "Potential_Duty_To_Speak_Out",
    "Professional_Vigilance_Obligation"
  ],
  "proeth:description": "A discernible trend toward inferior commercial products emerges in the manufacturing sector, observable to engineers working within the industry. This decline becomes the foundational condition that motivates Engineer A\u0027s subsequent advocacy activities.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to Engineer A\u0027s committee involvement; background condition",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Product Quality Decline Observed"
}

Description: As a result of his sustained participation in the Citizens Committee for Quality Products, Engineer A rises to become a leading spokesman for the group. This prominence amplifies his public visibility and correspondingly increases his exposure to employer retaliation.

Temporal Marker: After joining the committee; before the threat from Engineer B

Activates Constraints:
  • Employer_Awareness_Risk_Constraint
  • Professional_Reputation_Visibility_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A likely feels a sense of purpose and validation; committee members may feel emboldened; XYZ management may feel increasing discomfort as Engineer A's profile rises

Stakeholder Consequences:
  • engineer_a: Increased influence but also increased professional vulnerability; personal identity becomes tied to advocacy role
  • citizens_committee: Gains credibility and reach through a recognized spokesman
  • xyz_manufacturing: Risk of public association between Engineer A's advocacy and company reputation grows
  • engineer_b: Becomes more aware of Engineer A's external activities; pressure to respond increases

Learning Moment: Shows that professional advocacy carries escalating personal risk as visibility increases; students should understand that ethical courage often requires accepting greater exposure the more effective one becomes. Prominence in public advocacy is not ethically neutral — it changes the stakes for all parties.

Ethical Implications: Highlights the tension between freedom of professional expression and employer loyalty; raises questions about whether effectiveness in advocacy creates greater ethical scrutiny; illustrates how visibility amplifies both impact and vulnerability in whistleblowing-adjacent situations

Discussion Prompts:
  • Does an engineer's growing public prominence change their ethical obligations regarding how they frame their advocacy?
  • At what point does an employer have a legitimate interest in an employee's external professional activities?
  • How should Engineer A have anticipated and prepared for the risks that came with becoming a leading spokesman?
Tension: medium Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Event_Engineer_A_Gains_Committee_Prominence",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does an engineer\u0027s growing public prominence change their ethical obligations regarding how they frame their advocacy?",
    "At what point does an employer have a legitimate interest in an employee\u0027s external professional activities?",
    "How should Engineer A have anticipated and prepared for the risks that came with becoming a leading spokesman?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A likely feels a sense of purpose and validation; committee members may feel emboldened; XYZ management may feel increasing discomfort as Engineer A\u0027s profile rises",
  "proeth-scenario:ethicalImplications": "Highlights the tension between freedom of professional expression and employer loyalty; raises questions about whether effectiveness in advocacy creates greater ethical scrutiny; illustrates how visibility amplifies both impact and vulnerability in whistleblowing-adjacent situations",
  "proeth-scenario:learningMoment": "Shows that professional advocacy carries escalating personal risk as visibility increases; students should understand that ethical courage often requires accepting greater exposure the more effective one becomes. Prominence in public advocacy is not ethically neutral \u2014 it changes the stakes for all parties.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "citizens_committee": "Gains credibility and reach through a recognized spokesman",
    "engineer_a": "Increased influence but also increased professional vulnerability; personal identity becomes tied to advocacy role",
    "engineer_b": "Becomes more aware of Engineer A\u0027s external activities; pressure to respond increases",
    "xyz_manufacturing": "Risk of public association between Engineer A\u0027s advocacy and company reputation grows"
  },
  "proeth:activatesConstraint": [
    "Employer_Awareness_Risk_Constraint",
    "Professional_Reputation_Visibility_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/82#Action_Joining_Citizens_Committee_Advocacy",
  "proeth:causesStateChange": "Engineer A transitions from anonymous participant to named public figure within the advocacy movement; employer risk of associating Engineer A\u0027s views with XYZ Manufacturing increases; Engineer A\u0027s statements carry greater weight and receive broader attention",
  "proeth:createsObligation": [
    "Maintain_Accuracy_In_Public_Statements",
    "Avoid_Employer_Identification_In_Advocacy"
  ],
  "proeth:description": "As a result of his sustained participation in the Citizens Committee for Quality Products, Engineer A rises to become a leading spokesman for the group. This prominence amplifies his public visibility and correspondingly increases his exposure to employer retaliation.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After joining the committee; before the threat from Engineer B",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Engineer A Gains Committee Prominence"
}

Description: XYZ Manufacturing, through Engineer B, perceives Engineer A's public advocacy activities as embarrassing to the company, even though no specific companies or products were named. This perception — whether accurate or not — becomes the triggering condition for the retaliatory threat.

Temporal Marker: After Engineer A's public advocacy becomes visible; immediately before Engineer B's threat

Activates Constraints:
  • Employer_Retaliation_Risk_Constraint
  • Employee_Rights_Protection_Constraint
  • Supervisor_Authority_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer B may feel institutional pressure and personal irritation; XYZ leadership may feel defensive and exposed; Engineer A may be unaware of the perception forming against him

Stakeholder Consequences:
  • engineer_a: Professional standing at XYZ becomes precarious without his knowledge
  • engineer_b: Feels compelled to act to protect company reputation, risking his own ethical standing
  • xyz_manufacturing: Organizational reputation concern overrides consideration of employee rights
  • citizens_committee: Indirectly implicated in triggering an employment conflict

Learning Moment: Demonstrates how institutional self-interest can reframe ethical advocacy as disloyalty; students should examine how the framing of 'embarrassment' shifts moral responsibility. The perception of harm — not actual harm — becomes the basis for retaliation, which is itself an ethical failure.

Ethical Implications: Reveals the conflict between institutional reputation management and individual professional rights; exposes how power dynamics within organizations can suppress legitimate public interest advocacy; raises questions about whether reputational harm is a cognizable injury when advocacy is truthful and general

Discussion Prompts:
  • Is an employer's perception of embarrassment sufficient justification for restricting an employee's lawful public advocacy?
  • How does the absence of named companies in Engineer A's advocacy affect the legitimacy of Engineer B's concern?
  • What does it reveal about organizational ethics when institutions respond to criticism by silencing critics rather than examining the underlying concern?
Crisis / Turning Point Tension: high Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Event_Employer_Embarrassment_Perceived",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is an employer\u0027s perception of embarrassment sufficient justification for restricting an employee\u0027s lawful public advocacy?",
    "How does the absence of named companies in Engineer A\u0027s advocacy affect the legitimacy of Engineer B\u0027s concern?",
    "What does it reveal about organizational ethics when institutions respond to criticism by silencing critics rather than examining the underlying concern?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer B may feel institutional pressure and personal irritation; XYZ leadership may feel defensive and exposed; Engineer A may be unaware of the perception forming against him",
  "proeth-scenario:ethicalImplications": "Reveals the conflict between institutional reputation management and individual professional rights; exposes how power dynamics within organizations can suppress legitimate public interest advocacy; raises questions about whether reputational harm is a cognizable injury when advocacy is truthful and general",
  "proeth-scenario:learningMoment": "Demonstrates how institutional self-interest can reframe ethical advocacy as disloyalty; students should examine how the framing of \u0027embarrassment\u0027 shifts moral responsibility. The perception of harm \u2014 not actual harm \u2014 becomes the basis for retaliation, which is itself an ethical failure.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "citizens_committee": "Indirectly implicated in triggering an employment conflict",
    "engineer_a": "Professional standing at XYZ becomes precarious without his knowledge",
    "engineer_b": "Feels compelled to act to protect company reputation, risking his own ethical standing",
    "xyz_manufacturing": "Organizational reputation concern overrides consideration of employee rights"
  },
  "proeth:activatesConstraint": [
    "Employer_Retaliation_Risk_Constraint",
    "Employee_Rights_Protection_Constraint",
    "Supervisor_Authority_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/82#Action_Joining_Citizens_Committee_Advocacy",
  "proeth:causesStateChange": "Relationship between Engineer A and XYZ management shifts from professional to adversarial; Engineer A\u0027s employment security becomes uncertain; the advocacy issue is now framed internally as a loyalty/embarrassment problem rather than a quality/ethics problem",
  "proeth:createsObligation": [
    "Engineer_B_Duty_To_Act_Within_Code",
    "XYZ_Management_Duty_Not_To_Retaliate_For_Lawful_Advocacy"
  ],
  "proeth:description": "XYZ Manufacturing, through Engineer B, perceives Engineer A\u0027s public advocacy activities as embarrassing to the company, even though no specific companies or products were named. This perception \u2014 whether accurate or not \u2014 becomes the triggering condition for the retaliatory threat.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer A\u0027s public advocacy becomes visible; immediately before Engineer B\u0027s threat",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Employer Embarrassment Perceived"
}

Description: As a direct result of Engineer B's threat of discharge, Engineer A's employment status becomes precarious and uncertain. This is the concrete outcome of the threat action — Engineer A now faces a real risk of job loss that constrains his future choices.

Temporal Marker: Simultaneous with and immediately following Engineer B's threat

Activates Constraints:
  • Employee_Livelihood_Protection_Constraint
  • Coercion_Prohibition_Constraint
  • Professional_Independence_Constraint
  • NSPE_Code_Retaliation_Prohibition
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A likely experiences fear, anger, and moral conflict; Engineer B may feel justified or uncomfortable with the confrontation; colleagues observing the situation may feel chilled in their own advocacy impulses

Stakeholder Consequences:
  • engineer_a: Immediate economic anxiety; forced to choose between livelihood and ethical commitments; potential psychological stress
  • engineer_b: Has now committed a potentially Code-violating act with personal professional consequences
  • xyz_manufacturing: Has created legal and ethical liability through the threat
  • citizens_committee: May lose a key spokesman if Engineer A capitulates; broader chilling effect on engineering advocacy
  • engineering_profession: The threat signals to other engineers that public advocacy carries personal risk, potentially suppressing legitimate professional speech

Learning Moment: This is the ethical crucible of the case — the moment where abstract principles meet concrete personal cost. Students should grapple with the real human weight of ethical decisions: Engineer A's choice to continue advocacy despite this threat is not costless courage but a decision made under genuine duress. The event also demonstrates that retaliation itself constitutes an independent ethical violation.

Ethical Implications: Exposes the structural vulnerability of employed engineers who attempt to exercise professional independence; reveals how economic dependency can be weaponized to suppress ethical conduct; demonstrates that retaliation against legitimate advocacy is itself an ethical violation under the NSPE Code, not merely an employment law issue

Discussion Prompts:
  • How should an engineer weigh personal economic security against professional ethical obligations when they conflict directly?
  • Does the threat of discharge change Engineer A's ethical obligations, or only the personal cost of fulfilling them?
  • What institutional mechanisms should exist to protect engineers from this kind of coercion, and who is responsible for creating them?
Crisis / Turning Point Tension: high Pacing: crisis
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Event_Engineer_A_s_Employment_Threatened",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How should an engineer weigh personal economic security against professional ethical obligations when they conflict directly?",
    "Does the threat of discharge change Engineer A\u0027s ethical obligations, or only the personal cost of fulfilling them?",
    "What institutional mechanisms should exist to protect engineers from this kind of coercion, and who is responsible for creating them?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences fear, anger, and moral conflict; Engineer B may feel justified or uncomfortable with the confrontation; colleagues observing the situation may feel chilled in their own advocacy impulses",
  "proeth-scenario:ethicalImplications": "Exposes the structural vulnerability of employed engineers who attempt to exercise professional independence; reveals how economic dependency can be weaponized to suppress ethical conduct; demonstrates that retaliation against legitimate advocacy is itself an ethical violation under the NSPE Code, not merely an employment law issue",
  "proeth-scenario:learningMoment": "This is the ethical crucible of the case \u2014 the moment where abstract principles meet concrete personal cost. Students should grapple with the real human weight of ethical decisions: Engineer A\u0027s choice to continue advocacy despite this threat is not costless courage but a decision made under genuine duress. The event also demonstrates that retaliation itself constitutes an independent ethical violation.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "citizens_committee": "May lose a key spokesman if Engineer A capitulates; broader chilling effect on engineering advocacy",
    "engineer_a": "Immediate economic anxiety; forced to choose between livelihood and ethical commitments; potential psychological stress",
    "engineer_b": "Has now committed a potentially Code-violating act with personal professional consequences",
    "engineering_profession": "The threat signals to other engineers that public advocacy carries personal risk, potentially suppressing legitimate professional speech",
    "xyz_manufacturing": "Has created legal and ethical liability through the threat"
  },
  "proeth:activatesConstraint": [
    "Employee_Livelihood_Protection_Constraint",
    "Coercion_Prohibition_Constraint",
    "Professional_Independence_Constraint",
    "NSPE_Code_Retaliation_Prohibition"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/82#Action_Threatening_Discharge_for_Advocacy",
  "proeth:causesStateChange": "Engineer A\u0027s professional autonomy is materially constrained by fear of economic harm; the power imbalance between Engineer A and Engineer B becomes acute; Engineer A must now weigh personal economic security against professional ethical obligations",
  "proeth:createsObligation": [
    "Engineer_A_Must_Decide_Whether_To_Comply_Or_Continue",
    "Engineer_B_Obligation_Not_To_Follow_Through_On_Unlawful_Threat",
    "NSPE_Obligation_To_Investigate_Code_Violation_By_Engineer_B"
  ],
  "proeth:description": "As a direct result of Engineer B\u0027s threat of discharge, Engineer A\u0027s employment status becomes precarious and uncertain. This is the concrete outcome of the threat action \u2014 Engineer A now faces a real risk of job loss that constrains his future choices.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Simultaneous with and immediately following Engineer B\u0027s threat",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer A\u0027s Employment Threatened"
}

Description: Upon retrospective analysis by the NSPE Ethics Board, Engineer B's threat of discharge is determined to itself constitute a violation of the NSPE Code of Ethics. This is an outcome of the Ethics Board's deliberative process and transforms the threat from a workplace conflict into a formal professional ethics matter.

Temporal Marker: During/after NSPE Ethics Board evaluation; retrospective determination

Activates Constraints:
  • NSPE_Disciplinary_Procedure_Constraint
  • Professional_Accountability_Constraint
  • Code_Enforcement_Obligation
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A may feel vindicated but the outcome may be bittersweet if professional damage has already occurred; Engineer B faces professional embarrassment and potential sanction; the engineering community receives a clarifying signal about the limits of employer authority

Stakeholder Consequences:
  • engineer_a: Professional vindication; advocacy retroactively confirmed as ethical; potential restoration of standing
  • engineer_b: Professional record marked by Code violation finding; personal and reputational consequences
  • xyz_manufacturing: Institutional conduct implicitly criticized through finding against its supervisor
  • engineering_profession: Precedent established that retaliation against public advocacy violates professional norms; chilling effect on future retaliation is intended
  • nspe_ethics_board: Institutional authority affirmed; Code interpreted in favor of professional independence

Learning Moment: This outcome teaches students that ethical adjudication can run in both directions — not only validating the whistleblower but sanctioning the retaliator. It demonstrates that the NSPE Code is not merely aspirational but has enforcement teeth, and that supervisors are not exempt from its provisions. Students should understand that power does not confer ethical immunity.

Ethical Implications: Establishes that professional ethical obligations apply symmetrically — engineers in supervisory roles are bound by the Code in how they treat subordinates; reveals that institutional authority can itself be exercised unethically; demonstrates the role of professional bodies in protecting the conditions necessary for ethical engineering practice, including freedom from coercion

Discussion Prompts:
  • Why is it significant that the Ethics Board found Engineer B's threat to be a Code violation, rather than simply finding Engineer A's conduct to be acceptable?
  • What practical effect does an ethics board finding have on the behavior of supervisors in similar situations going forward?
  • Does the retrospective nature of this finding adequately protect engineers who face retaliation in real time, or does the system need earlier intervention mechanisms?
Tension: medium Pacing: aftermath
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Event_Engineer_B_s_Code_Violation_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Why is it significant that the Ethics Board found Engineer B\u0027s threat to be a Code violation, rather than simply finding Engineer A\u0027s conduct to be acceptable?",
    "What practical effect does an ethics board finding have on the behavior of supervisors in similar situations going forward?",
    "Does the retrospective nature of this finding adequately protect engineers who face retaliation in real time, or does the system need earlier intervention mechanisms?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A may feel vindicated but the outcome may be bittersweet if professional damage has already occurred; Engineer B faces professional embarrassment and potential sanction; the engineering community receives a clarifying signal about the limits of employer authority",
  "proeth-scenario:ethicalImplications": "Establishes that professional ethical obligations apply symmetrically \u2014 engineers in supervisory roles are bound by the Code in how they treat subordinates; reveals that institutional authority can itself be exercised unethically; demonstrates the role of professional bodies in protecting the conditions necessary for ethical engineering practice, including freedom from coercion",
  "proeth-scenario:learningMoment": "This outcome teaches students that ethical adjudication can run in both directions \u2014 not only validating the whistleblower but sanctioning the retaliator. It demonstrates that the NSPE Code is not merely aspirational but has enforcement teeth, and that supervisors are not exempt from its provisions. Students should understand that power does not confer ethical immunity.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Professional vindication; advocacy retroactively confirmed as ethical; potential restoration of standing",
    "engineer_b": "Professional record marked by Code violation finding; personal and reputational consequences",
    "engineering_profession": "Precedent established that retaliation against public advocacy violates professional norms; chilling effect on future retaliation is intended",
    "nspe_ethics_board": "Institutional authority affirmed; Code interpreted in favor of professional independence",
    "xyz_manufacturing": "Institutional conduct implicitly criticized through finding against its supervisor"
  },
  "proeth:activatesConstraint": [
    "NSPE_Disciplinary_Procedure_Constraint",
    "Professional_Accountability_Constraint",
    "Code_Enforcement_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/82#Action_Ethics_Board_Evaluating_Engineer_B",
  "proeth:causesStateChange": "Engineer B\u0027s conduct is formally classified as a Code violation; the case establishes precedent that retaliating against engineers for legitimate public advocacy is itself professionally sanctionable; Engineer A\u0027s conduct is retrospectively validated as ethical",
  "proeth:createsObligation": [
    "NSPE_Obligation_To_Communicate_Finding",
    "Engineer_B_Obligation_To_Remedy_Conduct",
    "Professional_Community_Awareness_Of_Retaliation_Prohibition"
  ],
  "proeth:description": "Upon retrospective analysis by the NSPE Ethics Board, Engineer B\u0027s threat of discharge is determined to itself constitute a violation of the NSPE Code of Ethics. This is an outcome of the Ethics Board\u0027s deliberative process and transforms the threat from a workplace conflict into a formal professional ethics matter.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During/after NSPE Ethics Board evaluation; retrospective determination",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Engineer B\u0027s Code Violation Established"
}

Description: The NSPE Ethics Board retrospectively determines that Engineer A's public advocacy activities — joining the committee, making general statements, and appearing before legislators — were ethically justified under the NSPE Code of Ethics. This outcome formally resolves the ethical ambiguity surrounding Engineer A's conduct.

Temporal Marker: During/after NSPE Ethics Board evaluation; retrospective determination

Activates Constraints:
  • Professional_Precedent_Constraint
  • Engineer_Advocacy_Rights_Affirmation
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A experiences relief and vindication; the committee members may feel emboldened; Engineer B and XYZ management face the discomfort of having their conduct implicitly criticized; the broader engineering community receives reassurance that advocacy is protected

Stakeholder Consequences:
  • engineer_a: Professional reputation restored; personal sacrifice retrospectively affirmed as worthwhile
  • citizens_committee: Legitimacy of the organization's methods confirmed
  • engineer_b: Implicit criticism of the decision to threaten Engineer A
  • engineering_profession: Clarity on the scope of professional advocacy rights; stronger foundation for future advocacy
  • public: Indirectly benefits from a professional culture that protects engineers who speak out on quality and safety issues

Learning Moment: Demonstrates that ethical conduct, even when costly in the short term, can be vindicated through professional institutions. Students should understand that the design of Engineer A's advocacy — keeping statements general, working through a cross-company coalition, avoiding defamation — was not merely strategic but was itself ethically significant in enabling the validation outcome. Ethical advocacy requires both courage and craft.

Ethical Implications: Affirms the primacy of public welfare in engineering ethics over employer loyalty; demonstrates that professional codes can protect individual engineers who act in the public interest; raises questions about whether formal validation adequately compensates for the personal costs borne by ethical actors; highlights the importance of institutional design in enabling ethical conduct

Discussion Prompts:
  • Would the Ethics Board's finding have been different if Engineer A had named specific companies? What does this tell us about the ethics of advocacy strategy?
  • Is retrospective validation by an ethics board sufficient protection for engineers who face real-time retaliation? What are its limits?
  • What responsibility does the engineering profession as a whole bear for creating conditions where Engineer A had to risk his job to advocate for public welfare?
Tension: low Pacing: aftermath
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#Event_Engineer_A_s_Advocacy_Validated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Would the Ethics Board\u0027s finding have been different if Engineer A had named specific companies? What does this tell us about the ethics of advocacy strategy?",
    "Is retrospective validation by an ethics board sufficient protection for engineers who face real-time retaliation? What are its limits?",
    "What responsibility does the engineering profession as a whole bear for creating conditions where Engineer A had to risk his job to advocate for public welfare?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Engineer A experiences relief and vindication; the committee members may feel emboldened; Engineer B and XYZ management face the discomfort of having their conduct implicitly criticized; the broader engineering community receives reassurance that advocacy is protected",
  "proeth-scenario:ethicalImplications": "Affirms the primacy of public welfare in engineering ethics over employer loyalty; demonstrates that professional codes can protect individual engineers who act in the public interest; raises questions about whether formal validation adequately compensates for the personal costs borne by ethical actors; highlights the importance of institutional design in enabling ethical conduct",
  "proeth-scenario:learningMoment": "Demonstrates that ethical conduct, even when costly in the short term, can be vindicated through professional institutions. Students should understand that the design of Engineer A\u0027s advocacy \u2014 keeping statements general, working through a cross-company coalition, avoiding defamation \u2014 was not merely strategic but was itself ethically significant in enabling the validation outcome. Ethical advocacy requires both courage and craft.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "citizens_committee": "Legitimacy of the organization\u0027s methods confirmed",
    "engineer_a": "Professional reputation restored; personal sacrifice retrospectively affirmed as worthwhile",
    "engineer_b": "Implicit criticism of the decision to threaten Engineer A",
    "engineering_profession": "Clarity on the scope of professional advocacy rights; stronger foundation for future advocacy",
    "public": "Indirectly benefits from a professional culture that protects engineers who speak out on quality and safety issues"
  },
  "proeth:activatesConstraint": [
    "Professional_Precedent_Constraint",
    "Engineer_Advocacy_Rights_Affirmation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/82#Action_Ethics_Board_Evaluating_Engineer_B",
  "proeth:causesStateChange": "Engineer A\u0027s professional standing is restored and affirmed; the case becomes a reference point for future engineers considering similar advocacy; the scope of permissible professional speech is clarified",
  "proeth:createsObligation": [
    "NSPE_Obligation_To_Publish_And_Disseminate_Finding",
    "Engineering_Community_Awareness_Of_Advocacy_Rights"
  ],
  "proeth:description": "The NSPE Ethics Board retrospectively determines that Engineer A\u0027s public advocacy activities \u2014 joining the committee, making general statements, and appearing before legislators \u2014 were ethically justified under the NSPE Code of Ethics. This outcome formally resolves the ethical ambiguity surrounding Engineer A\u0027s conduct.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During/after NSPE Ethics Board evaluation; retrospective determination",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Engineer A\u0027s Advocacy Validated"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: As a result of his sustained participation in the Citizens Committee for Quality Products, Engineer A gains prominence within the advocacy group

Necessary Factors (NESS):
  • Engineer A's voluntary decision to join the Citizens Committee
  • Sustained and consistent participation over time
  • Existence of the Citizens Committee as an organized advocacy body
Sufficient Factors:
  • Voluntary joining + sustained participation + organized committee structure = prominence achieved
Counterfactual Test: Without Engineer A's initial decision to join and maintain participation, he would not have gained prominence; prominence was contingent entirely on continued voluntary engagement
Responsibility Attribution:

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

Causal Sequence:
  1. Product Quality Decline Observed (Event 1)
    A discernible trend toward inferior commercial products emerges, motivating engineers to organize
  2. Joining Citizens Committee Advocacy (Action 1)
    Engineer A voluntarily joins the cross-company Citizens Committee for Quality Products
  3. Keeping Advocacy Statements General (Action 2)
    Engineer A and the committee deliberately maintain general, non-employer-specific public statements
  4. Sustained Participation
    Engineer A continues active engagement with the committee over time, building credibility
  5. Engineer A Gains Committee Prominence (Event 2)
    Engineer A achieves a prominent role within the Citizens Committee as a recognized advocate
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#CausalChain_7a1b8154",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a result of his sustained participation in the Citizens Committee for Quality Products, Engineer A gains prominence within the advocacy group",
  "proeth:causalSequence": [
    {
      "proeth:description": "A discernible trend toward inferior commercial products emerges, motivating engineers to organize",
      "proeth:element": "Product Quality Decline Observed (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A voluntarily joins the cross-company Citizens Committee for Quality Products",
      "proeth:element": "Joining Citizens Committee Advocacy (Action 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A and the committee deliberately maintain general, non-employer-specific public statements",
      "proeth:element": "Keeping Advocacy Statements General (Action 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A continues active engagement with the committee over time, building credibility",
      "proeth:element": "Sustained Participation",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A achieves a prominent role within the Citizens Committee as a recognized advocate",
      "proeth:element": "Engineer A Gains Committee Prominence (Event 2)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Joining Citizens Committee Advocacy (Action 1)",
  "proeth:counterfactual": "Without Engineer A\u0027s initial decision to join and maintain participation, he would not have gained prominence; prominence was contingent entirely on continued voluntary engagement",
  "proeth:effect": "Engineer A Gains Committee Prominence (Event 2)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s voluntary decision to join the Citizens Committee",
    "Sustained and consistent participation over time",
    "Existence of the Citizens Committee as an organized advocacy body"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Voluntary joining + sustained participation + organized committee structure = prominence achieved"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: XYZ Manufacturing, through Engineer B, perceives Engineer A's public advocacy activities as embarrassing to the employer, triggered by Engineer A's elevated visibility within the Citizens Committee

Necessary Factors (NESS):
  • Engineer A's elevated public profile within the Citizens Committee
  • XYZ Manufacturing's awareness of Engineer A's advocacy role
  • Employer's subjective interpretation of advocacy as reputationally damaging
  • Absence of explicit employer-specific criticism in Engineer A's statements
Sufficient Factors:
  • Engineer A's prominence + employer awareness + employer's reputational sensitivity = perceived embarrassment
Counterfactual Test: If Engineer A had remained a low-profile committee member without prominence, XYZ Manufacturing may not have perceived the advocacy as sufficiently embarrassing to warrant a threat; the perception of embarrassment was amplified by Engineer A's visibility
Responsibility Attribution:

Agent: Engineer B (on behalf of XYZ Manufacturing)
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Joining Citizens Committee Advocacy (Action 1)
    Engineer A joins and actively participates in the Citizens Committee
  2. Engineer A Gains Committee Prominence (Event 2)
    Engineer A becomes a prominent, publicly visible advocate within the committee
  3. XYZ Manufacturing Awareness
    Engineer B and XYZ Manufacturing become aware of Engineer A's elevated public advocacy role
  4. Employer Embarrassment Perceived (Event 3)
    XYZ Manufacturing subjectively interprets Engineer A's advocacy as embarrassing to the company
  5. Threatening Discharge for Advocacy (Action 3)
    Engineer B issues an explicit threat of discharge to Engineer A as a consequence of perceived embarrassment
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#CausalChain_0015e634",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "XYZ Manufacturing, through Engineer B, perceives Engineer A\u0027s public advocacy activities as embarrassing to the employer, triggered by Engineer A\u0027s elevated visibility within the Citizens Committee",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A joins and actively participates in the Citizens Committee",
      "proeth:element": "Joining Citizens Committee Advocacy (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A becomes a prominent, publicly visible advocate within the committee",
      "proeth:element": "Engineer A Gains Committee Prominence (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B and XYZ Manufacturing become aware of Engineer A\u0027s elevated public advocacy role",
      "proeth:element": "XYZ Manufacturing Awareness",
      "proeth:step": 3
    },
    {
      "proeth:description": "XYZ Manufacturing subjectively interprets Engineer A\u0027s advocacy as embarrassing to the company",
      "proeth:element": "Employer Embarrassment Perceived (Event 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B issues an explicit threat of discharge to Engineer A as a consequence of perceived embarrassment",
      "proeth:element": "Threatening Discharge for Advocacy (Action 3)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Gains Committee Prominence (Event 2)",
  "proeth:counterfactual": "If Engineer A had remained a low-profile committee member without prominence, XYZ Manufacturing may not have perceived the advocacy as sufficiently embarrassing to warrant a threat; the perception of embarrassment was amplified by Engineer A\u0027s visibility",
  "proeth:effect": "Employer Embarrassment Perceived (Event 3)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s elevated public profile within the Citizens Committee",
    "XYZ Manufacturing\u0027s awareness of Engineer A\u0027s advocacy role",
    "Employer\u0027s subjective interpretation of advocacy as reputationally damaging",
    "Absence of explicit employer-specific criticism in Engineer A\u0027s statements"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B (on behalf of XYZ Manufacturing)",
  "proeth:sufficientFactors": [
    "Engineer A\u0027s prominence + employer awareness + employer\u0027s reputational sensitivity = perceived embarrassment"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: As a direct result of Engineer B's threat of discharge, Engineer A's employment status becomes precarious, placing Engineer A under professional and financial pressure

Necessary Factors (NESS):
  • Engineer B's explicit issuance of a discharge threat
  • Engineer A's employment relationship with XYZ Manufacturing
  • Engineer B's supervisory authority over Engineer A
  • Engineer A's continued advocacy activities that triggered the threat
Sufficient Factors:
  • Supervisory authority + explicit discharge threat + employment dependency = employment status made precarious
Counterfactual Test: Without Engineer B's explicit threat, Engineer A's employment would not have been placed in jeopardy; the threat was the direct and sole mechanism by which employment became precarious
Responsibility Attribution:

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

Causal Sequence:
  1. Employer Embarrassment Perceived (Event 3)
    XYZ Manufacturing perceives Engineer A's advocacy as embarrassing
  2. Threatening Discharge for Advocacy (Action 3)
    Engineer B explicitly warns Engineer A that continued advocacy will result in discharge
  3. Engineer A's Employment Threatened (Event 4)
    Engineer A's employment status becomes directly precarious as a result of the threat
  4. Continuing Advocacy Despite Threat (Action 4)
    Engineer A faces a critical decision point: cease advocacy or continue despite employment risk
  5. Engineer B's Code Violation Established (Event 5)
    NSPE Ethics Board retrospectively determines Engineer B's threat constituted a professional code violation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#CausalChain_565b6b8b",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a direct result of Engineer B\u0027s threat of discharge, Engineer A\u0027s employment status becomes precarious, placing Engineer A under professional and financial pressure",
  "proeth:causalSequence": [
    {
      "proeth:description": "XYZ Manufacturing perceives Engineer A\u0027s advocacy as embarrassing",
      "proeth:element": "Employer Embarrassment Perceived (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B explicitly warns Engineer A that continued advocacy will result in discharge",
      "proeth:element": "Threatening Discharge for Advocacy (Action 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A\u0027s employment status becomes directly precarious as a result of the threat",
      "proeth:element": "Engineer A\u0027s Employment Threatened (Event 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A faces a critical decision point: cease advocacy or continue despite employment risk",
      "proeth:element": "Continuing Advocacy Despite Threat (Action 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "NSPE Ethics Board retrospectively determines Engineer B\u0027s threat constituted a professional code violation",
      "proeth:element": "Engineer B\u0027s Code Violation Established (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Threatening Discharge for Advocacy (Action 3)",
  "proeth:counterfactual": "Without Engineer B\u0027s explicit threat, Engineer A\u0027s employment would not have been placed in jeopardy; the threat was the direct and sole mechanism by which employment became precarious",
  "proeth:effect": "Engineer A\u0027s Employment Threatened (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s explicit issuance of a discharge threat",
    "Engineer A\u0027s employment relationship with XYZ Manufacturing",
    "Engineer B\u0027s supervisory authority over Engineer A",
    "Engineer A\u0027s continued advocacy activities that triggered the threat"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Supervisory authority + explicit discharge threat + employment dependency = employment status made precarious"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Upon retrospective analysis by the NSPE Ethics Board, Engineer B's threat of discharge is determined to constitute a violation of the engineering professional code of ethics

Necessary Factors (NESS):
  • Engineer B's explicit issuance of a discharge threat tied to Engineer A's lawful advocacy
  • NSPE Ethics Board's deliberate decision to evaluate Engineer B's conduct (Action 5)
  • Existence of a professional code of ethics prohibiting retaliation against engineers for lawful public advocacy
  • Engineer A's advocacy being general and not constituting a breach of employer confidentiality or professional duty
Sufficient Factors:
  • Discharge threat for lawful advocacy + professional code prohibiting such retaliation + NSPE evaluation = code violation established
Counterfactual Test: If Engineer B had not issued the discharge threat, no code violation would have occurred; alternatively, if the NSPE Ethics Board had not evaluated the conduct, the violation would not have been formally established even if it existed substantively
Responsibility Attribution:

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

Causal Sequence:
  1. Employer Embarrassment Perceived (Event 3)
    XYZ Manufacturing perceives reputational harm from Engineer A's public prominence
  2. Threatening Discharge for Advocacy (Action 3)
    Engineer B issues explicit discharge threat to suppress Engineer A's lawful advocacy
  3. Continuing Advocacy Despite Threat (Action 4)
    Engineer A continues advocacy, making the ethical conflict a concrete, reviewable matter
  4. Ethics Board Evaluating Engineer B (Action 5)
    NSPE Ethics Board undertakes deliberate analytical review of Engineer B's conduct
  5. Engineer B's Code Violation Established (Event 5)
    NSPE formally determines Engineer B's threat constituted a professional ethics code violation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#CausalChain_b3c49ecd",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon retrospective analysis by the NSPE Ethics Board, Engineer B\u0027s threat of discharge is determined to constitute a violation of the engineering professional code of ethics",
  "proeth:causalSequence": [
    {
      "proeth:description": "XYZ Manufacturing perceives reputational harm from Engineer A\u0027s public prominence",
      "proeth:element": "Employer Embarrassment Perceived (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B issues explicit discharge threat to suppress Engineer A\u0027s lawful advocacy",
      "proeth:element": "Threatening Discharge for Advocacy (Action 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A continues advocacy, making the ethical conflict a concrete, reviewable matter",
      "proeth:element": "Continuing Advocacy Despite Threat (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "NSPE Ethics Board undertakes deliberate analytical review of Engineer B\u0027s conduct",
      "proeth:element": "Ethics Board Evaluating Engineer B (Action 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "NSPE formally determines Engineer B\u0027s threat constituted a professional ethics code violation",
      "proeth:element": "Engineer B\u0027s Code Violation Established (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Threatening Discharge for Advocacy (Action 3)",
  "proeth:counterfactual": "If Engineer B had not issued the discharge threat, no code violation would have occurred; alternatively, if the NSPE Ethics Board had not evaluated the conduct, the violation would not have been formally established even if it existed substantively",
  "proeth:effect": "Engineer B\u0027s Code Violation Established (Event 5)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s explicit issuance of a discharge threat tied to Engineer A\u0027s lawful advocacy",
    "NSPE Ethics Board\u0027s deliberate decision to evaluate Engineer B\u0027s conduct (Action 5)",
    "Existence of a professional code of ethics prohibiting retaliation against engineers for lawful public advocacy",
    "Engineer A\u0027s advocacy being general and not constituting a breach of employer confidentiality or professional duty"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Discharge threat for lawful advocacy + professional code prohibiting such retaliation + NSPE evaluation = code violation established"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: The NSPE Ethics Board retrospectively determines that Engineer A's public advocacy activities — joining the committee, keeping statements general, and continuing despite the threat — were consistent with and protected by the engineering code of ethics

Necessary Factors (NESS):
  • Engineer A's deliberate choice to keep advocacy statements general and non-employer-specific (Action 2)
  • Engineer A's decision to continue advocacy despite the discharge threat (Action 4)
  • NSPE Ethics Board's independent evaluation of Engineer A's conduct (Action 5)
  • The advocacy activities not constituting a breach of confidentiality, professional duty, or employer-specific harm
Sufficient Factors:
  • General statements + no breach of professional duty + continued lawful advocacy + NSPE review = advocacy validated as ethically compliant
Counterfactual Test: If Engineer A had made employer-specific or confidential statements, the advocacy would not have been validated; if Engineer A had ceased advocacy under threat, there would have been no conduct to validate; without NSPE evaluation, validation would not have been formally established
Responsibility Attribution:

Agent: Engineer A (primary); NSPE Ethics Board (secondary, institutional)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Joining Citizens Committee Advocacy (Action 1) + Keeping Advocacy Statements General (Action 2)
    Engineer A joins the committee and deliberately structures advocacy to remain general and professionally appropriate
  2. Threatening Discharge for Advocacy (Action 3)
    Engineer B's threat creates an adversarial ethical conflict requiring resolution
  3. Continuing Advocacy Despite Threat (Action 4)
    Engineer A chooses to continue lawful advocacy despite employment risk, demonstrating commitment to professional duty
  4. Ethics Board Evaluating Engineer B (Action 5)
    NSPE Ethics Board evaluates both Engineer B's and Engineer A's conduct as part of its independent analysis
  5. Engineer A's Advocacy Validated (Event 6)
    NSPE formally determines Engineer A's advocacy was ethically compliant and protected under the professional code
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/82#",
    "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/82#CausalChain_53165fe3",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The NSPE Ethics Board retrospectively determines that Engineer A\u0027s public advocacy activities \u2014 joining the committee, keeping statements general, and continuing despite the threat \u2014 were consistent with and protected by the engineering code of ethics",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A joins the committee and deliberately structures advocacy to remain general and professionally appropriate",
      "proeth:element": "Joining Citizens Committee Advocacy (Action 1) + Keeping Advocacy Statements General (Action 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B\u0027s threat creates an adversarial ethical conflict requiring resolution",
      "proeth:element": "Threatening Discharge for Advocacy (Action 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A chooses to continue lawful advocacy despite employment risk, demonstrating commitment to professional duty",
      "proeth:element": "Continuing Advocacy Despite Threat (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "NSPE Ethics Board evaluates both Engineer B\u0027s and Engineer A\u0027s conduct as part of its independent analysis",
      "proeth:element": "Ethics Board Evaluating Engineer B (Action 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "NSPE formally determines Engineer A\u0027s advocacy was ethically compliant and protected under the professional code",
      "proeth:element": "Engineer A\u0027s Advocacy Validated (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Keeping Advocacy Statements General (Action 2) + Continuing Advocacy Despite Threat (Action 4)",
  "proeth:counterfactual": "If Engineer A had made employer-specific or confidential statements, the advocacy would not have been validated; if Engineer A had ceased advocacy under threat, there would have been no conduct to validate; without NSPE evaluation, validation would not have been formally established",
  "proeth:effect": "Engineer A\u0027s Advocacy Validated (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s deliberate choice to keep advocacy statements general and non-employer-specific (Action 2)",
    "Engineer A\u0027s decision to continue advocacy despite the discharge threat (Action 4)",
    "NSPE Ethics Board\u0027s independent evaluation of Engineer A\u0027s conduct (Action 5)",
    "The advocacy activities not constituting a breach of confidentiality, professional duty, or employer-specific harm"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (primary); NSPE Ethics Board (secondary, institutional)",
  "proeth:sufficientFactors": [
    "General statements + no breach of professional duty + continued lawful advocacy + NSPE review = advocacy validated as ethically compliant"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (6)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
Case 61-10 ruling before
Entity1 is before Entity2
Discussion analysis of current case time:before
http://www.w3.org/2006/time#before
What we have said does not conflict with the holding in Case 61-10, in which it was found that engin... [more]
Engineer A joining the Citizens Committee and becoming a leading spokesman before
Entity1 is before Entity2
Engineer B's threat of discharge time:before
http://www.w3.org/2006/time#before
Engineer A joins a group... becomes a leading spokesman... Engineer B, the supervisor of Engineer A,... [more]
Engineer A's concern about inferior products before
Entity1 is before Entity2
Engineer A joining the Citizens Committee time:before
http://www.w3.org/2006/time#before
Engineer A... became concerned about what he regards as a trend toward the production of 'cheap' pro... [more]
Engineer A's public advocacy (letters, legislative appearances) before
Entity1 is before Entity2
Engineer B's warning time:before
http://www.w3.org/2006/time#before
Engineer A becomes a leading spokesman... including public statements, letters to local newspapers a... [more]
Engineer B's threat before
Entity1 is before Entity2
Discussion/ethical analysis of the case time:before
http://www.w3.org/2006/time#before
The Discussion section retrospectively analyzes these events against the NSPE Code of Ethics, conclu... [more]
Engineer A's advocacy activities overlaps
Entity1 starts before Entity2 and ends during Entity2
Engineer A's employment at XYZ Manufacturing time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps
Engineer A, employed by the XYZ Manufacturing Company... becomes a leading spokesman for their cause... [more]
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.