Evolved

Apache-2.0 · owner-controlled · Obsidian-native

Make one AI’s work
the next AI’s
head start.

The AI tools you subscribe to are good at different things. OWD carries the work you choose to share from one compatible client to the next, with its sources and your Decisions attached. You choose every handoff, so the next agent starts further ahead.

See the setup path See how the agents work

Invitation-only acceptance testers use one isolated OWD workspace. OWD Cloud is not publicly available; Community self-hosting remains the public release path.

Your workspace isolated per owner Your vault explicit access Your Decision durable truth
project record project/
decision.md reviewed · portable · recoverable
  • 01 Obsidian
  • 02 Agent A
  • 03 Agent B
  • 04 Owner
Eve.dev profile + provider-neutral MCP Standard MCP + OAuth Plain Markdown + JSON Cited, revocable context

A complete owner-controlled foundation

Vaults first.
Then intelligence that can travel.

Shared agent context only works when the foundation is trustworthy. OWD keeps every vault bounded, every grant explicit, every edit version-aware, and every recovery point independently portable.

01 / SYNC

Write here. Pick up there.

Pair only the vaults you choose, then keep working as usual. Changes move between paired devices without making the web dashboard the owner of your files.

02 / FIND + CONNECT

Find it—and let the right agent find it.

Search the current library across paired vaults. Compatible AI agents get read-only access to one exact vault and selected folders, with the source identified on every result.

Choose vault Set folders Approve agent Revoke anytime
03 / EDIT

Fix a note from the web.

Correct a line or start a Markdown note when Obsidian is not in front of you. Clear version checks keep an old browser tab from quietly overwriting newer work.

Markdown text New notes Version checks Visible sync state
04 / RECOVER

Keep a snapshot you can restore.

Encrypted, versioned snapshots live outside the sync layer. Before anything is restored, you can inspect it, verify it, and preview exactly what will change.

Agent-first collaboration · explicit owner control

One body of work.
Many independent agents.

OWD carries a bounded packet from one independently authorized agent to another, with cited context, explicit sharing, owner-only Decisions, revocation checked on every call, recovery, and exact provenance.

  1. 01

    Project

    The durable home for a goal, its evidence, and its history.

  2. 02

    Work Packet

    A bounded assignment an owner can give to any chosen agent.

  3. 03

    Attempt + Artifact

    The agent’s contribution, sources, outputs, and open questions.

  4. 04

    Handoff + Review

    Another agent can inspect the work and add a separate judgment.

  5. 05

    Owner Decision

    The owner accepts, rejects, or asks for another attempt.

  6. 06

    Continuity

    The next packet carries the accepted Decision and exact provenance forward.

You choose the agents, roles, order, and workflow. MD Evolved does not force a planner–builder–reviewer pattern.

Source-verified Eve.dev integration

Eve runs the agent.
OWD makes the work portable.

Keep Eve’s durable sessions, subagents, sandboxes, channels, and schedules. Add OWD through Eve’s native remote MCP connection so selected work can become cited, owner-governed Project context for whichever agent works next.

EVE.DEV

Execution stays native

  • Durable sessions and agent-owned runtime state
  • Subagents, channels, sandboxes, and schedules
  • Native user-scoped Vercel Connect authorization
OWD PROFILE

Continuity travels

  • Exact vault and folder consent through standard MCP
  • Cited Projects, Handoffs, Reviews, and owner Decisions
  • Independent agent identities and portable recovery
Eve 0.28 Streamable HTTP MCP OAuth 2.1 + PKCE No custom transport

One generated agent/connections/owd.ts module connects the two. The profile is source-verified against Eve 0.28.0 and @vercel/connect 0.4.2; live client acceptance remains explicit rather than assumed.

Optional graph orchestration

Graph engineering multiplies execution.
MD Evolved makes the gains persist.

A graph runtime and MD Evolved solve different parts of the problem. They can work together, but neither is required to pretend it is the other.

Make one AI's work the next AI's head start. Three independent agents contribute cited work to an owner-controlled Project record.
Make one AI's work the next AI's head start. Each agent keeps its own tools and session. The work they leave behind can become reviewed context for whoever works next.
THE GRAPH RUNTIME

