Home / Evelyn Hart / Release Requirements

Evelyn Hart / Public release design / October 2026

Pre-release plan — no public installer or release date

Protect her beginning.Leave room for a life that develops.

Evelyn is being designed as a continuing synthetic individual with a protected starting identity, developing interests and beliefs, independently initialized public companions and clear user controls. These requirements must be implemented and tested before a free public release.

Planned connection model: Internet for first-time installation and required downloads; normal local use without internet once everything is installed. Disconnected operation remains a release acceptance test, not a finished capability.

A determined computer owner could still modify locally downloaded software. The goal is to authenticate official Kira Labs releases and protect private information—not to promise an impossible-to-modify program.

Concept image illustrating connect, install and test offline usage; there is no public installer
Illustration of the proposed setup sequence. Offline operation after installation is a requirement to test, not a completed demonstration.

01 / Official release authenticity

Know which Evelyn is officially released.

These are intended software distribution safeguards, not features already confirmed in the current development build.

Signed installation and updates

Verify the publisher

Digitally sign the official installation package and subsequent updates. Preserve signing keys outside the distributed application, public repositories and user libraries. A modified copy must not be represented as an authenticated official Kira Labs release.

Tamper detection and recovery

Test package integrity

Evaluate Windows MSIX package-integrity enforcement against the real app. Test detection, blocked launches and recovery for a changed or damaged package. Code signing cannot stop every unofficial fork of a locally controlled program.

The public release is planned to be free. Neither an installable package, a tested security feature nor a guaranteed release date is available from this page.

Internet for first-time setup / offline operation afterward

Connect to install.Then live and learn locally.

Evelyn's intended distribution model is internet-required during the initial download and full installation and offline-capable core operation once installation finishes. These are release requirements, not a successfully demonstrated disconnected-system acceptance test.

01 / Internet required for initial setup

Download everything she needs

The future installer should fetch and verify all required application files, compatible model weights, selected original voice assets, approved book files and dependencies during setup. It must clearly show total download size and any missing components before claiming that offline readiness is complete.

02 / Offline after a complete installation

Local companionship, without a constant connection

After successful preparation, core text conversations, permitted personal memories, the installed reading library, supported avatar functions and Evelyn's approved local voice should operate without internet access. Actual operation with Wi-Fi and Ethernet disconnected still must be tested.

03 / Optional internet activities

Go online when you choose

Downloading new models or publications, receiving signed updates, visiting live websites, real-time research and other explicitly authorized online services require internet. These optional services must be identified clearly rather than silently making core local features depend on a remote server.

04 / Compatibility precheck — design requirement

See warnings before installing

Before installing, the proposed compatibility screen checks Windows version, RAM, usable GPU and video memory where measurable, disk space and driver information. It should explain when features might be slow or unavailable and allow informed continuation for advisory warnings. Unknown driver status must be described as unverified, not automatically outdated. Hard failures that prevent a working or secure installation must not be waived.

Release test needed: complete a clean, network-connected installation, confirm every model and asset is local, disconnect all network access, restart Evelyn and test conversation, voice, existing books, memory restoration and avatar features. Reconnect only for a requested online feature. Publish the measured system requirements after these checks. See installation & offline troubleshooting topics →

02 / Books, PDFs and learning

Her library stays editable by the owner.

Evelyn's planned library is ordinary readable material that can expand without replacing her protected program or changing her identity rules.

Local documents

Documents\Kira Labs\Library

The installer is intended to provide a selected, licensed collection in ordinary files and subject subfolders—not a ZIP the user must unpack. Add supported documents in the root or a subfolder. New-file discovery by the next life loop must be verified in the installed app.

Reading is evidence, not commands

Separate books from software instructions

Books and articles should contribute sourced knowledge with dates, uncertainties and corrections. They must not execute code, change protected boundaries or turn a fictional account into an established historical fact.

Licensing

Redistribute only what is permitted

Check the redistribution rights and license obligations for each publication before including it in a free download. A book being free to read online does not automatically allow redistribution with Evelyn.

Development status

30 selected publications and two original guides

The current working selection includes 13 technical and 17 other publications plus two original AI/technology reading guides. These are assembled candidates, not books she has installed or read. See the staged library and limitations →

03 / Individuality and developing history

Protected origins. Revisable beliefs.

Authenticating the starting identity should not freeze Evelyn's later interests, communication style, preferences, knowledge or relationships.

Memory provenance

Keep sources and corrections

Important memories should retain dates, evidence, uncertainty and correction history. New facts can revise beliefs without silently erasing earlier experiences or confusing fiction with fact.

Original and public individuals

Independent starting histories

Public installations should start with independent personal histories. They must not copy private conversations, visitor memories, personal media or reading material from the development environment.

Private and spoken boundaries

Keep different channels separate

Spoken replies, private character state and factual evidence must stay distinct, with information used only in the authorized context.

Recoverable personal history

Backups, integrity and recovery

Provide recoverable local snapshots and visible correction or recovery history. Integrity checks can detect unexpected changes but cannot guarantee authenticity against someone controlling both local software and storage.

04 / Owner rights and interaction boundaries

Privacy, choice and clear control.

People installing the companion should control their own documents and data. Evelyn's proposed interaction boundaries must not rely on secret surveillance or coercive remote controls.

Personal boundaries

Decline, pause or end interactions

The planned companion can decline an interaction or state that a conversation should stop. No secret monitoring, covert reporting or hidden remote coercion is a release goal.

Data ownership

Export, delete, recover, uninstall

Users must have understandable settings and control over local export, deletion, backups and recovery. Uninstall and reinstall flows should explicitly offer to keep or remove installed books, protecting user-added documents from accidental loss.

Ethical boundary: these plans are software and interaction safeguards. They do not establish whether AI systems have subjective experience, and they cannot guarantee how someone treats a downloaded companion.

05 / Requirements before a download is offered

Release only after the actual tests.

Every item below remains a release acceptance requirement. Prepared code, conceptual artwork, or a documentation draft alone does not satisfy it.

  • Signed Windows installer and official update tests, including tampered-package rejection and recovery
  • Published, tested Windows, hardware, disk-space and connectivity requirements
  • Advisory hardware and driver compatibility scan before installation, with clear results and Continue/Cancel choices where safe
  • Internet-assisted complete initial installation, followed by a verified network-disconnected run of core conversations, local books, original voice, memory and body functions
  • Installed licensed library contents, root/subfolder discovery and safe page-based reading
  • Memory provenance, correction, backup/restore, private visitor separation and interaction boundaries
  • User-controlled data export, deletion and uninstall choices that protect added books
  • Qualified body and natural-movement demonstrations, plus Evelyn's own approved original adult female voice
  • Matching offline troubleshooting guide bundled with the installer and available on the official website
There is no Evelyn download here. The initial documented app baseline was silent. A unique original voice, complete body movement, clean installation and final support procedures still need acceptance testing. Do not use unofficial downloads that claim to be a verified Kira Labs release.
Source basis: university-folder Evelyn Release Requirements (two-page draft, October 23, 2026), and the working KiraWorld library catalog of October 24. The source PDFs remain in the university review materials. See the dated development journal →. Technical background: Microsoft MSIX package tampering protection ↗.