Protest Support Conflict
Screen protest-support facts for assignment conflict.
Description
A protest-assignment conflict screen combines supplied support indicators with an overlap between the assignment and organization.
A protest-assignment conflict screen combines supplied support indicators with an overlap between the assignment and organization. It applies a fixed editorial priority.1
Screen protest-support facts for assignment conflict.
When to use Protest Support Conflict
Use this tool to screen protest-support facts for assignment conflict.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use Protest Support Conflict and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter financialSupport, organizationalRole, publicAdvocacy, assignmentOverlapsSupport using the field table and calculation rules, then run the tool.
- Read conflictIndicatorCount, conflictLevel, triggeredIndicators. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| financialSupport | Financial support provided | boolean | Required |
| organizationalRole | Organizational role held | boolean | Required |
| publicAdvocacy | Public advocacy made | boolean | Required |
| assignmentOverlapsSupport | Assignment overlaps supported cause | boolean | Required |
Enter four booleans. Return support count, active indicator keys in fixed order and recommendation. Support can be counted even when lack of assignment overlap yields none.
count=financial+organizational+public; no overlap→none; overlap with organization or ≥2→reassign; else count1→disclose Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| conflictIndicatorCount | Conflict indicator count | integer; minimum: 0 |
| conflictLevel | Conflict level | string; one of "none", "disclose", "reassign" |
| triggeredIndicators | Triggered indicators | list of string |
{
"input": {
"financialSupport": true,
"organizationalRole": false,
"publicAdvocacy": false,
"assignmentOverlapsSupport": true
},
"output": {
"conflictIndicatorCount": 1,
"conflictLevel": "disclose",
"triggeredIndicators": [
"financialSupport"
]
}
}Limitations and assumptions
No actual support, conflict policy or disciplinary decision is verified.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Beat Holdings Conflict: Find securities holdings that overlap organizations on a reporting beat. For a complementary task, use Conflict Map Disclosure: Audit conflict-map methodology and uncertainty disclosures.
References
-
Protest Support Conflict — tool.io
Similar or alternative tools
- Beat Holdings Conflict
Find securities holdings that overlap organizations on a reporting beat.
- Conflict Map Disclosure
Audit conflict-map methodology and uncertainty disclosures.