Integration & Ecosystem
MNFST Integration & Ecosystem
Your other tools manage actions. MNFST gives them meaning.
The Integration Philosophy
MNFST doesn’t replace your existing tools—it enhances them by connecting everything to your central purpose.
When you check off a task in Google Calendar, MNFST asks: “Which vision does this serve?”
When you complete a card in Trello, MNFST links it to: “What you actually want.”
This is the difference between managing tasks and living intentionally.
Core Integration Architecture
How MNFST Connects
┌─────────────────────────────────────────────────────────────┐
│ MNFST │
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ Visions │ │ Actions │ │ Journal │ │ Values │ │
│ └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘ │
│ │ │ │ │ │
│ └────────────┴────────────┴────────────┘ │
│ │ │
│ API Layer │
│ │ │
└─────────────────────────┼───────────────────────────────────┘
│
┌───────────────┼───────────────┐
│ │ │
▼ ▼ ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ Google │ │ Trello │ │ Notion │
│ Calendar │ │ │ │ │
└──────────┘ └──────────┘ └──────────┘
Planned Integrations
Google Calendar
| Feature | How It Works |
|---|---|
| Event → Vision | When you create an event, optionally link it to an MNFST vision |
| Task completion | Completing a Google Task updates the associated MNFST action |
| Vision context | See which vision each calendar event serves |
| Reflection triggers | Schedule reflection prompts as calendar events |
Use case: You schedule a meeting. MNFST asks, “Which vision does this meeting serve?” Now you know why you’re going to that meeting.
Trello
| Feature | How It Works |
|---|---|
| Board → Vision | Map a Trello board to an MNFST vision |
| Card → Action | Trello cards sync as MNFST actions |
| Completion sync | Moving a card to “Done” marks the MNFST action complete |
| Vision metadata | See vision context on Trello cards |
Use case: Your project board in Trello becomes linked to a vision. Every card you complete is a step toward what you actually want—not just project completion.
Notion
| Feature | How It Works |
|---|---|
| Database → Visions | Sync a Notion database with MNFST visions |
| Page → Journal | Notion pages can become MNFST journal entries |
| Task sync | Notion tasks sync bi-directionally with MNFST actions |
| Templates | MNFST-informed Notion templates for vision planning |
Use case: Your Notion workspace becomes vision-aware. Every database, every page, every task connects to your central purpose.
API Capabilities
MNFST exposes core endpoints for external integration:
Core Objects (API-ready)
| Object | Can Export | Can Import | Description |
|---|---|---|---|
| Visions | ✅ | ✅ | Your desired realities |
| Actions | ✅ | ✅ | Tasks linked to visions |
| Journal Entries | ✅ | ✅ | Free-form entries |
| Reflections | ✅ | ❌ | 1-10 ratings (read-only export) |
Internal Objects (MNFST-only)
| Object | Why No Export |
|---|---|
| Beliefs | Deeply personal; no external equivalent |
| Values | Integral to MNFST schema |
| Limitations | Require MNFST’s fear categorization |
| Connections | Inter-vision relationships |
The “Return to MNFST” Principle
No matter which tool you use, you’ll always come back to MNFST because:
- Clarity lives here — Your visions are stored and refined in MNFST
- The questions are here — 60 questions strengthen your neural pathways
- The “why” is here — Other tools manage what; MNFST holds why
- Resilience builds here — Neural pathway strengthening happens through MNFST’s process
External tools become tributaries flowing into MNFST’s central river.
Schema for Consciousness
MNFST is a schema for the architecture of objects in consciousness:
┌─────────────────────────────────────────────────────┐
│ CONSCIOUSNESS │
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ Beliefs │────▶│ Values │────▶│ Visions │ │
│ └─────────┘ └─────────┘ └────┬────┘ │
│ │ │
│ ▼ │
│ ┌──────────┐ │
│ │ Actions │ │
│ └──────────┘ │
│ │
│ Other apps manage Actions │
│ MNFST connects Actions to everything above │
└─────────────────────────────────────────────────────┘
Most apps only see Actions. MNFST sees the entire architecture.
Integration Benefits
For Users
| Benefit | Description |
|---|---|
| Unified purpose | All your tools serve your central vision |
| Context everywhere | See “why” in every calendar event, every card, every task |
| Reduced friction | Use tools you already know; MNFST adds meaning |
| No tool switching for clarity | Your vision is always accessible |
For Developers
| Benefit | Description |
|---|---|
| Clean API | RESTful endpoints for core objects |
| Webhook support | React to MNFST events in your systems |
| OAuth integration | Standard authentication flow |
| Documentation | Full API docs for integration builders |
The Ecosystem Vision
Phase 1: Core Integrations
- Google Calendar
- Trello
- Notion
Phase 2: Expanded Integrations
- Todoist
- Asana
- Microsoft Outlook
- Apple Reminders
Phase 3: Developer Platform
- Public API
- Webhook subscriptions
- Custom integration builder
- Third-party app marketplace
Why This Matters
Every tool you use asks: “What are you doing?”
Only MNFST asks: “Why are you doing it?”
When your calendar, your project board, and your notes all connect to MNFST, you’re not just managing tasks—you’re living your vision.
Your tools work for you. MNFST makes sure they work for what you actually want.