E.M.M.A. governance
Every action Lucy proposes goes through E.M.M.A.: what Lucy may do is defined by capability grants, owner approvals and consent records, and E.M.M.A. keeps a tamper-evident record of what happened.
◐ Prototype / under testing
THE ECOSYSTEM · REAL SOFTWARE, DIFFERENT STAGES
What we're building,
and how it fits together.
Fenton Lab builds a governed AI operating system, Lucy AIOS, and independent software around it. This page shows the real interfaces where they exist and says plainly what each piece does today.
Fenton Lab is sharing authentic development previews of the Lucy ecosystem. These applications are actively being engineered and tested. Screenshots may show demonstration data, incomplete features, or capabilities awaiting validation. Displayed functionality does not imply commercial availability.
Nothing here is available to buy, download or use yet. Everything shown is in development on Fenton Lab's own machines. Screenshots come from the running software with fictional or freshly created demonstration data.
- ✓ Implemented and demonstrated
- Working in Fenton Lab's development builds and shown here as it runs. Not released.
- ◐ Prototype / under testing
- Built and being tested. Parts may change or be removed.
- ○ Planned / research
- Designed or being researched. No release software yet.
01 HOW IT FITS
One governed core, independent neighbours.
Lucy decides what work matters. E.M.M.A. decides whether it may run. R1 decides what resource posture the machine can safely support.
LUCY AIOS · GOVERNED CORE
- E.M.M.A.Governance: approvals, capability grants, consent and evidence
- R1Runtime and resource management
- Eagle EyeRead-only security observation
- HelixEngineering work, admitted through Lucy's governance
CONNECTED BY A SIGNED BRIDGE · IN DEVELOPMENT
Lucy ProjectsClaims & Evidence ManagementINDEPENDENT · NO LUCY GOVERNANCE INSIDE
Glimwynn · EyravonDesktop companions with their own identity and permissions02 FLAGSHIP · RESEARCH & DEVELOPMENT
Lucy AIOS.
A Windows-native, local-first AI operating system designed around human oversight, recorded evidence and clearly defined execution boundaries.
◐ Prototype / under testing Not available to buy, download or use.
R1 runtime & resources
R1 shapes work to what the machine can safely support, alongside Lucy's memory-pressure policy, and shows CPU, memory and disk readings in the dashboard.
◐ Prototype / under testing
Eagle Eye back end
Read-only security observation: it watches the host and incoming instructions, and records security facts as evidence. Eagle Eye observes only; it never approves or runs work. Today it checks engineering work arriving from Helix.
◐ Development-stage back-end component
Helix back end
An engineering-work pipeline. Helix can only propose bounded work; Lucy owns the task identity and the build ticket, the owner approves through Lucy's normal approval step, and Lucy's own executor runs it.
◐ Development-stage back-end component
Eagle Eye and Helix have no user interface of their own, so they are described rather than pictured.
03 EXPERIMENTAL APPLICATION
Lucy Projects — Claims & Evidence Management.
An experimental application for organizing projects, documentation and evidence workflows, with a tamper-evident audit trail and human sign-off where it matters.
◐ Prototype / under testing Shown with a fictional demonstration project only.
- ◐ Projects, milestones, tasks and workflows, with an audit record of each change.
- ◐ Evidence and documentation kept with the project, and readiness that a person signs off, never the AI.
- ◐ A signed bridge to Lucy AIOS, tested in development: each side authorizes its own actions.
04 EXPERIMENTAL DEVELOPER TOOL
Lucy AI Coding Studio.
A browser-based coding workspace with a code editor, AI companion panels and a registry of engineering agents. It runs on Fenton Lab's own machine.
◐ Prototype / under testing Shown with a fictional sample project only. No AI service was connected or called for these screenshots.
- ◐ A code editor that loads entirely from the application itself, with nothing downloaded from outside services. Working in a development branch.
- ◐ AI companion panels. Provider connections are not yet verified, and no AI results are shown here.
- ○ Engineering agents. Today they exist only as a registry; autonomous execution, queues and completion checks are not implemented.
- ○ Evidence records for coding work. An audit panel exists, but no evidence has been verified yet.
05 THE INDEPENDENT LINEUP
Desktop companions.
Companions are separate products with their own identity and permissions. They don't contain Lucy's governance components.
Glimwynn the desktop fox
An expressive fox companion with local memory, privacy controls and optional AI providers, being prepared for a controlled, invitation-only private beta.
◐ Prototype · private beta preparation
Eyravon the desktop eagle
A watchful eagle companion with a calm, deliberate personality and its own independent identity.
◐ Prototype · in development
Pictures of the companions will be added once their artwork is approved for the web. See the companion collection.
06 NEXT
In progress and planned.
Work that is under way or designed, but not yet running as release software.
- ◐ ChatGPT and MCP integration: three read-only local tools have passed initial tests; secure remote connectivity is still in development.
- ○ Fenton Lab Ecosystem Manager: a planned central place for approved plugins, individual permissions, updates and connection status. No software exists yet.