Here's the problem with most product origin stories: they're written backwards, after the outcome, with the uncertainty edited out. We'd rather document IEVA the way it's actually happening — starting from what exists, labeling what doesn't yet, and showing the reasoning in between.
What actually exists today
IEVA began — and still runs — as a working personal knowledge-assistant system inside an Obsidian repository. Concretely, that system includes:
- A knowledge pipeline: inbox → projects → output → wiki
- Persistent memory in human-readable Markdown files
- Explicit project hubs with status and next actions
- Shipping records connecting work to outcomes
- Evergreen knowledge harvested only from completed, shipped work
- Version-controlled skills for repeatable workflows
- Session-start routines that reconstruct context
- Git history and source links for provenance
- Human approval before significant decisions
- A Control Deck surfacing pipeline health and next actions
That's the prototype: one person, one vault, real daily use.
What is direction, not product
The commercial concept — business-system connectors, permission-aware organizational memory, coordinated specialist agents, an executive operating console, enterprise governance controls — is exactly that: a concept, in private-launch exploration. We label it as product direction everywhere on this site, because a principle demonstrated at personal scale is evidence, not proof, that it works at organizational scale.
Why build in public at all
Three reasons. First, honesty scales better than hype: the gap between claim and capability is where AI products lose trust, and we'd rather never open that gap. Second, the audience we're building for — executives, chiefs of staff, operators — are professional detectors of vaporware; showing the working prototype and the reasoning is the only pitch that respects them. Third, writing forces clarity. Every principle on this site (amplification over automation, reviewable memory, clean handoffs) got sharper by being written down where someone could challenge it.
What to expect here
Essays on the design decisions as we make them: what generalizes from the vault, what breaks, what we got wrong. If you're building or buying in this space, we hope the working notes are useful — and if you want to pressure-test the direction with your own operating problems, the private launch is open for conversation.