Rideshare Period 1 2 3 Gap Checker
Map independently observed rideshare operational period before separately reviewing actual personal/platform policies; operational label alone is not a gap or coverage verdict. Independently established columns: app online waiting period independently established, accepted ride en-route period independently established, passenger transport period independently established. Unknown observations and overlapping candidates retained; not automatic semantic parsing, proof of identity, fraud, authenticity, compliance or coverage.
Description
Rideshare periods distinguish app waiting, accepted-trip travel and passenger transport under a stated evidence scheme.
Rideshare periods distinguish app waiting, accepted-trip travel and passenger transport under a stated evidence scheme.1
A period label does not determine coverage under a particular policy. The tool compares supplied binary annotations with a fixed candidate scheme and distinguishes compatible from fully witnessed candidates.
When to use Rideshare Period 1 2 3 Gap Checker
Use this tool to calculate or review the supplied observations under the stated rules. Establish the contract, jurisdiction, reporting basis, currency and dated evidence that apply.
How to use Rideshare Period 1 2 3 Gap Checker and understand its results
- Establish the contract, jurisdiction, reporting basis, currency and dated evidence that apply.
- Enter observedFeatureFlags, featureKnownFlags, using the field meanings and rules below, then run the tool.
- Read result.compatibleClasses, result.witnessedClasses, result.unknownFeatureIndices, using the output meanings and calculation rules below. Review unknown feature positions and distinguish compatible from witnessed candidates.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| observedFeatureFlags | Observed feature flags | list of number | Required |
| featureKnownFlags | Feature known flags; binary 1 means the matched observation is known, 0 means unknown | list of number | Required |
Supply exactly three aligned binary observed and known flags: waiting with app active, traveling after trip acceptance, and transporting a passenger. Fixed candidates require [1,0,0], [0,1,0] and [0,0,1] respectively. Known mismatches exclude a candidate; unknown constrained flags retain compatibility but prevent witnessing. All-known zero or conflicting active states match no candidate.
| Candidate | App waiting | Travel after acceptance | Passenger transport |
|---|---|---|---|
| period-1 | Known present | Known absent | Known absent |
| period-2 | Known absent | Known present | Known absent |
| period-3 | Known absent | Known absent | Known present |
candidateCompatible=all constrained known flags equal candidate; candidateWitnessed=all constrained flags known and equal Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or qualified reference | object |
| result.compatibleClasses | compatible Classes | list |
| result.witnessedClasses | witnessed Classes | list |
| result.unknownFeatureIndices | unknown Feature Indices; zero-based positions in the relevant supplied record or adjacent-pair list; unresolved records kept separate from known results | list |
{
"input": {
"observedFeatureFlags": [
1,
0,
0
],
"featureKnownFlags": [
1,
1,
1
]
},
"output": {
"result": {
"compatibleClasses": [
"period-1"
],
"witnessedClasses": [
"period-1"
],
"unknownFeatureIndices": []
}
}
}Limitations and assumptions
Period candidates depend on the documented phase and the fixed scheme. They do not establish which insurer or endorsement covers a loss.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Named Non Owner Policy Frequent Borrower Coverage Lookup: Named non-owner auto forms can cover specified liability for a named person using non-owned vehicles under exclusions. For a complementary comparison, use Broad Form Named Operator Driver Exclusions Minimum Note: Named-operator/broad-form policies can limit protection by driver rather than insure all use of an identified vehicle.
References
-
Rideshare Period 1 2 3 Gap Checker — tool.io
Similar or alternative tools
- Named Non Owner Policy Frequent Borrower Coverage Lookup
Named non-owner auto forms can cover specified liability for a named person using non-owned vehicles under exclusions.
- Broad Form Named Operator Driver Exclusions Minimum Note
Named-operator/broad-form policies can limit protection by driver rather than insure all use of an identified vehicle.