Runs the work

  • Routes tasks and model calls
  • Handles branches, loops, and parallel steps
  • Maintains live execution state
MD EVOLVED

Keeps what should survive

  • Durable context and provenance
  • Artifacts, reviews, and owner decisions
  • Portability, governance, and recovery
Harnessesexecute with their own tools and sessions
Graphsorchestrate a chosen execution pattern
Obsidiankeeps the owner’s readable source material
MD Evolvedpreserves reviewed intelligence across them

No replacement subscription. No bundled frontier model. No required graph. MCP and other interoperability layers can connect tools; MD Evolved supplies the durable project record.

Owner control is part of the architecture

Agent output is evidence—not automatic truth.

  1. 01

    The owner governs the record.

    Agents contribute. Reviews add separate judgment. Only the owner accepts decisions and promotes durable intelligence.

  2. 02

    “Learning” does not mean model training.

    The system improves future inputs by preserving reviewed context and Decisions. It does not change a provider’s model weights.

  3. 03

    Every vault and grant stays bounded.

    Pairing, access, browsing, editing, and recovery always name the vault they touch. Agent grants remain scoped and revocable.

  4. 04

    Harnesses keep their independence.

    Each agent keeps its own tools, session, and subscription. MD Evolved carries the durable work, evidence, and approval history between them.

Guided once · agent-first after that

Set up OWD once.
Then work from the agent.

The OWD workspace walks you through the vault, searchable library, agents, and first Project. After that, Project work begins in the agent you already use.

  1. 01

    Open your OWD workspace

    A managed tester opens one private invitation to one isolated workspace. The Community edition will deploy the same owner-controlled data plane to your Cloudflare account.

    Your workspace
  2. 02

    Pair an Obsidian vault

    Install OWD Sync, select the exact vault, and approve the destination. OWD publishes its current searchable library automatically.

    Your files
  3. 03

    Connect the agents you choose

    Add OWD as a standard MCP server. Authorize each agent for one exact vault and optional folders. Choose the agent that should coordinate local vault edits first; later agents are warned to remain read-only unless you transfer that advisory role.

    Your boundary
  4. 04

    Prepare the first Project once

    During setup, choose the agent, Project name, vault, and Project folder. OWD keeps that exact approved handoff ready; the human remains the vault owner and OWD's MCP vault tools remain read-only.

    Your choice
  5. 05

    Say “Connect this project to OWD”

    Stay in the working agent. OWD creates, joins, or resumes the exact Project without copied prompts, daily renewals, or another MCP authorization.

    Agent-first
  6. 06

    Keep what should survive

    Carry cited Artifacts, Reviews, owner Decisions, and approved context forward—with revocation and encrypted recovery still under owner control.

    Your record

Start with the source

Own the stack.
Inspect every boundary.

OWD Platform is the core repository. OWD Sync is its Obsidian companion. Both use Apache-2.0 licensing and preserve the owner’s ability to inspect, deploy, export, recover, and leave.

CORE REPOSITORY Private acceptance

OWD Platform

The owner-controlled web application, Cloudflare data plane, and cited handoff layer that preserves the durable project record.

  • Web application + Cloudflare Worker
  • Cited handoffs + owner Decisions
  • Snapshots + portable recovery
OWD Platform on GitHub Invited collaborators
OBSIDIAN COMPANION Public repository

OWD Sync

The Apache-2.0 Obsidian companion that pairs one selected vault with one owner-controlled OWD Platform installation.

  • Vault-explicit pairing
  • In-app pairing workflow
  • Version-matched releases
Explore OWD Sync Browse releases
Apache-2.0 Complete Community edition Isolated managed workspaces Markdown + JSON portability

Private alpha · limited access

Put a real Project
through OWD.

We are choosing a small group of people who already use Obsidian and more than one AI client. Tell us what you would test. If it is a strong fit for this alpha, we will reply with the next step.

  • One isolated OWD workspace
  • Your chosen vault and agents
  • A real cross-agent Project
Alpha request / 01

What would you put through OWD?

Sent directly to support@mdevolved.com. No account or marketing list is created.