---
mdfy_bundle: 1
id: Ih0eUczw
title: "Phase 2 strategy: connectors, replacements, first-principles"
url: https://mdfy.app/b/Ih0eUczw
document_count: 3
updated: 2026-05-15T17:43:33.084Z
analysis_generated_at: 2026-05-15T17:43:33.084Z
analysis_stale: true
source: "mdfy.app"
---
# Phase 2 strategy: connectors, replacements, first-principles

> Three working notes from a strategy review session on 2026-05-15. Native AI integrations roadmap, what current surfaces to replace, first-principles drift check.

**Intent:** Capture three companion strategy thoughts so they live as one shareable URL.

> ⚠ _Analysis may be stale — one or more member docs were edited after the last analysis run. Re-run the canvas to refresh._

## Summary

These three strategic documents form a comprehensive analysis of mdfy's transition from URL-based sharing to native AI platform integrations. The collection evaluates foundational principle alignment, maps improvement opportunities through native skills, and provides a framework for replacing existing product surfaces with more effective alternatives.

## Themes

- strategic alignment assessment
- native AI platform integration
- product surface evolution
- cross-platform user experience

## Cross-document insights

- The cross-AI structural moat is actually at risk from native skills if framed incorrectly - positioning as 'support every AI' dilutes the core value proposition of 'one URL works in 3 AIs'
- Current high-maintenance surfaces like the Electron desktop app and Chrome extension's AI capture mode are strategic dead ends that should be replaced rather than enhanced
- The zero friction principle is weakening specifically around 'friction to use well' despite maintaining 'friction to try', indicating a concerning strategic drift
- Bundle scope deserves equal marketing billing with Hub scope since AGENTS.md fit demonstrates bundle-level value that current messaging underemphasizes

## Key takeaways

- Strategic drift is occurring specifically around the authored-not-extracted principle and zero friction to use well, requiring immediate course correction
- Native AI skills offer bidirectional read-write capabilities and cross-platform reach that current URL-paste approach cannot match
- High-maintenance current surfaces should be strategically replaced rather than incrementally improved, with Electron desktop app and Chrome extension AI capture as primary candidates

## Open questions / gaps

- Competitive analysis missing - no evaluation of how native skills positioning affects competitive differentiation beyond internal principle alignment
- User adoption metrics and transition planning absent - unclear how users would migrate from current surfaces to native alternatives
- Resource allocation and timeline considerations not addressed for implementing the native skills roadmap

## Notable connections

- **doc:dEgO6Qml** ↔ **doc:LpLbS250** — Principles assessment identifies zero friction weakening that native skills directly address through improved user experience
- **doc:LpLbS250** ↔ **doc:NpXe_CnP** — Native skills capabilities inform which current surfaces become obsolete and should be replaced rather than maintained
- **doc:dEgO6Qml** ↔ **doc:NpXe_CnP** — Strategic principle of zero friction supports aggressive surface replacement decisions to reduce maintenance overhead

## Concepts (this bundle)

- **LLM-native design**
- **Cross-AI strategy**
- **Authored not extracted**
- **Zero friction**
- **Graph in response**
- **Native AI skills**
- **Surface replacement**

## Concept relations

- **Native AI skills** ↔ **Zero friction** — friction reduction
- **Cross-AI strategy** ↔ **Native AI skills** — strategic tension
- **Surface replacement** ↔ **Native AI skills** — better alternatives

1. [Native skills + connectors: what improvements are possible](https://mdfy.app/LpLbS250)

2. [Native skills vs current surfaces — what should we replace](https://mdfy.app/NpXe_CnP)

3. [First-principles check: are we drifting?](https://mdfy.app/dEgO6Qml)


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