Skip to content

Main content

Modal Successor Count Budget Tool

Finite modal truth from supplied successor counts, with vacuous necessity at zero successors.

Loading tool…

Description

Finite modal truth from supplied successor counts, with vacuous necessity at zero successors.

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.

Finite modal truth from supplied successor counts, with vacuous necessity at zero successors.

When to use this tool

Use Modal Successor Count Budget 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 successors, satisfying. 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 box, diamond, counterexamples. Inspect box, diamond before interpreting the associated values.

Require nonnegative integer successors and satisfying within zero through successors. Return box=(satisfying===successors), diamond=(satisfying>0), and counterexamples=successors-satisfying.1

Input fieldMeaning and unitsAccepted input
successorsSuccessorsRequired. Safe integer; minimum 0.
satisfyingSatisfyingRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
boxBoxRequired. Boolean.
diamondDiamondRequired. Boolean.
counterexamplesCounterexamplesRequired. Safe integer.
json
{
  "input": {
    "successors": 0,
    "satisfying": 0
  },
  "output": {
    "box": true,
    "diamond": false,
    "counterexamples": 0
  }
}

Limitations and assumptions

  • The counts summarize one world's successors under one predicate. With no successors box is true and diamond false; the underlying graph and truth assignments are not verified.
  • 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/modal-successor-count-budget — tool.io

Similar or alternative tools