Skip to content

Main content

Argument Assumption Scope Depth Tool

Audit explicit opening/closing assumption-scope actions without evaluating argument validity.

Loading tool…

Description

Audit explicit opening/closing assumption-scope actions without evaluating argument validity.

A logical calculation operates on a stated representation: truth values, token lists, counts, or an explicitly supplied relation. Checking one assignment, pair, trace, or witness is different from proving a formula or validating an entire argument. Empty domains, duplicate tokens, and scope conventions can change the result.

Audit explicit opening/closing assumption-scope actions without evaluating argument validity.

When to use this tool

Use Argument Assumption Scope Depth when you need this exact local truth, count, token, relation, or witness check within a larger logic workflow.

How to use the tool and how it works

  1. Enter actions, initialDepth. 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 finalDepth, peakDepth. Use the output convention below.

For nonnegative integer initialDepth accept actions open and close. Increase or decrease depth in order, rejecting any negative intermediate depth; return finalDepth and peakDepth including the initial depth.1

Input fieldMeaning and unitsAccepted input
actionsActionsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
initialDepthInitial DepthRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
finalDepthFinal DepthRequired. Safe integer.
peakDepthPeak DepthRequired. Safe integer.
json
{
  "input": {
    "actions": [
      "open",
      "open",
      "close"
    ],
    "initialDepth": 0
  },
  "output": {
    "finalDepth": 1,
    "peakDepth": 2
  }
}

Limitations and assumptions

  • Unclosed scopes may leave positive finalDepth. This checks a supplied nesting action sequence without identifying assumptions, validating proof rules, or parsing a derivation.
  • 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.

Alternative or Complementary methods

Use a parser, scope-aware representation, model checker, or proof procedure when the supplied token or witness representation is insufficient. A local passing check should not be promoted to global validity.

References

  1. Calculation and input contract: philosophy/argument-assumption-scope-depth — tool.io

Similar or alternative tools