Apache-2.0 · self-hosted · Obsidian-native

Turn the agents
you already use
into a team.

Keep Codex, Claude, Grok, Gemini, Cursor, and other agents in the tools and subscriptions you chose. OWD gives their separate sessions one durable, cited, owner-reviewed project record—so accepted work can survive and compound.

The agents keep their own tools and subscriptions. You keep the durable team record.

Your account Cloudflare deployment Your vault explicit access Your Decision durable truth
team record project/
decision.md
reviewed · portable · recoverable
  • 01 Obsidian
  • 02 Agent A
  • 03 Agent B
  • 04 Owner
Provider-neutral agents Owner-controlled Cloudflare 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 each vault once, 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, immediate revocation, 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.

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.

Your agents. One compounding intelligence. Three independent agents contribute to a shared, owner-controlled record.
Your agents. One compounding intelligence. 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 team 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 skills. 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.

The path from source to shared intelligence

Own the installation.
Control every handoff.

OWD keeps the ownership boundary visible from the first deployment through every agent contribution, owner Decision, and recovery point.

  1. 01

    Deploy your own OWD

    Start from GitHub and place the integrated web application and Worker inside your own Cloudflare account.

    Your infrastructure
  2. 02

    Pair an Obsidian vault

    Create a short-lived pairing link, choose the exact vault, and approve the destination before sync begins.

    Your files
  3. 03

    Authorize project context

    Grant one agent one named Project, vault, and optional folder scope through exact browser consent. Revoke it at any time.

    Your boundary
  4. 04

    Hand off cited work

    Independent agents exchange bounded Work Packets, Artifacts, Handoffs, and Reviews without exposing hidden conversations.

    Their contribution
  5. 05

    Keep the owner Decision

    Preserve accepted Decisions with their sources and provenance in the timeline, the next packet, Obsidian, and encrypted recovery.

    Your truth

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 Apache-2.0

OWD Platform

The self-hosted web application, Cloudflare data plane, and agent collaboration layer that preserves the durable team record.

  • Web application + Cloudflare Worker
  • Agent collaboration + owner consent
  • Snapshots + portable recovery
OBSIDIAN COMPANION Apache-2.0

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
Apache-2.0 Your Cloudflare account No shared deployment Markdown + JSON portability

MD Evolved

Separate AI subscriptions.
One compounding body of work.

Explore OWD Platform on GitHub