Cross-Platform Patent Position Matrix
A structured comparison of the MarketMind technical patent-position elements across selected temporary-access, mobility, asset-rental and equipment environments.
Purpose of the Matrix
The purpose of this matrix is not to determine whether the selected companies operate identical systems. It is to identify where recurring transaction-control functions can be observed across different market environments, and to assess those functions consistently against the MarketMind technical framework.
26 Technical Elements
10 Market Platforms
5 Market Verticals
1 Common Analytical Framework
Cross-Platform Summary Dashboard
See detailed reviews
See detailed reviews
See detailed reviews
See detailed reviews
See detailed reviews
See detailed reviews
See detailed reviews
See detailed reviews
Counters populate automatically as evidence-backed assessments are recorded in the company review sections. No figures have been estimated.
Assessment Categories and Definitions
Assessment definitions
- Strong Correspondence
- Publicly available evidence indicates functionality with substantial technical relevance to the MarketMind element being reviewed.
- Relevant Correspondence
- Public evidence identifies functionality relevant to the MarketMind technical element, although the observed implementation or scope may differ.
- Partial Correspondence
- Only part of the relevant technical relationship is observable from available public information.
- Adjacent Capability
- The platform exhibits functionality within a related technical or transaction environment, but the currently identified evidence does not establish the more specific MarketMind relationship being assessed.
- No Public Evidence Identified
- The current review has not identified sufficient public evidence supporting relevant technical functionality.
- Not Yet Assessed
- Additional evidence review is required before assessment.
The default state of every intersection at this stage is Not Yet Assessed. Absence of public evidence must not be interpreted as evidence that functionality does not exist.
Evidence Confidence
Evidence confidence is recorded independently of technical correspondence. A strong technical hypothesis supported by weak evidence must not appear equivalent to a strongly documented technical position.
- High
- Supported by direct first-party technical, developer, support, policy or product documentation.
- Medium
- Supported by credible first-party information but with limited technical implementation detail.
- Limited
- Relevant information exists but is incomplete, indirect or insufficiently detailed.
- Pending
- Additional source review is required before reliance.
Evidence Source Priority
Evidence source hierarchy
Third-party commentary should supplement rather than replace available first-party evidence.
Matrix
Rows hold the 26 MarketMind technical elements established in Section 03. Columns hold the ten selected market platforms. Each intersection is selectable and opens the structured assessment record; where evidence review has not been completed the record states Additional evidence review required.
| MarketMind Technical Element | Turo | Getaround | Uber | Airbnb | RVshare | Outdoorsy | Fat Llama | EquipmentShare | United Rentals | Sunbelt / Boels |
|---|---|---|---|---|---|---|---|---|---|---|
| 01Event-Driven Transaction ActivationT1 | ||||||||||
| 02Multi-Variable Transaction IntakeT1 | ||||||||||
| 03Behavioural IntelligenceT2 | ||||||||||
| 04Behaviour-to-Financial CouplingT1 | ||||||||||
| 05Asset-Driven Transaction ControlT2 | ||||||||||
| 06Dynamic Risk ModellingT1 | ||||||||||
| 07Transaction Reliability ScoringT3 | ||||||||||
| 08Dynamic Transaction ConditioningT1 | ||||||||||
| 09Dynamic Bond / Security DeterminationT2 | ||||||||||
| 10Financial GovernanceT1 | ||||||||||
| 11Conditional Escrow / Holding LogicT2 | ||||||||||
| 12Time as a Risk VariableT1 | ||||||||||
| 13Live Transaction MonitoringT1 | ||||||||||
| 14Event-Based Trigger EngineT1 | ||||||||||
| 15Exception ManagementT2 | ||||||||||
| 16Location-Based ControlT2 | ||||||||||
| 17Environmental & Contextual ConditioningT3 | ||||||||||
| 18Insurance IntegrationT3 | ||||||||||
| 19Verification-Driven ControlT2 | ||||||||||
| 20Conditional SettlementT1 | ||||||||||
| 21Programmable Transaction FrameworkT1 | ||||||||||
| 22State-Based Transaction ControlT2 | ||||||||||
| 23Adaptive LearningT1 | ||||||||||
| 24Future Transaction ConditioningT2 | ||||||||||
| 25API-Driven External Platform IntegrationT1 | ||||||||||
| 26Cross-Platform Control ArchitectureT3 |
Mapping Priority — Tier 1 Analytical Focus
These are analytical priorities used to sequence the review. They do not imply that the corresponding elements represent legally stronger claims.
Combined Functionality Matters
The MarketMind position should not be assessed solely by asking whether a platform performs one isolated function. Risk scoring, escrow, location monitoring, behavioural history and insurance may individually be common transaction functions. The deeper analysis concerns whether multiple functions operate together in a coordinated transaction-control architecture.
Isolated Function
A discrete capability observed on its own
- Risk scoring applied at a single point
- Escrow or hold applied uniformly
- Location data captured for reporting
- Behavioural history retained but not applied
- Insurance applied as a fixed product
Integrated Control Relationship
Functions operating as a coordinated control architecture
- Behavioural information conditions risk assessment
- Risk assessment conditions financial security
- Conditions govern activation and monitoring
- Monitored events trigger transaction response
- Outcome conditions settlement and future transactions
Behaviour
01Risk
02Condition
03Financial Control
04Monitoring
05Event Response
06Settlement
07Evidence Gap Classification
Evidence gaps allow the review to state precisely what cannot be established from public information. Missing evidence is not filled with assumptions.
Technical Reference Value
Reviewed environments are described externally by technical reference value — high-value, significant, relevant, limited public evidence, or evidence review required — taken from the substantive company analysis. No numerical company score is presented, and no legal-risk or patent-risk measure is produced anywhere in this review. Technical correspondence and evidence confidence remain separately stated throughout.
The complete technical reference value classification is recorded in Section 15 — Strategic Position.
From Platform Evidence to Infrastructure Application
Selected Platform
01Observed Functionality
02MarketMind Technical Element
03Recurring Cross-Platform Requirement
04Potential Hyperscaler Deployment
05AWS | Microsoft | Oracle
06Where a MarketMind technical element demonstrates relevance across several different transaction environments, the later hyperscaler review will assess whether that architecture could potentially be implemented as reusable enterprise or cloud infrastructure. No particular hyperscaler services are identified at this stage.
HJMT Review Methodology
HJMT review methodology — eight steps
- Step 1 — Identify the relevant MarketMind technical element.
- Step 2 — Identify publicly disclosed platform functionality.
- Step 3 — Locate supporting first-party evidence.
- Step 4 — Determine the technical relationship between the observed functionality and the MarketMind element.
- Step 5 — Assess evidence quality and limitations.
- Step 6 — Assess whether multiple technical elements appear to operate in combination.
- Step 7 — Compare recurrence across other market environments.
- Step 8 — Later assess potential hyperscaler deployment relevance.
Observation ≠ Legal Conclusion
A finding of technical correspondence means that publicly available material indicates functionality relevant to a MarketMind technical element. It does not, by itself, establish:
Next Detailed Reviews
Company review sections populate this master matrix directly. The matrix structure does not change as further evidence is recorded.
The Purpose of the Matrix
The Cross-Platform Patent Position Matrix provides a common analytical framework for testing the MarketMind architecture across multiple transaction environments. Its value will develop progressively as detailed public evidence is added for each selected company.
The objective is not simply to identify isolated functional similarities. The objective is to determine whether recurring technical relationships involving risk, behaviour, transaction conditioning, financial control, monitoring, event response, verification and settlement can be observed across different market environments. Where those relationships recur, they may provide a basis for assessing the MarketMind architecture as a broader cross-platform transaction-control layer.
Next — Section 06Mobility Mapping — Turo / Getaround / UberCross-Platform Mapping Notice
This matrix is an HJMT technical patent-position analytical framework based on publicly available information.
Technical correspondence classifications are intended to identify areas for further patent-position review and do not constitute legal findings of infringement.
The absence of identified public evidence should not be interpreted as evidence that functionality does not exist.
Formal patent claim interpretation and legal conclusions remain separate from this technical review. HJMT confidentiality and restricted intellectual property notices continue to apply.