ConfidentialHJMT Solutions Patent Position Review
Section 15.2
Methodology
Method applied when recording publicly observable platform functionality and assessing technical correspondence with elements of the MarketMind patent position.
15.2.1
Review Method
- 01Identify the relevant MarketMind technical element.
- 02Identify publicly observable platform functionality.
- 03Locate first-party supporting evidence.
- 04Separate public fact from HJMT technical inference.
- 05Assess technical correspondence.
- 06Assess evidence quality.
- 07Identify implementation uncertainty.
- 08Assess relationships between multiple functions.
- 09Compare recurrence across market environments.
- 10Assess potential hyperscaler deployment pathway.
HJMT Analysis
Each step is applied per element, per company. Public observation and HJMT analysis are always recorded in separate fields so the reader can distinguish evidence from interpretation.
15.2.2
Source Hierarchy
Source types recognised in this review
- Official Technical Documentation
- API Documentation
- Developer Documentation
- Support Documentation
- Product Documentation
- Terms
- Policy
- Insurance / Protection Documentation
- Public Filing
- Corporate Publication
- Official Blog / Engineering Material
- Other First-Party Public Source
- Supplementary External Source
First-party sources published by the company or provider concerned are preferred in all cases. Third-party commentary is not used to establish functionality.
15.2.3
Evidence Record Fields
- Public Source
- Date / Access Date
- Observed Functionality
- Relevant MarketMind Element
- HJMT Technical Analysis
- Evidence Confidence
- Evidence Gap
- Potential MarketMind Extension
15.2.4
Assessment Categories
Strong CorrespondenceRelevant CorrespondencePartial CorrespondenceAdjacent CapabilityNo Public Evidence Identified
| Category | Definition |
|---|---|
| Strong Correspondence | Publicly documented functionality closely tracks the technical relationship described by the element. |
| Relevant Correspondence | Publicly documented functionality addresses the same technical relationship in a recognisable form. |
| Partial Correspondence | Part of the technical relationship is publicly documented; other parts are not evidenced. |
| Adjacent Capability | Related functionality exists publicly but does not itself address the element's technical relationship. |
| No Public Evidence Identified | No first-party public source describing this relationship was identified during the review. |
| Not Yet Assessed | No review of this cell has been carried out in the current review. |
Express Limitation
These categories describe technical correspondence only. None of them states, implies or supports an infringement conclusion.
15.2.5
Evidence Confidence Levels
| Level | Meaning |
|---|---|
| High | Multiple current first-party sources describe the functionality directly. |
| Medium | A first-party source describes the functionality, with some implementation detail absent. |
| Limited | Public description is brief, indirect or partial; the observation is recorded conservatively. |
| Pending | No assessment has been entered for this cell in the current review. |
Correspondence category and evidence confidence are recorded separately throughout. A strong correspondence supported by limited evidence remains a limited-evidence finding.
15.2.6
Evidence Gap Treatment
Recorded evidence-gap categories
- Backend Implementation Not Public
- Internal Risk Logic Not Public
- Relationship Between Functions Unclear
- Current Technical Source Required
- Source No Longer Public
- Partial Workflow Only
- Financial Execution Not Public
- Model / Algorithm Not Disclosed
- API Architecture Not Public
HJMT Analysis
Gaps are recorded plainly and are neither overstated nor minimised. They indicate what further material would be required for a fuller technical assessment.
15.2.7
Chronology Recording
- Where a source records a publication or last-updated date, that date is stored with the record.
- Where no date is published, the record states that no date is recorded rather than estimating one.
- Date accessed is recorded for every source so that later reviewers can compare against the current published version.
- Chronology is recorded for reference only. This review draws no priority, precedence or timing conclusion.
15.2.8
Terminology
This review uses neutral technical terminology throughout, including technical correspondence, functional correspondence, observed functionality, publicly observable capability, architectural similarity, platform correspondence, potential integration pathway and patent-position mapping. Terms such as infringement, violation, copying and misappropriation are not used and no such conclusion is expressed or implied.
15.2.9
Limitations of Assessment
- Public documentation describes user-facing behaviour and rarely describes backend implementation.
- Absence of public evidence is recorded as absence of evidence only, never as absence of functionality.
- Platform documentation changes over time; each record carries the date accessed.
- Functional similarity between systems is a technical observation and not a legal characterisation.
- No source was obtained through access to any confidential, internal or non-public system.