TOS Limitation Liability Arbitration Presence Checker

Caller independently verified scope/version applicable liability/arbitration terms evidence, clause presence not enforceability. Independently declared positive requirements, overlapping/unknown classes retained. Caller independently verifies policy, evidence, dates and applicability; not legal/compliance advice or causal business-success prediction.

Description

Contract clauses can be separately annotated for a review rubric.

Contract clauses can be separately annotated for a review rubric.^[1]

Presence indicators do not determine the enforceability of arbitration or liability terms in a particular jurisdiction. Use this tool to compare independently annotated features with the stated candidate rules.

When to use TOS Limitation Liability Arbitration Presence Checker

Use this tool to compare independently annotated features with the stated candidate rules. Establish the business period, event definitions, jurisdiction or agreement edition, and independently documented evidence or comparison rubric.

How to use TOS Limitation Liability Arbitration Presence Checker and understand its results

Establish the business period, event definitions, jurisdiction or agreement edition, and independently documented evidence or comparison rubric.
Enter callerTosClausesClassIds, callerTosClausesRequirements, observedTosClausesEvidence, knownTosClausesFlags, using the field meanings and rules below, then run the tool.
Read compatibleCallerClasses, fullyWitnessedCallerClasses. Interpret the fields using their units, signs and evidence conventions below.
If input validation fails, correct the reported field and run again. Before applying the result, check reference scope, model assumptions and any missing evidence or placeholder values.

Input field	Meaning	Value type	Requirement
callerTosClausesClassIds	Caller tos clauses class ids	list of string	Required
callerTosClausesRequirements	Caller tos clauses requirements	list of list of number	Required
observedTosClausesEvidence	Observed tos clauses evidence	list of number	Required
knownTosClausesFlags	Known tos clauses flags; binary 1=known, 0=unknown, in the order described below	list of number	Required

Supply nonempty unique class IDs and a rectangular binary requirement matrix with one row per class and one column per observed feature. Every class must require at least one positive feature. Supply aligned binary observation and known-flag lists. A requirement 0 ignores its column; a requirement 1 permits a class only if the feature is unknown or observed present. Fully witnessed classes require every required feature to be known present. Return all compatible and fully witnessed caller classes in caller order; unknown evidence can leave several candidates, and known absent required evidence excludes a class. The rubric is supplied rather than installed.

compatible={class:each required column is unknown or present}; witnessed={class:each required column is known present}

Use the exact units, boundary rules, ordering and missing-evidence conventions above.

Output field	Meaning	Value type
compatibleCallerClasses	Every supplied class whose required features are unknown or known present	list of string
fullyWitnessedCallerClasses	Every supplied class with all required features known present	list of string

json

{
  "input": {
    "callerTosClausesClassIds": [
      "a",
      "b"
    ],
    "callerTosClausesRequirements": [
      [
        1,
        0
      ],
      [
        0,
        1
      ]
    ],
    "observedTosClausesEvidence": [
      1,
      0
    ],
    "knownTosClausesFlags": [
      1,
      0
    ]
  },
  "output": {
    "compatibleCallerClasses": [
      "a",
      "b"
    ],
    "fullyWitnessedCallerClasses": [
      "a"
    ]
  }
}

Limitations and assumptions

Features and criteria are independent annotations. Compatible candidates and retained unknown evidence do not establish an identity, interpretation, overall pass or permission.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse evidence arrays fail validation; the specific bounds and alignment requirements are stated above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful result reporting false, no matches or missing evidence.

Alternative or Complementary methods

Use IP Assignment Agreement Signed Checker for this related task: IP assignment coverage depends on which independently required contributors are covered by signed arrangements.

Use GDPR Privacy Cookie Banner Mvp Minimum Checker when its separate inputs and assumptions fit the question: Privacy and cookie obligations depend on data practices, jurisdiction and applicable rules.

References

TOS Limitation Liability Arbitration Presence Checker — tool.io

Similar or alternative tools

IP Assignment Agreement Signed Checker
IP assignment coverage depends on which independently required contributors are covered by signed arrangements.
GDPR Privacy Cookie Banner Mvp Minimum Checker
Privacy and cookie obligations depend on data practices, jurisdiction and applicable rules.