Conflict Map Disclosure

Audit conflict-map methodology and uncertainty disclosures.

Description

Conflict disclosures can be tracked against required categories.

Conflict disclosures can be tracked against required categories. Coverage is a normalized comparison of the supplied category labels.^[1]

Audit conflict-map methodology and uncertainty disclosures.

When to use Conflict Map Disclosure

Use this tool to audit conflict-map methodology and uncertainty disclosures.

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 Conflict Map Disclosure 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 requiredDisclosures, publishedDisclosures using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. 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
requiredDisclosures	Required map disclosures	list of string	Required
publishedDisclosures	Published disclosures	list of string	Required

Supply required and observed disclosure labels. Enter a nonempty required list and an observed list, which may be empty. Trim and lowercase entries for comparison; blank entries are errors. Deduplicate by normalized key. Return matched/missing required labels, unexpected observed labels, and coverage. Required order is preserved; the last trimmed spelling wins for duplicate keys.

coverage%=100×matchedUnique/requiredUnique

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "requiredDisclosures": [
      "alpha",
      "beta",
      "gamma"
    ],
    "publishedDisclosures": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No conflict is discovered and no disclosure content, completeness or ethical sufficiency is evaluated.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Protest Support Conflict: Screen protest-support facts for assignment conflict. For a complementary task, use Donation Disclosure Check: Compare caller-supplied expected and observed records for donation disclosure check.

References

Conflict Map Disclosure — tool.io

Similar or alternative tools

Protest Support Conflict
Screen protest-support facts for assignment conflict.
Donation Disclosure Check
Compare caller-supplied expected and observed records for donation disclosure check.