PASS 3: Temporal Dynamics
Case 93: Withholding Information Useful to Client/Public Agency
Timeline Overview
OWL-Time Temporal Structure 8 relations time: = w3.org/2006/time
Extracted Actions (5)
Volitional professional decisions with intentions and ethical contextDescription: Engineer X accepted a commission to provide engineering services for Client L in State P without first obtaining a certificate of authority to practice engineering in that state. This constitutes a deliberate business decision to proceed with a project across state lines without fulfilling the prerequisite licensure requirement.
Temporal Marker: Prior to project commencement, at time of engagement acceptance
Mental State: deliberate regarding acceptance of engagement; potentially inadvertent regarding the certificate of authority requirement
Intended Outcome: Secure and service a new client in State P, generating revenue for XYZ Engineering
Fulfills Obligations:
- Responsiveness to client need
- Pursuit of professional engagement within claimed area of competence
Guided By Principles:
- Legal compliance as prerequisite to professional practice
- Public protection through licensure systems
- Honest and lawful conduct in professional business dealings
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer X sought to expand business into a new state market and serve a new client (Client L), likely prioritizing revenue generation, competitive positioning, and client relationship development over strict regulatory compliance. The motivation may reflect either ignorance of State P's certificate of authority requirement or a calculated decision to proceed and address licensure retroactively.
Ethical Tension: Business opportunity and client service vs. professional obligation to comply with jurisdictional licensure laws before commencing practice. Self-interest in winning the contract competes with the duty to protect the public and uphold the integrity of the engineering licensure system.
Learning Significance: Illustrates that cross-jurisdictional practice carries distinct legal and ethical obligations beyond personal licensure. Engineers and firms must proactively verify and fulfill certificate of authority requirements in every state where they practice, regardless of competitive pressure or client urgency.
Stakes: Engineer X risks disciplinary action, fines, and reputational damage. XYZ Engineering's ability to practice in State P may be jeopardized. Client L's project may face legal complications if work is performed by an unlicensed entity. Public safety interests underlying licensure laws are undermined.
Decision Point: Yes - Story can branch here
- Decline the engagement until a certificate of authority is obtained from State P
- Immediately initiate the certificate of authority application process before or concurrent with contract signing, making commencement of work contingent on approval
- Refer Client L to a licensed State P engineering firm, potentially as a subconsultant or partner arrangement
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Action_Accept_Engagement_Without_Certificate",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the engagement until a certificate of authority is obtained from State P",
"Immediately initiate the certificate of authority application process before or concurrent with contract signing, making commencement of work contingent on approval",
"Refer Client L to a licensed State P engineering firm, potentially as a subconsultant or partner arrangement"
],
"proeth-scenario:characterMotivation": "Engineer X sought to expand business into a new state market and serve a new client (Client L), likely prioritizing revenue generation, competitive positioning, and client relationship development over strict regulatory compliance. The motivation may reflect either ignorance of State P\u0027s certificate of authority requirement or a calculated decision to proceed and address licensure retroactively.",
"proeth-scenario:consequencesIfAlternative": [
"Declining the engagement protects Engineer X from licensure violations but results in lost business; Client L must seek another firm, and no ethical violation occurs \u2014 this is the cleanest ethical outcome",
"Initiating the application concurrently demonstrates good faith and regulatory awareness, may cause project delays but avoids unlicensed practice; represents a responsible middle path that balances client service with compliance",
"Referring or partnering with a licensed State P firm ensures compliant service delivery for Client L, preserves a business relationship for Engineer X, and models collaborative professional ethics \u2014 though it sacrifices full project control and revenue"
],
"proeth-scenario:decisionSignificance": "Illustrates that cross-jurisdictional practice carries distinct legal and ethical obligations beyond personal licensure. Engineers and firms must proactively verify and fulfill certificate of authority requirements in every state where they practice, regardless of competitive pressure or client urgency.",
"proeth-scenario:ethicalTension": "Business opportunity and client service vs. professional obligation to comply with jurisdictional licensure laws before commencing practice. Self-interest in winning the contract competes with the duty to protect the public and uphold the integrity of the engineering licensure system.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "Engineer X risks disciplinary action, fines, and reputational damage. XYZ Engineering\u0027s ability to practice in State P may be jeopardized. Client L\u0027s project may face legal complications if work is performed by an unlicensed entity. Public safety interests underlying licensure laws are undermined.",
"proeth:description": "Engineer X accepted a commission to provide engineering services for Client L in State P without first obtaining a certificate of authority to practice engineering in that state. This constitutes a deliberate business decision to proceed with a project across state lines without fulfilling the prerequisite licensure requirement.",
"proeth:foreseenUnintendedEffects": [
"Risk of being unable to enforce contracts or seek court redress in State P",
"Risk of exposure to state licensure board sanctions",
"Potential inability to collect payment for services rendered",
"Competitive disadvantage if violation is reported and project is disrupted"
],
"proeth:fulfillsObligation": [
"Responsiveness to client need",
"Pursuit of professional engagement within claimed area of competence"
],
"proeth:guidedByPrinciple": [
"Legal compliance as prerequisite to professional practice",
"Public protection through licensure systems",
"Honest and lawful conduct in professional business dealings"
],
"proeth:hasAgent": "Engineer X (Owner, XYZ Engineering, State Q)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Business development versus regulatory compliance",
"proeth:resolutionReasoning": "Engineer X proceeded with the engagement without securing the certificate of authority, suggesting that business opportunity was prioritized over regulatory compliance, whether through oversight or deliberate choice"
},
"proeth:hasMentalState": "deliberate regarding acceptance of engagement; potentially inadvertent regarding the certificate of authority requirement",
"proeth:intendedOutcome": "Secure and service a new client in State P, generating revenue for XYZ Engineering",
"proeth:requiresCapability": [
"Knowledge of multi-state licensure and certificate of authority requirements",
"Due diligence in verifying legal authorization to practice in a new jurisdiction",
"Administrative capability to apply for and obtain out-of-state certificates of authority"
],
"proeth:temporalMarker": "Prior to project commencement, at time of engagement acceptance",
"proeth:violatesObligation": [
"Compliance with state engineering licensure laws and regulations of State P",
"Obligation to hold valid certificate of authority before practicing engineering in a jurisdiction",
"NSPE Code obligation to perform services only in areas of competence and within legal authorization",
"Professional obligation to protect public interest through proper licensure identification"
],
"proeth:withinCompetence": true,
"rdfs:label": "Accept Engagement Without Certificate"
}
Description: Upon learning that XYZ Engineering lacks a current certificate of authority in State P, Engineer A must make a deliberate choice about how to respond to a competitor's apparent licensure violation. This is a pivotal decision point requiring Engineer A to weigh collegial duty, reporting obligations, and potential self-interest.
Temporal Marker: At the time of discovery of XYZ Engineering's lack of certificate of authority
Mental State: deliberate and reflective
Intended Outcome: Respond to the discovered violation in a manner that is ethically appropriate, professionally collegial, and compliant with any state reporting obligations
Fulfills Obligations:
- Awareness and recognition of a professional licensure violation
- Obligation to consider public interest implications of the violation
Guided By Principles:
- Collegial and cooperative engagement with fellow professionals
- Honest and ethical conduct in competitive business situations
- Obligation not to use knowledge of a violation as a competitive weapon
- Independent professional judgment free from self-interest
- Public protection through enforcement of licensure requirements
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A, having discovered a competitor's apparent licensure violation, must reconcile multiple motivations: a genuine professional duty to uphold engineering standards and protect the public, a collegial responsibility toward a fellow engineer, and an unavoidable awareness of competitive self-interest given that Client L was previously Engineer A's client. The decision point forces Engineer A to examine whether the motivation to act is principled or self-serving.
Ethical Tension: Professional obligation to report licensure violations and protect public welfare vs. collegial duty to give a fellow engineer the benefit of the doubt and an opportunity to self-correct. Both values are legitimate. Compounding the tension is the appearance — or reality — of competitive self-interest, which could corrupt an otherwise ethical reporting impulse and calls Engineer A's objectivity into question.
Learning Significance: This is a critical teaching moment about conflicts of interest in professional ethics. Students must grapple with whether a reporting obligation is diminished or tainted by the reporter's self-interest, and how engineers should handle situations where doing the right thing also happens to benefit themselves. It also introduces the concept of proportionate response — that not every violation immediately warrants formal reporting.
Stakes: Engineer A's professional integrity and credibility are at risk if the motivation appears self-serving. Inaction risks complicity in an ongoing violation. Premature or punitive reporting without collegial contact could harm Engineer X unfairly and damage professional relationships. The credibility of the engineering profession's self-regulatory culture hangs in the balance.
Decision Point: Yes - Story can branch here
- Take no action, rationalizing that it is not Engineer A's responsibility to police a competitor's licensure status
- Immediately report the violation to State P authorities without first contacting Engineer X, citing a clear-cut obligation to report
- Consult with Engineer A's own professional society or ethics board for guidance before taking any action
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Action_Decide_Response_to_Discovered_Violation",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Take no action, rationalizing that it is not Engineer A\u0027s responsibility to police a competitor\u0027s licensure status",
"Immediately report the violation to State P authorities without first contacting Engineer X, citing a clear-cut obligation to report",
"Consult with Engineer A\u0027s own professional society or ethics board for guidance before taking any action"
],
"proeth-scenario:characterMotivation": "Engineer A, having discovered a competitor\u0027s apparent licensure violation, must reconcile multiple motivations: a genuine professional duty to uphold engineering standards and protect the public, a collegial responsibility toward a fellow engineer, and an unavoidable awareness of competitive self-interest given that Client L was previously Engineer A\u0027s client. The decision point forces Engineer A to examine whether the motivation to act is principled or self-serving.",
"proeth-scenario:consequencesIfAlternative": [
"Taking no action avoids the appearance of self-interest but constitutes a failure of professional duty; the violation continues unaddressed, potentially harming the public and the integrity of the licensure system",
"Immediate reporting without collegial contact fulfills the letter of the reporting obligation but bypasses a proportionate, collegial first step; may be perceived as punitive or self-interested and damages professional norms of courtesy and good faith",
"Seeking guidance from a professional society demonstrates ethical conscientiousness and protects Engineer A from acting impulsively or self-interestedly; introduces a delay but improves the quality and legitimacy of the eventual decision"
],
"proeth-scenario:decisionSignificance": "This is a critical teaching moment about conflicts of interest in professional ethics. Students must grapple with whether a reporting obligation is diminished or tainted by the reporter\u0027s self-interest, and how engineers should handle situations where doing the right thing also happens to benefit themselves. It also introduces the concept of proportionate response \u2014 that not every violation immediately warrants formal reporting.",
"proeth-scenario:ethicalTension": "Professional obligation to report licensure violations and protect public welfare vs. collegial duty to give a fellow engineer the benefit of the doubt and an opportunity to self-correct. Both values are legitimate. Compounding the tension is the appearance \u2014 or reality \u2014 of competitive self-interest, which could corrupt an otherwise ethical reporting impulse and calls Engineer A\u0027s objectivity into question.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "Engineer A\u0027s professional integrity and credibility are at risk if the motivation appears self-serving. Inaction risks complicity in an ongoing violation. Premature or punitive reporting without collegial contact could harm Engineer X unfairly and damage professional relationships. The credibility of the engineering profession\u0027s self-regulatory culture hangs in the balance.",
"proeth:description": "Upon learning that XYZ Engineering lacks a current certificate of authority in State P, Engineer A must make a deliberate choice about how to respond to a competitor\u0027s apparent licensure violation. This is a pivotal decision point requiring Engineer A to weigh collegial duty, reporting obligations, and potential self-interest.",
"proeth:foreseenUnintendedEffects": [
"Immediate reporting could damage Engineer X\u0027s business and appear self-serving given Engineer A\u0027s competitive interest",
"Failing to act at all could make Engineer A complicit in an ongoing licensure violation",
"Direct contact with Engineer X could resolve the matter without formal sanction but could also be perceived as interference",
"Any action taken could influence whether Client L remains with Engineer X or returns to Engineer A"
],
"proeth:fulfillsObligation": [
"Awareness and recognition of a professional licensure violation",
"Obligation to consider public interest implications of the violation"
],
"proeth:guidedByPrinciple": [
"Collegial and cooperative engagement with fellow professionals",
"Honest and ethical conduct in competitive business situations",
"Obligation not to use knowledge of a violation as a competitive weapon",
"Independent professional judgment free from self-interest",
"Public protection through enforcement of licensure requirements"
],
"proeth:hasAgent": "Engineer A (Owner, ABC Engineering, State P)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Collegial resolution versus immediate regulatory reporting versus self-interested inaction or exploitation",
"proeth:resolutionReasoning": "The discussion recommends a graduated response: Engineer A should first contact Engineer X directly to clarify and resolve the matter, only escalating to formal reporting if that effort fails, thereby balancing collegial duty against reporting obligations while guarding against self-interested misuse of the knowledge"
},
"proeth:hasMentalState": "deliberate and reflective",
"proeth:intendedOutcome": "Respond to the discovered violation in a manner that is ethically appropriate, professionally collegial, and compliant with any state reporting obligations",
"proeth:requiresCapability": [
"Knowledge of State P certificate of authority requirements",
"Ability to communicate professionally and collegially with a competitor",
"Ethical judgment to separate professional duty from competitive self-interest",
"Understanding of state licensure board reporting obligations and procedures"
],
"proeth:temporalMarker": "At the time of discovery of XYZ Engineering\u0027s lack of certificate of authority",
"proeth:violatesObligation": [
"Potential risk of violating duty of honest and fair dealing if self-interest influences chosen response",
"Risk of failing reporting obligation if Engineer A takes no action whatsoever"
],
"proeth:withinCompetence": true,
"rdfs:label": "Decide Response to Discovered Violation"
}
Description: Engineer A chooses to contact Engineer X directly to inform him of the certificate of authority requirement and seek clarification and voluntary compliance before considering any formal report to state authorities. This collegial first step is the recommended action prescribed by the discussion.
Temporal Marker: First recommended action point, following discovery of the violation
Mental State: deliberate and professionally motivated
Intended Outcome: Inform Engineer X of the certificate of authority requirement, explain its rationale and consequences of non-compliance, and give Engineer X the opportunity to rectify the oversight voluntarily without formal sanction
Fulfills Obligations:
- Collegial duty to inform a professional peer of a potential violation before escalating
- Obligation to act in good faith and with honest intent toward a competitor
- Duty to support the integrity of the licensure system
- NSPE Code obligation to act in a manner that advances the profession
Guided By Principles:
- Collegial and cooperative professional conduct
- Good faith engagement with professional peers
- Graduated and proportionate response to violations absent imminent public danger
- Transparency and honest communication
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A acts on the professional norm of collegial courtesy and proportionate response, recognizing that direct communication gives Engineer X the opportunity to correct an oversight without unnecessary professional harm. This action also allows Engineer A to demonstrate that the motivation is corrective rather than punitive or competitive, thereby preserving Engineer A's own ethical standing.
Ethical Tension: The duty to enforce professional standards and protect the public through formal channels vs. the collegial value of giving a fellow professional the benefit of the doubt and a chance to self-correct. There is also tension between thoroughness — ensuring the violation is definitively resolved — and restraint — not overstepping by acting as an informal enforcement officer.
Learning Significance: Demonstrates the principle of proportionate and graduated response in professional ethics enforcement. Students learn that the first obligation when discovering a peer's apparent violation is often collegial engagement, not immediate formal reporting. This models how professional self-regulation can function through peer accountability before institutional intervention.
Stakes: If the direct contact is handled poorly — perceived as threatening, condescending, or self-interested — it could damage the professional relationship and cause Engineer X to become defensive rather than compliant. If Engineer X ignores or dismisses the contact, Engineer A must then escalate, making this step a necessary precondition for justified formal reporting.
Decision Point: Yes - Story can branch here
- Send a written communication (letter or email) rather than a direct conversation, to create a documented record of the collegial outreach
- Contact Client L directly to inform them of the licensure issue, rather than approaching Engineer X first
- Skip direct contact and proceed immediately to formal reporting, arguing that the violation is clear and self-evident
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Action_Contact_Engineer_X_Directly",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Send a written communication (letter or email) rather than a direct conversation, to create a documented record of the collegial outreach",
"Contact Client L directly to inform them of the licensure issue, rather than approaching Engineer X first",
"Skip direct contact and proceed immediately to formal reporting, arguing that the violation is clear and self-evident"
],
"proeth-scenario:characterMotivation": "Engineer A acts on the professional norm of collegial courtesy and proportionate response, recognizing that direct communication gives Engineer X the opportunity to correct an oversight without unnecessary professional harm. This action also allows Engineer A to demonstrate that the motivation is corrective rather than punitive or competitive, thereby preserving Engineer A\u0027s own ethical standing.",
"proeth-scenario:consequencesIfAlternative": [
"Written communication creates a paper trail that protects Engineer A and provides clear evidence of good-faith outreach if formal reporting later becomes necessary; however, it may feel more formal and less collegial than a direct conversation",
"Contacting Client L bypasses Engineer X and could immediately destabilize the project relationship, potentially harming Client L\u0027s project timeline; it is generally considered inappropriate to undermine a colleague\u0027s client relationship without first addressing the issue with the colleague directly",
"Skipping direct contact and reporting immediately may be defensible if the violation is egregious or ongoing harm is imminent, but in this scenario it bypasses the recommended collegial step and risks appearing punitive or self-serving"
],
"proeth-scenario:decisionSignificance": "Demonstrates the principle of proportionate and graduated response in professional ethics enforcement. Students learn that the first obligation when discovering a peer\u0027s apparent violation is often collegial engagement, not immediate formal reporting. This models how professional self-regulation can function through peer accountability before institutional intervention.",
"proeth-scenario:ethicalTension": "The duty to enforce professional standards and protect the public through formal channels vs. the collegial value of giving a fellow professional the benefit of the doubt and a chance to self-correct. There is also tension between thoroughness \u2014 ensuring the violation is definitively resolved \u2014 and restraint \u2014 not overstepping by acting as an informal enforcement officer.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "If the direct contact is handled poorly \u2014 perceived as threatening, condescending, or self-interested \u2014 it could damage the professional relationship and cause Engineer X to become defensive rather than compliant. If Engineer X ignores or dismisses the contact, Engineer A must then escalate, making this step a necessary precondition for justified formal reporting.",
"proeth:description": "Engineer A chooses to contact Engineer X directly to inform him of the certificate of authority requirement and seek clarification and voluntary compliance before considering any formal report to state authorities. This collegial first step is the recommended action prescribed by the discussion.",
"proeth:foreseenUnintendedEffects": [
"Engineer X may view the contact as competitive interference",
"Resolution at this stage avoids formal disciplinary proceedings against Engineer X",
"Engineer A\u0027s competitive interest in the former client could be perceived as tainting the motivation for contact",
"Successful resolution benefits Engineer X\u0027s ability to enforce contracts and collect fees in State P"
],
"proeth:fulfillsObligation": [
"Collegial duty to inform a professional peer of a potential violation before escalating",
"Obligation to act in good faith and with honest intent toward a competitor",
"Duty to support the integrity of the licensure system",
"NSPE Code obligation to act in a manner that advances the profession"
],
"proeth:guidedByPrinciple": [
"Collegial and cooperative professional conduct",
"Good faith engagement with professional peers",
"Graduated and proportionate response to violations absent imminent public danger",
"Transparency and honest communication"
],
"proeth:hasAgent": "Engineer A (Owner, ABC Engineering, State P)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Genuine collegial assistance versus appearance or reality of competitive self-interest",
"proeth:resolutionReasoning": "The discussion endorses direct contact as the ethically appropriate first step, analogizing to BER Case 96-8, on the premise that inadvertent violations should first be addressed collegially, and that Engineer A\u0027s motivation should be professional duty rather than competitive advantage"
},
"proeth:hasMentalState": "deliberate and professionally motivated",
"proeth:intendedOutcome": "Inform Engineer X of the certificate of authority requirement, explain its rationale and consequences of non-compliance, and give Engineer X the opportunity to rectify the oversight voluntarily without formal sanction",
"proeth:requiresCapability": [
"Thorough knowledge of State P certificate of authority requirements and their legal consequences",
"Professional communication skills to deliver counsel to a competitor constructively",
"Ethical judgment to maintain appropriate boundaries and motivations during the contact"
],
"proeth:temporalMarker": "First recommended action point, following discovery of the violation",
"proeth:violatesObligation": [
"No obligations violated if action is taken in good faith; however, if motivated by competitive self-interest, would violate obligation to treat competitors fairly and honestly"
],
"proeth:withinCompetence": true,
"rdfs:label": "Contact Engineer X Directly"
}
Description: If Engineer A's direct communication with Engineer X fails to resolve the certificate of authority violation, Engineer A must then decide to formally notify the appropriate State P engineering licensure authorities of the ongoing violation. This escalation fulfills the reporting obligation that collegial first contact had temporarily deferred.
Temporal Marker: Post-communication decision point, only if direct contact with Engineer X fails to produce compliance
Mental State: obligatory and deliberate
Intended Outcome: Fulfill the legal and ethical obligation to report a known, unresolved licensure violation to the appropriate state authorities, ensuring enforcement of licensure laws that protect the public and the integrity of the profession
Fulfills Obligations:
- Legal obligation to report licensure violations to the state engineering board
- Ethical obligation to uphold the integrity of the licensure system
- Duty to protect public interest through enforcement of licensure requirements
- NSPE Code obligation to act in accordance with law and professional standards
Guided By Principles:
- Public protection through licensure enforcement
- Integrity and honesty in professional conduct
- Proportionate and graduated response to violations
- Obligation to uphold and advance the engineering profession
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Having fulfilled the collegial obligation by contacting Engineer X directly, Engineer A is now motivated by a clear professional duty to report an unresolved, ongoing licensure violation to the appropriate authorities. At this stage, the self-interest concern is mitigated by the demonstrated good-faith prior step, and the reporting obligation becomes unambiguous.
Ethical Tension: Loyalty to a fellow professional and reluctance to cause harm to a colleague's career and firm vs. the overriding duty to uphold public protection and the integrity of the engineering licensure system. Once collegial outreach has failed, this tension largely resolves in favor of reporting, but Engineer A may still experience discomfort about the consequences for Engineer X.
Learning Significance: Teaches students that professional reporting obligations are real and enforceable, not merely advisory. When collegial first steps fail, the ethical engineer must follow through with formal reporting. This action also illustrates that the graduated response model — collegial contact first, formal report second — is not merely a way to avoid reporting, but a structured ethical process that legitimizes formal action when necessary.
Stakes: Engineer X faces formal disciplinary proceedings, potential fines, and reputational damage. XYZ Engineering's ability to practice in State P may be suspended or denied. Client L's project faces uncertainty. Engineer A's professional credibility is affirmed if the report is made in good faith, or questioned if it appears retaliatory. The public interest in enforcing licensure standards is directly served.
Decision Point: Yes - Story can branch here
- Give Engineer X additional time before reporting, extending the informal resolution period
- Report the violation anonymously to avoid the appearance of self-interest
- Abandon the matter entirely after the failed direct contact, concluding that Engineer A has done enough
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Action_Report_Violation_to_Authorities",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Give Engineer X additional time before reporting, extending the informal resolution period",
"Report the violation anonymously to avoid the appearance of self-interest",
"Abandon the matter entirely after the failed direct contact, concluding that Engineer A has done enough"
],
"proeth-scenario:characterMotivation": "Having fulfilled the collegial obligation by contacting Engineer X directly, Engineer A is now motivated by a clear professional duty to report an unresolved, ongoing licensure violation to the appropriate authorities. At this stage, the self-interest concern is mitigated by the demonstrated good-faith prior step, and the reporting obligation becomes unambiguous.",
"proeth-scenario:consequencesIfAlternative": [
"Extending the informal period may be reasonable if Engineer X has shown good-faith effort but needs more time; however, indefinite delay allows the violation to continue and may compromise Engineer A\u0027s own compliance with reporting obligations",
"Anonymous reporting removes the self-interest optics but may be less credible to authorities and prevents Engineer A from being a named, accountable complainant; it also raises questions about whether anonymity is itself a form of evasion",
"Abandoning the matter after failed direct contact constitutes a failure of professional duty; Engineer A would be knowingly allowing an ongoing licensure violation to continue, which is itself an ethical breach"
],
"proeth-scenario:decisionSignificance": "Teaches students that professional reporting obligations are real and enforceable, not merely advisory. When collegial first steps fail, the ethical engineer must follow through with formal reporting. This action also illustrates that the graduated response model \u2014 collegial contact first, formal report second \u2014 is not merely a way to avoid reporting, but a structured ethical process that legitimizes formal action when necessary.",
"proeth-scenario:ethicalTension": "Loyalty to a fellow professional and reluctance to cause harm to a colleague\u0027s career and firm vs. the overriding duty to uphold public protection and the integrity of the engineering licensure system. Once collegial outreach has failed, this tension largely resolves in favor of reporting, but Engineer A may still experience discomfort about the consequences for Engineer X.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "Engineer X faces formal disciplinary proceedings, potential fines, and reputational damage. XYZ Engineering\u0027s ability to practice in State P may be suspended or denied. Client L\u0027s project faces uncertainty. Engineer A\u0027s professional credibility is affirmed if the report is made in good faith, or questioned if it appears retaliatory. The public interest in enforcing licensure standards is directly served.",
"proeth:description": "If Engineer A\u0027s direct communication with Engineer X fails to resolve the certificate of authority violation, Engineer A must then decide to formally notify the appropriate State P engineering licensure authorities of the ongoing violation. This escalation fulfills the reporting obligation that collegial first contact had temporarily deferred.",
"proeth:foreseenUnintendedEffects": [
"Formal sanction or investigation of Engineer X and XYZ Engineering",
"Potential disruption to Client L\u0027s project",
"Possible perception that Engineer A used the reporting mechanism to eliminate a competitor",
"Engineer X\u0027s potential inability to enforce contracts or collect fees in State P"
],
"proeth:fulfillsObligation": [
"Legal obligation to report licensure violations to the state engineering board",
"Ethical obligation to uphold the integrity of the licensure system",
"Duty to protect public interest through enforcement of licensure requirements",
"NSPE Code obligation to act in accordance with law and professional standards"
],
"proeth:guidedByPrinciple": [
"Public protection through licensure enforcement",
"Integrity and honesty in professional conduct",
"Proportionate and graduated response to violations",
"Obligation to uphold and advance the engineering profession"
],
"proeth:hasAgent": "Engineer A (Owner, ABC Engineering, State P)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Fulfillment of reporting duty versus risk of appearing to act from competitive self-interest",
"proeth:resolutionReasoning": "Having exhausted the collegial first-contact option without resolution, the reporting obligation becomes paramount; the prior good-faith attempt at resolution demonstrates that the action is motivated by professional duty rather than competitive self-interest"
},
"proeth:hasMentalState": "obligatory and deliberate",
"proeth:intendedOutcome": "Fulfill the legal and ethical obligation to report a known, unresolved licensure violation to the appropriate state authorities, ensuring enforcement of licensure laws that protect the public and the integrity of the profession",
"proeth:requiresCapability": [
"Knowledge of state licensure board reporting procedures",
"Ability to document and present the facts of the violation accurately",
"Ethical judgment to ensure report is made in good faith and not for competitive purposes"
],
"proeth:temporalMarker": "Post-communication decision point, only if direct contact with Engineer X fails to produce compliance",
"proeth:violatesObligation": [
"No obligations violated if reporting is done in good faith after exhausting collegial resolution; however, premature or bad-faith reporting would violate obligations of fair dealing with competitors"
],
"proeth:withinCompetence": true,
"rdfs:label": "Report Violation to Authorities"
}
Description: Upon being informed by Engineer A of the certificate of authority requirement, Engineer X must decide whether to take all appropriate steps to obtain the required certificate from State P's engineering licensure board. The discussion presents this as the expected response of a reasonable and prudent professional.
Temporal Marker: Engineer X's response point, following communication from Engineer A
Mental State: deliberate and compliance-motivated if action is taken
Intended Outcome: Achieve legal authorization to practice engineering in State P, protect XYZ Engineering's ability to enforce its contracts and collect fees, and avoid formal disciplinary proceedings by the State P licensure board
Fulfills Obligations:
- Legal obligation to hold a valid certificate of authority before practicing engineering in State P
- Ethical obligation to comply with state engineering licensure laws
- Duty to protect client interests by ensuring services are legally authorized
- NSPE Code obligation to perform services only within lawful authorization
Guided By Principles:
- Legal compliance as a prerequisite to professional practice
- Responsiveness to professional counsel from a peer
- Protection of client interests through lawful service delivery
- Integrity and accountability in professional conduct
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Upon being informed of the violation by Engineer A, Engineer X is motivated — ideally — by professional integrity, respect for the law, and the desire to protect both clients and the firm's reputation. In a less idealized framing, Engineer X may also be motivated by the pragmatic fear of formal disciplinary action if compliance is not achieved quickly. Both motivations can produce the same correct behavior.
Ethical Tension: The cost, delay, and administrative burden of obtaining a certificate of authority vs. the professional and legal obligation to comply with State P's licensure requirements. There may also be tension between admitting the oversight to Client L and attempting to conceal it, and between the short-term disruption of compliance and the long-term risk of non-compliance.
Learning Significance: Models the expected response of a professionally responsible engineer when a compliance failure is identified: prompt, transparent corrective action. Teaches students that how an engineer responds to a discovered violation is itself an ethical act, and that voluntary compliance after collegial notification is both the ethical and strategically prudent course of action. Also reinforces that licensure requirements are not bureaucratic technicalities but substantive protections.
Stakes: If Engineer X complies promptly, the violation is corrected, formal disciplinary action may be avoided, and the professional relationship with Engineer A and Client L is preserved. If Engineer X refuses or delays, formal reporting becomes inevitable, and the consequences — disciplinary action, fines, reputational damage, potential project disruption — escalate significantly.
Decision Point: Yes - Story can branch here
- Refuse to obtain the certificate, arguing that the work is nearly complete and compliance is no longer practically necessary
- Dispute the applicability of State P's certificate of authority requirement, seeking a legal opinion that the work does not constitute engineering practice in State P
- Withdraw from the project entirely rather than go through the process of obtaining the certificate
Narrative Role: resolution
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Action_Obtain_Certificate_of_Authority",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Refuse to obtain the certificate, arguing that the work is nearly complete and compliance is no longer practically necessary",
"Dispute the applicability of State P\u0027s certificate of authority requirement, seeking a legal opinion that the work does not constitute engineering practice in State P",
"Withdraw from the project entirely rather than go through the process of obtaining the certificate"
],
"proeth-scenario:characterMotivation": "Upon being informed of the violation by Engineer A, Engineer X is motivated \u2014 ideally \u2014 by professional integrity, respect for the law, and the desire to protect both clients and the firm\u0027s reputation. In a less idealized framing, Engineer X may also be motivated by the pragmatic fear of formal disciplinary action if compliance is not achieved quickly. Both motivations can produce the same correct behavior.",
"proeth-scenario:consequencesIfAlternative": [
"Refusing to comply after notification removes any good-faith defense, makes formal reporting by Engineer A virtually certain, and significantly increases the likelihood and severity of disciplinary action; it also signals a willful rather than inadvertent violation",
"Seeking a legal opinion may be legitimate if there is genuine ambiguity about jurisdictional applicability, but if used as a delay tactic or bad-faith challenge to a clear requirement, it compounds the ethical violation and exposes Engineer X to greater risk",
"Withdrawing from the project avoids further unlicensed practice but does not remedy the violation that has already occurred; Client L is harmed by the project disruption, and Engineer X still faces potential disciplinary action for the prior unlicensed work"
],
"proeth-scenario:decisionSignificance": "Models the expected response of a professionally responsible engineer when a compliance failure is identified: prompt, transparent corrective action. Teaches students that how an engineer responds to a discovered violation is itself an ethical act, and that voluntary compliance after collegial notification is both the ethical and strategically prudent course of action. Also reinforces that licensure requirements are not bureaucratic technicalities but substantive protections.",
"proeth-scenario:ethicalTension": "The cost, delay, and administrative burden of obtaining a certificate of authority vs. the professional and legal obligation to comply with State P\u0027s licensure requirements. There may also be tension between admitting the oversight to Client L and attempting to conceal it, and between the short-term disruption of compliance and the long-term risk of non-compliance.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "resolution",
"proeth-scenario:stakes": "If Engineer X complies promptly, the violation is corrected, formal disciplinary action may be avoided, and the professional relationship with Engineer A and Client L is preserved. If Engineer X refuses or delays, formal reporting becomes inevitable, and the consequences \u2014 disciplinary action, fines, reputational damage, potential project disruption \u2014 escalate significantly.",
"proeth:description": "Upon being informed by Engineer A of the certificate of authority requirement, Engineer X must decide whether to take all appropriate steps to obtain the required certificate from State P\u0027s engineering licensure board. The discussion presents this as the expected response of a reasonable and prudent professional.",
"proeth:foreseenUnintendedEffects": [
"Administrative burden and cost of certificate of authority application",
"Acknowledgment that prior practice in State P was conducted without proper authorization",
"Resolution of the matter without formal sanction if obtained promptly",
"Continued ability to serve Client L and future clients in State P"
],
"proeth:fulfillsObligation": [
"Legal obligation to hold a valid certificate of authority before practicing engineering in State P",
"Ethical obligation to comply with state engineering licensure laws",
"Duty to protect client interests by ensuring services are legally authorized",
"NSPE Code obligation to perform services only within lawful authorization"
],
"proeth:guidedByPrinciple": [
"Legal compliance as a prerequisite to professional practice",
"Responsiveness to professional counsel from a peer",
"Protection of client interests through lawful service delivery",
"Integrity and accountability in professional conduct"
],
"proeth:hasAgent": "Engineer X (Owner, XYZ Engineering, State Q)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Continuity of project versus administrative compliance burden",
"proeth:resolutionReasoning": "The discussion concludes that a reasonable and prudent engineer would recognize that obtaining the certificate of authority is clearly in XYZ Engineering\u0027s best interest, as the legal and financial risks of non-compliance far outweigh the administrative burden of compliance"
},
"proeth:hasMentalState": "deliberate and compliance-motivated if action is taken",
"proeth:intendedOutcome": "Achieve legal authorization to practice engineering in State P, protect XYZ Engineering\u0027s ability to enforce its contracts and collect fees, and avoid formal disciplinary proceedings by the State P licensure board",
"proeth:requiresCapability": [
"Knowledge of out-of-state certificate of authority application procedures",
"Administrative capability to compile required documentation for State P licensure board",
"Judgment to act promptly upon learning of the compliance gap"
],
"proeth:temporalMarker": "Engineer X\u0027s response point, following communication from Engineer A",
"proeth:violatesObligation": [
"If Engineer X fails to act: continued violation of State P licensure law, ongoing breach of ethical obligation to comply with applicable regulations"
],
"proeth:withinCompetence": true,
"rdfs:label": "Obtain Certificate of Authority"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changesDescription: Engineer A becomes aware that Engineer X is practicing engineering in State P without the required certificate of authority, triggering Engineer A's ethical and potentially legal obligations to respond.
Temporal Marker: After Engineer X has commenced the engagement with Client L, at an unspecified point during the project
Activates Constraints:
- Professional_Reporting_Obligation_Constraint
- Peer_Ethics_Enforcement_Constraint
- NSPE_Code_Section_III_Reporting_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A likely experiences conflict between professional duty to report and reluctance to create adversarial dynamics with a peer; possible discomfort about whether motivations are purely ethical or influenced by competitive interest; Engineer X is unaware of being observed; Client L remains unaware of the developing situation
- engineer_a: Now bears active ethical obligations; failure to act appropriately could itself constitute an ethics violation; must navigate competing pressures of peer relations, competitive interest, and professional duty
- engineer_x: Unaware that the violation has been discovered; continues in a vulnerable position of ongoing non-compliance
- client_l: Remains unaware but is the subject of growing professional concern about the legitimacy of services being received
- state_p_licensing_board: The regulatory system's enforcement mechanism is now engaged through a private professional observer
- public: Public protection function of licensure requirements is now being activated through peer observation
Learning Moment: This is the pivotal moment that transforms an abstract regulatory violation into an active ethical dilemma requiring decision. Students should understand that knowledge of a violation creates obligations — ignorance is no longer available as a shield — and that the manner of response matters as much as whether to respond.
Ethical Implications: Exposes the tension between professional solidarity and regulatory enforcement; raises the question of whether self-interest can ever legitimately motivate an ethical act; illustrates how the engineering profession relies on peer self-policing to protect the public when regulatory agencies cannot observe every violation directly
- How should Engineer A distinguish between a genuine ethical obligation to report and a self-interested motivation to eliminate a competitor — and does the distinction affect what Engineer A should do?
- At what threshold of certainty about the violation should Engineer A feel obligated to act — is suspicion enough, or must the violation be confirmed?
- What are the risks to Engineer A of acting (reporting) versus not acting (ignoring the violation), and how should those risks be weighed against professional duty?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Event_Violation_Discovered_by_Engineer_A",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"How should Engineer A distinguish between a genuine ethical obligation to report and a self-interested motivation to eliminate a competitor \u2014 and does the distinction affect what Engineer A should do?",
"At what threshold of certainty about the violation should Engineer A feel obligated to act \u2014 is suspicion enough, or must the violation be confirmed?",
"What are the risks to Engineer A of acting (reporting) versus not acting (ignoring the violation), and how should those risks be weighed against professional duty?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A likely experiences conflict between professional duty to report and reluctance to create adversarial dynamics with a peer; possible discomfort about whether motivations are purely ethical or influenced by competitive interest; Engineer X is unaware of being observed; Client L remains unaware of the developing situation",
"proeth-scenario:ethicalImplications": "Exposes the tension between professional solidarity and regulatory enforcement; raises the question of whether self-interest can ever legitimately motivate an ethical act; illustrates how the engineering profession relies on peer self-policing to protect the public when regulatory agencies cannot observe every violation directly",
"proeth-scenario:learningMoment": "This is the pivotal moment that transforms an abstract regulatory violation into an active ethical dilemma requiring decision. Students should understand that knowledge of a violation creates obligations \u2014 ignorance is no longer available as a shield \u2014 and that the manner of response matters as much as whether to respond.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"client_l": "Remains unaware but is the subject of growing professional concern about the legitimacy of services being received",
"engineer_a": "Now bears active ethical obligations; failure to act appropriately could itself constitute an ethics violation; must navigate competing pressures of peer relations, competitive interest, and professional duty",
"engineer_x": "Unaware that the violation has been discovered; continues in a vulnerable position of ongoing non-compliance",
"public": "Public protection function of licensure requirements is now being activated through peer observation",
"state_p_licensing_board": "The regulatory system\u0027s enforcement mechanism is now engaged through a private professional observer"
},
"proeth:activatesConstraint": [
"Professional_Reporting_Obligation_Constraint",
"Peer_Ethics_Enforcement_Constraint",
"NSPE_Code_Section_III_Reporting_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/93#Action_Accept_Engagement_Without_Certificate",
"proeth:causesStateChange": "Engineer A moves from uninformed third party to informed professional observer with active ethical obligations; the violation transitions from a private non-compliance issue to one with a known witness who has professional duties to act",
"proeth:createsObligation": [
"Engineer_A_Must_Decide_How_to_Respond",
"Engineer_A_Must_Contact_Engineer_X_Directly_First",
"Engineer_A_Must_Not_Ignore_Known_Violation",
"Engineer_A_Must_Report_if_Direct_Contact_Fails"
],
"proeth:description": "Engineer A becomes aware that Engineer X is practicing engineering in State P without the required certificate of authority, triggering Engineer A\u0027s ethical and potentially legal obligations to respond.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "After Engineer X has commenced the engagement with Client L, at an unspecified point during the project",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Violation Discovered by Engineer A"
}
Description: Following Engineer A's direct communication with Engineer X, an outcome is produced — either Engineer X agrees to obtain the certificate of authority (compliance) or refuses/fails to act (non-compliance), which determines whether escalation to authorities becomes obligatory.
Temporal Marker: After Engineer A contacts Engineer X directly, before any report to authorities
Activates Constraints:
- Conditional_Reporting_Obligation_Constraint
- Escalation_Trigger_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A experiences relief if Engineer X agrees to comply, or frustration and moral pressure if Engineer X refuses or ignores the communication; Engineer X experiences either a wake-up call prompting corrective action or defensiveness and possible resentment; the outcome carries significant emotional weight for both parties' professional relationship
- engineer_a: Compliance outcome discharges immediate obligation with minimal conflict; non-compliance outcome forces Engineer A into an adversarial reporting role with potential professional and relational consequences
- engineer_x: Compliance outcome allows face-saving resolution and avoidance of formal disciplinary action; non-compliance outcome significantly escalates exposure to formal sanctions
- client_l: Compliance outcome means services will be legitimized; non-compliance outcome may result in project disruption if Engineer X is ultimately sanctioned
- state_p_licensing_board: Compliance outcome may resolve the violation without formal involvement; non-compliance outcome requires formal regulatory response
- public: Compliance outcome restores the protective function of licensure; non-compliance outcome prolongs exposure to unverified engineering practice
Learning Moment: Illustrates that the prescribed ethical response sequence is not merely procedural — each step produces a consequential outcome that reshapes obligations. Students should understand that the direct-contact-first approach respects professional collegiality while still enforcing compliance, and that the outcome of that contact is not discretionary in determining next steps.
Ethical Implications: Reveals the ethical architecture of graduated response — the principle that the least coercive effective intervention is preferable to immediate escalation; raises questions about whether professional courtesy can ever be used to shield ongoing violations; illustrates the difference between resolving an ethics issue and merely managing its visibility
- Why does the NSPE framework prescribe direct peer communication before regulatory reporting — what values does this sequence reflect, and are those values always appropriate?
- If Engineer X promises to obtain the certificate but delays indefinitely, at what point does Engineer A's obligation to report become active?
- Should the outcome of the direct contact step be documented, and what are the implications if Engineer A later needs to demonstrate that this step was taken in good faith?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Event_Direct_Contact_Outcome_Determined",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Why does the NSPE framework prescribe direct peer communication before regulatory reporting \u2014 what values does this sequence reflect, and are those values always appropriate?",
"If Engineer X promises to obtain the certificate but delays indefinitely, at what point does Engineer A\u0027s obligation to report become active?",
"Should the outcome of the direct contact step be documented, and what are the implications if Engineer A later needs to demonstrate that this step was taken in good faith?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A experiences relief if Engineer X agrees to comply, or frustration and moral pressure if Engineer X refuses or ignores the communication; Engineer X experiences either a wake-up call prompting corrective action or defensiveness and possible resentment; the outcome carries significant emotional weight for both parties\u0027 professional relationship",
"proeth-scenario:ethicalImplications": "Reveals the ethical architecture of graduated response \u2014 the principle that the least coercive effective intervention is preferable to immediate escalation; raises questions about whether professional courtesy can ever be used to shield ongoing violations; illustrates the difference between resolving an ethics issue and merely managing its visibility",
"proeth-scenario:learningMoment": "Illustrates that the prescribed ethical response sequence is not merely procedural \u2014 each step produces a consequential outcome that reshapes obligations. Students should understand that the direct-contact-first approach respects professional collegiality while still enforcing compliance, and that the outcome of that contact is not discretionary in determining next steps.",
"proeth-scenario:narrativePacing": "crisis",
"proeth-scenario:stakeholderConsequences": {
"client_l": "Compliance outcome means services will be legitimized; non-compliance outcome may result in project disruption if Engineer X is ultimately sanctioned",
"engineer_a": "Compliance outcome discharges immediate obligation with minimal conflict; non-compliance outcome forces Engineer A into an adversarial reporting role with potential professional and relational consequences",
"engineer_x": "Compliance outcome allows face-saving resolution and avoidance of formal disciplinary action; non-compliance outcome significantly escalates exposure to formal sanctions",
"public": "Compliance outcome restores the protective function of licensure; non-compliance outcome prolongs exposure to unverified engineering practice",
"state_p_licensing_board": "Compliance outcome may resolve the violation without formal involvement; non-compliance outcome requires formal regulatory response"
},
"proeth:activatesConstraint": [
"Conditional_Reporting_Obligation_Constraint",
"Escalation_Trigger_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/93#Action_Contact_Engineer_X_Directly",
"proeth:causesStateChange": "The situation bifurcates: (1) Compliance path \u2014 Engineer X initiates certificate of authority process, violation moves toward resolution, Engineer A\u0027s reporting obligation may be discharged; (2) Non-compliance path \u2014 Engineer A\u0027s obligation to report to State P licensing authorities becomes active and mandatory",
"proeth:createsObligation": [
"If_Non_Compliant_Engineer_A_Must_Report_to_Licensing_Board",
"If_Compliant_Engineer_A_Obligation_to_Report_May_Be_Satisfied"
],
"proeth:description": "Following Engineer A\u0027s direct communication with Engineer X, an outcome is produced \u2014 either Engineer X agrees to obtain the certificate of authority (compliance) or refuses/fails to act (non-compliance), which determines whether escalation to authorities becomes obligatory.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "After Engineer A contacts Engineer X directly, before any report to authorities",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Direct Contact Outcome Determined"
}
Description: Engineer X successfully obtains the required certificate of authority to practice engineering in State P, resolving the active licensure violation and legitimizing the ongoing engagement with Client L.
Temporal Marker: After Engineer A contacts Engineer X directly and Engineer X takes corrective action; before or concurrent with continued project work
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer X likely feels relief and possibly gratitude that the matter was handled privately rather than through formal complaint; Engineer A experiences satisfaction that the peer-first approach worked and the violation is resolved without adversarial escalation; Client L, if informed, gains confidence in the legitimacy of the engagement
- engineer_x: Violation resolved without formal disciplinary record; professional reputation preserved; now in full compliance and able to continue the project legitimately
- engineer_a: Professional obligation discharged; demonstrates that peer-to-peer ethics enforcement can be effective; relationship with Engineer X preserved or potentially strengthened
- client_l: Services legitimized retroactively; project can proceed without regulatory risk; may or may not be informed of the prior violation
- state_p_licensing_board: Regulatory compliance restored without formal enforcement action; the self-policing function of the profession has worked as intended
- public: Regulatory protection fully restored; engineering work now performed by a properly licensed provider
Learning Moment: Demonstrates the ideal resolution pathway — that peer-first intervention can resolve compliance failures without formal adversarial processes, and that the engineering profession's self-policing mechanisms can protect the public effectively when individual engineers act with integrity. Also raises the question of whether the prior unlicensed work should be disclosed or remediated.
Ethical Implications: Illustrates the restorative potential of professional ethics frameworks; raises unresolved questions about retroactive legitimacy of unlicensed work; demonstrates that compliance is a continuous obligation, not a one-time threshold; highlights the value of professional collegiality as an enforcement mechanism while also exposing its limitations when violations are not discovered by peers
- Does obtaining the certificate of authority retroactively legitimize the engineering work performed during the period of non-compliance, or does that prior work remain legally and ethically problematic?
- Should Client L be informed that their engineer was practicing without proper licensure during part of the engagement — and who bears the obligation to disclose this?
- What systemic changes could prevent this type of violation from occurring in the first place, rather than relying on peer discovery and correction after the fact?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Event_Certificate_of_Authority_Obtained",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Does obtaining the certificate of authority retroactively legitimize the engineering work performed during the period of non-compliance, or does that prior work remain legally and ethically problematic?",
"Should Client L be informed that their engineer was practicing without proper licensure during part of the engagement \u2014 and who bears the obligation to disclose this?",
"What systemic changes could prevent this type of violation from occurring in the first place, rather than relying on peer discovery and correction after the fact?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "Engineer X likely feels relief and possibly gratitude that the matter was handled privately rather than through formal complaint; Engineer A experiences satisfaction that the peer-first approach worked and the violation is resolved without adversarial escalation; Client L, if informed, gains confidence in the legitimacy of the engagement",
"proeth-scenario:ethicalImplications": "Illustrates the restorative potential of professional ethics frameworks; raises unresolved questions about retroactive legitimacy of unlicensed work; demonstrates that compliance is a continuous obligation, not a one-time threshold; highlights the value of professional collegiality as an enforcement mechanism while also exposing its limitations when violations are not discovered by peers",
"proeth-scenario:learningMoment": "Demonstrates the ideal resolution pathway \u2014 that peer-first intervention can resolve compliance failures without formal adversarial processes, and that the engineering profession\u0027s self-policing mechanisms can protect the public effectively when individual engineers act with integrity. Also raises the question of whether the prior unlicensed work should be disclosed or remediated.",
"proeth-scenario:narrativePacing": "aftermath",
"proeth-scenario:stakeholderConsequences": {
"client_l": "Services legitimized retroactively; project can proceed without regulatory risk; may or may not be informed of the prior violation",
"engineer_a": "Professional obligation discharged; demonstrates that peer-to-peer ethics enforcement can be effective; relationship with Engineer X preserved or potentially strengthened",
"engineer_x": "Violation resolved without formal disciplinary record; professional reputation preserved; now in full compliance and able to continue the project legitimately",
"public": "Regulatory protection fully restored; engineering work now performed by a properly licensed provider",
"state_p_licensing_board": "Regulatory compliance restored without formal enforcement action; the self-policing function of the profession has worked as intended"
},
"proeth:causedByAction": "http://proethica.org/cases/93#Action_Obtain_Certificate_of_Authority",
"proeth:causesStateChange": "The licensure violation is resolved; Engineer X is now legally authorized to practice in State P; Client L\u0027s engagement is legitimized; Engineer A\u0027s reporting obligation is discharged; the regulatory system\u0027s protective function is restored",
"proeth:createsObligation": [
"Engineer_X_Must_Maintain_Certificate_Renewal",
"Engineer_X_Must_Comply_with_State_P_Practice_Standards"
],
"proeth:description": "Engineer X successfully obtains the required certificate of authority to practice engineering in State P, resolving the active licensure violation and legitimizing the ongoing engagement with Client L.",
"proeth:emergencyStatus": "routine",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "After Engineer A contacts Engineer X directly and Engineer X takes corrective action; before or concurrent with continued project work",
"proeth:urgencyLevel": "low",
"rdfs:label": "Certificate of Authority Obtained"
}
Description: Engineer X begins practicing engineering in State P without holding the required certificate of authority, constituting an active regulatory violation from the moment of engagement.
Temporal Marker: At project commencement, when Engineer X accepts engagement from Client L
Activates Constraints:
- Interstate_Licensure_Compliance_Constraint
- Certificate_of_Authority_Required_Constraint
- Public_Protection_Regulatory_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer X may feel confident or unaware of the severity of the violation; Client L is unaware and therefore unaffected emotionally at this stage; the public is silently exposed to risk from potentially unvetted engineering practice
- engineer_x: Exposed to disciplinary action, fines, potential license revocation in home state, and civil liability; professional reputation at risk
- client_l: Receiving engineering services of uncertain legal standing; contracts may be unenforceable; project approvals could be challenged
- public: Exposed to engineering work not verified as meeting State P standards; regulatory protections undermined
- state_p_licensing_board: Regulatory authority is being circumvented, undermining the integrity of the licensure system
- xyz_engineering: Firm may face institutional liability if violation is attributed to organizational practice rather than individual oversight
Learning Moment: Illustrates that licensure violations are not merely administrative technicalities — they are instantaneous legal and ethical breaches that expose clients, the public, and the engineer to real harm. Students should understand that interstate practice requires proactive compliance before engagement begins.
Ethical Implications: Reveals the tension between commercial opportunity and regulatory compliance; raises questions about whether engineers have an affirmative duty to self-police jurisdictional requirements; highlights how individual non-compliance erodes systemic public trust in the engineering profession
- Why do states require certificates of authority rather than simply recognizing out-of-state licenses, and what public interests does this serve?
- At what point does Engineer X bear full ethical and legal responsibility — when they accepted the engagement or when they first performed engineering work?
- Should Client L bear any responsibility for verifying Engineer X's licensure status before retaining their services?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Event_Licensure_Violation_Occurs",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Why do states require certificates of authority rather than simply recognizing out-of-state licenses, and what public interests does this serve?",
"At what point does Engineer X bear full ethical and legal responsibility \u2014 when they accepted the engagement or when they first performed engineering work?",
"Should Client L bear any responsibility for verifying Engineer X\u0027s licensure status before retaining their services?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "Engineer X may feel confident or unaware of the severity of the violation; Client L is unaware and therefore unaffected emotionally at this stage; the public is silently exposed to risk from potentially unvetted engineering practice",
"proeth-scenario:ethicalImplications": "Reveals the tension between commercial opportunity and regulatory compliance; raises questions about whether engineers have an affirmative duty to self-police jurisdictional requirements; highlights how individual non-compliance erodes systemic public trust in the engineering profession",
"proeth-scenario:learningMoment": "Illustrates that licensure violations are not merely administrative technicalities \u2014 they are instantaneous legal and ethical breaches that expose clients, the public, and the engineer to real harm. Students should understand that interstate practice requires proactive compliance before engagement begins.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"client_l": "Receiving engineering services of uncertain legal standing; contracts may be unenforceable; project approvals could be challenged",
"engineer_x": "Exposed to disciplinary action, fines, potential license revocation in home state, and civil liability; professional reputation at risk",
"public": "Exposed to engineering work not verified as meeting State P standards; regulatory protections undermined",
"state_p_licensing_board": "Regulatory authority is being circumvented, undermining the integrity of the licensure system",
"xyz_engineering": "Firm may face institutional liability if violation is attributed to organizational practice rather than individual oversight"
},
"proeth:activatesConstraint": [
"Interstate_Licensure_Compliance_Constraint",
"Certificate_of_Authority_Required_Constraint",
"Public_Protection_Regulatory_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/93#Action_Accept_Engagement_Without_Certificate",
"proeth:causesStateChange": "Engineer X transitions from licensed engineer (State Q) to unlicensed practitioner (State P); regulatory violation is active and ongoing; Client L is unknowingly receiving services from an unlicensed provider",
"proeth:createsObligation": [
"Engineer_X_Must_Obtain_Certificate_or_Cease_Practice",
"Engineer_X_Must_Disclose_Licensure_Status_to_Client",
"Discovering_Engineer_Must_Address_Violation"
],
"proeth:description": "Engineer X begins practicing engineering in State P without holding the required certificate of authority, constituting an active regulatory violation from the moment of engagement.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "At project commencement, when Engineer X accepts engagement from Client L",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Licensure Violation Occurs"
}
Description: Client L, previously served by Engineer A of ABC Engineering in State P, transitions to retaining Engineer X of XYZ Engineering in State Q, severing the prior professional relationship.
Temporal Marker: Prior to or concurrent with Engineer X's engagement, before the violation is discovered
Activates Constraints:
- Professional_Courtesy_Constraint
- Client_Confidentiality_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel professionally displaced or concerned about the client's welfare; Client L is likely neutral or optimistic about the new arrangement; Engineer X is likely confident about the new business opportunity
- engineer_a: Loss of client revenue; potential concern about the quality of services Client L will receive; later positioned as an informed third-party observer of the violation
- client_l: Gains a new engineering provider but unknowingly one operating outside legal compliance in State P
- engineer_x: Gains a new client and project opportunity, but proceeds into a compliance-deficient engagement
- abc_engineering: Loss of business from Client L; no ongoing project responsibilities
Learning Moment: Demonstrates that client transitions are normal business events but can create contexts where professional observation and ethical responsibilities emerge. Engineer A's prior relationship with Client L is what enables the later discovery of the violation.
Ethical Implications: Raises questions about the boundaries of professional loyalty and whether concern for a former client's welfare is ethically distinguishable from competitive protectionism; highlights how business relationships intersect with professional ethics obligations
- Does Engineer A have any residual professional obligations to Client L after the client relationship ends?
- How does the prior client relationship affect Engineer A's motivations when discovering the violation — and how should students distinguish legitimate concern from competitive self-interest?
- Should engineers have a duty to inform former clients when they observe potential risks in the services a successor engineer is providing?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#Event_Client_Relationship_Transferred",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Does Engineer A have any residual professional obligations to Client L after the client relationship ends?",
"How does the prior client relationship affect Engineer A\u0027s motivations when discovering the violation \u2014 and how should students distinguish legitimate concern from competitive self-interest?",
"Should engineers have a duty to inform former clients when they observe potential risks in the services a successor engineer is providing?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "Engineer A may feel professionally displaced or concerned about the client\u0027s welfare; Client L is likely neutral or optimistic about the new arrangement; Engineer X is likely confident about the new business opportunity",
"proeth-scenario:ethicalImplications": "Raises questions about the boundaries of professional loyalty and whether concern for a former client\u0027s welfare is ethically distinguishable from competitive protectionism; highlights how business relationships intersect with professional ethics obligations",
"proeth-scenario:learningMoment": "Demonstrates that client transitions are normal business events but can create contexts where professional observation and ethical responsibilities emerge. Engineer A\u0027s prior relationship with Client L is what enables the later discovery of the violation.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"abc_engineering": "Loss of business from Client L; no ongoing project responsibilities",
"client_l": "Gains a new engineering provider but unknowingly one operating outside legal compliance in State P",
"engineer_a": "Loss of client revenue; potential concern about the quality of services Client L will receive; later positioned as an informed third-party observer of the violation",
"engineer_x": "Gains a new client and project opportunity, but proceeds into a compliance-deficient engagement"
},
"proeth:activatesConstraint": [
"Professional_Courtesy_Constraint",
"Client_Confidentiality_Constraint"
],
"proeth:causesStateChange": "Client L moves from active client of Engineer A to former client; Engineer A\u0027s ongoing professional duties to Client L cease; Engineer X assumes the client relationship and associated professional responsibilities",
"proeth:createsObligation": [
"Engineer_A_Must_Respect_Client_Autonomy",
"Engineer_A_Must_Not_Improperly_Solicit_Return_of_Client"
],
"proeth:description": "Client L, previously served by Engineer A of ABC Engineering in State P, transitions to retaining Engineer X of XYZ Engineering in State Q, severing the prior professional relationship.",
"proeth:emergencyStatus": "low",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "Prior to or concurrent with Engineer X\u0027s engagement, before the violation is discovered",
"proeth:urgencyLevel": "low",
"rdfs:label": "Client Relationship Transferred"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: Engineer A chooses to contact Engineer X directly to inform him of the certificate of authority requirement, producing an outcome — either Engineer X takes corrective action or the violation persists — that determines the subsequent course of Engineer A's professional obligations
Necessary Factors (NESS):
- Engineer A's discovery of the violation (Event 3)
- Engineer A's ethical obligation under professional codes to address observed violations
- Engineer A's volitional choice to pursue direct communication as the first remedial step
- Engineer X's receipt of and response to Engineer A's communication
Sufficient Factors:
- Discovery of violation + ethical duty to act + choice of direct contact = direct contact outcome is produced, contingent on Engineer X's response
Responsibility Attribution:
Agent: Engineer A (ABC Engineering) for initiating contact; Engineer X for determining the outcome through response
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Violation Discovered by Engineer A (Event 3)
Engineer A becomes aware of XYZ Engineering's unlicensed practice in State P -
Decide Response to Discovered Violation (Action 2)
Engineer A evaluates options: direct contact, reporting to authorities, or inaction -
Contact Engineer X Directly (Action 3)
Engineer A selects direct communication as the first and least adversarial remedial step, consistent with professional ethics norms -
Obtain Certificate of Authority (Action 5)
Engineer X must decide whether to comply by obtaining the certificate or to continue without it -
Direct Contact Outcome Determined (Event 4)
The outcome of Engineer A's direct contact is resolved: either Engineer X obtains the certificate (compliance) or fails to act (escalation required)
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#CausalChain_46acd218",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A chooses to contact Engineer X directly to inform him of the certificate of authority requirement, producing an outcome \u2014 either Engineer X takes corrective action or the violation persists \u2014 that determines the subsequent course of Engineer A\u0027s professional obligations",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A becomes aware of XYZ Engineering\u0027s unlicensed practice in State P",
"proeth:element": "Violation Discovered by Engineer A (Event 3)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A evaluates options: direct contact, reporting to authorities, or inaction",
"proeth:element": "Decide Response to Discovered Violation (Action 2)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A selects direct communication as the first and least adversarial remedial step, consistent with professional ethics norms",
"proeth:element": "Contact Engineer X Directly (Action 3)",
"proeth:step": 3
},
{
"proeth:description": "Engineer X must decide whether to comply by obtaining the certificate or to continue without it",
"proeth:element": "Obtain Certificate of Authority (Action 5)",
"proeth:step": 4
},
{
"proeth:description": "The outcome of Engineer A\u0027s direct contact is resolved: either Engineer X obtains the certificate (compliance) or fails to act (escalation required)",
"proeth:element": "Direct Contact Outcome Determined (Event 4)",
"proeth:step": 5
}
],
"proeth:cause": "Decide Response to Discovered Violation (Action 2) \u2192 Contact Engineer X Directly (Action 3)",
"proeth:counterfactual": "Had Engineer A chosen not to contact Engineer X (e.g., immediately reporting to authorities or taking no action), the direct contact outcome event would not occur; had Engineer X already been compliant, contact would have produced no remedial outcome",
"proeth:effect": "Direct Contact Outcome Determined (Event 4)",
"proeth:necessaryFactors": [
"Engineer A\u0027s discovery of the violation (Event 3)",
"Engineer A\u0027s ethical obligation under professional codes to address observed violations",
"Engineer A\u0027s volitional choice to pursue direct communication as the first remedial step",
"Engineer X\u0027s receipt of and response to Engineer A\u0027s communication"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A (ABC Engineering) for initiating contact; Engineer X for determining the outcome through response",
"proeth:sufficientFactors": [
"Discovery of violation + ethical duty to act + choice of direct contact = direct contact outcome is produced, contingent on Engineer X\u0027s response"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer X accepted a commission to provide engineering services for Client L in State P without first obtaining the required certificate of authority, thereby initiating unlicensed practice
Necessary Factors (NESS):
- Engineer X's volitional decision to accept the commission
- Absence of a valid certificate of authority in State P at time of engagement
- State P's legal requirement for a certificate of authority to practice engineering
Sufficient Factors:
- Combination of accepting commission + lack of certificate + existence of state licensure law = violation occurs automatically upon commencement of services
Responsibility Attribution:
Agent: Engineer X (XYZ Engineering)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Accept Engagement Without Certificate (Action 1)
Engineer X makes the volitional decision to accept Client L's commission in State P without verifying or obtaining the required certificate of authority -
Client Relationship Transferred (Event 2)
Client L formally transitions from ABC Engineering to XYZ Engineering, formalizing the engagement that triggers the practice requirement -
Licensure Violation Occurs (Event 1)
Engineer X begins rendering engineering services in State P, constituting unlicensed practice under state law -
Violation Discovered by Engineer A (Event 3)
Engineer A, the prior engineer of record for Client L, becomes aware of XYZ Engineering's lack of certificate of authority -
Decide Response to Discovered Violation (Action 2)
Engineer A must now determine the appropriate ethical and professional response to the discovered violation
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#CausalChain_510560a9",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer X accepted a commission to provide engineering services for Client L in State P without first obtaining the required certificate of authority, thereby initiating unlicensed practice",
"proeth:causalSequence": [
{
"proeth:description": "Engineer X makes the volitional decision to accept Client L\u0027s commission in State P without verifying or obtaining the required certificate of authority",
"proeth:element": "Accept Engagement Without Certificate (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "Client L formally transitions from ABC Engineering to XYZ Engineering, formalizing the engagement that triggers the practice requirement",
"proeth:element": "Client Relationship Transferred (Event 2)",
"proeth:step": 2
},
{
"proeth:description": "Engineer X begins rendering engineering services in State P, constituting unlicensed practice under state law",
"proeth:element": "Licensure Violation Occurs (Event 1)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A, the prior engineer of record for Client L, becomes aware of XYZ Engineering\u0027s lack of certificate of authority",
"proeth:element": "Violation Discovered by Engineer A (Event 3)",
"proeth:step": 4
},
{
"proeth:description": "Engineer A must now determine the appropriate ethical and professional response to the discovered violation",
"proeth:element": "Decide Response to Discovered Violation (Action 2)",
"proeth:step": 5
}
],
"proeth:cause": "Accept Engagement Without Certificate (Action 1)",
"proeth:counterfactual": "Had Engineer X obtained the certificate of authority prior to accepting the commission, or declined the engagement until properly licensed, no violation would have occurred",
"proeth:effect": "Licensure Violation Occurs (Event 1)",
"proeth:necessaryFactors": [
"Engineer X\u0027s volitional decision to accept the commission",
"Absence of a valid certificate of authority in State P at time of engagement",
"State P\u0027s legal requirement for a certificate of authority to practice engineering"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer X (XYZ Engineering)",
"proeth:sufficientFactors": [
"Combination of accepting commission + lack of certificate + existence of state licensure law = violation occurs automatically upon commencement of services"
],
"proeth:withinAgentControl": true
}
Causal Language: Client L's transition from ABC Engineering to XYZ Engineering places Engineer A in a position of awareness regarding the successor firm's activities, creating the conditions under which Engineer A discovers the certificate of authority deficiency
Necessary Factors (NESS):
- Client L's prior relationship with Engineer A and ABC Engineering
- Engineer A's professional familiarity with State P's licensure requirements
- XYZ Engineering's failure to obtain the certificate of authority before practicing
- Engineer A's access to information about XYZ Engineering's practice in State P
Sufficient Factors:
- Combination of Engineer A's prior client relationship + knowledge of state requirements + XYZ Engineering's visible unlicensed practice = discovery of violation
Responsibility Attribution:
Agent: Engineer X (XYZ Engineering) as root cause; Engineer A as discovering party
Type: indirect
Within Agent Control:
Yes
Causal Sequence:
-
Accept Engagement Without Certificate (Action 1)
Engineer X accepts commission without required certificate, creating the underlying violation -
Client Relationship Transferred (Event 2)
Client L moves from ABC Engineering to XYZ Engineering, alerting Engineer A to XYZ Engineering's involvement in State P -
Licensure Violation Occurs (Event 1)
XYZ Engineering practices without certificate, making the violation an observable fact -
Violation Discovered by Engineer A (Event 3)
Engineer A, prompted by awareness of the client transfer, identifies that XYZ Engineering lacks the required certificate of authority -
Decide Response to Discovered Violation (Action 2)
Engineer A is now ethically and professionally obligated to determine a course of action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#CausalChain_c68bbee6",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Client L\u0027s transition from ABC Engineering to XYZ Engineering places Engineer A in a position of awareness regarding the successor firm\u0027s activities, creating the conditions under which Engineer A discovers the certificate of authority deficiency",
"proeth:causalSequence": [
{
"proeth:description": "Engineer X accepts commission without required certificate, creating the underlying violation",
"proeth:element": "Accept Engagement Without Certificate (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "Client L moves from ABC Engineering to XYZ Engineering, alerting Engineer A to XYZ Engineering\u0027s involvement in State P",
"proeth:element": "Client Relationship Transferred (Event 2)",
"proeth:step": 2
},
{
"proeth:description": "XYZ Engineering practices without certificate, making the violation an observable fact",
"proeth:element": "Licensure Violation Occurs (Event 1)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A, prompted by awareness of the client transfer, identifies that XYZ Engineering lacks the required certificate of authority",
"proeth:element": "Violation Discovered by Engineer A (Event 3)",
"proeth:step": 4
},
{
"proeth:description": "Engineer A is now ethically and professionally obligated to determine a course of action",
"proeth:element": "Decide Response to Discovered Violation (Action 2)",
"proeth:step": 5
}
],
"proeth:cause": "Client Relationship Transferred (Event 2)",
"proeth:counterfactual": "Had Engineer X obtained the certificate of authority before beginning services, Engineer A would have discovered no violation even upon learning of the client transfer",
"proeth:effect": "Violation Discovered by Engineer A (Event 3)",
"proeth:necessaryFactors": [
"Client L\u0027s prior relationship with Engineer A and ABC Engineering",
"Engineer A\u0027s professional familiarity with State P\u0027s licensure requirements",
"XYZ Engineering\u0027s failure to obtain the certificate of authority before practicing",
"Engineer A\u0027s access to information about XYZ Engineering\u0027s practice in State P"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "Engineer X (XYZ Engineering) as root cause; Engineer A as discovering party",
"proeth:sufficientFactors": [
"Combination of Engineer A\u0027s prior client relationship + knowledge of state requirements + XYZ Engineering\u0027s visible unlicensed practice = discovery of violation"
],
"proeth:withinAgentControl": true
}
Causal Language: Upon being informed by Engineer A of the certificate of authority requirement, Engineer X must decide whether to obtain the certificate, and upon doing so, Engineer X successfully obtains the required certificate of authority, resolving the violation
Necessary Factors (NESS):
- Engineer A's direct notification to Engineer X of the specific requirement and its violation
- Engineer X's volitional decision to comply (Action 5)
- State P licensing authority's processing and approval of XYZ Engineering's certificate application
- XYZ Engineering meeting the substantive requirements for the certificate of authority
Sufficient Factors:
- Notification of violation + Engineer X's decision to comply + meeting licensure requirements + authority approval = certificate obtained and violation resolved
Responsibility Attribution:
Agent: Engineer X (XYZ Engineering) bears primary responsibility for obtaining the certificate; Engineer A's notification is the proximate trigger for the remedial action
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Violation Discovered by Engineer A (Event 3)
Engineer A identifies that XYZ Engineering lacks the required certificate of authority in State P -
Contact Engineer X Directly (Action 3)
Engineer A notifies Engineer X of the specific licensure requirement and the existing violation -
Obtain Certificate of Authority (Action 5)
Engineer X, now explicitly informed, makes the volitional decision to comply and submits an application for the certificate of authority -
Direct Contact Outcome Determined — Success (Event 4)
The outcome of Engineer A's direct contact is compliance: Engineer X initiates and completes the certificate process -
Certificate of Authority Obtained (Event 5)
State P grants XYZ Engineering the certificate of authority, resolving the violation and legitimizing ongoing practice
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#CausalChain_89f3f1e5",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Upon being informed by Engineer A of the certificate of authority requirement, Engineer X must decide whether to obtain the certificate, and upon doing so, Engineer X successfully obtains the required certificate of authority, resolving the violation",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A identifies that XYZ Engineering lacks the required certificate of authority in State P",
"proeth:element": "Violation Discovered by Engineer A (Event 3)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A notifies Engineer X of the specific licensure requirement and the existing violation",
"proeth:element": "Contact Engineer X Directly (Action 3)",
"proeth:step": 2
},
{
"proeth:description": "Engineer X, now explicitly informed, makes the volitional decision to comply and submits an application for the certificate of authority",
"proeth:element": "Obtain Certificate of Authority (Action 5)",
"proeth:step": 3
},
{
"proeth:description": "The outcome of Engineer A\u0027s direct contact is compliance: Engineer X initiates and completes the certificate process",
"proeth:element": "Direct Contact Outcome Determined \u2014 Success (Event 4)",
"proeth:step": 4
},
{
"proeth:description": "State P grants XYZ Engineering the certificate of authority, resolving the violation and legitimizing ongoing practice",
"proeth:element": "Certificate of Authority Obtained (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Contact Engineer X Directly (Action 3)",
"proeth:counterfactual": "Without Engineer A\u0027s direct contact, Engineer X may have continued practicing without the certificate indefinitely; without Engineer X\u0027s decision to comply, notification alone would not produce the certificate",
"proeth:effect": "Certificate of Authority Obtained (Event 5)",
"proeth:necessaryFactors": [
"Engineer A\u0027s direct notification to Engineer X of the specific requirement and its violation",
"Engineer X\u0027s volitional decision to comply (Action 5)",
"State P licensing authority\u0027s processing and approval of XYZ Engineering\u0027s certificate application",
"XYZ Engineering meeting the substantive requirements for the certificate of authority"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer X (XYZ Engineering) bears primary responsibility for obtaining the certificate; Engineer A\u0027s notification is the proximate trigger for the remedial action",
"proeth:sufficientFactors": [
"Notification of violation + Engineer X\u0027s decision to comply + meeting licensure requirements + authority approval = certificate obtained and violation resolved"
],
"proeth:withinAgentControl": true
}
Causal Language: If Engineer A's direct communication with Engineer X fails to resolve the certificate of authority violation, Engineer A is ethically obligated to escalate by reporting the violation to the relevant licensing authorities
Necessary Factors (NESS):
- Engineer A's prior direct contact with Engineer X (Action 3) having failed to produce compliance
- Continued unlicensed practice by Engineer X following notification
- Engineer A's professional ethical obligation to protect public welfare by reporting unresolved violations
- Existence of a licensing authority with jurisdiction over the violation
Sufficient Factors:
- Failed direct contact outcome + continuing violation + ethical duty to escalate = obligation and action to report to authorities is triggered
Responsibility Attribution:
Agent: Engineer A bears responsibility for fulfilling the reporting obligation; Engineer X bears responsibility for creating the conditions that necessitate the report through non-compliance
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Contact Engineer X Directly (Action 3)
Engineer A makes direct contact with Engineer X regarding the certificate of authority requirement -
Direct Contact Outcome Determined — Failure (Event 4)
Engineer X fails to obtain the certificate or otherwise resolve the violation following Engineer A's notification -
Licensure Violation Continues (Event 1 — ongoing)
XYZ Engineering continues practicing in State P without the required certificate, sustaining the violation -
Report Violation to Authorities (Action 4)
Engineer A, having exhausted direct resolution, fulfills the ethical obligation to report the ongoing violation to State P's licensing authority -
Regulatory Enforcement Initiated
State P licensing authority receives the report and initiates formal enforcement proceedings against XYZ Engineering
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/93#",
"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/93#CausalChain_8e87c692",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "If Engineer A\u0027s direct communication with Engineer X fails to resolve the certificate of authority violation, Engineer A is ethically obligated to escalate by reporting the violation to the relevant licensing authorities",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A makes direct contact with Engineer X regarding the certificate of authority requirement",
"proeth:element": "Contact Engineer X Directly (Action 3)",
"proeth:step": 1
},
{
"proeth:description": "Engineer X fails to obtain the certificate or otherwise resolve the violation following Engineer A\u0027s notification",
"proeth:element": "Direct Contact Outcome Determined \u2014 Failure (Event 4)",
"proeth:step": 2
},
{
"proeth:description": "XYZ Engineering continues practicing in State P without the required certificate, sustaining the violation",
"proeth:element": "Licensure Violation Continues (Event 1 \u2014 ongoing)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A, having exhausted direct resolution, fulfills the ethical obligation to report the ongoing violation to State P\u0027s licensing authority",
"proeth:element": "Report Violation to Authorities (Action 4)",
"proeth:step": 4
},
{
"proeth:description": "State P licensing authority receives the report and initiates formal enforcement proceedings against XYZ Engineering",
"proeth:element": "Regulatory Enforcement Initiated",
"proeth:step": 5
}
],
"proeth:cause": "Direct Contact Outcome Determined (Event 4) \u2014 Failure Outcome",
"proeth:counterfactual": "Had Engineer X complied upon direct contact and obtained the certificate, the reporting obligation would not arise; had Engineer A chosen to ignore the unresolved violation, reporting would not occur but Engineer A would bear ethical responsibility for inaction",
"proeth:effect": "Report Violation to Authorities (Action 4)",
"proeth:necessaryFactors": [
"Engineer A\u0027s prior direct contact with Engineer X (Action 3) having failed to produce compliance",
"Continued unlicensed practice by Engineer X following notification",
"Engineer A\u0027s professional ethical obligation to protect public welfare by reporting unresolved violations",
"Existence of a licensing authority with jurisdiction over the violation"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A bears responsibility for fulfilling the reporting obligation; Engineer X bears responsibility for creating the conditions that necessitate the report through non-compliance",
"proeth:sufficientFactors": [
"Failed direct contact outcome + continuing violation + ethical duty to escalate = obligation and action to report to authorities is triggered"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (8)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Client L's relationship with Engineer A |
before
Entity1 is before Entity2 |
Client L retaining Engineer X |
time:before
http://www.w3.org/2006/time#before |
Client L is a former client of Engineer A's firm...Engineer X is retained to provide engineering ser... [more] |
| clarification discussion between Engineer A and Engineer X |
before
Entity1 is before Entity2 |
Engineer X obtaining certificate of authority |
time:before
http://www.w3.org/2006/time#before |
part of the discussion between Engineer A and Engineer X would presumably include an explanation...A... [more] |
| Review Engineer A visiting Engineer B's firm |
before
Entity1 is before Entity2 |
discovery of potential safety code violations |
time:before
http://www.w3.org/2006/time#before |
As part of a peer review visit, Review Engineer A visited Engineer B's firm. Following a review of t... [more] |
| discussion between Engineer A and Engineer X (failed resolution) |
before
Entity1 is before Entity2 |
Engineer A informing Engineer X of intent to notify authorities |
time:before
http://www.w3.org/2006/time#before |
if they were unable to resolve the issue, Review Engineer A would have an obligation to inform Engin... [more] |
| Engineer A informing Engineer X of intent to notify authorities |
before
Entity1 is before Entity2 |
reporting to proper authorities |
time:before
http://www.w3.org/2006/time#before |
Review Engineer A must inform Engineer B that as a professional engineer, Engineer A's only alternat... [more] |
| NSPE Board of Ethical Review examination of BER Case 96-8 |
before
Entity1 is before Entity2 |
present case analysis |
time:before
http://www.w3.org/2006/time#before |
As illustrated in BER Case 96-8, when an engineer becomes aware of a violation...In the present case... [more] |
| direct communication between Engineer A and Engineer X |
before
Entity1 is before Entity2 |
reporting violation to state licensing authorities |
time:before
http://www.w3.org/2006/time#before |
most state engineering licensure boards impose an obligation upon engineers to report violations...t... [more] |
| Engineer X being retained by Client L without certificate of authority |
before
Entity1 is before Entity2 |
Engineer A learning of the licensure violation |
time:before
http://www.w3.org/2006/time#before |
Engineer X is retained to provide engineering services for Client L located in State P for a project... [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.