ZOYA OS

• The problem

  • Projects, notes and decisions are spread across many places, and every new chat starts from nothing.
  • An answer with no source cannot be trusted for real work.
  • An assistant that can act needs clear limits on what it may read, change and send.
  • Most assistants are a chat window, and they forget what you told them last week.

• What ZOYA is not

  • It is not the Zoya chatbot on this site, which is a small, rule-based guide to my portfolio.
  • It is a separate, private system.
  • It is not just a chat window.
  • Abilities that are not built are said plainly, not implied.

• What ZOYA is for

  • One assistant that knows my projects and my context, and says where each answer came from.
  • Memory that I approve, so it stays accurate and I stay in control.
  • Tools that run only with permission, one skill at a time.
  • One assistant across all my projects, not a new chat for each.

• What I wanted to improve

  • Answer from my own notes, with the source shown, instead of guessing.
  • Keep everything private and owner-controlled by default.
  • Add abilities slowly, each behind its own approval.
  • Remember what I told it last week, with my approval.

How one question moves through it

• Now: a trusted core

  Private dashboard, answers grounded in my notes, approved memory and three skills, all working on my own machine.

• Next: from my machine to production

  Set up the hosted database, choose a model provider I am willing to send private notes to, and deploy only after the security checklist passes.

• Then: voice

  Build and measure a worker that listens and speaks. Voice counts as done only after a real spoken question gets a spoken answer in a measured time.

• Later: reach into my other tools

  Task automation, links to approved apps, proactive help, access from more than one device, and specialist workflows that always ask a human first. None of these is built.

• 12

  Skills planned

• 3

  Working locally

• 9

  Waiting on connections

• Not yet

  Voice round trip

• Working locally

  Dashboard, grounded answers with citations, approved memory, and the three skills.

• Checked on real accounts, not in production

  Owner-only sign-in and reading approved notes from the private repository have been tested against real accounts, but only from my machine.

• Planned or blocked

  A hosted memory database, a production deployment, the speech worker and the nine outside-facing skills.

• Grounded answers

  Replies come from approved notes and carry the note and version they used. If the notes do not cover a question, ZOYA is meant to say so rather than fill the gap.

• Memory with approval

  New memories start as proposals. Only the ones I approve, and that have not expired, can shape an answer. Working locally; a hosted database is still to come.

• Skills with permissions

  Twelve skills are planned. Three work today: search my notes, plan a task and manage approved memory. The other nine need safe connections first and are marked blocked, not done.

• A private dashboard

  An owner-only view with a glowing 3D visual, charts, chat and skill panels. Its overview is built from a counts-only snapshot, so it shows totals and charts, not note text.

• Voice, planned

  The browser side and short-lived access passes are in place. The speech engine that listens and talks back is not working yet, so voice is not claimed as a feature.

• Project intelligence, planned

  Reading repositories and tracking projects is a future skill. It is blocked until it can run in a safe, limited environment.

• What I own

  • The product idea and what it should and should not do.
  • The trust rules: owner-only access, approval for memory, one permission per skill.
  • The order in which abilities are added.
  • The development of the working parts, using AI coding assistants under my direction.

• Not claimed here

  • Voice, outside-app connections, proactive help and multi-device access are plans.
  • No public users, no benchmarks and no production traffic exist.
  • The Zoya chatbot on this site is a separate project.