Three versions, one operating model.

The versions

• Version 01 · Local

  Local edition

  A downloadable, local-first Obsidian vault you run with your own coding agent and model provider. Built for one person.

  • Knowledge pipeline and reviewable memory
  • Repeatable agent skills and a Control Deck
  • Plain Markdown files you own
  Working prototypeSee the local edition

• Version 02 · Connected

  Advanced Edition

  The same Markdown vault with a runtime underneath it. Agents never hold the keys: only the action gateway holds write credentials.

  • Governed connectors to the tools you use
  • Permission-aware memory
  • Coordinated specialist agents
  Private-launch capabilitySee the Advanced Edition

• Version 03 · Builders

  IEVA Harness

  A thin runtime layer around the coding agents you already use — Claude Code and Codex — that makes each action recorded, reviewable, and gated.

  • Session logging and policy
  • Approvals and bounded delegation
  • A learning loop you can inspect
  Product directionSee the IEVA Harness

Who this is for

Founders

Carry the whole company's context while switching between product, fundraising, hiring, and customers — without dropping commitments in the gaps.

Executives

Enter every meeting prepared, keep decisions from being silently re-litigated, and see risk building before it lands on the agenda.

Chiefs of staff

Turn executive intent into a reliable cadence: briefings assembled, follow-ups tracked, decision records accurate — and everything reviewable.

Senior operators

Run multiple workstreams with delegated legwork that comes back checkable, not just plausible.

Product & innovation leaders

Keep continuous market and research intelligence flowing into decisions, with sources attached.

The patterns

• Example operating pattern

  Executive morning briefing

  Start the day with what changed, what is due, and what stalled — assembled from authorized sources overnight, every item citing where it came from.

  In practice: 06:00 — briefing assembles: two overnight signals from the deal thread, a decision due before Thursday's board prep, one commitment aging past its date.

  Concept workflow

• Example operating pattern

  Meeting preparation and follow-up

  Walk into meetings with relationship context, open items, and relevant decisions in hand; walk out with commitments captured and follow-ups tracked to completion.

  In practice: Before the partner call: last meeting's open questions, the pricing decision and its rationale, and the two emails that changed the picture since.

  Concept workflow

• Example operating pattern

  Decision continuity

  Decisions keep their rationale, owner, and source. When a settled question resurfaces, IEVA surfaces the decision record beside it — revise deliberately or move on.

  In practice: A thread proposes reopening the launch date. The decision register shows the delay decision, its three reasons, and who owns it.

  Concept workflow

• Example operating pattern

  Portfolio and project review

  Recurring reviews of project state, next actions, and drift — the prototype's project hubs and shipping records, generalized to a portfolio.

  In practice: Friday review: nine workstreams, two without a next action, one whose owner hasn't touched it since the decision that changed its scope.

  Concept workflow

• Example operating pattern

  Research and market intelligence

  Delegate research to bounded agents that return synthesized, cited briefs — feeding preparation and decisions rather than piling up as unread reports.

  In practice: "What changed in the competitor's pricing this quarter?" returns as a two-page brief, every claim linked to its source.

  Concept workflow

• Example operating pattern

  Board and investor preparation

  Assemble the quarter's decisions, outcomes, and open risks from records that already exist — instead of a two-week archaeology project.

  In practice: Board prep pulls the decision register, shipped outcomes, and the risk items the monitoring cadence has been tracking since May.

  Concept workflow

• Example operating pattern

  Strategic communications and content

  Draft external communication grounded in your actual positions, voice, and audience context — with drafts that wait for your review, always.

  In practice: A partner update drafts from the project record and your writing voice; you edit one paragraph and approve the send.

  Concept workflow

• Example operating pattern

  Opportunity and risk monitoring

  Standing watch over the signals you define — contract dates, market moves, stalled commitments — surfaced with context when they cross a threshold.

  In practice: A renewal window opens in 30 days; the briefing flags it with the relationship history and last negotiation's notes attached.

  Concept workflow

• Example operating pattern

  Coordinating specialist agents

  Run several bounded workstreams in parallel — research, drafting, monitoring — each with visible status and a clean handoff for review.

  In practice: Four delegations run overnight. Over coffee, you review four handoffs: accept two, revise one, discard one.

  Concept workflow

A note on maturity

The mechanisms behind these patterns — pipeline, memory, cadence, skills, provenance, approval — run today in IEVA’s single-user prototype. The organizational versions described here are product direction being shaped with the private-launch cohort. If one of these patterns is the problem you live with, tell us about it.