Mitigator

Select any passage to ask a question about it or to propose replacement wording.

Mitigator

Part of Nidus Ontology V3 · Glossary entry · Relationship Map

Definition

A Mitigator is a discrete action, resource deployment, or procedural adjustment taken during a visit that gains access, or reduces the hazard, while a Constraint stands. Calling ahead, using an alternate entry point, donning personal protective equipment, bringing an ATV, requesting law enforcement, or securing an animal are examples of Mitigators.

Ontological Position

An operational object, and an event rather than a plan. It records something done at a place at a time, by a Technician, in answer to an obstacle that the visit met.

A Mitigator is where an obstacle stops being a wall and becomes work. The constraint stays: the gate someone propped open is open for that visit, the dog is still at the property, the refused entry stands until the owner relents. What the Mitigator supplies is the means to work in the presence of that condition, and the record of how the work was reached.

A Mitigator is atomic and answers one obstacle. A call ahead followed by a locksmith is two Mitigators, and each is judged on its own.

  • A Mitigator targets exactly one Constraint (Constraint ||──o{ Mitigator).
  • A Mitigator is taken by one or more Technicians (Technician }o──o{ Mitigator).
  • A Mitigator may arise within an Assignment (Assignment }o──o{ Mitigator).
  • A Mitigator may use Equipment (Mitigator }o──o{ Equipment).
  • A Mitigator may be annotated by Reviews (Mitigator ||──o{ Review).

Properties

Character

  • Target Constraint — the one Constraint the action answers, named on every Mitigator.
  • Type — the kind of action taken, taken from Mitigator Type.

Provenance

  • Time — when the action was taken.
  • Outcome — how it went, recorded for every attempt. Values: Successful, Partially Successful, Unsuccessful.

Rules

  1. A Mitigator targets one Constraint and names it. A Mitigator recorded against no Constraint is meaningless.
  2. A Mitigator is atomic. Each action is its own record, and a sequence of actions is a sequence of Mitigators.
  3. A Mitigator gains access in the presence of the Constraint and records how the work was reached. The condition itself is met again by a later visit, which records it as that visit found it.
  4. A successful Mitigator leaves the Constraint constraining. The Constraint record is unchanged by it: each visit states the condition as it met it.
  5. A failed attempt is recorded as it happened. Outcome is stated for every Mitigator, and an unsuccessful one is evidence about the obstacle.
  6. A Mitigator is taken during a visit by the Technician who took it. It may arise within an Assignment, and the visit it belongs to is recorded wherever one exists.
  7. All Constraints must be eliminated or mitigated before work proceeds.
  8. Mitigations and mitigation attempts remain a part of the site record to inform future mitigations.

Relations

Every relation this concept takes part in is drawn on the relationship map.

Relationship diagram: Mitigator
Open this diagram at full size