{"artifact":{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/methodology","byteLength":1143,"description":"Structured methodology notes, dataset summary, and report timing metadata.","format":"methodology","label":"Methodology artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"dfa7b4e58e7d90f29db6db4879122bbb8116349d500df0ea73ca3f249dade398","status":"live"},"document":{"category":"Partner intelligence","datasetSummary":{"trackedPartners":21,"partnerLanes":4,"sampleRows":5,"searchQueries":4,"window":"H2 2026 watchlist"},"generatedAt":"2026-03-23T00:00:00.000Z","methodology":["Anchored the report in Tempo's March 18, 2026 mainnet launch, Tempo docs, the public MPP services directory, and partner-owned wallet and payment documentation published through March 23, 2026.","Ranked names by lane density and evidence breadth rather than logo count, with direct Tempo evidence weighted above generic ecosystem adjacency.","Separated core watch names from secondary and narrative-adjacent names so design-partner demand signals do not get confused with integration depth.","Preferred operator monitoring value over launch theater: the key question is which names define wallet control, payment reach, data visibility, or enterprise workload demand."],"publishedAt":"2026-03-23T00:00:00.000Z","slug":"tempo-ecosystem-partner-map-h2-2026","title":"Tempo Ecosystem Partner Map, H2 2026","updatedAt":"2026-03-23T00:00:00.000Z"},"generatedAt":"2026-05-04T00:14:12.444Z","kind":"deep_report_methodology","operatorAccess":null,"payer":null}