Windmill Headspin Power Move Prereq Checker

Caller independently documented qualified-supervision/progression/medical review prerequisites for power-move review; not physical clearance or execution instructions for heads pins. Independently declared positive evidence requirements; overlaps and unknowns retained. Caller independently establishes score/style/protocol/reference applicability; not physical readiness, safe training or injury risk diagnosis.

Description

Power-move prerequisites depend on independently established training evidence and a review rubric.

Power-move prerequisites depend on independently established training evidence and a review rubric.1

Compatible classes with unknown evidence do not establish readiness or permission to attempt a move. Use Windmill Headspin Power Move Prereq Checker to evaluate the supplied inputs under the specific model below.

When to use Windmill Headspin Power Move Prereq Checker

Use Windmill Headspin Power Move Prereq Checker to evaluate the supplied inputs under the specific model below. Define the classes and required evidence columns, then distinguish observed presence from whether each observation is known.

How to use Windmill Headspin Power Move Prereq Checker and understand its results

  1. Define the classes and required evidence columns, then distinguish observed presence from whether each observation is known.
  2. Enter Caller power move review class ids, Caller power move review requirements, Observed power move review evidence, Known power move review flags using the field table and validation rules below, then run the tool.
  3. Read Compatible caller classes, Fully witnessed caller classes and interpret units, signs, ordering and placeholders as explained below.
  4. If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
Input fieldMeaningValue typeRequirement
callerPowerMoveReviewClassIdsCaller power move review class idsarray of stringRequired; constraints below
callerPowerMoveReviewRequirementsCaller power move review requirementsarray of arrayRequired; constraints below
observedPowerMoveReviewEvidenceObserved power move review evidencearray of numberRequired; constraints below
knownPowerMoveReviewFlagsKnown power move review flagsarray of numberRequired; constraints below

Supply unique nonblank class IDs, one rectangular binary requirement row per class, and aligned binary observation and known-flag arrays. Each class must require at least one positive witness. Requirement 0 ignores an evidence column; requirement 1 needs a known positive observation for full witnessing. An unknown requirement remains compatible, while a known absent requirement excludes the class. Both returned class lists preserve caller order. No readiness rubric is installed and compatible does not mean fully witnessed or approved.

compatible = no required known absence; fully witnessed = every required witness known and positive

Field order, units and branch conditions follow the implementation explanation above.

Output fieldMeaningValue type
compatibleCallerClassesCaller classes with no known absence of required evidence; unknown witnesses may remain.array of string
fullyWitnessedCallerClassesCaller classes for which every required witness is both known and positive.array of string
json
{
  "input": {
    "callerPowerMoveReviewClassIds": [
      "a",
      "b"
    ],
    "callerPowerMoveReviewRequirements": [
      [
        1,
        0
      ],
      [
        0,
        1
      ]
    ],
    "observedPowerMoveReviewEvidence": [
      1,
      0
    ],
    "knownPowerMoveReviewFlags": [
      1,
      0
    ]
  },
  "output": {
    "compatibleCallerClasses": [
      "a",
      "b"
    ],
    "fullyWitnessedCallerClasses": [
      "a"
    ]
  }
}

Limitations and assumptions

Compatible classes with unknown evidence do not establish readiness or permission to attempt a move. Apply the exact scope and assumptions described above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.

Alternative or Complementary methods

Use Pointe Readiness Age Ankle Test Checklist for a related task: Pointe assessment requires independently observed evidence and a qualified review context.

Use Pointe Shank Vamp Height Strength Lookup for a related task: Pointe-shoe shank and vamp properties interact with fit and technique.

References

  1. Windmill Headspin Power Move Prereq Checker — tool.io

Similar or alternative tools

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