---
mdfy_bundle: 1
id: 8IkpnVgX
title: "Engineering decisions + cross-AI strategy"
url: https://mdfy.app/b/8IkpnVgX
document_count: 3
updated: 2026-05-14T19:20:02.321Z
analysis_generated_at: 2026-05-14T19:20:02.321Z
source: "mdfy.app"
---
# Engineering decisions + cross-AI strategy

> A working bundle: the ADR for shipping graph_data in URLs, the cross-AI moat argument, and a hands-on integration note for Cursor. Three docs that explain *what we're building and why* in 10 minutes of reading.

**Intent:** Frame the platform decisions a reviewer would want to verify in 10 minutes.

## Summary

These documents establish mdfy's platform strategy centered on cross-AI portability through bundle URLs that embed rich analysis data. The technical decision to ship graph_data inside URLs enables a viral loop where recipients get more value than senders could provide elsewhere, creating a structural competitive moat based on vendor neutrality that individual AI companies cannot replicate.

## Themes

- cross-platform portability
- competitive differentiation
- technical architecture
- integration workflows

## Cross-document insights

- The decision to embed graph_data in URLs transforms a simple sharing mechanism into a competitive moat - no single AI vendor can replicate cross-competitor portability without undermining their own platform strategy.
- The viral loop mechanism depends on URLs providing more value to recipients than senders could deliver through native platform features, making the technical implementation decision strategically critical.
- Platform integration patterns reveal that mdfy succeeds by fitting into existing workflows rather than requiring users to adopt new tools, with different surfaces (Cursor, ChatGPT, Claude) needing different integration approaches.
- The tension between token cost optimization and strategic value delivery suggests that technical trade-offs must be evaluated through the lens of competitive positioning, not just operational efficiency.

## Key takeaways

- Cross-AI portability through bundle URLs creates a structural competitive advantage that individual AI vendors cannot replicate without harming their own competitive positions.
- The technical decision to embed graph_data in URLs is strategically critical - it transforms simple document sharing into a viral growth mechanism that provides more value to recipients than native platform alternatives.
- Success depends on seamless integration into existing AI workflows rather than requiring users to adopt new tools, with each platform needing tailored integration patterns while maintaining consistent URL behavior.

## Open questions / gaps

- Performance metrics and user adoption data to validate the theoretical competitive advantages described in the strategy document.
- Technical specifications for the graph_data format and versioning strategy to ensure long-term URL stability.
- Detailed analysis of potential competitive responses from major AI vendors and defensive strategies.
- User experience research on how different integration patterns affect adoption and retention across platforms.

## Notable connections

- **doc:rBRZ_nni** ↔ **doc:kxn9T-Vv** — The strategic moat theory depends entirely on the technical implementation of graph_data embedding - without rich URL payloads, there's no viral loop advantage.
- **doc:kxn9T-Vv** ↔ **doc:TEuiwop8** — The bundle URL decision enables practical integrations like Cursor - the technical choice directly impacts real-world usability patterns.
- **doc:rBRZ_nni** ↔ **doc:TEuiwop8** — Cross-AI portability strategy manifests in practice through integrations like Cursor that demonstrate consistent URL behavior across different AI platforms.

## Concepts (this bundle)

- **Cross-AI Portability**
- **Viral Loop**
- **Structural Moat**
- **URL Contract**
- **Analysis Staleness**
- **Privacy Gating**
- **AI Memory**
- **Vendor Neutrality**

## Concept relations

- **Cross-AI Portability** ↔ **Structural Moat** — creates
- **Structural Moat** ↔ **Vendor Neutrality** — requires
- **Viral Loop** ↔ **Cross-AI Portability** — depends on
- **URL Contract** ↔ **Cross-AI Portability** — enables

1. [The structural moat: cross-AI portability](https://mdfy.app/rBRZ_nni) — Why cross-AI portability is the moat. Read first.

2. [Decision: ship graph_data inside the bundle URL](https://mdfy.app/kxn9T-Vv) — The ADR that operationalises the strategy.

3. [Wiring mdfy into Cursor](https://mdfy.app/TEuiwop8) — Concrete tool wiring — the URL shape this ADR produces flowing into Cursor.


_Digest view — follow any link above to fetch that doc's full markdown. Add `?full=1` to this URL for the concatenated payload._