Modus Ponens Inference Step Validator (P→Q, P ⊢ Q)

Validate a modus ponens step using identifier operands for its conditional, affirmed premise, and claimed conclusion.

Description

Modus ponens infers a conditional’s consequent when its antecedent is affirmed.

Modus ponens infers a conditional’s consequent when its antecedent is affirmed. Matching atom identifiers establishes this elementary inference pattern.1

The tool returns matchesRule. Interpret the result under the rule and assumptions below; an encoded premise’s truth is not independently established.

When to use Modus Ponens Inference Step Validator (P→Q, P ⊢ Q)

Use this for the following task: Validate a modus ponens step using identifier operands for its conditional, affirmed premise, and claimed conclusion. Prepare the specified logical encoding before running the check or transformation.

How to use Modus Ponens Inference Step Validator (P→Q, P ⊢ Q) and understand its results

  1. Prepare the requested Boolean values, complete truth-table rows, or identifier atoms. An atom is a name such as p or premise_1, not a natural-language sentence.
  2. Enter antecedent, consequent, affirmed, conclusion according to the field table, then run the tool.
  3. Read matchesRule. Use the matching rule, assignment order or nonempty-class assumptions below to interpret the result.
  4. For a false check, inspect the supplied encoding and matching rule. A well-formed false result is different from an input error.
Input fieldMeaningValue type and boundsRequirement
antecedentAntecedentstring; maximum text length 100; pattern ^(?!(?:true|false)$)[A-Za-z_][A-Za-z0-9_]*$(?![\s\S])Required
consequentConsequentstring; maximum text length 100; pattern ^(?!(?:true|false)$)[A-Za-z_][A-Za-z0-9_]*$(?![\s\S])Required
affirmedAffirmedstring; maximum text length 100; pattern ^(?!(?:true|false)$)[A-Za-z_][A-Za-z0-9_]*$(?![\s\S])Required
conclusionConclusionstring; maximum text length 100; pattern ^(?!(?:true|false)$)[A-Za-z_][A-Za-z0-9_]*$(?![\s\S])Required

Enter the conditional’s two identifiers, the affirmed premise and claimed conclusion. Return true when affirmed equals antecedent and conclusion equals consequent.

P→Q, P ⊢ Q

The symbols and boundary conditions refer to the supplied fields and the implementation described above.

Output fieldMeaningValue type
matchesRuleMatches Ruleboolean
json
{
  "input": {
    "antecedent": "p",
    "consequent": "q",
    "affirmed": "p",
    "conclusion": "q"
  },
  "output": {
    "matchesRule": true
  }
}

Limitations and assumptions

Operands are case-sensitive identifier atoms, not complete expressions. The tool does not parse a proof or determine whether the premises are true.

The supplied encodings must represent the intended propositions or classes. No natural-language parsing or assessment of empirical premise truth is performed. Malformed input gives a tool error rather than a logical false result.

Alternative or Complementary methods

Choose Modus Tollens Inference Step Validator (P→Q, ¬Q ⊢ ¬P) when you need its operation: Validate a modus tollens step by matching the identifiers negated in its premise and conclusion. Choose Affirming the Consequent Fallacy Flag Detector for the complementary operation: Detect the affirming-the-consequent pattern with distinct identifier atoms.

Background reference: Additional rules for TFL.

References

  1. Additional rules for TFL — forallx Calgary, Open Logic Project

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies