{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Action_Engineer_B_Completes_Prior_Projects",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Negotiate explicit written agreement with prior employer about future use of project references upon departure",
    "Limit portfolio to only projects where Engineer B held sole or lead responsible charge",
    "Document each project\u0027s attribution details contemporaneously to ensure future accuracy"
  ],
  "proeth-scenario:characterMotivation": "Engineer B sought to build professional competency and a legitimate project portfolio through standard employment at a prior firm, with no apparent intent to later exploit that experience in ethically ambiguous ways. The work was completed in good faith as part of normal professional practice.",
  "proeth-scenario:consequencesIfAlternative": [
    "A written agreement would have provided clear authorization for later use, potentially preventing the entire ethical dispute and giving XYZ Engineers a defensible disclosure framework",
    "Restricting portfolio scope would have reduced the breadth of qualifications available to XYZ Engineers but would have eliminated ambiguity about Engineer B\u0027s actual role and contribution",
    "Contemporaneous documentation would have enabled precise, project-level attribution in future proposals, making the partial-disclosure format unnecessary and the ethical violation avoidable"
  ],
  "proeth-scenario:decisionSignificance": "Establishes that ethical complications can originate in entirely routine professional actions; students learn that downstream attribution problems are often rooted in upstream ambiguity about who \u0027owns\u0027 project experience and how it may be represented later.",
  "proeth-scenario:ethicalTension": "Individual professional achievement vs. institutional ownership of project work \u2014 engineers routinely build careers on prior project experience, but the boundary between personal credential and employer proprietary contribution is rarely made explicit at the time of execution.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The integrity of professional credentials, the prior firm\u0027s intellectual and reputational interests, and the foundation of a career portfolio that will later be used in public procurement contexts where accuracy is legally and ethically required.",
  "proeth:description": "Engineer B completes a body of bridge and culvert design work at a previous firm, establishing a professional portfolio without involving proprietary design concepts. This creates the experiential record that will later be used in XYZ Engineers\u0027 qualification proposals.",
  "proeth:foreseenUnintendedEffects": [
    "Work product becomes portable professional credential that future employers may leverage"
  ],
  "proeth:fulfillsObligation": [
    "Competent execution of engineering work",
    "Avoidance of misappropriating proprietary design concepts"
  ],
  "proeth:guidedByPrinciple": [
    "Professional competence",
    "Honest representation of experience",
    "Respect for prior employer\u0027s intellectual property"
  ],
  "proeth:hasAgent": "Engineer B (Project Engineer at prior firm)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Build professional competence and a verifiable record of project experience",
  "proeth:requiresCapability": [
    "Bridge and culvert design",
    "Project execution under supervision or licensure"
  ],
  "proeth:temporalMarker": "Prior to current events",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer B Completes Prior Projects"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Action_XYZ_Hires_Engineer_B",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Hire Engineer B but commit internally to full, project-level attribution in all qualification proposals before entering new markets",
    "Enter States Q and Z markets based only on XYZ\u0027s existing organizational experience, without leveraging Engineer B\u0027s prior-firm portfolio",
    "Seek explicit legal and ethics counsel on how to properly represent Engineer B\u0027s prior work before submitting any qualification proposals"
  ],
  "proeth-scenario:characterMotivation": "XYZ Engineers sought competitive market expansion into new states and identified Engineer B\u0027s prior project portfolio as a strategic qualification asset to satisfy client and licensing board experience requirements. The hiring decision was instrumentally motivated \u2014 Engineer B\u0027s past work was the primary credential being acquired alongside the person.",
  "proeth-scenario:consequencesIfAlternative": [
    "Full attribution commitment would have eliminated the ethical violation entirely and positioned XYZ Engineers as a transparent competitor, with no material disadvantage since the experience would still be disclosed",
    "Limiting proposals to XYZ\u0027s own organizational record would have been honest but potentially uncompetitive, forcing XYZ to build genuine institutional experience before expanding \u2014 a slower but ethically sound growth path",
    "Proactive ethics and legal review would have identified the State Z rule specificity in advance, allowing compliant proposal formats to be designed before any submissions were made, avoiding regulatory exposure altogether"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how organizational decisions made at the business strategy level can create ethical exposure at the professional practice level; students learn that firms bear responsibility for how they structure and represent the qualifications of new hires in public procurement.",
  "proeth-scenario:ethicalTension": "Legitimate business growth and talent acquisition vs. the risk of misrepresenting organizational capability \u2014 hiring someone to \u0027bring\u0027 prior project credentials conflates the firm\u0027s present capacity with an individual\u0027s historical work performed elsewhere, potentially misleading clients about XYZ\u0027s institutional experience.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "XYZ Engineers\u0027 reputation and licensure standing in new markets, Engineer B\u0027s professional integrity, client and public reliance on accurate qualification statements, and the competitive fairness of the procurement process for other firms.",
  "proeth:description": "XYZ Engineers makes a deliberate hiring decision to bring Engineer B on as a project manager, specifically to support expansion of bridge and culvert design services into States Q and Z. This decision is predicated on leveraging Engineer B\u0027s prior project experience as a qualification asset.",
  "proeth:foreseenUnintendedEffects": [
    "Attribution of prior employer\u0027s projects in proposals may create disclosure complexity"
  ],
  "proeth:fulfillsObligation": [
    "Acquiring qualified personnel for new service areas",
    "Building legitimate professional capacity"
  ],
  "proeth:guidedByPrinciple": [
    "Competence in service delivery",
    "Honest representation of firm capabilities"
  ],
  "proeth:hasAgent": "XYZ Engineers (Firm leadership / hiring authority)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Expand competitive market presence in States Q and Z by acquiring a project manager with a relevant project portfolio",
  "proeth:requiresCapability": [
    "Firm-level strategic planning",
    "Personnel assessment",
    "Market expansion judgment"
  ],
  "proeth:temporalMarker": "At time of hiring",
  "proeth:withinCompetence": true,
  "rdfs:label": "XYZ Hires Engineer B"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Action_Engineer_A_Investigates_Marketing_Practice",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Ignore the practice entirely and compete on the merits of ABC Consultants\u0027 own qualifications",
    "Raise the concern informally and directly with Engineer B or XYZ Engineers before considering any regulatory report",
    "Report the concern to NSPE\u0027s Board of Ethical Review for guidance before deciding whether to file with any state licensing board"
  ],
  "proeth-scenario:characterMotivation": "Engineer A, as a direct competitor disadvantaged by XYZ Engineers\u0027 qualification proposals, had both a personal competitive interest and a professional ethical interest in scrutinizing the attribution practice. The NSPE Code of Ethics places affirmative obligations on engineers to uphold the integrity of the profession, motivating Engineer A to treat this as a professional duty rather than merely a competitive grievance.",
  "proeth-scenario:consequencesIfAlternative": [
    "Ignoring the practice would avoid any appearance of competitive motivation but would leave a potentially misleading procurement practice unchallenged, potentially harming public clients and the profession\u0027s integrity \u2014 and would abdicate Engineer A\u0027s affirmative ethical obligations",
    "Direct informal engagement could resolve the issue without regulatory involvement if XYZ Engineers corrected the format voluntarily, but risks being perceived as a threat or being ignored, and may not be appropriate where a clear violation has occurred",
    "Seeking BER guidance first would be a cautious and professionally responsible approach, but the BER process is advisory and retrospective \u2014 it would delay any reporting and might not constitute fulfillment of an immediate obligation if a clear violation is occurring"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that ethical obligations do not disappear because the person fulfilling them has a personal stake in the outcome; simultaneously teaches that engineers must examine their own motivations honestly and ensure their actions are grounded in genuine professional principle rather than competitive advantage.",
  "proeth-scenario:ethicalTension": "Professional duty to report potential ethics violations vs. the appearance of self-interested competitive motivation \u2014 Engineer A\u0027s investigation is ethically valid but complicated by the fact that Engineer A stands to benefit commercially if XYZ Engineers is sanctioned, raising questions about whether the reporting impulse is principled or opportunistic.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer A\u0027s own professional integrity and reputation, the fairness of the competitive procurement environment, the profession\u0027s self-regulatory credibility, and the risk that a competitor-driven complaint will be perceived as bad-faith rather than principled.",
  "proeth:description": "Upon noticing XYZ Engineers\u0027 qualification proposals, Engineer A makes a deliberate decision to investigate whether the attribution practice constitutes a misleading or unethical representation. This is a proactive professional judgment to scrutinize a competitor\u0027s conduct rather than ignore it.",
  "proeth:foreseenUnintendedEffects": [
    "Investigation by a competitor may appear self-serving or motivated by competitive interest rather than genuine ethical concern"
  ],
  "proeth:fulfillsObligation": [
    "Professional vigilance regarding unethical conduct in the profession",
    "Initial step toward upholding public trust in engineering representations"
  ],
  "proeth:guidedByPrinciple": [
    "NSPE Code of Ethics obligation to report unethical conduct",
    "Integrity of the profession",
    "Public protection through honest qualification submissions"
  ],
  "proeth:hasAgent": "Engineer A (Engineer / competitor at ABC Consultants)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional self-interest vs. Ethical obligation",
    "proeth:resolutionReasoning": "Engineer A resolves the tension by grounding the investigation in objective rule analysis (NSPE Code and state board rules) rather than competitive motivation, lending legitimacy to the inquiry"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Determine whether XYZ Engineers\u0027 proposal formatting violates professional ethics standards or licensing board rules",
  "proeth:requiresCapability": [
    "Ethical reasoning",
    "Familiarity with NSPE Code of Ethics",
    "Ability to identify potentially misleading professional representations"
  ],
  "proeth:temporalMarker": "Upon noticing the proposals",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Investigates Marketing Practice"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Action_Engineer_A_Reviews_Applicable_Rules",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Apply only the NSPE Code of Ethics as a single universal standard without reviewing state-specific board rules",
    "Report to both state boards simultaneously without differentiating the strength of the violation finding in each jurisdiction",
    "Retain legal counsel to conduct the jurisdictional review rather than performing it personally"
  ],
  "proeth-scenario:characterMotivation": "Engineer A recognized that ethical and legal obligations are jurisdiction-specific and that a single undifferentiated assessment could lead to either over-reporting (where no clear violation exists) or under-reporting (where a clear violation does exist). The deliberate jurisdiction-by-jurisdiction analysis reflects professional rigor and a commitment to grounding action in actual applicable standards rather than generalized ethical intuition.",
  "proeth-scenario:consequencesIfAlternative": [
    "Using only NSPE standards would have produced an ambiguous finding insufficient to clearly obligate reporting in either state, potentially causing Engineer A to either over-report or under-report relative to actual obligations",
    "Reporting to both boards without differentiation would have been an overreach in State Q where no clear violation was established, potentially exposing Engineer A to criticism for filing an unsubstantiated complaint and undermining the credibility of the legitimate State Z report",
    "Legal counsel review would have been thorough and defensible but may have been unnecessary given that Engineer A was capable of conducting the analysis \u2014 and would have introduced delay; however, it could have provided additional protection against a claim that the complaint was filed in bad faith"
  ],
  "proeth-scenario:decisionSignificance": "Exemplifies the principle that ethical obligations in engineering practice are not monolithic \u2014 they vary by jurisdiction, context, and the specificity of applicable rules. Students learn that professional ethical reasoning requires research, not just instinct, and that the same conduct can be simultaneously compliant in one jurisdiction and violating in another.",
  "proeth-scenario:ethicalTension": "Thoroughness and accuracy vs. the temptation to apply a uniform standard across jurisdictions for simplicity \u2014 and the deeper tension between acting on moral intuition that \u0027something is wrong\u0027 versus the professional obligation to establish that a specific rule has been clearly violated before reporting a colleague.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The accuracy and legitimacy of any subsequent report, Engineer A\u0027s credibility as a complainant, fairness to XYZ Engineers and Engineer B (who should not be reported where no clear violation exists), and the integrity of the licensing board processes in both states.",
  "proeth:description": "Engineer A conducts a deliberate, jurisdiction-specific review of the NSPE Code of Ethics and the licensing board rules in both State Q and State Z to assess whether XYZ Engineers\u0027 disclosure practice constitutes a violation. This analytical decision produces differentiated findings across the two jurisdictions.",
  "proeth:foreseenUnintendedEffects": [
    "Findings may obligate Engineer A to report, creating professional and relational risk; findings may also exonerate XYZ Engineers in one jurisdiction"
  ],
  "proeth:fulfillsObligation": [
    "Due diligence before making an ethics complaint",
    "Respect for jurisdictional specificity of licensing rules",
    "Honest and evidence-based professional judgment"
  ],
  "proeth:guidedByPrinciple": [
    "Factual basis for ethics reporting",
    "Respect for rule of law and licensing authority",
    "Proportionality in ethics enforcement"
  ],
  "proeth:hasAgent": "Engineer A (Engineer / competitor at ABC Consultants)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Uniform reporting vs. Jurisdiction-specific rules",
    "proeth:resolutionReasoning": "Engineer A accepts that ethical obligations are jurisdiction-specific and that the same conduct may be actionable in one state but not another, resolving the tension through rigorous rule-based analysis"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Establish an objective, rule-based foundation for determining whether a reportable violation has occurred in either or both states",
  "proeth:requiresCapability": [
    "Legal and regulatory research",
    "Ethical analysis",
    "Comparative rule interpretation across jurisdictions"
  ],
  "proeth:temporalMarker": "During investigation",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Reviews Applicable Rules"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Action_Engineer_A_Reports_to_State_Z_Board",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline to report to State Z despite the clear violation finding, treating the matter as resolved by personal knowledge",
    "Report to State Z anonymously to reduce the appearance of competitive motivation",
    "Report to State Z but simultaneously notify XYZ Engineers of the complaint to give them an opportunity to respond before the board acts"
  ],
  "proeth-scenario:characterMotivation": "Engineer A, having established through careful research that State Z\u0027s specific and stringent rules were clearly violated by XYZ Engineers\u0027 partial attribution format, acted on the affirmative professional obligation to report clear ethics violations to the appropriate authority. The BER\u0027s framing of this as an obligation rather than a discretionary choice reflects the NSPE Code\u0027s expectation that engineers actively uphold the profession\u0027s integrity.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining to report despite a clear violation would constitute a failure of professional duty under the NSPE Code and would allow a misleading procurement practice to continue unchallenged, harming public clients and disadvantaging honest competitors",
    "Anonymous reporting would reduce the appearance of self-interest but might undermine the complaint\u0027s credibility and could be seen as evasive; licensing boards generally prefer identified complainants who can be questioned and who stand behind their allegations",
    "Notifying XYZ Engineers simultaneously could be seen as a courtesy but risks being perceived as a threat or an attempt to pressure a private settlement rather than allowing the regulatory process to function properly; it could also give XYZ Engineers time to preemptively respond in ways that complicate the board\u0027s investigation"
  ],
  "proeth-scenario:decisionSignificance": "The climactic ethical decision of the case: students learn that when a clear violation of a specific rule is established, reporting is not optional \u2014 it is a professional duty. This challenges the common instinct to avoid conflict or \u0027mind one\u0027s own business\u0027 and establishes that self-regulation of the profession requires engineers to act when violations are evident.",
  "proeth-scenario:ethicalTension": "Affirmative duty to report clear violations vs. collegial reluctance to formally report a fellow engineer \u2014 and the ongoing tension between principled whistleblowing and the appearance of competitive motivation, which Engineer A must navigate by ensuring the report is factually grounded and professionally framed rather than adversarial.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "XYZ Engineers\u0027 and Engineer B\u0027s professional licenses and standing in State Z, the integrity of State Z\u0027s procurement processes and public clients who relied on the proposals, Engineer A\u0027s own professional credibility, and the broader precedent for how attribution in qualification proposals will be treated in that jurisdiction.",
  "proeth:description": "Following the jurisdiction-specific rule review, Engineer A makes the decision to report XYZ Engineers\u0027 attribution practice to State Z\u0027s licensing board, where the rules are more specific and stringent and where a clear violation is found to have occurred. The BER concludes this reporting constitutes a clear ethical obligation, not merely a discretionary act.",
  "proeth:foreseenUnintendedEffects": [
    "Report may appear self-serving given competitive relationship",
    "May create professional friction or legal exposure",
    "If anonymous, may be less effective per BER 02-11 guidance"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code of Ethics obligation to report known violations of the Code",
    "Obligation to protect public trust in engineering qualification representations",
    "Obligation to uphold integrity of the licensing and procurement process"
  ],
  "proeth:guidedByPrinciple": [
    "Public protection",
    "Integrity of the profession",
    "Honest representation in engineering qualifications",
    "Accountability to licensing authorities"
  ],
  "proeth:hasAgent": "Engineer A (Engineer / competitor at ABC Consultants)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional self-interest vs. Ethical obligation; Anonymous vs. signed reporting",
    "proeth:resolutionReasoning": "The BER resolves the tension by affirming that the clarity of the State Z violation creates an unambiguous reporting obligation that supersedes concerns about competitive appearance; the factual grounding of the complaint provides its legitimacy"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill a professional ethical obligation to report a clear violation of State Z\u0027s licensing rules regarding attribution of prior project experience in qualification submissions",
  "proeth:requiresCapability": [
    "Ethics complaint drafting",
    "Knowledge of licensing board procedures",
    "Professional courage to report misconduct"
  ],
  "proeth:temporalMarker": "After review, upon conclusion of BER deliberation",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Reports to State Z Board"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Action_Engineer_A_Declines_State_Q_Report",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Report to State Q anyway, arguing that the practice was ethically questionable even if not clearly prohibited",
    "Request that State Q\u0027s licensing board issue an advisory opinion on whether the disclosure format complies with its rules, without filing a formal complaint",
    "Advocate publicly or through professional associations for State Q to adopt more specific attribution rules similar to State Z\u0027s, without involving the licensing board in this specific case"
  ],
  "proeth-scenario:characterMotivation": "Engineer A, having found that State Q\u0027s rules were not clearly violated by XYZ Engineers\u0027 disclosure format, correctly applied the principle that an obligation to report requires a clear violation \u2014 not merely a suspicion, a competitive grievance, or a judgment that the practice was imprudent. The decision reflects disciplined application of the BER\u0027s own precedent-based standard rather than expansive self-appointed enforcement.",
  "proeth-scenario:consequencesIfAlternative": [
    "Reporting to State Q without a clear violation finding would likely result in the complaint being dismissed, would damage Engineer A\u0027s credibility as a good-faith complainant, and could expose Engineer A to criticism for using the regulatory process as a competitive weapon \u2014 undermining the legitimacy of the valid State Z report as well",
    "Requesting an advisory opinion is a constructive middle path that informs State Q\u0027s board of the practice without making a formal accusation, potentially prompting clarification of the rules without penalizing XYZ Engineers for conduct that was not clearly prohibited \u2014 a professionally responsible and forward-looking approach",
    "Advocating for rule reform addresses the systemic gap that allowed the ambiguity to exist in State Q without punishing XYZ Engineers for conduct that fell into that gap; this is the most constructive long-term response to the finding that State Q\u0027s rules were insufficiently specific"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students the critical distinction between conduct that is ethically questionable and conduct that clearly violates a specific rule \u2014 and that professional reporting obligations are bounded by that distinction. Over-reporting where no clear violation exists is itself an ethical problem, not a sign of heightened professional virtue.",
  "proeth-scenario:ethicalTension": "The temptation to report in State Q anyway \u2014 where the practice may have been ethically questionable even if not clearly rule-violating \u2014 vs. the professional obligation to constrain reporting to situations where clear violations are established, avoiding the weaponization of licensing board complaints as competitive tools.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "The fairness of the regulatory process in State Q, XYZ Engineers\u0027 and Engineer B\u0027s right not to face unsubstantiated complaints, Engineer A\u0027s credibility as a principled actor rather than a strategic complainant, and the integrity of the profession\u0027s self-regulatory mechanisms which depend on complaints being filed in good faith on clear grounds.",
  "proeth:description": "Engineer A decides not to report the attribution practice to State Q\u0027s licensing board, based on the finding that State Q\u0027s rules (similar to NSPE standards) were not clearly violated by XYZ Engineers\u0027 disclosure format. The BER affirms this as the correct determination \u2014 no obligation to report exists where no clear violation is established.",
  "proeth:foreseenUnintendedEffects": [
    "XYZ Engineers faces no sanction in State Q despite disclosure that \u0027could have been clearer\u0027",
    "Decision may be perceived as inconsistent given reporting to State Z"
  ],
  "proeth:fulfillsObligation": [
    "Proportionality in ethics enforcement \u2013 not reporting where no clear violation exists",
    "Avoiding misuse of licensing board complaint processes",
    "Honest assessment of rule applicability"
  ],
  "proeth:guidedByPrinciple": [
    "Factual basis for ethics complaints",
    "Proportionality",
    "Respect for jurisdictional rule distinctions",
    "Avoiding harassment through unfounded complaints"
  ],
  "proeth:hasAgent": "Engineer A (Engineer / competitor at ABC Consultants)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Uniform reporting vs. Jurisdiction-specific rules; Clarity of disclosure vs. misrepresentation threshold",
    "proeth:resolutionReasoning": "Engineer A and the BER resolve the tension by holding that the misrepresentation threshold is not clearly met under State Q rules, making a complaint unwarranted; the gray area is resolved in favor of not reporting absent clear rule violation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Avoid filing an unsupported or speculative ethics complaint in a jurisdiction where the rules do not clearly condemn the conduct in question",
  "proeth:requiresCapability": [
    "Ethical judgment under ambiguity",
    "Regulatory interpretation",
    "Proportional application of ethics enforcement"
  ],
  "proeth:temporalMarker": "After review, upon conclusion of BER deliberation",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Declines State Q Report"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Action_Partial_Attribution_Disclosure_in_Proposals",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Repeat the prior-employer attribution explicitly within each individual project description",
    "Create a clearly labeled and visually distinct \u0027Prior Experience\u0027 section separated from XYZ\u0027s own organizational project history",
    "Consult State Q and State Z licensing boards proactively to confirm whether the proposed format satisfies their specific disclosure requirements"
  ],
  "proeth-scenario:characterMotivation": "XYZ Engineers and Engineer B sought a proposal format that was efficient and readable while still technically disclosing the prior-employer attribution \u2014 placing it once at the section level rather than repeating it project-by-project. The motivation was likely a combination of formatting convenience, competitive presentation strategy, and a belief that a single disclosure was sufficient to satisfy transparency requirements.",
  "proeth-scenario:consequencesIfAlternative": [
    "Project-level attribution would have satisfied both states\u0027 requirements, eliminated the ethical violation, and still allowed the experience to serve as a qualification \u2014 the most straightforward compliant path",
    "A structurally separate section would have made the distinction between Engineer B\u0027s prior work and XYZ\u0027s organizational work unmistakably clear to reviewers, satisfying both the letter and spirit of disclosure rules",
    "Board consultation would have revealed State Z\u0027s more stringent requirements before any proposals were submitted, enabling compliant formatting and demonstrating good-faith regulatory engagement that could itself be a competitive differentiator"
  ],
  "proeth-scenario:decisionSignificance": "The central teaching moment of the case: ethical compliance is not satisfied by technically including required information if the format renders that information functionally invisible. Students learn that disclosure must be meaningful and contextually clear, not merely present somewhere in a document.",
  "proeth-scenario:ethicalTension": "Efficiency and competitive presentation vs. full transparency and non-deception \u2014 a single attribution disclosure may be technically present but functionally obscured if readers reviewing individual project descriptions do not connect them back to the section-level note, creating a de facto misleading impression of XYZ\u0027s organizational experience.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Regulatory compliance in two jurisdictions with different standards, the integrity of public procurement processes, potential harm to competing firms who present their qualifications honestly, and the professional licenses of both Engineer B and XYZ Engineers\u0027 principals.",
  "proeth:description": "XYZ Engineers and Engineer B decide to disclose Engineer B\u0027s prior employer affiliation only once at the beginning of the individual qualification section, rather than repeating the attribution within each specific project description. This structural choice in proposal formatting creates the central ethical ambiguity of the case.",
  "proeth:foreseenUnintendedEffects": [
    "Reviewers may not connect the prior employer attribution to each individual project description, creating a misleading impression that projects were performed under XYZ Engineers"
  ],
  "proeth:fulfillsObligation": [
    "Partial disclosure of prior employer affiliation at section level"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency in professional representations",
    "Avoidance of misleading statements",
    "Honest disclosure of experience provenance"
  ],
  "proeth:hasAgent": "XYZ Engineers and Engineer B (jointly, proposal preparation team)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Transparency vs. Practicality",
    "proeth:resolutionReasoning": "XYZ Engineers and Engineer B resolved the tradeoff in favor of practical brevity, disclosing affiliation once rather than per project; this resolution was insufficient under State Z\u0027s rules and created an ethically problematic gray area under State Q\u0027s rules"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Present Engineer B\u0027s prior project experience as supporting qualifications while reducing repetitive language throughout the proposal document",
  "proeth:requiresCapability": [
    "Proposal writing",
    "Knowledge of state licensing board submission requirements",
    "Ethical judgment regarding disclosure standards"
  ],
  "proeth:temporalMarker": "At proposal submission",
  "proeth:violatesObligation": [
    "NSPE Code of Ethics Section II.5(a) \u2013 prohibition on false statements or omission of material facts",
    "State Z licensing board rules requiring explicit per-project attribution",
    "Obligation of full and honest representation in qualification submissions"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Partial Attribution Disclosure in Proposals"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Event_Engineer_B_Gains_Experience",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Who \u0027owns\u0027 a project for qualification purposes \u2014 the engineer who designed it or the firm that employed them?",
    "What obligations does an engineer have when moving firms to ensure prior work is accurately represented?",
    "How should firms structure qualification proposals to honor both the engineer\u0027s experience and the prior firm\u0027s institutional contribution?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral for Engineer B at the time \u2014 routine professional development. Retrospectively significant once misattribution emerges. Prior firm stakeholders may feel ownership over the project record.",
  "proeth-scenario:ethicalImplications": "Reveals a foundational tension between individual professional identity and institutional attribution; sets up the downstream misrepresentation problem; raises questions about what honesty in credentialing requires",
  "proeth-scenario:learningMoment": "Professional credentials are not purely personal \u2014 projects completed within a firm belong institutionally to that firm. Engineers must understand the distinction between individual competence and institutional attribution when representing prior work.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_b": "Gains legitimate professional credentials that enhance employability",
    "prior_firm": "Retains institutional claim to projects completed under its auspices; becomes an aggrieved party if attribution is obscured",
    "public_clients": "Expect accurate representation of who performed prior work when evaluating qualifications",
    "xyz_engineers": "Will later leverage this record, creating ethical and legal exposure"
  },
  "proeth:activatesConstraint": [
    "AccurateCredentialRepresentation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/19#Action_Engineer_B_Completes_Prior_Projects",
  "proeth:causesStateChange": "Engineer B now holds a portfolio of prior projects; this record exists independently and can be referenced in future qualification proposals, but only with accurate attribution",
  "proeth:createsObligation": [
    "Engineer B must accurately represent project history",
    "Any firm employing Engineer B must attribute projects correctly"
  ],
  "proeth:description": "Engineer B accumulates professional experience and project history at a prior firm, creating a record of completed projects that becomes a marketable credential. This experience record becomes the foundation for future qualification proposals.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to XYZ Engineers employment (indeterminate past)",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Engineer B Gains Experience"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Event_XYZ_Market_Entry_Occurs",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What due diligence should a firm perform before submitting qualification proposals in a new state?",
    "Does competitive pressure to win contracts justify ambiguity in how prior experience is presented?",
    "How do varying state standards create ethical risk for firms operating across jurisdictions?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Optimistic and ambitious for XYZ Engineers and Engineer B; competitive concern for firms already operating in States Q and Z including ABC Consultants and Engineer A.",
  "proeth-scenario:ethicalImplications": "Illustrates how business decisions have cascading ethical consequences; raises the question of whether firms exploit regulatory ambiguity strategically; highlights the public interest stake in accurate qualification disclosures",
  "proeth-scenario:learningMoment": "Market expansion into multiple jurisdictions multiplies compliance obligations. Engineers and firms must proactively understand and satisfy each jurisdiction\u0027s rules, not assume uniform standards apply.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a_abc": "Faces new competitive pressure, motivating scrutiny of XYZ\u0027s qualifications",
    "engineer_b": "Professional reputation is now publicly staked on the accuracy of qualification proposals",
    "prior_firm": "May lose competitive advantage if its projects are effectively appropriated by XYZ without attribution",
    "state_clients": "Exposed to potentially misleading qualification information when selecting engineering firms",
    "xyz_engineers": "Gains competitive opportunity but also incurs compliance risk across two regulatory jurisdictions"
  },
  "proeth:activatesConstraint": [
    "TruthfulRepresentation_Constraint",
    "StateBoard_Compliance_Constraint_Q",
    "StateBoard_Compliance_Constraint_Z"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/19#Action_XYZ_Hires_Engineer_B",
  "proeth:causesStateChange": "XYZ Engineers is now a market participant in States Q and Z; qualification proposals are being submitted; the firm and Engineer B are now subject to both states\u0027 professional conduct rules",
  "proeth:createsObligation": [
    "XYZ must comply with each state\u0027s qualification disclosure rules",
    "Engineer B must ensure accurate representation of prior work",
    "Proposals must not create false impressions about project authorship"
  ],
  "proeth:description": "XYZ Engineers begins actively marketing bridge and culvert design services in States Q and Z, entering a competitive marketplace where qualification-based selection processes govern contract awards. This market entry triggers the submission of qualification proposals that become the subject of ethical scrutiny.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer B is hired by XYZ Engineers",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "XYZ Market Entry Occurs"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Event_Attribution_Ambiguity_Created",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is a technically accurate but structurally misleading disclosure an ethical violation? Why or why not?",
    "What standard should govern how qualification proposals represent prior work \u2014 the intent of the preparer or the reasonable understanding of the reader?",
    "Does it matter whether XYZ/Engineer B intended to mislead, or is the effect sufficient to establish an ethical violation?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Potentially unaware or rationalizing for XYZ/Engineer B; alarming and frustrating for Engineer A who perceives unfair competitive advantage; concerning for state clients who may be misled.",
  "proeth-scenario:ethicalImplications": "Exposes the gap between technical compliance and genuine honesty; raises questions about the ethics of exploiting ambiguity; illustrates how structural choices in documents can constitute misrepresentation; highlights the public interest in accurate qualification processes",
  "proeth-scenario:learningMoment": "Ambiguity in professional representations is not ethically neutral. Engineers have an affirmative duty to ensure their qualifications are not misleading, even if technically defensible. Format and structure of disclosures matter as much as content.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a_abc": "Competitive disadvantage if XYZ wins contracts on the basis of misleading qualifications",
    "engineer_b": "Professional license potentially at risk, especially in State Z",
    "prior_firm": "Work performed under its auspices may be credited to a competitor",
    "state_procurement_clients": "Risk of selecting a firm based on inaccurate qualification information",
    "xyz_engineers": "Faces reputational and regulatory risk if misrepresentation is confirmed"
  },
  "proeth:activatesConstraint": [
    "TruthfulRepresentation_Constraint",
    "NSPE_Code_III.3_Honesty",
    "StateZ_Stringent_Attribution_Rule"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/19#Action_Partial_Attribution_Disclosure_in_Proposals",
  "proeth:causesStateChange": "Qualification proposals now exist in the public procurement record containing potentially misleading attribution; the misrepresentation is now an observable fact available to competitors and state boards",
  "proeth:createsObligation": [
    "Potential obligation on Engineer A to investigate and report",
    "Obligation on XYZ/Engineer B to correct misrepresentation",
    "State boards may have obligation to investigate if notified"
  ],
  "proeth:description": "The qualification proposals submitted by XYZ Engineers create an ambiguous representation of project authorship: Engineer B\u0027s prior projects are listed at the beginning of the individual qualification section but the attribution to Engineer B\u0027s prior firm is not repeated within each specific project description. This structural ambiguity means readers may reasonably infer that XYZ Engineers performed work it did not perform.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During XYZ\u0027s marketing campaign in States Q and Z",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Attribution Ambiguity Created"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Event_Competitor_Awareness_Triggered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How should Engineer A distinguish between a genuine ethical concern and competitive self-interest when deciding whether to report?",
    "Does Engineer A have an obligation to investigate before reporting, or is awareness of a potential violation sufficient?",
    "What risks does Engineer A face \u2014 professionally, legally, and reputationally \u2014 by reporting or by not reporting?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Competitive alarm and moral concern for Engineer A \u2014 uncertainty about whether this is a genuine violation or competitive overreaction; potential self-doubt about motivations; frustration at perceived unfairness.",
  "proeth-scenario:ethicalImplications": "Reveals the conflict between professional duty to report and self-interested motivation; illustrates the complexity of third-party reporting obligations; raises questions about the ethics of using professional codes as competitive tools",
  "proeth-scenario:learningMoment": "When an engineer notices a potential ethical violation by a competitor, their own motivations and objectivity must be examined. The duty to report is a professional obligation, not a competitive weapon, and must be exercised with good faith and due diligence.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "abc_consultants": "May benefit competitively if XYZ is found in violation, creating conflict of interest concern for Engineer A",
    "engineer_a": "Now faces a professional and ethical dilemma with potential reporting obligations",
    "engineer_b": "Exposure to professional discipline becomes more likely",
    "state_boards": "May receive a complaint triggering formal investigation",
    "xyz_engineers": "Risk of scrutiny and potential reporting increases"
  },
  "proeth:activatesConstraint": [
    "NSPE_Code_III.2_Reporting_Obligation",
    "ProfessionalDuty_To_Investigate"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/19#Action_Engineer_A_Investigates_Marketing_Practice",
  "proeth:causesStateChange": "Engineer A is now an informed party with potential reporting obligations; the ethical situation expands from a two-party matter (XYZ/Engineer B) to include a third-party observer with professional duties",
  "proeth:createsObligation": [
    "Engineer A must determine whether a violation has occurred before reporting",
    "Engineer A must review applicable codes and rules",
    "Engineer A must act in good faith, not merely competitive interest"
  ],
  "proeth:description": "Engineer A, working at competing firm ABC Consultants, becomes aware of XYZ Engineers\u0027 marketing practice and the attribution format used in their qualification proposals. This awareness is the precipitating event that initiates Engineer A\u0027s ethical deliberation and investigation.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During or after XYZ\u0027s submission of qualification proposals",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Competitor Awareness Triggered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Event_Differential_State_Rules_Discovered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Should the NSPE Code of Ethics be interpreted to fill gaps where state rules are ambiguous, or does it only supplement state rules?",
    "Is it ethically sufficient for Engineer A to report only to State Z and not State Q, even if the underlying conduct is the same?",
    "What does the differential outcome across states reveal about the adequacy of current professional regulation?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Clarifying but also complicating for Engineer A \u2014 relief at having a clear answer for State Z, but uncertainty and perhaps frustration that State Q\u0027s ambiguity prevents a clear reporting obligation there. Potential anxiety about acting correctly.",
  "proeth-scenario:ethicalImplications": "Exposes the fragmentation of professional ethics across jurisdictions; raises questions about whether engineers should be held to the highest applicable standard regardless of jurisdiction; illustrates how regulatory ambiguity can shield misconduct",
  "proeth-scenario:learningMoment": "Professional ethical obligations are not uniform across jurisdictions. Engineers operating in multiple states must understand that varying regulatory standards create varying obligations, and that what is permissible in one jurisdiction may be a clear violation in another.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Gains clarity on obligations but must now act on them, accepting personal and professional risk",
    "engineer_b": "Professional license in State Z is at significant risk",
    "engineering_profession": "Jurisdictional inconsistency in standards is revealed as a systemic problem",
    "state_q_board": "Will not receive a complaint; potential violation may persist unaddressed",
    "state_z_board": "Will likely receive a complaint requiring formal response",
    "xyz_engineers": "State Z exposure is now clearly established; State Q exposure remains uncertain"
  },
  "proeth:activatesConstraint": [
    "StateZ_Reporting_Obligation_Activated",
    "StateQ_Reporting_Obligation_Ambiguous"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/19#Action_Engineer_A_Reviews_Applicable_Rules",
  "proeth:causesStateChange": "The ethical situation bifurcates: State Z presents a clear violation requiring reporting; State Q presents an ambiguous situation not requiring reporting. Engineer A\u0027s obligations are now jurisdiction-specific.",
  "proeth:createsObligation": [
    "Engineer A has clear obligation to report to State Z board",
    "Engineer A has no clear obligation (but possible discretion) regarding State Q",
    "Engineer A must act on findings in good faith"
  ],
  "proeth:description": "Engineer A\u0027s review of the NSPE Code of Ethics and the licensing board rules of States Q and Z reveals that the two states have materially different standards governing attribution in qualification proposals. State Q\u0027s rules are similar to NSPE standards and do not clearly prohibit XYZ\u0027s practice, while State Z\u0027s rules are more specific and stringent and appear to have been clearly violated.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During Engineer A\u0027s review of applicable rules",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Differential State Rules Discovered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Event_State_Z_Violation_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What personal risks does Engineer A accept by reporting to State Z, and are those risks ethically relevant to the decision?",
    "How should Engineer A document and present the violation to State Z\u0027s board to ensure a fair and complete investigation?",
    "If XYZ\u0027s violation in State Z is confirmed, what remedies are appropriate \u2014 for the profession, for clients, and for the prior firm whose work was misrepresented?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Gravity and resolve for Engineer A \u2014 the ambiguity is resolved and action is required; anxiety and potential defensiveness for XYZ/Engineer B if they become aware; concern among state procurement officials about past contract awards.",
  "proeth-scenario:ethicalImplications": "Demonstrates the concrete activation of mandatory reporting obligations; illustrates that professional ethics requires action even at personal cost; raises questions about the adequacy of remedies for qualification misrepresentation; highlights the public interest in accurate professional credentials",
  "proeth-scenario:learningMoment": "When a violation is clearly established, professional reporting obligations become mandatory, not discretionary. Engineers must act on confirmed violations even when doing so is personally and professionally uncomfortable.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Must now report, accepting potential retaliation risk and the burden of being a whistleblower",
    "engineer_b": "Professional license in State Z at serious risk; potential career consequences",
    "prior_firm": "May be recognized as the rightful author of attributed projects",
    "public_clients_state_z": "Past procurement decisions may have been based on misleading information",
    "state_z_board": "Obligated to receive and investigate complaint; institutional credibility engaged",
    "xyz_engineers": "Faces formal disciplinary proceedings, potential loss of State Z licensure or market access"
  },
  "proeth:activatesConstraint": [
    "NSPE_Code_III.2_Mandatory_Reporting",
    "StateZ_Board_Jurisdiction_Constraint",
    "PublicTrust_Protection_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/19#Action_Engineer_A_Reviews_Applicable_Rules",
  "proeth:causesStateChange": "A confirmed ethical and regulatory violation now exists on record; Engineer A\u0027s reporting obligation is activated; XYZ/Engineer B\u0027s regulatory exposure in State Z is concrete and imminent",
  "proeth:createsObligation": [
    "Engineer A has a clear, non-discretionary obligation to report to State Z board",
    "State Z board has obligation to investigate upon receipt of complaint",
    "XYZ Engineers and Engineer B face potential disciplinary proceedings in State Z"
  ],
  "proeth:description": "As a result of Engineer A\u0027s review, it becomes an established factual and ethical conclusion that XYZ Engineers\u0027 qualification proposals violated State Z\u0027s specific and stringent attribution rules. This outcome transforms the situation from a suspected irregularity into a confirmed violation with clear reporting implications.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Upon completion of Engineer A\u0027s rules review",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "State Z Violation Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#Event_BER_Precedent_Applied",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How much weight should BER precedent carry relative to an individual engineer\u0027s own ethical judgment?",
    "Does the BER\u0027s conclusion that there is no obligation to report to State Q mean XYZ\u0027s conduct there was ethical, or only that it was not clearly prohibited?",
    "What does the application of precedent from 1976 (BER 76-4) to a modern qualification proposal context reveal about the durability of core ethical principles?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Validating for Engineer A if the conclusion aligns with their own analysis; potentially sobering for XYZ/Engineer B as institutional authority confirms the violation; educational and clarifying for the broader engineering community.",
  "proeth-scenario:ethicalImplications": "Illustrates the role of institutional ethical authority in professional practice; reveals that \u0027no obligation to report\u0027 does not mean \u0027no ethical concern\u0027; demonstrates how precedent-based reasoning applies general principles to specific jurisdictional contexts",
  "proeth-scenario:learningMoment": "Professional ethics is not merely personal judgment \u2014 it is informed by institutional precedent, codes, and authoritative analysis. Engineers should consult BER opinions and applicable codes before concluding whether a violation exists and whether reporting is required.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Obligations are formally confirmed, providing institutional backing for the decision to report",
    "engineer_b": "Professional jeopardy in State Z is now supported by authoritative ethical analysis",
    "engineering_profession": "Gains clearer guidance on attribution in qualification proposals across jurisdictions",
    "future_engineers": "Have access to precedent that clarifies obligations in similar situations",
    "state_boards": "BER analysis provides persuasive authority for their own disciplinary proceedings",
    "xyz_engineers": "BER conclusion increases legitimacy and weight of any State Z complaint"
  },
  "proeth:activatesConstraint": [
    "NSPE_Precedent_Consistency_Constraint",
    "Engineer_A_Reporting_Obligation_State_Z"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/19#Action_Engineer_A_Reviews_Applicable_Rules__triggering_BE",
  "proeth:causesStateChange": "Ethical guidance is now formally established; Engineer A\u0027s obligations are authoritatively confirmed; the case becomes part of the body of professional ethics precedent",
  "proeth:createsObligation": [
    "Engineer A\u0027s obligation to report to State Z is formally confirmed by BER",
    "Engineering community is put on notice of applicable standards",
    "Future cases must be assessed against this precedent"
  ],
  "proeth:description": "The Board of Ethical Review analyzes the case using precedent cases BER 76-4 and BER 02-11, applying established ethical reasoning to conclude that Engineer A has no obligation to report to State Q but has a clear obligation to report to State Z. This application of precedent transforms prior case law into binding ethical guidance for the present situation.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "BER analysis phase (after facts established)",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "BER Precedent Applied"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#CausalChain_83e93c23",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B accumulates professional experience and project history at a prior firm, creating a record of completed bridge and culvert design work that becomes the basis for future marketing claims",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B performs bridge and culvert design work at a previous firm, generating a professional portfolio",
      "proeth:element": "Engineer B Completes Prior Projects",
      "proeth:step": 1
    },
    {
      "proeth:description": "The completed work becomes part of Engineer B\u0027s professional history and qualifications record",
      "proeth:element": "Engineer B Gains Experience",
      "proeth:step": 2
    },
    {
      "proeth:description": "XYZ Engineers recruits Engineer B specifically because of this accumulated project experience",
      "proeth:element": "XYZ Hires Engineer B",
      "proeth:step": 3
    },
    {
      "proeth:description": "XYZ uses Engineer B\u0027s credentials as the foundation for entering bridge and culvert markets in States Q and Z",
      "proeth:element": "XYZ Market Entry Occurs",
      "proeth:step": 4
    },
    {
      "proeth:description": "The prior work is represented in qualification proposals in a manner that obscures its institutional origin",
      "proeth:element": "Attribution Ambiguity Created",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Completes Prior Projects (Action 1)",
  "proeth:counterfactual": "Without completing prior projects, Engineer B would have no experiential record to reference, and XYZ\u0027s subsequent marketing claims would have no factual basis whatsoever",
  "proeth:effect": "Engineer B Gains Experience (Event 1)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s active employment at prior firm",
    "Completion of substantive bridge and culvert design projects",
    "Institutional attribution of that work to Engineer B\u0027s professional record"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Completion of a body of work at prior firm + professional documentation of that work + Engineer B\u0027s personal involvement in design decisions"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#CausalChain_74189c74",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "XYZ Engineers and Engineer B decide to disclose Engineer B\u0027s prior employer affiliation only once at the beginning of the proposal, creating an ambiguous representation of project ownership that obscures the institutional origin of the referenced work",
  "proeth:causalSequence": [
    {
      "proeth:description": "XYZ and Engineer B adopt a single-instance disclosure format for prior employer affiliation",
      "proeth:element": "Partial Attribution Disclosure in Proposals",
      "proeth:step": 1
    },
    {
      "proeth:description": "Qualification proposals submitted to States Q and Z create unclear impressions about who completed the referenced projects",
      "proeth:element": "Attribution Ambiguity Created",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A notices the ambiguous marketing materials and identifies a potential ethical issue",
      "proeth:element": "Competitor Awareness Triggered",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A undertakes a deliberate investigation into whether the attribution practice violates applicable rules",
      "proeth:element": "Engineer A Investigates Marketing Practice",
      "proeth:step": 4
    },
    {
      "proeth:description": "Investigation confirms that the ambiguous disclosure violates State Z\u0027s licensing board rules",
      "proeth:element": "State Z Violation Established",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Partial Attribution Disclosure in Proposals (Action 3)",
  "proeth:counterfactual": "Had XYZ disclosed prior employer affiliation prominently and repeatedly for each referenced project, the ambiguity would not have arisen and the ethical violation would likely not have occurred",
  "proeth:effect": "Attribution Ambiguity Created (Event 3)",
  "proeth:necessaryFactors": [
    "Decision to limit disclosure to a single, non-repeated reference",
    "Structural formatting of proposals that lists multiple projects without repeated attribution",
    "Absence of per-project prior-employer identification"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "XYZ Engineers and Engineer B (shared)",
  "proeth:sufficientFactors": [
    "Single-instance disclosure format + multi-project listing without repeated attribution + reviewer tendency to associate listed projects with the submitting firm"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#CausalChain_d5b4e1e3",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon noticing XYZ Engineers\u0027 qualification proposals, Engineer A makes a deliberate decision to investigate the attribution practice, which leads to a jurisdiction-specific review that reveals differing rules between States Q and Z",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A becomes aware of XYZ\u0027s qualification proposals through competitive market observation",
      "proeth:element": "Competitor Awareness Triggered",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A decides to formally investigate whether the attribution practice is ethically or legally problematic",
      "proeth:element": "Engineer A Investigates Marketing Practice",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A conducts a jurisdiction-specific review of NSPE Code and licensing board rules for States Q and Z",
      "proeth:element": "Engineer A Reviews Applicable Rules",
      "proeth:step": 3
    },
    {
      "proeth:description": "The review reveals that State Z has explicit rules prohibiting the attribution practice while State Q does not have equivalent provisions",
      "proeth:element": "Differential State Rules Discovered",
      "proeth:step": 4
    },
    {
      "proeth:description": "The differential rules finding leads to the conclusion that XYZ\u0027s practice violates State Z\u0027s specific requirements",
      "proeth:element": "State Z Violation Established",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Investigates Marketing Practice (Action 4)",
  "proeth:counterfactual": "Without Engineer A\u0027s deliberate investigation, the differential state rules would not have been discovered in this context, and no report to State Z would have followed from this chain of events",
  "proeth:effect": "Differential State Rules Discovered (Event 5)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s awareness of XYZ\u0027s marketing materials",
    "Engineer A\u0027s decision to actively investigate rather than ignore the practice",
    "Existence of genuinely different rules between States Q and Z"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Engineer A\u0027s investigative decision + access to NSPE Code and state licensing board rules + actual regulatory divergence between the two states"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#CausalChain_cc02493b",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "XYZ Engineers makes a deliberate hiring decision to bring Engineer B on as a project manager, specifically to leverage Engineer B\u0027s prior project history to qualify for bridge and culvert contracts in new jurisdictions",
  "proeth:causalSequence": [
    {
      "proeth:description": "XYZ makes a strategic hiring decision targeting Engineer B\u0027s bridge and culvert project portfolio",
      "proeth:element": "XYZ Hires Engineer B",
      "proeth:step": 1
    },
    {
      "proeth:description": "XYZ begins submitting qualification proposals in States Q and Z using Engineer B\u0027s credentials",
      "proeth:element": "XYZ Market Entry Occurs",
      "proeth:step": 2
    },
    {
      "proeth:description": "XYZ and Engineer B adopt a disclosure practice that mentions prior employer affiliation only once and ambiguously",
      "proeth:element": "Partial Attribution Disclosure in Proposals",
      "proeth:step": 3
    },
    {
      "proeth:description": "Qualification proposals create unclear representations about project ownership and institutional origin",
      "proeth:element": "Attribution Ambiguity Created",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A at ABC Consultants notices XYZ\u0027s marketing practices and begins scrutiny",
      "proeth:element": "Competitor Awareness Triggered",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "XYZ Hires Engineer B (Action 2)",
  "proeth:counterfactual": "Without hiring Engineer B, XYZ would lack the project history necessary to credibly market bridge and culvert services in States Q and Z, making market entry significantly less viable or requiring a different qualification strategy",
  "proeth:effect": "XYZ Market Entry Occurs (Event 2)",
  "proeth:necessaryFactors": [
    "XYZ\u0027s strategic intent to enter bridge and culvert markets",
    "Engineer B\u0027s possession of relevant prior project credentials",
    "XYZ\u0027s decision to use Engineer B\u0027s history as a qualification basis"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "XYZ Engineers (organizational decision-makers)",
  "proeth:sufficientFactors": [
    "Deliberate hiring of Engineer B for credential leverage + XYZ\u0027s existing organizational capacity + availability of target markets in States Q and Z"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#CausalChain_eeefb777",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A conducts a deliberate, jurisdiction-specific review of the NSPE Code of Ethics and the licensing board rules of States Q and Z, which reveals that State Z has explicit provisions violated by XYZ\u0027s practice while State Q does not, leading to differentiated reporting decisions",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A conducts a systematic, jurisdiction-by-jurisdiction review of NSPE Code and state licensing board rules",
      "proeth:element": "Engineer A Reviews Applicable Rules",
      "proeth:step": 1
    },
    {
      "proeth:description": "Review reveals State Z has explicit attribution disclosure requirements that State Q lacks",
      "proeth:element": "Differential State Rules Discovered",
      "proeth:step": 2
    },
    {
      "proeth:description": "XYZ\u0027s single-instance disclosure practice is determined to violate State Z\u0027s specific licensing board rules",
      "proeth:element": "State Z Violation Established",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A files a report with State Z\u0027s licensing board based on the confirmed violation",
      "proeth:element": "Engineer A Reports to State Z Board",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A decides not to report to State Q because no equivalent rule violation was identified",
      "proeth:element": "Engineer A Declines State Q Report",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Reviews Applicable Rules (Action 5)",
  "proeth:counterfactual": "Without the jurisdiction-specific review, Engineer A would not have identified the State Z violation with sufficient specificity to justify a report, and would not have had a principled basis for declining to report to State Q",
  "proeth:effect": "State Z Violation Established (Event 6) and Engineer A Declines State Q Report (Action 7)",
  "proeth:necessaryFactors": [
    "Jurisdiction-specific review methodology distinguishing State Q from State Z",
    "Actual existence of differing rules between the two states",
    "Engineer A\u0027s capacity to correctly interpret and apply the discovered rules"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Thorough rule review + genuine regulatory divergence + Engineer A\u0027s correct legal interpretation = differentiated violation findings for each state"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/19#",
    "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/19#CausalChain_25c19b1a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Following the jurisdiction-specific rule review, Engineer A makes the decision to report XYZ Engineers to State Z\u0027s licensing board, which triggers a formal ethical review process in which the Board of Ethical Review analyzes the case using precedent cases BER 76-4 and BER 02-11",
  "proeth:causalSequence": [
    {
      "proeth:description": "XYZ and Engineer B adopt an ambiguous single-instance disclosure format",
      "proeth:element": "Partial Attribution Disclosure in Proposals",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A\u0027s review confirms the disclosure practice violates State Z\u0027s explicit rules",
      "proeth:element": "State Z Violation Established",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A files a formal complaint with State Z\u0027s licensing board",
      "proeth:element": "Engineer A Reports to State Z Board",
      "proeth:step": 3
    },
    {
      "proeth:description": "The Board of Ethical Review formally analyzes the case, applying BER 76-4 and BER 02-11 to determine ethical obligations",
      "proeth:element": "BER Precedent Applied",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER issues findings on the propriety of XYZ\u0027s attribution practice and Engineer A\u0027s reporting decisions under applicable ethical standards",
      "proeth:element": "Ethical Determination Issued",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Reports to State Z Board (Action 6)",
  "proeth:counterfactual": "Without Engineer A\u0027s report to State Z, the BER would not have been engaged to apply precedent to this specific fact pattern; the ethical analysis would not have been formally institutionalized",
  "proeth:effect": "BER Precedent Applied (Event 7)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s formal report to State Z licensing board",
    "State Z Violation being established as a factual and ethical conclusion",
    "Existence of applicable BER precedent cases addressing attribution in qualification proposals"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (for initiating report); XYZ Engineers and Engineer B (for creating the conditions requiring BER review)",
  "proeth:sufficientFactors": [
    "Formal report submission + established State Z violation + BER\u0027s jurisdiction to review + availability of directly applicable precedent cases"
  ],
  "proeth:withinAgentControl": true
}