PASS 3: Temporal Dynamics
Case 148: Employment—Duty To Disclose Revocation Of Contractor License
Timeline Overview
OWL-Time Temporal Structure 12 relations time: = w3.org/2006/time
Extracted Actions (4)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A, while actively performing design services for Client B, chose not to disclose a pending ethics complaint filed against him by Client C relating to similar services, determining that the mere allegation did not rise to the level requiring mandatory disclosure. The Board found this decision ethical while recommending Engineer A weigh voluntary limited disclosure as a matter of professional prudence.
Temporal Marker: During active service to Client B (BER Case 97-11, 1997)
Mental State: deliberate
Intended Outcome: Continue providing services to Client B without introducing potentially damaging, unproven allegations that could disrupt the professional relationship or unfairly prejudice Client B's perception
Fulfills Obligations:
- Avoided premature disclosure of unproven, potentially false allegations
- Protected own professional reputation from baseless or maliciously motivated claims
- Continued faithful service to Client B
Guided By Principles:
- Protection from disclosure of unproven allegations
- Faithful agency to client
- Prudent professional judgment regarding disclosure thresholds
- Distinction between allegations and adjudicated findings
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A sought to protect himself from the reputational and business harm of disclosing an unproven allegation, reasoning that a mere complaint — not yet adjudicated or substantiated — did not constitute the kind of established fact that would trigger a mandatory disclosure obligation. He likely also weighed the risk of prejudicing Client B's perception of his work based on an unrelated and potentially unfounded complaint.
Ethical Tension: The engineer's right to be presumed innocent of unproven allegations versus the client's right to make fully informed decisions about who is performing services on their behalf; the duty of transparency with current clients versus the risk of causing unjustified harm to one's professional reputation based on a pending and unresolved complaint; proactive honesty versus the principle that disclosure of unproven matters may itself be misleading or premature.
Learning Significance: Provides a critical comparative precedent that sharpens the distinction between Engineer A's situation and Engineer F's. While Engineer A's non-disclosure involved an unproven, pending allegation, Engineer F's non-disclosure involved a completed, adjudicated disciplinary action — a materially more serious omission. Teaches students to evaluate disclosure obligations along a spectrum of certainty and materiality, and demonstrates that the Board's ethical reasoning is context-sensitive rather than absolutist. Also introduces the concept of 'voluntary limited disclosure' as a middle path between mandatory disclosure and complete silence.
Stakes: Client B's ability to make informed decisions about their service provider; Engineer A's professional reputation if the complaint becomes public through other means; the integrity of the client-engineer trust relationship; the precedent set for how engineers handle pending disciplinary matters in active client relationships.
Decision Point: Yes - Story can branch here
- Voluntarily disclose the pending complaint to Client B in a measured, factual manner, emphasizing its unproven status and providing context, as the Board recommended as a matter of prudence.
- Disclose the existence of the complaint to Client B but request a brief pause in services until the matter is resolved, allowing the client to make an informed decision about continuity.
- Proactively resolve or respond to the pending complaint as quickly as possible before it could affect the Client B relationship, treating rapid resolution as the primary ethical obligation.
Narrative Role: falling_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Action_Non-Disclosure_to_Active_Client__BER_97-11_Precede",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Voluntarily disclose the pending complaint to Client B in a measured, factual manner, emphasizing its unproven status and providing context, as the Board recommended as a matter of prudence.",
"Disclose the existence of the complaint to Client B but request a brief pause in services until the matter is resolved, allowing the client to make an informed decision about continuity.",
"Proactively resolve or respond to the pending complaint as quickly as possible before it could affect the Client B relationship, treating rapid resolution as the primary ethical obligation."
],
"proeth-scenario:characterMotivation": "Engineer A sought to protect himself from the reputational and business harm of disclosing an unproven allegation, reasoning that a mere complaint \u2014 not yet adjudicated or substantiated \u2014 did not constitute the kind of established fact that would trigger a mandatory disclosure obligation. He likely also weighed the risk of prejudicing Client B\u0027s perception of his work based on an unrelated and potentially unfounded complaint.",
"proeth-scenario:consequencesIfAlternative": [
"Voluntary disclosure with appropriate framing would have demonstrated transparency and respect for Client B\u0027s autonomy, potentially strengthening rather than damaging the relationship \u2014 and would have aligned with the Board\u0027s recommendation for professional prudence even though it was not required.",
"Disclosing and offering a service pause would have given Client B maximum agency but risked disrupting project continuity and potentially prejudicing the client against Engineer A before the complaint was resolved \u2014 a higher-risk approach with uncertain benefits.",
"Prioritizing rapid complaint resolution would have been practically beneficial but would not have addressed the immediate disclosure question, and the timeline of complaint resolution is rarely within the engineer\u0027s unilateral control."
],
"proeth-scenario:decisionSignificance": "Provides a critical comparative precedent that sharpens the distinction between Engineer A\u0027s situation and Engineer F\u0027s. While Engineer A\u0027s non-disclosure involved an unproven, pending allegation, Engineer F\u0027s non-disclosure involved a completed, adjudicated disciplinary action \u2014 a materially more serious omission. Teaches students to evaluate disclosure obligations along a spectrum of certainty and materiality, and demonstrates that the Board\u0027s ethical reasoning is context-sensitive rather than absolutist. Also introduces the concept of \u0027voluntary limited disclosure\u0027 as a middle path between mandatory disclosure and complete silence.",
"proeth-scenario:ethicalTension": "The engineer\u0027s right to be presumed innocent of unproven allegations versus the client\u0027s right to make fully informed decisions about who is performing services on their behalf; the duty of transparency with current clients versus the risk of causing unjustified harm to one\u0027s professional reputation based on a pending and unresolved complaint; proactive honesty versus the principle that disclosure of unproven matters may itself be misleading or premature.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "falling_action",
"proeth-scenario:stakes": "Client B\u0027s ability to make informed decisions about their service provider; Engineer A\u0027s professional reputation if the complaint becomes public through other means; the integrity of the client-engineer trust relationship; the precedent set for how engineers handle pending disciplinary matters in active client relationships.",
"proeth:description": "Engineer A, while actively performing design services for Client B, chose not to disclose a pending ethics complaint filed against him by Client C relating to similar services, determining that the mere allegation did not rise to the level requiring mandatory disclosure. The Board found this decision ethical while recommending Engineer A weigh voluntary limited disclosure as a matter of professional prudence.",
"proeth:foreseenUnintendedEffects": [
"Client B might learn of the complaint through other parties and feel the information should have been disclosed",
"Risk of appearing to conceal relevant professional history if complaint became public"
],
"proeth:fulfillsObligation": [
"Avoided premature disclosure of unproven, potentially false allegations",
"Protected own professional reputation from baseless or maliciously motivated claims",
"Continued faithful service to Client B"
],
"proeth:guidedByPrinciple": [
"Protection from disclosure of unproven allegations",
"Faithful agency to client",
"Prudent professional judgment regarding disclosure thresholds",
"Distinction between allegations and adjudicated findings"
],
"proeth:hasAgent": "Engineer A (Professional Engineer, BER Case 97-11)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Protection from reputational harm of unproven allegations vs. proactive candor with client",
"proeth:resolutionReasoning": "Engineer A resolved the conflict by treating the unproven allegation as insufficient to trigger mandatory disclosure; the Board affirmed this as ethical while noting that voluntary limited disclosure would have been the more professionally responsible course of action"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Continue providing services to Client B without introducing potentially damaging, unproven allegations that could disrupt the professional relationship or unfairly prejudice Client B\u0027s perception",
"proeth:requiresCapability": [
"Professional judgment regarding disclosure obligations",
"Ability to assess the materiality and relevance of pending complaints",
"Ethical reasoning about duties to clients during active engagements"
],
"proeth:temporalMarker": "During active service to Client B (BER Case 97-11, 1997)",
"proeth:violatesObligation": [
"Arguably, the spirit of proactive candor with clients about matters that could affect their interests (though Board found this ethical)",
"Missed opportunity to demonstrate transparency and professional responsibility through voluntary limited disclosure"
],
"proeth:withinCompetence": true,
"rdfs:label": "Non-Disclosure to Active Client (BER 97-11 Precedent)"
}
Description: Engineer F deliberately allowed an unlicensed individual unrelated to his contracting firm to use his contractor license number on a separate project, constituting the original act of professional misconduct. This decision directly violated contractor licensing regulations and ultimately led to the revocation of his contractor's license.
Temporal Marker: Past (indeterminate, prior to employment application)
Mental State: deliberate
Intended Outcome: Enable an unlicensed individual to perform work under the cover of Engineer F's contractor license number, likely as a favor or for financial benefit
Guided By Principles:
- Public safety paramount (NSPE First Fundamental Canon)
- Honesty and integrity in all professional dealings
- Avoidance of deceptive acts (NSPE Code)
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer F likely sought to assist an acquaintance or colleague who lacked proper licensing credentials, possibly motivated by personal loyalty, financial arrangement, or a belief that the unlicensed individual was sufficiently competent despite lacking formal credentials. He may have rationalized that the harm was minimal since no one was directly endangered at the time of the decision.
Ethical Tension: Personal loyalty and short-term helpfulness versus professional integrity and regulatory compliance; the immediate benefit to the unlicensed individual versus the long-term protection of the public that licensing systems are designed to provide; collegial generosity versus the fiduciary duty owed to the profession and the public.
Learning Significance: Illustrates that professional licenses are non-transferable instruments of public trust, not personal property to be lent or shared. Demonstrates how a single act of misplaced generosity or ethical compromise can trigger cascading consequences that follow a professional across career transitions and domains, even when the original misconduct occurs outside one's primary licensed profession.
Stakes: Immediate revocation of contractor's license; long-term reputational damage; public safety risk from unlicensed work being performed under false credentials; potential harm to the integrity of the licensing system; future employability and professional standing as an engineer.
Decision Point: Yes - Story can branch here
- Decline to share the license number and instead advise the individual on how to obtain proper licensing or work under a legitimately licensed contractor.
- Refer the unlicensed individual to a properly licensed contractor who could legally supervise the project.
- Report the situation to the relevant licensing board to seek guidance on whether any legal arrangement could allow the individual to perform the work.
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Action_Unlicensed_Individual_License_Sharing",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline to share the license number and instead advise the individual on how to obtain proper licensing or work under a legitimately licensed contractor.",
"Refer the unlicensed individual to a properly licensed contractor who could legally supervise the project.",
"Report the situation to the relevant licensing board to seek guidance on whether any legal arrangement could allow the individual to perform the work."
],
"proeth-scenario:characterMotivation": "Engineer F likely sought to assist an acquaintance or colleague who lacked proper licensing credentials, possibly motivated by personal loyalty, financial arrangement, or a belief that the unlicensed individual was sufficiently competent despite lacking formal credentials. He may have rationalized that the harm was minimal since no one was directly endangered at the time of the decision.",
"proeth-scenario:consequencesIfAlternative": [
"Declining would have preserved Engineer F\u0027s contractor\u0027s license, maintained his professional record, and avoided the downstream employment disclosure dilemma entirely \u2014 though the unlicensed individual would have been unable to proceed with the project as planned.",
"Referring the individual to a licensed contractor would have ensured the project was completed legally and safely, protecting all parties while still providing practical assistance without personal professional risk.",
"Seeking licensing board guidance would have demonstrated good faith, potentially uncovered a lawful path forward, and created a documented record of ethical intent \u2014 significantly reducing or eliminating exposure to disciplinary action."
],
"proeth-scenario:decisionSignificance": "Illustrates that professional licenses are non-transferable instruments of public trust, not personal property to be lent or shared. Demonstrates how a single act of misplaced generosity or ethical compromise can trigger cascading consequences that follow a professional across career transitions and domains, even when the original misconduct occurs outside one\u0027s primary licensed profession.",
"proeth-scenario:ethicalTension": "Personal loyalty and short-term helpfulness versus professional integrity and regulatory compliance; the immediate benefit to the unlicensed individual versus the long-term protection of the public that licensing systems are designed to provide; collegial generosity versus the fiduciary duty owed to the profession and the public.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "Immediate revocation of contractor\u0027s license; long-term reputational damage; public safety risk from unlicensed work being performed under false credentials; potential harm to the integrity of the licensing system; future employability and professional standing as an engineer.",
"proeth:description": "Engineer F deliberately allowed an unlicensed individual unrelated to his contracting firm to use his contractor license number on a separate project, constituting the original act of professional misconduct. This decision directly violated contractor licensing regulations and ultimately led to the revocation of his contractor\u0027s license.",
"proeth:foreseenUnintendedEffects": [
"Risk of regulatory discovery and license revocation",
"Potential public safety hazard from unlicensed work in fire protection context",
"Reputational damage if misconduct became known"
],
"proeth:guidedByPrinciple": [
"Public safety paramount (NSPE First Fundamental Canon)",
"Honesty and integrity in all professional dealings",
"Avoidance of deceptive acts (NSPE Code)"
],
"proeth:hasAgent": "Engineer F (Owner, Fire Sprinkler Contracting Firm)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Personal benefit or loyalty vs. regulatory compliance and public safety",
"proeth:resolutionReasoning": "Engineer F resolved the conflict in favor of personal interest, disregarding regulatory obligations and public safety, resulting in adjudicated wrongdoing and contractor license revocation"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Enable an unlicensed individual to perform work under the cover of Engineer F\u0027s contractor license number, likely as a favor or for financial benefit",
"proeth:requiresCapability": [
"Knowledge of contractor licensing regulations",
"Understanding of the limits of license authority",
"Professional judgment regarding public safety in fire protection"
],
"proeth:temporalMarker": "Past (indeterminate, prior to employment application)",
"proeth:violatesObligation": [
"Duty to hold paramount public safety, health, and welfare",
"Duty to avoid deceptive acts",
"Duty to act with integrity and honesty in all professional activities",
"Regulatory obligation to prevent unauthorized use of contractor license",
"Duty to practice only within authorized and licensed scope"
],
"proeth:withinCompetence": false,
"rdfs:label": "Unlicensed Individual License Sharing"
}
Description: Engineer F answered 'no' to the employment application question asking whether he had ever been disciplined in the practice of professional engineering or had his license suspended or revoked, choosing a narrow legalistic interpretation that excluded his contractor's license revocation. This decision withheld material information relevant to his character, integrity, and fitness as a professional engineer.
Temporal Marker: Application stage (prior to hire)
Mental State: deliberate
Intended Outcome: Secure employment at the engineering firm by avoiding disclosure of the contractor's license revocation, relying on the technical wording of the question to justify the omission
Fulfills Obligations:
- Narrow technical compliance with the literal wording of the application question regarding professional engineering license discipline
Guided By Principles:
- Honesty and candor in employer-employee relationships
- Avoidance of deceptive acts (NSPE Code)
- Whole-person integrity standard (BER Case 75-5)
- Public safety paramount, especially in fire protection context
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer F likely sought to protect his employment prospects by exploiting a perceived technical ambiguity in the application question, which referenced 'professional engineering' discipline specifically. He may have genuinely convinced himself that the contractor's license revocation was legally distinct from his PE license record, or he may have consciously chosen the most self-serving interpretation available to avoid disqualification from a desirable position.
Ethical Tension: Literal legal accuracy versus the spirit of honest disclosure; self-interest in securing employment versus the prospective employer's legitimate right to assess character and fitness; narrow legalistic reasoning versus the broader ethical obligation of honesty that the engineering profession demands; short-term career protection versus long-term professional integrity.
Learning Significance: Demonstrates the critical distinction between technical truthfulness and genuine honesty — a foundational concept in engineering ethics. Teaches that ethical obligations require disclosure of the spirit and intent of questions, not merely their narrowest literal reading. Highlights how selective omission can constitute deception even when no explicit falsehood is stated, and that character-based questions on professional applications are designed to capture the whole person, not just one licensed domain.
Stakes: Engineer F's immediate employment opportunity; the hiring firm's ability to make an informed decision about a candidate's integrity and fitness; the firm's professional reputation if the omission is later discovered; the foundational trust relationship between employer and employee; Engineer F's long-term career and PE license standing if the omission is treated as a separate ethics violation.
Decision Point: Yes - Story can branch here
- Answer 'no' to the narrow PE-specific question but proactively attach a written addendum disclosing the contractor's license revocation and its circumstances.
- Answer 'yes' and provide a full written explanation of the contractor's license revocation, its context, and what was learned from the experience.
- Contact the hiring firm's HR department before submitting the application to ask for clarification on whether the question was intended to encompass non-PE licenses, creating a documented good-faith inquiry.
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Action_Negative_Disclosure_Answer_on_Application",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Answer \u0027no\u0027 to the narrow PE-specific question but proactively attach a written addendum disclosing the contractor\u0027s license revocation and its circumstances.",
"Answer \u0027yes\u0027 and provide a full written explanation of the contractor\u0027s license revocation, its context, and what was learned from the experience.",
"Contact the hiring firm\u0027s HR department before submitting the application to ask for clarification on whether the question was intended to encompass non-PE licenses, creating a documented good-faith inquiry."
],
"proeth-scenario:characterMotivation": "Engineer F likely sought to protect his employment prospects by exploiting a perceived technical ambiguity in the application question, which referenced \u0027professional engineering\u0027 discipline specifically. He may have genuinely convinced himself that the contractor\u0027s license revocation was legally distinct from his PE license record, or he may have consciously chosen the most self-serving interpretation available to avoid disqualification from a desirable position.",
"proeth-scenario:consequencesIfAlternative": [
"Attaching a voluntary addendum would have satisfied both the literal question and the ethical duty of transparency, allowing the employer to make a fully informed decision while demonstrating Engineer F\u0027s honesty \u2014 likely the most professionally favorable outcome even if it introduced uncertainty.",
"Answering \u0027yes\u0027 with full explanation would have demonstrated integrity and given Engineer F the opportunity to frame the incident on his own terms, potentially mitigating its impact; the employer might still have hired him based on his candor and the non-PE nature of the offense.",
"Seeking clarification would have created a documented record of good faith, shifted interpretive responsibility to the employer, and likely resulted in a more complete and defensible disclosure \u2014 protecting Engineer F from later accusations of deliberate concealment."
],
"proeth-scenario:decisionSignificance": "Demonstrates the critical distinction between technical truthfulness and genuine honesty \u2014 a foundational concept in engineering ethics. Teaches that ethical obligations require disclosure of the spirit and intent of questions, not merely their narrowest literal reading. Highlights how selective omission can constitute deception even when no explicit falsehood is stated, and that character-based questions on professional applications are designed to capture the whole person, not just one licensed domain.",
"proeth-scenario:ethicalTension": "Literal legal accuracy versus the spirit of honest disclosure; self-interest in securing employment versus the prospective employer\u0027s legitimate right to assess character and fitness; narrow legalistic reasoning versus the broader ethical obligation of honesty that the engineering profession demands; short-term career protection versus long-term professional integrity.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "Engineer F\u0027s immediate employment opportunity; the hiring firm\u0027s ability to make an informed decision about a candidate\u0027s integrity and fitness; the firm\u0027s professional reputation if the omission is later discovered; the foundational trust relationship between employer and employee; Engineer F\u0027s long-term career and PE license standing if the omission is treated as a separate ethics violation.",
"proeth:description": "Engineer F answered \u0027no\u0027 to the employment application question asking whether he had ever been disciplined in the practice of professional engineering or had his license suspended or revoked, choosing a narrow legalistic interpretation that excluded his contractor\u0027s license revocation. This decision withheld material information relevant to his character, integrity, and fitness as a professional engineer.",
"proeth:foreseenUnintendedEffects": [
"Risk of later discovery of the omission by the employer",
"Potential undermining of trust if the revocation became known post-hire",
"Misrepresentation of character and integrity to the prospective employer"
],
"proeth:fulfillsObligation": [
"Narrow technical compliance with the literal wording of the application question regarding professional engineering license discipline"
],
"proeth:guidedByPrinciple": [
"Honesty and candor in employer-employee relationships",
"Avoidance of deceptive acts (NSPE Code)",
"Whole-person integrity standard (BER Case 75-5)",
"Public safety paramount, especially in fire protection context"
],
"proeth:hasAgent": "Engineer F (Applicant, Professional Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Self-interest and employment prospects vs. duty of candor and full disclosure",
"proeth:resolutionReasoning": "Engineer F resolved the conflict by adopting a legalistic interpretation that technically answered the question as worded while withholding material character information, prioritizing employment prospects over ethical candor; the Discussion section concludes this resolution was ethically deficient"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Secure employment at the engineering firm by avoiding disclosure of the contractor\u0027s license revocation, relying on the technical wording of the question to justify the omission",
"proeth:requiresCapability": [
"Understanding of professional disclosure obligations",
"Ethical judgment regarding scope of required disclosure",
"Ability to interpret employment application questions in good faith"
],
"proeth:temporalMarker": "Application stage (prior to hire)",
"proeth:violatesObligation": [
"Duty of full and honest disclosure to prospective employers",
"Duty to avoid deceptive acts (NSPE Code)",
"Duty to act with integrity and candor in all professional dealings",
"Obligation not to misrepresent professional history or character",
"Duty to act as a faithful agent and trustee"
],
"proeth:withinCompetence": true,
"rdfs:label": "Negative Disclosure Answer on Application"
}
Description: After being hired, Engineer F made no proactive effort to disclose the contractor's license revocation to his new employer at any point, allowing the employer to remain uninformed until independently discovering the information through unspecified means. This ongoing omission compounded the initial failure to disclose at the application stage.
Temporal Marker: Post-hire (indeterminate, prior to employer's independent discovery)
Mental State: deliberate
Intended Outcome: Maintain employment and avoid the professional and reputational consequences of disclosing the contractor's license revocation to the employer
Guided By Principles:
- Honesty and candor in all professional relationships
- Faithful agency and trustee obligations to employer
- Going beyond minimum compliance to demonstrate integrity (NSPE Discussion principle)
- Whole-person integrity standard (BER Case 75-5)
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Having already omitted the information on the application, Engineer F faced increasing psychological pressure to maintain consistency with his prior non-disclosure. Proactive post-hire disclosure would have required admitting both the original revocation and the omission on the application — effectively compounding the perceived risk. He may have rationalized that the matter was resolved, historical, and unlikely to surface, or that disclosure would cause more harm than continued silence.
Ethical Tension: The ongoing duty of honesty and transparency in a professional relationship versus the self-protective instinct to avoid compounding an already compromised situation; the employer's right to know material facts about an employee's professional history versus Engineer F's fear of termination or further disciplinary action; the principle that ethical obligations do not expire after the initial opportunity for disclosure has passed.
Learning Significance: Illustrates that ethical obligations are continuous, not one-time events — the duty to be honest with an employer does not end at the application stage. Teaches that post-hire non-disclosure can transform a passive omission into an active, ongoing deception that compounds the original ethical failure. Also demonstrates how one ethical lapse creates pressure toward further lapses, showing the 'slippery slope' dynamic in professional misconduct.
Stakes: The employment relationship's foundation of trust; the firm's ongoing exposure to reputational risk from employing someone with an undisclosed disciplinary history; Engineer F's PE license, which could face scrutiny if the pattern of non-disclosure is treated as a separate ethics violation; the firm's clients, who may have a stake in knowing the full professional background of engineers working on their projects.
Decision Point: Yes - Story can branch here
- Shortly after being hired, schedule a private meeting with a supervisor or HR representative to voluntarily disclose the contractor's license revocation and explain the application answer, framing it as a clarification rather than a confession.
- Consult with a professional ethics advisor or attorney about the disclosure obligation and act on that guidance before the information surfaces independently.
- Disclose the revocation in the context of a performance review or professional development discussion, positioning it as part of a broader reflection on professional lessons learned.
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Action_Post-Hire_Non-Disclosure_of_Revocation",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Shortly after being hired, schedule a private meeting with a supervisor or HR representative to voluntarily disclose the contractor\u0027s license revocation and explain the application answer, framing it as a clarification rather than a confession.",
"Consult with a professional ethics advisor or attorney about the disclosure obligation and act on that guidance before the information surfaces independently.",
"Disclose the revocation in the context of a performance review or professional development discussion, positioning it as part of a broader reflection on professional lessons learned."
],
"proeth-scenario:characterMotivation": "Having already omitted the information on the application, Engineer F faced increasing psychological pressure to maintain consistency with his prior non-disclosure. Proactive post-hire disclosure would have required admitting both the original revocation and the omission on the application \u2014 effectively compounding the perceived risk. He may have rationalized that the matter was resolved, historical, and unlikely to surface, or that disclosure would cause more harm than continued silence.",
"proeth-scenario:consequencesIfAlternative": [
"Voluntary early disclosure would have demonstrated integrity and given Engineer F control over the narrative; while potentially uncomfortable, it would have been far less damaging than discovery by the employer through independent means, and might have preserved the employment relationship.",
"Seeking professional guidance would have provided legal and ethical clarity, potentially resulting in a structured disclosure strategy that minimized risk while fulfilling the obligation \u2014 and would have demonstrated good faith if the matter was later scrutinized.",
"Contextual disclosure in a professional development setting would have been less confrontational, framed the incident as a growth experience, and still satisfied the ethical obligation \u2014 though timing it to a performance review might appear strategic if scrutinized."
],
"proeth-scenario:decisionSignificance": "Illustrates that ethical obligations are continuous, not one-time events \u2014 the duty to be honest with an employer does not end at the application stage. Teaches that post-hire non-disclosure can transform a passive omission into an active, ongoing deception that compounds the original ethical failure. Also demonstrates how one ethical lapse creates pressure toward further lapses, showing the \u0027slippery slope\u0027 dynamic in professional misconduct.",
"proeth-scenario:ethicalTension": "The ongoing duty of honesty and transparency in a professional relationship versus the self-protective instinct to avoid compounding an already compromised situation; the employer\u0027s right to know material facts about an employee\u0027s professional history versus Engineer F\u0027s fear of termination or further disciplinary action; the principle that ethical obligations do not expire after the initial opportunity for disclosure has passed.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "The employment relationship\u0027s foundation of trust; the firm\u0027s ongoing exposure to reputational risk from employing someone with an undisclosed disciplinary history; Engineer F\u0027s PE license, which could face scrutiny if the pattern of non-disclosure is treated as a separate ethics violation; the firm\u0027s clients, who may have a stake in knowing the full professional background of engineers working on their projects.",
"proeth:description": "After being hired, Engineer F made no proactive effort to disclose the contractor\u0027s license revocation to his new employer at any point, allowing the employer to remain uninformed until independently discovering the information through unspecified means. This ongoing omission compounded the initial failure to disclose at the application stage.",
"proeth:foreseenUnintendedEffects": [
"Continued erosion of trust if discovery occurred",
"Compounding of initial deceptive omission over time",
"Risk of more severe consequences upon eventual discovery"
],
"proeth:guidedByPrinciple": [
"Honesty and candor in all professional relationships",
"Faithful agency and trustee obligations to employer",
"Going beyond minimum compliance to demonstrate integrity (NSPE Discussion principle)",
"Whole-person integrity standard (BER Case 75-5)"
],
"proeth:hasAgent": "Engineer F (Employee, Professional Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Preserving employment security vs. ongoing duty of honest disclosure",
"proeth:resolutionReasoning": "Engineer F continued to resolve the conflict in favor of self-interest and employment preservation, forgoing voluntary disclosure and allowing the employer to remain uninformed; the Discussion section identifies this as a failure that undermined the foundational trust of the employment relationship"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Maintain employment and avoid the professional and reputational consequences of disclosing the contractor\u0027s license revocation to the employer",
"proeth:requiresCapability": [
"Professional judgment regarding ongoing disclosure obligations",
"Ethical reasoning about duties to employer beyond initial application stage",
"Courage to disclose damaging but relevant professional history"
],
"proeth:temporalMarker": "Post-hire (indeterminate, prior to employer\u0027s independent discovery)",
"proeth:violatesObligation": [
"Duty of ongoing candor and honest dealing with employer",
"Duty to act as a faithful agent and trustee",
"Duty to avoid deceptive acts through continued concealment",
"Obligation to maintain trust and integrity in the employer-employee relationship",
"Duty to hold paramount public safety given fire protection context"
],
"proeth:withinCompetence": true,
"rdfs:label": "Post-Hire Non-Disclosure of Revocation"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changesDescription: Engineer F's contractor's license was formally revoked by the relevant licensing authority as a direct consequence of allowing an unlicensed individual to use his contractor license number on an unrelated project. This revocation created a permanent disciplinary record attached to Engineer F's contracting credentials.
Temporal Marker: Prior to employment application; exact date unspecified but after the license-sharing incident
Activates Constraints:
- Honesty_Disclosure_Constraint
- Professional_Integrity_Constraint
- Future_Application_Truthfulness_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer F likely experienced shame, anxiety, and concern about professional reputation; colleagues and clients of the contracting firm may have felt betrayed or alarmed; the unlicensed individual may have felt implicated or relieved depending on outcomes; the broader professional engineering community would view this as a cautionary example of regulatory consequences
- engineer_f: Permanent disciplinary record created; loss of contracting business capability; reputational damage in contracting sector; future obligation to disclose on professional applications
- unlicensed_individual: Project may have proceeded under false credentials, raising quality and safety concerns for that project's stakeholders
- clients_of_contracting_firm: Potential exposure to work performed under improperly licensed conditions
- future_employers: Unaware of disciplinary history unless Engineer F discloses, creating information asymmetry and potential risk
- public: Regulatory system functioned as intended by removing a contractor who violated licensing rules, but downstream effects on public trust remain
Learning Moment: Regulatory sanctions create lasting records that follow professionals across career transitions; the revocation of one type of license (contractor) can have cascading implications for how a professional is perceived in another domain (professional engineering), even if that second license is technically unaffected. Students should understand that disciplinary history is not compartmentalized.
Ethical Implications: Reveals tension between the technical scope of a disciplinary action (contractor license only) and its broader moral significance as evidence of character; raises questions about whether professional integrity is domain-specific or holistic; highlights how regulatory systems function as proxies for public trust in professional competence and honesty
- Should the revocation of a contractor's license automatically require disclosure on a professional engineering application, even if the PE license was never suspended?
- What does the licensing authority's decision to revoke—rather than merely warn or fine—signal about the severity of license-sharing violations?
- How does this event change Engineer F's ethical obligations going forward, and at what point did those obligations arise?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Event_Contractor_License_Revocation",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Should the revocation of a contractor\u0027s license automatically require disclosure on a professional engineering application, even if the PE license was never suspended?",
"What does the licensing authority\u0027s decision to revoke\u2014rather than merely warn or fine\u2014signal about the severity of license-sharing violations?",
"How does this event change Engineer F\u0027s ethical obligations going forward, and at what point did those obligations arise?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer F likely experienced shame, anxiety, and concern about professional reputation; colleagues and clients of the contracting firm may have felt betrayed or alarmed; the unlicensed individual may have felt implicated or relieved depending on outcomes; the broader professional engineering community would view this as a cautionary example of regulatory consequences",
"proeth-scenario:ethicalImplications": "Reveals tension between the technical scope of a disciplinary action (contractor license only) and its broader moral significance as evidence of character; raises questions about whether professional integrity is domain-specific or holistic; highlights how regulatory systems function as proxies for public trust in professional competence and honesty",
"proeth-scenario:learningMoment": "Regulatory sanctions create lasting records that follow professionals across career transitions; the revocation of one type of license (contractor) can have cascading implications for how a professional is perceived in another domain (professional engineering), even if that second license is technically unaffected. Students should understand that disciplinary history is not compartmentalized.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"clients_of_contracting_firm": "Potential exposure to work performed under improperly licensed conditions",
"engineer_f": "Permanent disciplinary record created; loss of contracting business capability; reputational damage in contracting sector; future obligation to disclose on professional applications",
"future_employers": "Unaware of disciplinary history unless Engineer F discloses, creating information asymmetry and potential risk",
"public": "Regulatory system functioned as intended by removing a contractor who violated licensing rules, but downstream effects on public trust remain",
"unlicensed_individual": "Project may have proceeded under false credentials, raising quality and safety concerns for that project\u0027s stakeholders"
},
"proeth:activatesConstraint": [
"Honesty_Disclosure_Constraint",
"Professional_Integrity_Constraint",
"Future_Application_Truthfulness_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/148#Action_Unlicensed_Individual_License_Sharing",
"proeth:causesStateChange": "Engineer F transitions from licensed contractor to revoked-license status; a formal disciplinary record is created; Engineer F\u0027s ability to operate a fire sprinkler contracting firm is terminated; a disclosure obligation is triggered for all future professional applications",
"proeth:createsObligation": [
"Obligation_To_Disclose_Disciplinary_Record_On_Future_Applications",
"Obligation_To_Acknowledge_Regulatory_Sanction",
"Obligation_To_Reflect_On_Professional_Conduct"
],
"proeth:description": "Engineer F\u0027s contractor\u0027s license was formally revoked by the relevant licensing authority as a direct consequence of allowing an unlicensed individual to use his contractor license number on an unrelated project. This revocation created a permanent disciplinary record attached to Engineer F\u0027s contracting credentials.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Prior to employment application; exact date unspecified but after the license-sharing incident",
"proeth:urgencyLevel": "high",
"rdfs:label": "Contractor License Revocation"
}
Description: Despite the revocation of his contractor's license, Engineer F's professional engineering license was never suspended or revoked by the relevant PE licensing authority. This outcome created an ambiguous factual condition that Engineer F later exploited in his application response.
Temporal Marker: Concurrent with or shortly after the contractor license revocation; prior to employment application
Activates Constraints:
- Truthfulness_In_Application_Constraint
- Spirit_vs_Letter_Of_Disclosure_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer F may have experienced relief that his PE license survived; this relief may have rationalized or encouraged the subsequent narrow interpretation of the application question; future employer would feel deceived upon discovery; ethics reviewers feel concern about the loophole this creates
- engineer_f: Retains professional engineering credentials and career pathway; gains a factual basis for a technically narrow but ethically problematic answer on future applications
- future_employer: Exposed to the risk of hiring someone with undisclosed disciplinary history due to the regulatory gap
- pe_licensing_authority: Its inaction inadvertently creates an information asymmetry that undermines employer trust
- public: Potentially exposed to a professional engineer whose broader fitness for practice has not been fully vetted
Learning Moment: The technical survival of one license does not morally cleanse a professional's record; students should grapple with the difference between what is technically true and what is fully honest, and understand that application questions are designed to surface fitness concerns, not merely legal technicalities.
Ethical Implications: Exposes the gap between regulatory compliance and ethical conduct; raises the question of whether honesty requires going beyond the literal truth to provide full context; highlights how compartmentalized licensing systems can inadvertently enable misleading self-presentation
- Does the PE licensing authority's failure to act on the contractor revocation imply that the violation was irrelevant to PE practice, or does it simply reflect a jurisdictional gap?
- If Engineer F's PE license was never touched, is he morally obligated to volunteer information about the contractor license revocation? Why or why not?
- How should engineering application forms be designed to close the loophole that Engineer F exploited?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Event_PE_License_Non-Suspension_Outcome",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Does the PE licensing authority\u0027s failure to act on the contractor revocation imply that the violation was irrelevant to PE practice, or does it simply reflect a jurisdictional gap?",
"If Engineer F\u0027s PE license was never touched, is he morally obligated to volunteer information about the contractor license revocation? Why or why not?",
"How should engineering application forms be designed to close the loophole that Engineer F exploited?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer F may have experienced relief that his PE license survived; this relief may have rationalized or encouraged the subsequent narrow interpretation of the application question; future employer would feel deceived upon discovery; ethics reviewers feel concern about the loophole this creates",
"proeth-scenario:ethicalImplications": "Exposes the gap between regulatory compliance and ethical conduct; raises the question of whether honesty requires going beyond the literal truth to provide full context; highlights how compartmentalized licensing systems can inadvertently enable misleading self-presentation",
"proeth-scenario:learningMoment": "The technical survival of one license does not morally cleanse a professional\u0027s record; students should grapple with the difference between what is technically true and what is fully honest, and understand that application questions are designed to surface fitness concerns, not merely legal technicalities.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"engineer_f": "Retains professional engineering credentials and career pathway; gains a factual basis for a technically narrow but ethically problematic answer on future applications",
"future_employer": "Exposed to the risk of hiring someone with undisclosed disciplinary history due to the regulatory gap",
"pe_licensing_authority": "Its inaction inadvertently creates an information asymmetry that undermines employer trust",
"public": "Potentially exposed to a professional engineer whose broader fitness for practice has not been fully vetted"
},
"proeth:activatesConstraint": [
"Truthfulness_In_Application_Constraint",
"Spirit_vs_Letter_Of_Disclosure_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/148#Action_Unlicensed_Individual_License_Sharing",
"proeth:causesStateChange": "Engineer F retains active PE license status; a factual gap emerges between his contractor disciplinary record and his PE license record; this gap creates the conditions for a technically-narrow-but-misleading application response",
"proeth:createsObligation": [
"Obligation_To_Consider_Whether_Omission_Is_Misleading",
"Obligation_To_Represent_Full_Professional_History_Accurately"
],
"proeth:description": "Despite the revocation of his contractor\u0027s license, Engineer F\u0027s professional engineering license was never suspended or revoked by the relevant PE licensing authority. This outcome created an ambiguous factual condition that Engineer F later exploited in his application response.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Concurrent with or shortly after the contractor license revocation; prior to employment application",
"proeth:urgencyLevel": "low",
"rdfs:label": "PE License Non-Suspension Outcome"
}
Description: The engineering firm that hired Engineer F subsequently discovered the existence of his contractor's license revocation, a fact that had not been disclosed during the application process. This discovery triggered immediate questions about Engineer F's honesty, integrity, and fitness as a professional engineer.
Temporal Marker: After Engineer F was hired; exact timing unspecified
Activates Constraints:
- Employer_Duty_To_Investigate_Fitness_Constraint
- Professional_Integrity_Review_Constraint
- Honesty_Retroactive_Assessment_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: The firm's leadership likely experienced shock, betrayal, and anger upon discovering the omission; Engineer F likely felt fear, embarrassment, and anxiety about professional consequences; colleagues of Engineer F may have felt uncertainty and concern about working alongside someone whose integrity is now in question; the broader engineering community observing the case may feel concern about systemic trust in professional self-reporting
- engineer_f: Professional reputation severely damaged; employment at risk; potential referral to PE licensing board; forced to confront consequences of the application omission
- engineering_firm: Trust in internal hiring processes shaken; potential liability if Engineer F's conduct on firm projects is scrutinized; must decide on employment and reporting actions
- firm_clients: May question whether work performed by Engineer F meets expected standards of professional integrity
- pe_licensing_authority: May receive a referral or complaint triggering a formal investigation into Engineer F's PE license fitness
- public: Trust in engineering profession's self-policing mechanisms is implicated
Learning Moment: Omissions and misrepresentations on professional applications are rarely permanently hidden; the discovery of undisclosed disciplinary history compounds the original ethical violation with a second, often more damaging, integrity failure. Students should understand that the cover-up is frequently worse than the original offense in professional ethics contexts.
Ethical Implications: Reveals that professional integrity is not merely about avoiding detection but about building trustworthy relationships; demonstrates how a single act of omission creates cascading consequences for multiple stakeholders; raises questions about institutional responsibility for vetting professionals and the adequacy of self-reporting systems in maintaining public trust
- At the moment of discovery, what are the engineering firm's ethical and legal obligations toward Engineer F, its clients, and the public?
- Does the firm bear any responsibility for not discovering the contractor license revocation before hiring Engineer F?
- How does the discovery of the omission change the ethical analysis of Engineer F's original application answer—does it matter that he was eventually caught?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Event_Firm_Discovers_Revocation",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"At the moment of discovery, what are the engineering firm\u0027s ethical and legal obligations toward Engineer F, its clients, and the public?",
"Does the firm bear any responsibility for not discovering the contractor license revocation before hiring Engineer F?",
"How does the discovery of the omission change the ethical analysis of Engineer F\u0027s original application answer\u2014does it matter that he was eventually caught?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "The firm\u0027s leadership likely experienced shock, betrayal, and anger upon discovering the omission; Engineer F likely felt fear, embarrassment, and anxiety about professional consequences; colleagues of Engineer F may have felt uncertainty and concern about working alongside someone whose integrity is now in question; the broader engineering community observing the case may feel concern about systemic trust in professional self-reporting",
"proeth-scenario:ethicalImplications": "Reveals that professional integrity is not merely about avoiding detection but about building trustworthy relationships; demonstrates how a single act of omission creates cascading consequences for multiple stakeholders; raises questions about institutional responsibility for vetting professionals and the adequacy of self-reporting systems in maintaining public trust",
"proeth-scenario:learningMoment": "Omissions and misrepresentations on professional applications are rarely permanently hidden; the discovery of undisclosed disciplinary history compounds the original ethical violation with a second, often more damaging, integrity failure. Students should understand that the cover-up is frequently worse than the original offense in professional ethics contexts.",
"proeth-scenario:narrativePacing": "crisis",
"proeth-scenario:stakeholderConsequences": {
"engineer_f": "Professional reputation severely damaged; employment at risk; potential referral to PE licensing board; forced to confront consequences of the application omission",
"engineering_firm": "Trust in internal hiring processes shaken; potential liability if Engineer F\u0027s conduct on firm projects is scrutinized; must decide on employment and reporting actions",
"firm_clients": "May question whether work performed by Engineer F meets expected standards of professional integrity",
"pe_licensing_authority": "May receive a referral or complaint triggering a formal investigation into Engineer F\u0027s PE license fitness",
"public": "Trust in engineering profession\u0027s self-policing mechanisms is implicated"
},
"proeth:activatesConstraint": [
"Employer_Duty_To_Investigate_Fitness_Constraint",
"Professional_Integrity_Review_Constraint",
"Honesty_Retroactive_Assessment_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/148#Action_Negative_Disclosure_Answer_on_Application",
"proeth:causesStateChange": "The employment relationship is destabilized; Engineer F\u0027s credibility and honesty are formally in question within the firm; the firm must now make decisions about Engineer F\u0027s continued employment and whether to report findings to licensing authorities; the ethical case crystallizes around this discovery moment",
"proeth:createsObligation": [
"Obligation_Of_Firm_To_Evaluate_Engineer_F_Fitness",
"Obligation_Of_Firm_To_Consider_Disciplinary_Or_Termination_Action",
"Obligation_To_Reassess_Engineer_F_Trustworthiness",
"Potential_Obligation_To_Report_To_PE_Licensing_Authority"
],
"proeth:description": "The engineering firm that hired Engineer F subsequently discovered the existence of his contractor\u0027s license revocation, a fact that had not been disclosed during the application process. This discovery triggered immediate questions about Engineer F\u0027s honesty, integrity, and fitness as a professional engineer.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "After Engineer F was hired; exact timing unspecified",
"proeth:urgencyLevel": "high",
"rdfs:label": "Firm Discovers Revocation"
}
Description: Engineer F was presumably hired by the engineering firm following his submission of the employment application in which he answered 'no' to the disciplinary history question. This hiring outcome represents the firm's reliance on Engineer F's incomplete and misleading application response.
Temporal Marker: After submission of employment application; before post-hire discovery of revocation
Activates Constraints:
- Employer_Reliance_On_Accurate_Disclosure_Constraint
- Employee_Ongoing_Honesty_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer F likely felt relief and perhaps justification upon being hired; the firm's hiring managers felt confidence in their selection; no immediate emotional alarm exists at this stage, making the subsequent discovery more dramatically impactful by contrast
- engineer_f: Gains employment and professional opportunity, but at the cost of an ongoing deception that creates future vulnerability
- engineering_firm: Exposed to reputational, legal, and ethical risk by unknowingly employing someone with an undisclosed disciplinary record
- firm_clients: Potentially exposed to work performed by an engineer whose full professional history was not vetted
- public: Trust in professional hiring and credentialing systems implicitly at risk
Learning Moment: The moment of being hired under false pretenses is not the end of an ethical problem but the beginning of a compounding one; students should understand that ongoing employment built on a misrepresentation creates a continuing obligation to correct the record, not merely a historical wrong. The hiring event also illustrates institutional vulnerability when background verification is inadequate.
Ethical Implications: Illustrates how institutional trust systems (self-reported applications) are vulnerable to exploitation; raises questions about the distribution of responsibility between individual professionals and institutional gatekeepers; highlights how a single act of omission initiates an ongoing ethical failure rather than a discrete one-time wrong
- Once hired, did Engineer F have an ethical obligation to proactively correct his application misrepresentation? At what point, if any, does that obligation expire?
- What verification practices should engineering firms implement to avoid relying solely on self-reported disciplinary history?
- Does the firm bear any moral responsibility for the situation it finds itself in after hiring Engineer F without independent verification?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Event_Engineer_F_Hired_By_Firm",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Once hired, did Engineer F have an ethical obligation to proactively correct his application misrepresentation? At what point, if any, does that obligation expire?",
"What verification practices should engineering firms implement to avoid relying solely on self-reported disciplinary history?",
"Does the firm bear any moral responsibility for the situation it finds itself in after hiring Engineer F without independent verification?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "Engineer F likely felt relief and perhaps justification upon being hired; the firm\u0027s hiring managers felt confidence in their selection; no immediate emotional alarm exists at this stage, making the subsequent discovery more dramatically impactful by contrast",
"proeth-scenario:ethicalImplications": "Illustrates how institutional trust systems (self-reported applications) are vulnerable to exploitation; raises questions about the distribution of responsibility between individual professionals and institutional gatekeepers; highlights how a single act of omission initiates an ongoing ethical failure rather than a discrete one-time wrong",
"proeth-scenario:learningMoment": "The moment of being hired under false pretenses is not the end of an ethical problem but the beginning of a compounding one; students should understand that ongoing employment built on a misrepresentation creates a continuing obligation to correct the record, not merely a historical wrong. The hiring event also illustrates institutional vulnerability when background verification is inadequate.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"engineer_f": "Gains employment and professional opportunity, but at the cost of an ongoing deception that creates future vulnerability",
"engineering_firm": "Exposed to reputational, legal, and ethical risk by unknowingly employing someone with an undisclosed disciplinary record",
"firm_clients": "Potentially exposed to work performed by an engineer whose full professional history was not vetted",
"public": "Trust in professional hiring and credentialing systems implicitly at risk"
},
"proeth:activatesConstraint": [
"Employer_Reliance_On_Accurate_Disclosure_Constraint",
"Employee_Ongoing_Honesty_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/148#Action_Negative_Disclosure_Answer_on_Application",
"proeth:causesStateChange": "Engineer F enters a new professional role under false pretenses; the firm\u0027s trust is extended based on incomplete information; a latent risk of discovery is created; Engineer F\u0027s ongoing silence about the revocation transitions from pre-hire omission to post-hire active concealment",
"proeth:createsObligation": [
"Obligation_Of_Engineer_F_To_Perform_Competently_And_Honestly_As_Employee",
"Obligation_Of_Firm_To_Supervise_And_Evaluate_Engineer_F",
"Ongoing_Obligation_Of_Engineer_F_To_Correct_Misleading_Application_Response"
],
"proeth:description": "Engineer F was presumably hired by the engineering firm following his submission of the employment application in which he answered \u0027no\u0027 to the disciplinary history question. This hiring outcome represents the firm\u0027s reliance on Engineer F\u0027s incomplete and misleading application response.",
"proeth:emergencyStatus": "low",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "After submission of employment application; before post-hire discovery of revocation",
"proeth:urgencyLevel": "low",
"rdfs:label": "Engineer F Hired By Firm"
}
Description: As an automatic consequence of the contractor license revocation, a formal disciplinary record was created in Engineer F's professional history within the contractor licensing regulatory system. This record became a discoverable artifact that would later surface during post-hire investigation.
Temporal Marker: Simultaneous with contractor license revocation; prior to employment application
Activates Constraints:
- Permanent_Disciplinary_Record_Disclosure_Constraint
- Future_Application_Truthfulness_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer F may not have fully appreciated the permanence and discoverability of the record at the time; later, when the record surfaces, the emotional impact is retrospectively significant; the firm experiences the impact of the record's existence as a betrayal of trust
- engineer_f: Carries a permanent mark on his professional history that cannot be erased and will surface in background checks
- future_employers: Have access, in principle, to this record if they conduct proper due diligence
- regulatory_system: Record serves its intended function of protecting future employers and the public by preserving disciplinary history
- public: Benefits from a system that, when properly used, flags professionals with disciplinary histories
Learning Moment: Regulatory disciplinary records are permanent and discoverable; professionals cannot assume that discipline in one domain will remain invisible when they transition to another professional context. The existence of a discoverable record fundamentally changes the ethical calculus of non-disclosure—it is not merely an omission but a gamble on non-discovery.
Ethical Implications: Highlights the tension between professional rehabilitation and permanent accountability; raises questions about information access and transparency in professional credentialing; demonstrates how regulatory systems are designed to protect future stakeholders from undisclosed risks, and how professionals who circumvent these systems undermine public trust
- Should disciplinary records from one professional licensing domain (contractor) be automatically shared with or accessible to other licensing authorities (PE boards)?
- How does the existence of a discoverable record change the moral weight of Engineer F's decision not to disclose it on his application?
- What role should permanent disciplinary records play in professional rehabilitation—should there be a statute of limitations on required disclosure?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#Event_Disciplinary_Record_Created",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Should disciplinary records from one professional licensing domain (contractor) be automatically shared with or accessible to other licensing authorities (PE boards)?",
"How does the existence of a discoverable record change the moral weight of Engineer F\u0027s decision not to disclose it on his application?",
"What role should permanent disciplinary records play in professional rehabilitation\u2014should there be a statute of limitations on required disclosure?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "Engineer F may not have fully appreciated the permanence and discoverability of the record at the time; later, when the record surfaces, the emotional impact is retrospectively significant; the firm experiences the impact of the record\u0027s existence as a betrayal of trust",
"proeth-scenario:ethicalImplications": "Highlights the tension between professional rehabilitation and permanent accountability; raises questions about information access and transparency in professional credentialing; demonstrates how regulatory systems are designed to protect future stakeholders from undisclosed risks, and how professionals who circumvent these systems undermine public trust",
"proeth-scenario:learningMoment": "Regulatory disciplinary records are permanent and discoverable; professionals cannot assume that discipline in one domain will remain invisible when they transition to another professional context. The existence of a discoverable record fundamentally changes the ethical calculus of non-disclosure\u2014it is not merely an omission but a gamble on non-discovery.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"engineer_f": "Carries a permanent mark on his professional history that cannot be erased and will surface in background checks",
"future_employers": "Have access, in principle, to this record if they conduct proper due diligence",
"public": "Benefits from a system that, when properly used, flags professionals with disciplinary histories",
"regulatory_system": "Record serves its intended function of protecting future employers and the public by preserving disciplinary history"
},
"proeth:activatesConstraint": [
"Permanent_Disciplinary_Record_Disclosure_Constraint",
"Future_Application_Truthfulness_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/148#Action_Unlicensed_Individual_License_Sharing",
"proeth:causesStateChange": "A permanent, discoverable record of professional discipline enters the regulatory information ecosystem; Engineer F\u0027s professional history is permanently altered; the record exists independently of Engineer F\u0027s choices about disclosure and can be accessed by third parties",
"proeth:createsObligation": [
"Obligation_To_Disclose_Record_On_All_Relevant_Future_Applications",
"Obligation_To_Acknowledge_Record_When_Directly_Asked"
],
"proeth:description": "As an automatic consequence of the contractor license revocation, a formal disciplinary record was created in Engineer F\u0027s professional history within the contractor licensing regulatory system. This record became a discoverable artifact that would later surface during post-hire investigation.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "Simultaneous with contractor license revocation; prior to employment application",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Disciplinary Record Created"
}
Causal Chains (6)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: Engineer F deliberately allowed an unlicensed individual unrelated to his contracting firm to use his license, which served as the direct basis for the formal revocation by the licensing authority
Necessary Factors (NESS):
- Engineer F's deliberate decision to share his contractor's license
- The unlicensed individual being unrelated to Engineer F's contracting firm
- Licensing authority's jurisdiction and enforcement authority
- Existence of regulations prohibiting such license sharing
Sufficient Factors:
- Deliberate license sharing with unrelated unlicensed party + regulatory prohibition + licensing authority enforcement action
Responsibility Attribution:
Agent: Engineer F
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Unlicensed Individual License Sharing (Action 1)
Engineer F makes the deliberate volitional decision to allow an unrelated unlicensed individual to use his contractor's license -
Regulatory Violation Established
The act of sharing constitutes a clear violation of contractor licensing regulations, creating grounds for disciplinary action -
Licensing Authority Investigation/Discovery
The relevant licensing authority becomes aware of the violation and initiates formal proceedings -
Disciplinary Record Created (Event 5)
As an automatic consequence of the revocation process, a formal disciplinary record is created against Engineer F -
Contractor License Revocation (Event 1)
The licensing authority formally revokes Engineer F's contractor's license as a direct consequence of the violation
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#CausalChain_5ac47753",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer F deliberately allowed an unlicensed individual unrelated to his contracting firm to use his license, which served as the direct basis for the formal revocation by the licensing authority",
"proeth:causalSequence": [
{
"proeth:description": "Engineer F makes the deliberate volitional decision to allow an unrelated unlicensed individual to use his contractor\u0027s license",
"proeth:element": "Unlicensed Individual License Sharing (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "The act of sharing constitutes a clear violation of contractor licensing regulations, creating grounds for disciplinary action",
"proeth:element": "Regulatory Violation Established",
"proeth:step": 2
},
{
"proeth:description": "The relevant licensing authority becomes aware of the violation and initiates formal proceedings",
"proeth:element": "Licensing Authority Investigation/Discovery",
"proeth:step": 3
},
{
"proeth:description": "As an automatic consequence of the revocation process, a formal disciplinary record is created against Engineer F",
"proeth:element": "Disciplinary Record Created (Event 5)",
"proeth:step": 4
},
{
"proeth:description": "The licensing authority formally revokes Engineer F\u0027s contractor\u0027s license as a direct consequence of the violation",
"proeth:element": "Contractor License Revocation (Event 1)",
"proeth:step": 5
}
],
"proeth:cause": "Unlicensed Individual License Sharing (Action 1)",
"proeth:counterfactual": "Without Engineer F\u0027s deliberate act of sharing his license, no violation would have occurred and the revocation would not have been triggered; the licensing authority had no independent basis to revoke absent the violation",
"proeth:effect": "Contractor License Revocation (Event 1)",
"proeth:necessaryFactors": [
"Engineer F\u0027s deliberate decision to share his contractor\u0027s license",
"The unlicensed individual being unrelated to Engineer F\u0027s contracting firm",
"Licensing authority\u0027s jurisdiction and enforcement authority",
"Existence of regulations prohibiting such license sharing"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer F",
"proeth:sufficientFactors": [
"Deliberate license sharing with unrelated unlicensed party + regulatory prohibition + licensing authority enforcement action"
],
"proeth:withinAgentControl": true
}
Causal Language: As an automatic consequence of the contractor license revocation, a formal disciplinary record was created, establishing a documented history of professional misconduct independent of Engineer F's subsequent choices
Necessary Factors (NESS):
- Formal revocation action by the licensing authority
- Existence of a regulatory record-keeping system for disciplinary actions
- The revocation meeting the threshold for formal disciplinary classification
Sufficient Factors:
- Formal revocation alone was sufficient to automatically generate the disciplinary record under standard licensing authority procedures
Responsibility Attribution:
Agent: Engineer F (originating cause); Licensing Authority (proximate administrative actor)
Type: indirect
Within Agent Control:
No
Causal Sequence:
-
Unlicensed Individual License Sharing (Action 1)
Root volitional cause: Engineer F shares his license with an unrelated unlicensed individual -
Contractor License Revocation (Event 1)
Licensing authority formally revokes Engineer F's contractor's license -
Automatic Administrative Processing
Licensing authority's administrative systems automatically process the revocation into the formal disciplinary record system -
Disciplinary Record Created (Event 5)
A permanent formal disciplinary record is established, making the revocation discoverable by employers and other licensing boards -
Record Accessibility to Third Parties
The disciplinary record becomes available through background checks, licensing board inquiries, and employment application verification processes
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#CausalChain_c92346af",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "As an automatic consequence of the contractor license revocation, a formal disciplinary record was created, establishing a documented history of professional misconduct independent of Engineer F\u0027s subsequent choices",
"proeth:causalSequence": [
{
"proeth:description": "Root volitional cause: Engineer F shares his license with an unrelated unlicensed individual",
"proeth:element": "Unlicensed Individual License Sharing (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "Licensing authority formally revokes Engineer F\u0027s contractor\u0027s license",
"proeth:element": "Contractor License Revocation (Event 1)",
"proeth:step": 2
},
{
"proeth:description": "Licensing authority\u0027s administrative systems automatically process the revocation into the formal disciplinary record system",
"proeth:element": "Automatic Administrative Processing",
"proeth:step": 3
},
{
"proeth:description": "A permanent formal disciplinary record is established, making the revocation discoverable by employers and other licensing boards",
"proeth:element": "Disciplinary Record Created (Event 5)",
"proeth:step": 4
},
{
"proeth:description": "The disciplinary record becomes available through background checks, licensing board inquiries, and employment application verification processes",
"proeth:element": "Record Accessibility to Third Parties",
"proeth:step": 5
}
],
"proeth:cause": "Contractor License Revocation (Event 1)",
"proeth:counterfactual": "Without the revocation, no disciplinary record would have been created; the record was a ministerial and automatic consequence of the revocation event itself",
"proeth:effect": "Disciplinary Record Created (Event 5)",
"proeth:necessaryFactors": [
"Formal revocation action by the licensing authority",
"Existence of a regulatory record-keeping system for disciplinary actions",
"The revocation meeting the threshold for formal disciplinary classification"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "Engineer F (originating cause); Licensing Authority (proximate administrative actor)",
"proeth:sufficientFactors": [
"Formal revocation alone was sufficient to automatically generate the disciplinary record under standard licensing authority procedures"
],
"proeth:withinAgentControl": false
}
Causal Language: Engineer F answered 'no' to the employment application question asking whether he had ever been disciplined, thereby concealing the contractor's license revocation and the associated disciplinary record from the hiring firm, which enabled his hiring
Necessary Factors (NESS):
- Existence of the disciplinary record from the contractor license revocation
- Employment application containing a direct question about prior disciplinary history
- Engineer F's deliberate false answer concealing the revocation
- The hiring firm's reliance on the application's accuracy in making its hiring decision
Sufficient Factors:
- False negative disclosure + firm's reasonable reliance on application truthfulness + absence of independent verification = hiring decision made on false premises
Responsibility Attribution:
Agent: Engineer F (primary); Hiring Firm (contributory for relying solely on self-disclosure without verification)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Disciplinary Record Created (Event 5)
Formal disciplinary record exists as a result of the contractor license revocation, creating a material fact Engineer F is obligated to disclose -
Negative Disclosure Answer on Application (Action 2)
Engineer F deliberately answers 'no' to the disciplinary history question, actively concealing the revocation from the prospective employer -
Firm's Reliance on Application
The hiring firm reviews the application and, relying on the accuracy of Engineer F's self-disclosure, proceeds without independent verification of disciplinary history -
Engineer F Hired By Firm (Event 4)
Engineer F is hired based on an application containing a material misrepresentation about his professional disciplinary history -
Ongoing Employment Under False Pretenses
Engineer F continues employment without correcting the misrepresentation, compounding the original deception
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#CausalChain_49e49657",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer F answered \u0027no\u0027 to the employment application question asking whether he had ever been disciplined, thereby concealing the contractor\u0027s license revocation and the associated disciplinary record from the hiring firm, which enabled his hiring",
"proeth:causalSequence": [
{
"proeth:description": "Formal disciplinary record exists as a result of the contractor license revocation, creating a material fact Engineer F is obligated to disclose",
"proeth:element": "Disciplinary Record Created (Event 5)",
"proeth:step": 1
},
{
"proeth:description": "Engineer F deliberately answers \u0027no\u0027 to the disciplinary history question, actively concealing the revocation from the prospective employer",
"proeth:element": "Negative Disclosure Answer on Application (Action 2)",
"proeth:step": 2
},
{
"proeth:description": "The hiring firm reviews the application and, relying on the accuracy of Engineer F\u0027s self-disclosure, proceeds without independent verification of disciplinary history",
"proeth:element": "Firm\u0027s Reliance on Application",
"proeth:step": 3
},
{
"proeth:description": "Engineer F is hired based on an application containing a material misrepresentation about his professional disciplinary history",
"proeth:element": "Engineer F Hired By Firm (Event 4)",
"proeth:step": 4
},
{
"proeth:description": "Engineer F continues employment without correcting the misrepresentation, compounding the original deception",
"proeth:element": "Ongoing Employment Under False Pretenses",
"proeth:step": 5
}
],
"proeth:cause": "Negative Disclosure Answer on Application (Action 2)",
"proeth:counterfactual": "Had Engineer F truthfully disclosed the contractor\u0027s license revocation, the firm would have had material information to evaluate; hiring may not have occurred or would have occurred under different terms; alternatively, had the firm conducted independent verification, the false answer alone would not have been sufficient",
"proeth:effect": "Engineer F Hired By Firm (Event 4)",
"proeth:necessaryFactors": [
"Existence of the disciplinary record from the contractor license revocation",
"Employment application containing a direct question about prior disciplinary history",
"Engineer F\u0027s deliberate false answer concealing the revocation",
"The hiring firm\u0027s reliance on the application\u0027s accuracy in making its hiring decision"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer F (primary); Hiring Firm (contributory for relying solely on self-disclosure without verification)",
"proeth:sufficientFactors": [
"False negative disclosure + firm\u0027s reasonable reliance on application truthfulness + absence of independent verification = hiring decision made on false premises"
],
"proeth:withinAgentControl": true
}
Causal Language: After being hired, Engineer F made no proactive effort to disclose the contractor's license revocation, forcing the firm to discover it through independent means rather than through Engineer F's own candor, prolonging the period during which the firm operated without material knowledge
Necessary Factors (NESS):
- Engineer F's continued employment with the firm following hiring
- Engineer F's ongoing knowledge of the undisclosed revocation
- Engineer F's deliberate choice not to proactively disclose after hiring
- The firm's eventual independent discovery mechanism (e.g., background check, licensing board inquiry, third-party report)
Sufficient Factors:
- Continued non-disclosure + firm's independent investigative action = eventual discovery without Engineer F's cooperation, but after a delay that exposed the firm to risk
Responsibility Attribution:
Agent: Engineer F (primary for non-disclosure); Hiring Firm (secondary for the investigative action that led to discovery)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Engineer F Hired By Firm (Event 4)
Engineer F begins employment based on a materially false application, creating an ongoing obligation to correct the misrepresentation -
Post-Hire Non-Disclosure of Revocation (Action 3)
Engineer F makes a continuing deliberate choice not to proactively disclose the contractor's license revocation to his employer -
Firm's Independent Investigation
The firm, through its own processes (background verification, licensing board inquiry, or other means), initiates or encounters information about Engineer F's disciplinary history -
Firm Discovers Revocation (Event 3)
The engineering firm discovers the contractor's license revocation independently, without Engineer F's cooperation or disclosure -
Firm's Response to Discovery
The firm must now assess the implications of the discovered misrepresentation for Engineer F's continued employment, professional credibility, and any work performed in reliance on his credentials
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#CausalChain_30ed5b0c",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "After being hired, Engineer F made no proactive effort to disclose the contractor\u0027s license revocation, forcing the firm to discover it through independent means rather than through Engineer F\u0027s own candor, prolonging the period during which the firm operated without material knowledge",
"proeth:causalSequence": [
{
"proeth:description": "Engineer F begins employment based on a materially false application, creating an ongoing obligation to correct the misrepresentation",
"proeth:element": "Engineer F Hired By Firm (Event 4)",
"proeth:step": 1
},
{
"proeth:description": "Engineer F makes a continuing deliberate choice not to proactively disclose the contractor\u0027s license revocation to his employer",
"proeth:element": "Post-Hire Non-Disclosure of Revocation (Action 3)",
"proeth:step": 2
},
{
"proeth:description": "The firm, through its own processes (background verification, licensing board inquiry, or other means), initiates or encounters information about Engineer F\u0027s disciplinary history",
"proeth:element": "Firm\u0027s Independent Investigation",
"proeth:step": 3
},
{
"proeth:description": "The engineering firm discovers the contractor\u0027s license revocation independently, without Engineer F\u0027s cooperation or disclosure",
"proeth:element": "Firm Discovers Revocation (Event 3)",
"proeth:step": 4
},
{
"proeth:description": "The firm must now assess the implications of the discovered misrepresentation for Engineer F\u0027s continued employment, professional credibility, and any work performed in reliance on his credentials",
"proeth:element": "Firm\u0027s Response to Discovery",
"proeth:step": 5
}
],
"proeth:cause": "Post-Hire Non-Disclosure of Revocation (Action 3)",
"proeth:counterfactual": "Had Engineer F proactively disclosed the revocation after hiring, the firm would have obtained the same information but through a transparent channel; the discovery event would have been replaced by a voluntary disclosure, potentially altering the severity of consequences for Engineer F and enabling the firm to respond more promptly",
"proeth:effect": "Firm Discovers Revocation (Event 3)",
"proeth:necessaryFactors": [
"Engineer F\u0027s continued employment with the firm following hiring",
"Engineer F\u0027s ongoing knowledge of the undisclosed revocation",
"Engineer F\u0027s deliberate choice not to proactively disclose after hiring",
"The firm\u0027s eventual independent discovery mechanism (e.g., background check, licensing board inquiry, third-party report)"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer F (primary for non-disclosure); Hiring Firm (secondary for the investigative action that led to discovery)",
"proeth:sufficientFactors": [
"Continued non-disclosure + firm\u0027s independent investigative action = eventual discovery without Engineer F\u0027s cooperation, but after a delay that exposed the firm to risk"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A, while actively performing design services for Client B, chose not to disclose a pending matter, establishing through BER 97-11 the ethical precedent that active professional relationships create affirmative disclosure obligations, which directly informs the standard against which Engineer F's non-disclosures are evaluated
Necessary Factors (NESS):
- An active professional service relationship between engineer and client/employer
- Existence of material information affecting the client's/employer's ability to make informed decisions
- Engineer's knowledge of the material information
- Engineer's deliberate choice not to disclose despite the active relationship
Sufficient Factors:
- Active professional relationship + material undisclosed information + engineer's knowledge + deliberate non-disclosure = ethical violation sufficient to warrant disciplinary action under NSPE codes as interpreted by BER 97-11
Responsibility Attribution:
Agent: Engineer A (in the BER 97-11 precedent context); Engineer F (as the party whose conduct is evaluated against this precedent)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Non-Disclosure to Active Client (Action 4 - BER 97-11)
Engineer A chooses not to disclose a pending material matter to Client B during an active professional engagement, creating the factual basis for the BER 97-11 ethical analysis -
BER 97-11 Ethical Determination
The NSPE Board of Ethical Review analyzes Engineer A's conduct and establishes that active professional relationships create affirmative disclosure obligations under the NSPE Code of Ethics -
Precedent Standard Established
BER 97-11 becomes an authoritative ethical standard applicable to analogous situations involving engineers with material undisclosed information in active professional relationships -
Application to Engineer F's Conduct
Engineer F's non-disclosures on his application and post-hire are evaluated against the BER 97-11 standard, which establishes that his conduct constitutes an ethical violation -
Reinforced Basis for Disciplinary Action Against Engineer F
The BER 97-11 precedent strengthens the ethical and potentially regulatory basis for disciplinary action against Engineer F, compounding the consequences already flowing from the contractor license revocation
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#CausalChain_4db12764",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A, while actively performing design services for Client B, chose not to disclose a pending matter, establishing through BER 97-11 the ethical precedent that active professional relationships create affirmative disclosure obligations, which directly informs the standard against which Engineer F\u0027s non-disclosures are evaluated",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A chooses not to disclose a pending material matter to Client B during an active professional engagement, creating the factual basis for the BER 97-11 ethical analysis",
"proeth:element": "Non-Disclosure to Active Client (Action 4 - BER 97-11)",
"proeth:step": 1
},
{
"proeth:description": "The NSPE Board of Ethical Review analyzes Engineer A\u0027s conduct and establishes that active professional relationships create affirmative disclosure obligations under the NSPE Code of Ethics",
"proeth:element": "BER 97-11 Ethical Determination",
"proeth:step": 2
},
{
"proeth:description": "BER 97-11 becomes an authoritative ethical standard applicable to analogous situations involving engineers with material undisclosed information in active professional relationships",
"proeth:element": "Precedent Standard Established",
"proeth:step": 3
},
{
"proeth:description": "Engineer F\u0027s non-disclosures on his application and post-hire are evaluated against the BER 97-11 standard, which establishes that his conduct constitutes an ethical violation",
"proeth:element": "Application to Engineer F\u0027s Conduct",
"proeth:step": 4
},
{
"proeth:description": "The BER 97-11 precedent strengthens the ethical and potentially regulatory basis for disciplinary action against Engineer F, compounding the consequences already flowing from the contractor license revocation",
"proeth:element": "Reinforced Basis for Disciplinary Action Against Engineer F",
"proeth:step": 5
}
],
"proeth:cause": "Non-Disclosure to Active Client (BER 97-11 Precedent) (Action 4)",
"proeth:counterfactual": "Had Engineer A disclosed the pending matter to Client B, no ethical violation would have occurred under BER 97-11; the precedent establishes that disclosure is the required conduct, making non-disclosure the causally operative deviation from the ethical standard",
"proeth:effect": "Disciplinary Record Created (Event 5) [as analogical precedent reinforcing Engineer F\u0027s disclosure obligations]",
"proeth:necessaryFactors": [
"An active professional service relationship between engineer and client/employer",
"Existence of material information affecting the client\u0027s/employer\u0027s ability to make informed decisions",
"Engineer\u0027s knowledge of the material information",
"Engineer\u0027s deliberate choice not to disclose despite the active relationship"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A (in the BER 97-11 precedent context); Engineer F (as the party whose conduct is evaluated against this precedent)",
"proeth:sufficientFactors": [
"Active professional relationship + material undisclosed information + engineer\u0027s knowledge + deliberate non-disclosure = ethical violation sufficient to warrant disciplinary action under NSPE codes as interpreted by BER 97-11"
],
"proeth:withinAgentControl": true
}
Causal Language: Despite the revocation of his contractor's license, Engineer F's professional engineering license was not suspended, establishing a critical factual distinction between the two license types that shapes the scope of Engineer F's ongoing professional obligations and the firm's exposure
Necessary Factors (NESS):
- The contractor's license revocation being treated as a separate regulatory action from PE licensure
- The PE licensing board's independent jurisdiction and discretionary authority
- The absence of automatic cross-license revocation provisions in the applicable regulatory framework
- The PE licensing board's determination that the contractor license violation did not independently warrant PE license suspension
Sufficient Factors:
- Regulatory separation of contractor and PE licensing regimes + PE board's independent discretionary determination = PE license remains intact despite contractor license revocation
Responsibility Attribution:
Agent: PE Licensing Board (administrative decision-maker); Engineer F (whose underlying conduct created the risk of PE license action)
Type: indirect
Within Agent Control:
No
Causal Sequence:
-
Unlicensed Individual License Sharing (Action 1)
Engineer F's deliberate license sharing creates a violation that triggers both contractor license revocation and potential PE license scrutiny -
Contractor License Revocation (Event 1)
Contractor licensing authority formally revokes Engineer F's contractor's license, creating a disciplinary record that may be reported to or reviewed by the PE licensing board -
PE Board Review or Notification
The PE licensing board becomes aware of the contractor license revocation through inter-agency reporting, Engineer F's own disclosure, or other mechanisms -
PE Board Independent Assessment
The PE board independently evaluates whether the contractor license violation warrants action against Engineer F's PE license under its own regulatory standards -
PE License Non-Suspension Outcome (Event 2)
The PE board determines that Engineer F's PE license will not be suspended, leaving him credentialed as a PE despite the contractor license revocation
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/148#",
"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/148#CausalChain_d5b73d9c",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Despite the revocation of his contractor\u0027s license, Engineer F\u0027s professional engineering license was not suspended, establishing a critical factual distinction between the two license types that shapes the scope of Engineer F\u0027s ongoing professional obligations and the firm\u0027s exposure",
"proeth:causalSequence": [
{
"proeth:description": "Engineer F\u0027s deliberate license sharing creates a violation that triggers both contractor license revocation and potential PE license scrutiny",
"proeth:element": "Unlicensed Individual License Sharing (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "Contractor licensing authority formally revokes Engineer F\u0027s contractor\u0027s license, creating a disciplinary record that may be reported to or reviewed by the PE licensing board",
"proeth:element": "Contractor License Revocation (Event 1)",
"proeth:step": 2
},
{
"proeth:description": "The PE licensing board becomes aware of the contractor license revocation through inter-agency reporting, Engineer F\u0027s own disclosure, or other mechanisms",
"proeth:element": "PE Board Review or Notification",
"proeth:step": 3
},
{
"proeth:description": "The PE board independently evaluates whether the contractor license violation warrants action against Engineer F\u0027s PE license under its own regulatory standards",
"proeth:element": "PE Board Independent Assessment",
"proeth:step": 4
},
{
"proeth:description": "The PE board determines that Engineer F\u0027s PE license will not be suspended, leaving him credentialed as a PE despite the contractor license revocation",
"proeth:element": "PE License Non-Suspension Outcome (Event 2)",
"proeth:step": 5
}
],
"proeth:cause": "Contractor License Revocation (Event 1)",
"proeth:counterfactual": "Had the regulatory framework included automatic cross-license revocation, or had the PE board determined that the contractor license violation warranted PE license action, Engineer F\u0027s PE license would have been suspended or revoked, fundamentally altering his ability to be hired as a professional engineer",
"proeth:effect": "PE License Non-Suspension Outcome (Event 2)",
"proeth:necessaryFactors": [
"The contractor\u0027s license revocation being treated as a separate regulatory action from PE licensure",
"The PE licensing board\u0027s independent jurisdiction and discretionary authority",
"The absence of automatic cross-license revocation provisions in the applicable regulatory framework",
"The PE licensing board\u0027s determination that the contractor license violation did not independently warrant PE license suspension"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "PE Licensing Board (administrative decision-maker); Engineer F (whose underlying conduct created the risk of PE license action)",
"proeth:sufficientFactors": [
"Regulatory separation of contractor and PE licensing regimes + PE board\u0027s independent discretionary determination = PE license remains intact despite contractor license revocation"
],
"proeth:withinAgentControl": false
}
Allen Temporal Relations (12)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Engineer F owning fire sprinkler contracting firm |
before
Entity1 is before Entity2 |
Engineer F applying for professional engineering position |
time:before
http://www.w3.org/2006/time#before |
Previously, Engineer F was the owner of a fire sprinkler contracting firm... Engineer F is a profess... [more] |
| contractor's license revocation |
before
Entity1 is before Entity2 |
Engineer F applying for professional engineering position |
time:before
http://www.w3.org/2006/time#before |
Engineer F's contractor's license was revoked because he allowed an unlicensed individual... [and su... [more] |
| Engineer F submitting employment application with negative answer |
before
Entity1 is before Entity2 |
engineering firm discovering contractor's license revocation |
time:before
http://www.w3.org/2006/time#before |
Engineer F responds in the negative on the employment application. Later, the engineering firm learn... [more] |
| contractor's license revocation |
before
Entity1 is before Entity2 |
engineering firm discovering the revocation |
time:before
http://www.w3.org/2006/time#before |
Engineer F's contractor's license was revoked because he allowed an unlicensed individual... Later, ... [more] |
| Engineer A rendering services to Client B |
overlaps
Entity1 starts before Entity2 and ends during Entity2 |
state board contacting Engineer A about Client C complaint |
time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps |
During the rendering of services to Client B on this project, the state board of professional engine... [more] |
| state board contacting Engineer A |
before
Entity1 is before Entity2 |
Client B learning of the ethics complaint |
time:before
http://www.w3.org/2006/time#before |
During the rendering of services to Client B on this project, the state board of professional engine... [more] |
| Engineer A retained by Client B |
before
Entity1 is before Entity2 |
state board contacting Engineer A about Client C complaint |
time:before
http://www.w3.org/2006/time#before |
Engineer A was retained by Client B to perform design services... During the rendering of services t... [more] |
| BER Case 75-5 |
before
Entity1 is before Entity2 |
BER Case 97-11 |
time:before
http://www.w3.org/2006/time#before |
BER Case 75-5 from 1975... BER Case 97-11 from 1997. |
| BER Case 97-11 |
before
Entity1 is before Entity2 |
current Engineer F case analysis |
time:before
http://www.w3.org/2006/time#before |
Two previous Board of Ethical Review cases provide some background for considering this case. The fi... [more] |
| unlicensed individual using contractor license number on another project |
before
Entity1 is before Entity2 |
contractor's license revocation |
time:before
http://www.w3.org/2006/time#before |
Engineer F's contractor's license was revoked because he allowed an unlicensed individual who was un... [more] |
| employment application submission |
before
Entity1 is before Entity2 |
hiring decision |
time:before
http://www.w3.org/2006/time#before |
Engineer F is assumed to have realized that the employer would have wanted to know this information ... [more] |
| hiring of Engineer F |
before
Entity1 is before Entity2 |
engineering firm discovering contractor's license revocation |
time:before
http://www.w3.org/2006/time#before |
On the engineering firm employment application... Engineer F responds in the negative... Later, the ... [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.