ConfidentialHJMT Solutions Patent Position Review

Section 06.1

Turo — Patent-Position Technical Mapping

Publicly observed Turo functionality assessed against MarketMind technical elements. Public observation, HJMT analysis, HJMT inference and evidence gaps are recorded separately.

06.1

Turo — Company Profile

Company

Turo

Vertical

Peer-to-peer vehicle sharing / temporary vehicle access

Evidence Basis

Publicly available first-party material

A transaction environment involving a host vehicle, guest access, a defined trip period, identity and licence verification, vehicle-condition evidence, protection options, return requirements and post-trip financial or damage issues.

VehicleGuest / HostBookingVerificationCondition EvidenceProtectionReturn / Exception Handling

06.1.1

Verification & Activation

Public observation

Turo's current host guidance requires hosts to confirm a guest's driving licence as part of check-in. Where remote check-in is used, licence photographs are used for confirmation.

Turo states that licence confirmation must be completed before the trip starts, and hosts are instructed not to provide vehicle access to an unconfirmed guest. The process also includes pre-trip vehicle-condition documentation.

HJMT technical analysis

The observed workflow provides relevant public evidence that transaction access is conditioned on completion of a verification stage rather than on booking confirmation alone.

Relevant MarketMind technical elements

01 — Event-Driven Transaction Activation02 — Multi-Variable Transaction Intake19 — Verification-Driven Control22 — State-Based Transaction Control

Assessment

01Event-Driven Transaction ActivationRelevant Correspondence

19Verification-Driven ControlStrong Correspondence

22State-Based Transaction ControlRelevant Correspondence

Evidence confidence — High

High — first-party host guidance describing the check-in requirement.

Analysis is based on observable transaction workflow. Undisclosed backend rule architecture has not been inferred.

06.1.2

Asset Condition Evidence

Public observation

Turo requires or strongly relies upon pre-trip and post-trip vehicle photographs for documenting vehicle condition.

Damage mattersIncidental chargesLate-return issuesPayment disputesVehicle safetyCondition assessment

HJMT technical analysis

Photo evidence may include metadata relating to date, time and geolocation, which places verified asset-condition data in a relationship with timing and location information.

HJMT technical inference

Verified condition evidence appears to operate as an input to post-trip financial and dispute processes. The currently identified public sources do not establish the entire MarketMind conditional-settlement architecture.

Relevant MarketMind technical elements

05 — Asset-Driven Transaction Control12 — Time as a Risk Variable16 — Location-Based Control19 — Verification-Driven Control20 — Conditional Settlement

Assessment

05Asset-Driven Transaction ControlRelevant Correspondence

19Verification-Driven ControlStrong Correspondence

20Conditional SettlementPartial Correspondence

Public evidence demonstrates that verified condition evidence influences post-trip financial and dispute processes, but currently identified public sources do not establish the entire MarketMind conditional-settlement architecture.

Evidence confidence — High

High for condition verification.
Medium for broader settlement correspondence.

06.1.3

Time / Late Return

Public observation

Turo requires guests who need additional time to request a trip extension through the platform.

Host acceptanceVehicle availabilityAvailable payment funding

HJMT technical analysis

Where a vehicle remains beyond the authorised trip period without an approved extension, additional usage charges and late-return fees can apply. Time therefore operates as a transaction variable with financial consequence rather than as a scheduling label.

Relevant MarketMind technical elements

12 — Time as a Risk Variable14 — Event-Based Trigger Engine15 — Exception Management21 — Programmable Transaction Framework22 — State-Based Transaction Control

Scheduled End Time

Extension / Availability / Payment Conditions

Approved Extension or Unauthorised Additional Usage

Different Financial / Transaction Outcome

Assessment

12Time as a Risk VariableStrong Correspondence

14Event-Based Trigger EngineRelevant Correspondence

15Exception ManagementStrong Correspondence

21Programmable Transaction FrameworkPartial Correspondence

Evidence confidence — High

High — first-party additional-usage policy material for guests and hosts.

06.1.4

Protection / Risk Conditioning

Public observation

Turo states that the protection-plan options available to a guest may in some circumstances vary based upon factors such as age, trip details, vehicle type and other factors. Protection can also be subject to trip timing and vehicle-value conditions.

HJMT technical analysis

The publicly identified information demonstrates differential protection availability based upon transaction variables. It does not, by itself, disclose the complete internal risk model used to determine availability.

Relevant MarketMind technical elements

05 — Asset-Driven Transaction Control06 — Dynamic Risk Modelling08 — Dynamic Transaction Conditioning18 — Insurance Integration

Assessment

05Asset-Driven Transaction ControlRelevant Correspondence

08Dynamic Transaction ConditioningPartial Correspondence

18Insurance IntegrationStrong Correspondence

06Dynamic Risk ModellingAdjacent Capability

Adjacent capability trending toward partial correspondence; differential availability is observable, the determining risk model is not.

Evidence confidence — Medium

Medium — availability variation is described; the underlying model is not.

Backend implementation not public.

06.1.5

Turo — Summary

Current high-value observations

Verification before accessPre/post transaction asset evidenceTime-dependent transaction statesTrip-extension conditionsLate-return exception handlingFinancial consequences following timing deviationProtection linked to transaction / participant / vehicle factors

Strongest MarketMind reference areas

Verification-Driven ControlTime as a Risk VariableException ManagementAsset-Driven Transaction ControlEvent / State-Based Transaction HandlingProtection Integration

No overall Technical Correspondence Index is generated for this company.

06.1.6

Turo — Evidence Gaps

Detailed internal risk model not publicFull financial orchestration architecture not establishedBehaviour-to-financial coupling requires further evidenceAPI / backend architecture requires further evidence

Gap classification recorded for this review: Backend Implementation Not Public. Missing evidence has not been filled with assumptions.

06.1.7

Turo — Potential MarketMind Enhancement

If MarketMind were integrated around the observed platform environment, what additional control capability could the architecture potentially provide?

Broader multi-variable risk assessment could potentially extend the variables already captured at check-in.
Cross-transaction behavioural intelligence could potentially extend participant history beyond a single trip.
Dynamic financial security could potentially condition the security held against assessed transaction risk.
Predictive late-return risk could potentially condition trip terms before the scheduled end time.
Predictive damage risk could potentially draw on verified condition evidence across trips.
Adaptive settlement conditions could potentially apply settlement rules derived from verified transaction outcome.
Context-aware protection could potentially condition protection on timing, location and asset context.

These are potential extensions of the architecture. They are not statements that the platform lacks the capability.

06.1.8