CorrectiveActionRefusalState
Class
http://proethica.org/ontology/intermediate#CorrectiveActionRefusalState
Class Hierarchy
- Thing
- ↳ entity (bfo)
- ↳ continuant (bfo)
- ↳ specifically dependent continuant (bfo)
- ↳ State (proethica-core)
- ↳ Regulatory State (proethica-intermediate)
- ↳ CorrectiveActionRefusalState
Definition
A condition in which a responsible authority, having been made aware of a noncompliant contracting practice, refuses to address or correct the arrangement, so the noncompliance persists and escalation duties for other engineers become applicable. In this case, the City D Engineer refuses to address the contract arrangement with Firm Z despite the apparent procurement law violation.
Inherited from RegulatoryViolationState
A condition in which a policy or requirement is in force for the situation, here City policies requiring new infrastructure projects to be developed with climate resiliency in mind.
Case Provenance
Discovered in
This class was discovered during extraction of the case(s) above; the supporting verbatim quotes are in Source Evidence.
Properties
Action Constraints
Action should proceed advisedly, carefully, and sensitively, complying with the law and Code sections I.4, I.6, III.6, III.7
Engineer A should proceed within the City's approved channels of communication and respect Engineer D's authority
Activation Conditions
City D Engineer is notified of the apparent procurement law violation in the Firm Z contract awards and declines to take corrective action
Confidence
0.88
Obligation Activation
Appropriate Action Obligation per Code sections II.1.e, II.1.f, and III.8.a
Obligation to consider any duties they may have to report to the state licensure board
Persistence Type
inertial
Principle Transformation
The abstract duty to conform with state registration laws and to act honorably becomes, given the refusal, a concrete duty on Engineer A to take appropriate action within approved channels, verify all facts, and consider reporting to the state licensure board.ual
State Category
regulatory
Termination Conditions
Responsible parties follow a legal, ethical, and mutually acceptable solution correcting the contract arrangement with Firm Z
Property Structure
1 · Object and Data Properties
rdfs:domain on this class or ancestor
| Property | Range | Description |
|---|---|---|
| activatedByEvent inherited | Event | Event Calculus initiation: relates a State to the Event whose occurrence brings the State into being (the start boundary of the fluent). |
| activatesConstraint inherited | Constraint | Relates a State to a Constraint that the obtaining of the State activates, bounding the actions available to the role-bearers the state concerns (the S->Cs linkage). |
| activatesObligation inherited | Obligation | Relates a State to an Obligation that the obtaining of the State makes applicable. This is the forward, activating complement of defeasibleUnder (which records the State under which an obligation yields): a state such as hazard exposure or an undertaken commitment can bring an obligation into force for the role-bearers it concerns. |
| affects inherited | Agent | Relates a State to the Agent(s) it bears on in the case scenario (the parties whose situation the state changes), distinct from the obligations/constraints the state activates (activatesObligation / activatesConstraint). |
| terminatedByEvent inherited | Event | Event Calculus termination: relates a State to the Event whose occurrence ends the State (the end boundary of the fluent). |
2 · Definitional Attributes
SHACL definitional shape
| Attribute | Property (sh:path) | Description |
|---|---|---|
| state archetype | stateCategory | The content archetype, which drives the archetype subClassOf typing: EpistemicState, RiskState, CompetenceState, EmergencyState, ConflictOfInterestState, RegulatoryState, TemporalState, ResourceState, DisclosureState. A classification of the state content, explicitly NOT the activatesObligation relation. A routing input, not stored as a literal. |
| persistence type | persistenceType | Whether the state is an inertial fluent (holds until an event terminates it) or a non-inertial fluent (true at a single time point), the inertial versus non-inertial fluent distinction of Berreby et al. (2017) in the Event Calculus; a class-level datatype, a property of the fluent predicate itself. |
3 · Bearer Attributes
SHACL property shape
individual data
| Attribute | Property (sh:path) | Description |
|---|---|---|
| urgency level | urgencyLevel | The salience or acuteness of the state in this case (Jones 1991 moral-intensity salience; components include temporal immediacy, magnitude of consequences, and proximity). |
| activates obligation | activatesObligation | The obligation the state makes applicable, via the outgoing S->O activatesObligation edge; the incoming counterpart is defeasibleUnder (O->S), recording the obligation that yields when this state obtains. Range: Obligation. |
| activates constraint | activatesConstraint | The constraint the state activates, via the outgoing S->Cs activatesConstraint edge, bounding the actions available while the state holds. Range: Constraint. |
| affects | affects | The agent(s) the state bears on, via the S->Agent affects edge, resolved from the affected-parties text by embedding shortlist + LLM multi-select. Range: Agent. |
| subject | subject | The entity the state holds of (the bearer text); a kept literal that also feeds the defeasibility prompt as state context. |
| active period | activePeriod | The period over which the state holds, as extracted text. |
| triggering event | triggeringEvent | The event bringing the state into being; kept verbatim on the individual and also resolved to the activatedByEvent edge (the start boundary of the fluent). |
| terminated by | terminatedBy | What removes the state; kept verbatim on the individual and also resolved to the terminatedByEvent edge (the end boundary of the fluent). |
| activated by event | activatedByEvent | The Event whose occurrence initiates this state, via the outgoing activatedByEvent edge (the start boundary of the fluent). Range: Event. |
| terminated by event | terminatedByEvent | The Event whose occurrence ends this state, via the outgoing terminatedByEvent edge (the end boundary of the fluent). Range: Event. |
4 · Referenced By
rdfs:range on this class or ancestor
| From | Property | Description |
|---|---|---|
| Action | initiates inherited | Event Calculus initiation: relates a happening (Action or Event) to a State (fluent) that begins to hold as a result and persists until terminated (inertial) or holds momentarily (non-inertial). |
| Action | terminates inherited | Event Calculus termination: relates a happening (Action or Event) to a State (fluent) that ceases to hold as a result. |
| Event | initiates inherited | Event Calculus initiation: relates a happening (Action or Event) to a State (fluent) that begins to hold as a result and persists until terminated (inertial) or holds momentarily (non-inertial). |
| Event | terminates inherited | Event Calculus termination: relates a happening (Action or Event) to a State (fluent) that ceases to hold as a result. |
| Obligation | defeasibleUnder inherited | Relates an obligation to a State whose obtaining renders the obligation defeasible, that is, subject to override by a competing obligation with stronger normative support. The State specifies the context in which the obligation yields. |
Source Evidence
Text references
The BER holds that per Code sections II.1.e, II.1.f, and III.8.a, appropriate action must be taken.
The third question asks what steps must Engineer A take given the City D Engineer’s refusal to address the contract arrangement with Firm Z.
Source text
The third question asks what steps must Engineer A take given the City D Engineer’s refusal to address the contract arrangement with Firm Z. The BER holds that per Code sections II.1.e, II.1.f, and III.8.a, appropriate action must be taken.
@prefix core: <http://proethica.org/ontology/core#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix pcsh: <http://proethica.org/shapes/core#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix proeth-prov: <http://proethica.org/provenance#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
proeth:CorrectiveActionRefusalState a owl:Class ;
rdfs:label "CorrectiveActionRefusalState" ;
proeth:actionConstraints "Action should proceed advisedly, carefully, and sensitively, complying with the law and Code sections I.4, I.6, III.6, III.7",
"Engineer A should proceed within the City's approved channels of communication and respect Engineer D's authority" ;
proeth:activationConditions "City D Engineer is notified of the apparent procurement law violation in the Firm Z contract awards and declines to take corrective action" ;
proeth:confidence "0.88" ;
proeth:obligationActivation "Appropriate Action Obligation per Code sections II.1.e, II.1.f, and III.8.a",
"Obligation to consider any duties they may have to report to the state licensure board" ;
proeth:persistenceType "inertial" ;
proeth:principleTransformation "The abstract duty to conform with state registration laws and to act honorably becomes, given the refusal, a concrete duty on Engineer A to take appropriate action within approved channels, verify all facts, and consider reporting to the state licensure board.ual" ;
proeth:stateCategory "regulatory" ;
proeth:terminationConditions "Responsible parties follow a legal, ethical, and mutually acceptable solution correcting the contract arrangement with Firm Z" ;
proeth:textReferences "The BER holds that per Code sections II.1.e, II.1.f, and III.8.a, appropriate action must be taken.",
"The third question asks what steps must Engineer A take given the City D Engineer’s refusal to address the contract arrangement with Firm Z." ;
proeth-prov:discoveredInCase 6 ;
proeth-prov:discoveredInPass 1 ;
proeth-prov:discoveredInSection "discussion" ;
proeth-prov:firstDiscoveredAt "2026-07-05T03:39:15.809045+00:00"^^xsd:dateTime ;
proeth-prov:firstDiscoveredInCase 6 ;
proeth-prov:matchConfidence 0.75 ;
proeth-prov:matchReasoning "A refusal to address a known noncompliant contract arrangement is a specialization of the persisting regulatory violation condition; the ontology's reuse policy folds deferred or refused compliance conditions (Client Deferred Compliance State) into RegulatoryViolationState, so this candidate matches that parent at medium confidence rather than minting a compound variant." ;
proeth-prov:matchedOntologyClass proeth:RegulatoryViolationState ;
proeth-prov:matchedOntologyLabel "RegulatoryViolationState" ;
proeth-prov:matchesExisting true ;
proeth-prov:sourceText "The third question asks what steps must Engineer A take given the City D Engineer’s refusal to address the contract arrangement with Firm Z. The BER holds that per Code sections II.1.e, II.1.f, and III.8.a, appropriate action must be taken." ;
rdfs:comment "A condition in which a responsible authority, having been made aware of a noncompliant contracting practice, refuses to address or correct the arrangement, so the noncompliance persists and escalation duties for other engineers become applicable. In this case, the City D Engineer refuses to address the contract arrangement with Firm Z despite the apparent procurement law violation." ;
rdfs:subClassOf proeth:RegulatoryState ;
skos:definition "A condition in which a responsible authority, having been made aware of a noncompliant contracting practice, refuses to address or correct the arrangement, so the noncompliance persists and escalation duties for other engineers become applicable. In this case, the City D Engineer refuses to address the contract arrangement with Firm Z despite the apparent procurement law violation." ;
skos:scopeNote "[RegulatoryViolationState] A condition in which a policy or requirement is in force for the situation, here City policies requiring new infrastructure projects to be developed with climate resiliency in mind." ;
prov:generatedAtTime "2026-07-05T03:39:15.809045+00:00"^^xsd:dateTime ;
prov:wasAttributedTo "Case 6 Extraction",
"claude-fable-5" .
pcsh:CaseAnnotationShape a sh:NodeShape ;
rdfs:label "Shared per-case annotation schema (all nine components)"@en ;
rdfs:comment "The cross-component annotation fields on committed case individuals: proeth:confidence (extraction confidence, decimal; all components except Action, whose Step-3 contract carries no confidence field), proeth:textReferences (verbatim supporting quotes, universal), proeth-prov sourceText (the source snippet, on the Step-1/2 provenance layers; Step-3 A/E individuals ground via textReferences only), and the involvement gloss (proeth:caseInvolvement on role individuals, proeth:caseContext on obligation, capability, and constraint individuals). Values are per-individual; the fields do not individuate any type."@en ;
sh:property [ sh:description "Extraction confidence for this individual (0 to 1)." ;
sh:name "confidence" ;
sh:order 1 ;
sh:path proeth:confidence ],
[ sh:description "Verbatim case quotes supporting this individual." ;
sh:name "text references" ;
sh:order 2 ;
sh:path proeth:textReferences ],
[ sh:description "How this individual figures in the case narrative (role individuals; the same text is routed into rdfs:comment)." ;
sh:name "case involvement" ;
sh:order 3 ;
sh:path proeth:caseInvolvement ],
[ sh:description "Grounding context in this case (obligation, capability, and constraint individuals)." ;
sh:name "case context" ;
sh:order 4 ;
sh:path proeth:caseContext ] ;
sh:targetClass core:Action,
core:Capability,
core:Constraint,
core:Event,
core:Obligation,
core:Principle,
core:Resource,
core:Role,
core:State .
pcsh:StateDefinitionShape a sh:NodeShape ;
rdfs:label "State definition schema (type-level, descriptive, field contract)"@en ;
rdfs:comment "What individuates a state TYPE: its content archetype (drives the archetype subClassOf typing) and its persistence type (inertial vs non-inertial fluent, a class-level datatype). Its per-case urgency and the activatesObligation edge are per-individual and declared on StatePropertyShape, mirroring the Role/Principle/Obligation Definition/Property split and the state scopeNote (which names the condition and its persistence type as type-defining). Descriptive only (no validation result); state_category is a routing input, not stored as a literal."@en ;
sh:property [ sh:description "The content archetype, which drives the archetype subClassOf typing: EpistemicState, RiskState, CompetenceState, EmergencyState, ConflictOfInterestState, RegulatoryState, TemporalState, ResourceState, DisclosureState. A classification of the state content, explicitly NOT the activatesObligation relation. A routing input, not stored as a literal." ;
sh:name "state archetype" ;
sh:order 1 ;
sh:path proeth:stateCategory ],
[ sh:description "Whether the state is an inertial fluent (holds until an event terminates it) or a non-inertial fluent (true at a single time point), the inertial versus non-inertial fluent distinction of Berreby et al. (2017) in the Event Calculus; a class-level datatype, a property of the fluent predicate itself." ;
sh:name "persistence type" ;
sh:order 2 ;
sh:path proeth:persistenceType ] ;
sh:targetClass core:State .
pcsh:StatePropertyShape a sh:NodeShape ;
rdfs:label "State per-case schema (individual data, non-definitional)"@en ;
rdfs:comment "What a given state INDIVIDUAL is described by in a specific case: its bearer and holding period, its urgency (per-case salience), the event boundaries of the fluent, and the obligations, constraints, and agents its obtaining engages via edges. These do NOT individuate the state TYPE (that is StateDefinitionShape); their values are per-case, asserted on the individual. The proeth:principleTransformation synthesis literal (the S->P->O grounding written onto the individual by the state-edge pass) is deliberately not part of the extraction field contract. Descriptive only."@en ;
sh:property [ sh:description "The salience or acuteness of the state in this case (Jones 1991 moral-intensity salience; components include temporal immediacy, magnitude of consequences, and proximity)." ;
sh:name "urgency level" ;
sh:order 1 ;
sh:path proeth:urgencyLevel ],
[ sh:description "The obligation the state makes applicable, via the outgoing S->O activatesObligation edge; the incoming counterpart is defeasibleUnder (O->S), recording the obligation that yields when this state obtains. Range: Obligation." ;
sh:name "activates obligation" ;
sh:order 2 ;
sh:path core:activatesObligation ],
[ sh:description "The constraint the state activates, via the outgoing S->Cs activatesConstraint edge, bounding the actions available while the state holds. Range: Constraint." ;
sh:name "activates constraint" ;
sh:order 3 ;
sh:path core:activatesConstraint ],
[ sh:description "The agent(s) the state bears on, via the S->Agent affects edge, resolved from the affected-parties text by embedding shortlist + LLM multi-select. Range: Agent." ;
sh:name "affects" ;
sh:order 4 ;
sh:path core:affects ],
[ sh:description "The entity the state holds of (the bearer text); a kept literal that also feeds the defeasibility prompt as state context." ;
sh:name "subject" ;
sh:order 5 ;
sh:path proeth:subject ],
[ sh:description "The period over which the state holds, as extracted text." ;
sh:name "active period" ;
sh:order 6 ;
sh:path proeth:activePeriod ],
[ sh:description "The event bringing the state into being; kept verbatim on the individual and also resolved to the activatedByEvent edge (the start boundary of the fluent)." ;
sh:name "triggering event" ;
sh:order 7 ;
sh:path proeth:triggeringEvent ],
[ sh:description "What removes the state; kept verbatim on the individual and also resolved to the terminatedByEvent edge (the end boundary of the fluent)." ;
sh:name "terminated by" ;
sh:order 8 ;
sh:path proeth:terminatedBy ],
[ sh:description "The Event whose occurrence initiates this state, via the outgoing activatedByEvent edge (the start boundary of the fluent). Range: Event." ;
sh:name "activated by event" ;
sh:order 9 ;
sh:path core:activatedByEvent ],
[ sh:description "The Event whose occurrence ends this state, via the outgoing terminatedByEvent edge (the end boundary of the fluent). Range: Event." ;
sh:name "terminated by event" ;
sh:order 10 ;
sh:path core:terminatedByEvent ] ;
sh:targetClass core:State .
Metadata
Extraction details
Discovered in case
6
Discovered in pass
1
Discovered in section
discussion
First discovered
2026-07-05T03:39:15.809045+00:00
First case
6
Match Confidence
0.75
Match Reasoning
A refusal to address a known noncompliant contract arrangement is a specialization of the persisting regulatory violation condition; the ontology's reuse policy folds deferred or refused compliance conditions (Client Deferred Compliance State) into RegulatoryViolationState, so this candidate matches that parent at medium confidence rather than minting a compound variant.
Matched Ontology Label
RegulatoryViolationState
Matches Existing
true
Generated
2026-07-05T03:39:15.809045+00:00
Attributed to
['Case 6 Extraction', 'claude-fable-5']