IEVA · Offer · Local edition
Your executive operating system, in plain files you own.
Draft offer For founder review. Not a public offer.
The IEVA local edition is a downloadable, local-first Obsidian vault: a knowledge pipeline, reviewable memory, an evidence-gated wiki, repeatable agent skills, and a Control Deck. You run it with your own coding agent and your own model provider. It is built for one person.
The offer in brief
One download. No account, no telemetry, no remote runtime. Markdown is the durable layer, so everything IEVA knows about your work is a file you can read, correct, and keep.
Planned price
50EUR
One-time download. VAT treatment, license, refund, and update terms are to be confirmed.
- WhatA local-first Obsidian vault package, as a ZIP
- ScaleIndividual. One person, not a team
- Runs onYour coding agent, your model provider, Node 18+
- StatusPre-launch. The first sellable release is v0.2. Checkout is not open.
During pre-launch, cohort members receive an access code. No payment is processed on this site yet.
Who it is for
Founders, executives, chiefs of staff, and senior operators who already work with an AI coding agent, or are willing to, and want their context in files they control rather than in a chat history.
- You carry decisions, commitments, and open loops across many sessions and want them to survive.
- You want an assistant whose memory and procedures you can inspect and correct.
- You prefer a system that waits for approval over one that acts on its own.
It is not a fit if you want connected inboxes and calendars, a team workspace, or a hosted product with nothing to install. That is the connected edition.
What is in the package
Each component carries an honest maturity label. “Working prototype” means it exists in the pre-launch build today. “Product direction” means it is planned for a named release and is not yet delivered.
01 · Pipeline
A six-stage knowledge pipeline
Inbox, projects, output, wiki, reference, and an optional content workspace. Each stage has a written contract. Work moves through it instead of being filed.
Working prototypeIn the package today02 · Memory
Reviewable memory
Decisions, commitments, open loops, relationships, working patterns, and corrections live in plain Markdown files. You can open, correct, or delete any of them.
Working prototypeIn the package today03 · Wiki
An evidence-gated wiki
Evergreen knowledge is harvested only from shipped work, through one reviewed workflow. Drafts, imports, and model synthesis do not become canon.
Working prototypeIn the package today04 · Skills
Twelve portable agent skills
Setup, onboarding, session start, inbox triage, project creation, output records, harvest, weekly review, memory review, delegation, and more. Plain Markdown, provider-neutral.
Working prototypeIn the package today05 · Control Deck
A local Control Deck
An optional Obsidian plugin and theme that show pipeline health, active projects, and next actions. It makes no network calls. A Markdown fallback works without it.
Working prototypeIn the package today06 · Scripts
Local status and health checks
Dependency-free Node commands: status, doctor, bootstrap, and refresh. They report the real state of the installation before anything is changed.
Working prototypeIn the package today07 · Onboarding
Setup and onboarding, kept separate
Setup gets the system running and respects an existing vault. Onboarding then configures it for you, one question at a time. Nothing about you is assumed or bundled.
Working prototypeIn the package today08 · Cadence
Cadence presets and briefing templates
Daily, weekly, meeting-preparation, and decision-brief templates, with a cadence chosen at onboarding. Nothing is scheduled in the background. You start each routine.
Product directionPlanned · v0.209 · Command card
“Talking to IEVA”
One page with about fifteen phrases: close the session, run the weekly review, step back, remember, forget, review a skill change.
Product directionPlanned · v0.210 · Learning
Learning loop lite
An opt-in loop that turns your corrections into proposed skill improvements. Nothing changes without your approval, and every change can be undone.
Product directionPlanned · v0.3
Learning loop lite
Product direction
Planned for v0.3. IEVA can propose improvements to its own skills from your corrections. Nothing changes without your approval, and every change can be undone. You learn two phrases: “close the session” and “run the weekly review”.
- Session noteShort, redacted, opt-in
- PatternProblem, root cause, fix
- One proposalA single readable change
- Example-case checkReplayed in a clean context
- Your decisionApprove or reject, with evidence
- Accept or revertLogged either way
The rules of the loop Design principle
- Opt-in, and easy to pause
- Learning notes are off until you allow them during onboarding. “IEVA, step back” pauses capture. “Forget this session” deletes a note after you confirm.
- Short, redacted session notes
- At the end of a material session IEVA writes one short note: what was asked, what it did, your feedback, where it struggled. Credentials, payment data, identifiers, health data, and personnel records are never stored. Documents are linked, not copied.
- Patterns before proposals
- A weekly review turns notes into short pattern pages: problem, root cause, fix. A preference about you goes to your profile for approval instead. It is not written into a skill.
- One proposal at a time
- At most one new skill proposal per week. Each proposal is a readable file describing one change and the patterns behind it.
- Checked against your example cases
- Before you decide, the changed skill is replayed against saved example cases in a clean context, with no side effects. You see a pass or fail table with quoted evidence.
- You approve, or it reverts
- A change is accepted only if you approve it, every previously passing case still passes, and the case that triggered it passes. Otherwise the skill is restored from its snapshot.
- Snapshot and revert
- The skill is snapshotted before any change. A restore touches only that skill, and takes its own snapshot first, so the restore can be undone too.
- Rejections are remembered
- Every decision is logged. A rejected proposal is kept in full, so the same idea is not proposed again.
- Kept out of your wiki
- The loop has its own notebook inside the IEVA system folder. It never writes to your wiki, and it is never a harvest source. The wiki rule stays absolute.
- Working sessions stay lean
- Ordinary sessions load skills and your profile. They do not read the learning notebook. A lesson has to earn its way into a skill before it affects your work.
What it costs you
Up to a minute at the end of a session. About five minutes in the weekly review. Ten to fifteen minutes when there is a proposal to decide. These are design targets, not measurements.
Its honest limits
Session notes are the assistant’s own account of a session, not a machine trace, and they are labeled that way. The same model family replays and grades the example cases. That is why you see the quoted evidence and make the final call.
What it deliberately is not
The local edition stays small on purpose. These are left out, with the reason and where each belongs.
| Not included | Why | Where it belongs |
|---|---|---|
| Connectors to email, calendar, and documents | The local edition works on the files in your vault. It does not reach into business systems. | Connected edition |
| Scheduled briefings, reminders, background agents | These need a scheduler or a running service. This edition has no remote runtime. | Connected edition |
| Automatic or unattended skill changes | Material changes stay under human authority. There is no overnight loop and no auto-accept. | Not planned here |
| Approval gates enforced in code | In this edition, approval rules are part of IEVA’s operating contract. Your coding agent’s permission settings are the enforcement layer. | Connected edition |
| Machine execution traces and automatic grading | Session notes are the assistant’s own account, labeled as such. There is no objective grader for executive work at individual scale. | Later research |
| Team vaults, roles, organization audit trails | The local edition is built for one person. | Connected edition |
| Telemetry, usage metrics, productivity scores | No telemetry is a product promise. IEVA does not score you. | Not planned |
| A skill marketplace or vector search | Both add infrastructure and dependencies the skill set does not need. | Not planned here |
What you need to run it
Read this before you buy. The package is files and scripts. The intelligence comes from the agent and model you already use.
- An AI coding agent
- IEVA is operated by a coding agent that reads the vault’s instructions and skills. Claude Code and Codex are the planned tested agents. Others should work through the plain Markdown skills, untested.Test matrix to be confirmed
- Your own model provider
- You bring your own model account. Model usage is billed by your provider, not by Ækora, and is not part of the package price.
- Node.js 18 or later
- For the local status, health-check, and refresh scripts. No other runtime, and no package installs.
- Obsidian (optional)
- Recommended as the reading and review interface, and required for the Control Deck. The Markdown system works without it.Minimum version to be confirmed
- Operating system
- macOS and Windows are the planned test targets.To be confirmed by release testing
- About thirty minutes
- The install target for the first sellable release: from download to a healthy system check and the first onboarding question, with your coding agent doing the setup.
Roadmap, honestly labeled
Stages, not dates. A stage moves from direction to delivered only when it exists and has been tested.
- Today · v0.1Working prototype
Pre-launch build
The working system, shared with launch-cohort members. Not yet on general sale.
- Pipeline, memory structures, twelve skills, Control Deck, and local scripts
- Ships empty by design: no bundled identity, industry, or preferences
- v0.2Product direction
“Sellable”
An honest, tested package that matches what this site says, with published terms.
- A thirty-minute install path with copy-and-paste prompts and troubleshooting
- One memory format, checked by the health command
- Health checks that verify the wiki rule: every wiki article points at a real output record
- Core skills rewritten with clear steps, output formats, and done-when criteria
- Cadence presets, briefing templates, and the command card
- A published tested-with list, release checksums, and a changelog
- A documented manual update path and an optional Git guide
- v0.3Product direction
“Learning loop lite”
Make “learns from your corrections” and “versioned skills” true, under your authority.
- Four new skills: close a session, find patterns, propose a change, review a change
- A purpose file and version for every skill, with protected invariants
- Seventeen generic starter example cases
- Snapshot and restore commands, and learning checks in the health command
- A plain-language guide: how IEVA learns
- v0.4Concept workflow
“Polish”
A smoother first week and safer updates.
- A guided first week: five fifteen-minute days
- A clearly fictional demo project you can add and remove
- A read-only update planner that lists safe replacements and collisions, and never touches your content
Price and terms
The commercial terms are not final. Nothing on this page is an offer to sell. What is planned, and what is still open:
- Price
- 50 EUR is the planned price. Whether it includes VAT is not decided.To be confirmed
- License
- Planned as an individual license: one person, with changes allowed for your own use and no redistribution. The license text is in legal review. To be confirmed
- Updates
- The proposal is free updates across the 0.x releases, so early buyers receive v0.3 and v0.4. To be confirmed
- Refunds
- Refund terms are not defined yet. They will be published before checkout opens. To be confirmed
- Support
- Planned by email at hola@aekora.com, scoped to IEVA’s files and scripts. Obsidian, Node, your model provider, and custom modifications are outside that scope. To be confirmed
- Your content
- What you write in the vault is yours. The package collects nothing.
The path to the connected edition
Product direction
Two editions, one operating model. The connected operating layer extends the same model across authorized business systems: governed connectors, permission-aware executive memory, coordinated specialist agents, and approvals enforced by the platform. It is in private launch, shaped with a small cohort.
What you build in the local edition stays plain Markdown that you own. Upgrade terms between the editions are not defined yet.To be confirmed
Read more on the product and how it works pages.
Questions
Does anything leave my machine?
The package has no telemetry, no account, and no remote runtime. The Control Deck makes no network calls. Your coding agent talks to the model provider you chose, under that provider’s terms and your own settings.
Do I need Obsidian?
No. Markdown is the durable layer, and the system works from the files alone. Obsidian is the recommended interface and is needed for the Control Deck.
Will IEVA rewrite its own skills?
Not on its own. From v0.3 it can propose one change at a time. You see the proposal, the example-case results, and the evidence. You approve, or the skill is restored. There is no autonomous self-improvement in this edition.
Can I undo an accepted change?
Yes. Each change is snapshotted first, and a restore brings the skill back. Your learning notebook, profile, memory, and pipeline are never touched by a restore.
Is Git required?
No. Change records are readable files. Git is optional and stays under your control. The skill snapshots work the same way with or without it.
I already have an Obsidian vault. Can I add IEVA to it?
Setup starts by checking what is already there. Existing instructions, notes, plugins, and appearance settings are preserved until you authorize a merge, collision by collision.
Does the vault come with example content?
It ships empty by design: no bundled identity, industry, or preferences. A removable, clearly fictional demo project is a v0.4 concept.
Is 50 EUR the final price?
It is the planned price. VAT treatment, license, refund, and update terms are still to be confirmed, and checkout is not open.
How will updates arrive?
The plan for v0.2 is a documented manual path: unzip the new release beside your vault and have your agent replace only unmodified system files, showing you every collision. There is no in-vault update check, because there is no telemetry.
Is this the full IEVA product?
No. It is the first of two editions, at individual scale. The connected operating layer is the private-launch direction.
Private launch · Launching 2026
Work with the local edition early.
The local edition is in pre-launch. Cohort members see the package first. Tell us how you work and what breaks, and mention the local edition in the access conversation.