Skip to content

Main content

Duty Rule Specificity Depth Tool

Compare explicit rule-scope paths; path specificity does not establish ethical precedence.

Loading tool…

Description

Return scopePath length and whether broaderPath is an exact prefix, then extra levels only when it applies, otherwise zero.

Consent, disclosure, duties and exceptions can be represented as records and flags. A consistency check describes those representations; it cannot independently establish valid consent, a justified exception or satisfaction of a real obligation.

Return scopePath length and whether broaderPath is an exact prefix, then extra levels only when it applies, otherwise zero.

When to use this tool

Use Duty Rule Specificity Depth when you need a literal ethical-policy record or eligibility diagnostic.

How to use the tool and how it works

  1. Enter scopePath, broaderPath. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read depth, prefixApplies, additionalLevels. Inspect prefixApplies before interpreting the associated values.

Return scopePath length and whether broaderPath is an exact prefix, then extra levels only when it applies, otherwise zero.1

Input fieldMeaning and unitsAccepted input
scopePathScope PathRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
broaderPathBroader PathRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
depthDepth on the common length basis and sign convention above.Required. Safe integer.
prefixAppliesPrefix AppliesRequired. Boolean.
additionalLevelsAdditional LevelsRequired. Safe integer.
json
{
  "input": {
    "scopePath": [
      "A",
      "B",
      "C"
    ],
    "broaderPath": [
      "A"
    ]
  },
  "output": {
    "depth": 3,
    "prefixApplies": true,
    "additionalLevels": 2
  }
}

Limitations and assumptions

  • An empty broader path is a prefix of every path. This token hierarchy is a supplied model, not a rule of legal or moral priority.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Review source evidence, applicable rules and affected people's choices through the appropriate process. Authenticate permissions and evaluate substantive reasons separately from token membership and boolean flags.

References

  1. Calculation and input contract: ethics/duty-rule-specificity-depth — tool.io

Similar or alternative tools