01 · Local application
Elysia
Local models, private memory, and user-controlled hardware.
Engineering case study · EcoSyneva Commons LLC
Elysia Ecobotics
Local intelligence, governed development, and ecological computing.
I am developing Elysia Ecobotics as an ecosystem that combines a local AI application, developer tools with explicit permissions, and a public platform for research and collaboration. Its environmental purpose connects this software foundation to ongoing work in sensing and embodied systems.
- Local AI · v1.0 released
- Codev · VS Code extension
- Online · live platform
- Embodied systems · R&D
What is Elysia Ecobotics?
The central engineering problem is how to make AI useful across research, coding, and everyday work while keeping personal context and machine authority under the user’s control. I separate local computation, approved development work, and public participation into systems with distinct responsibilities.
The result spans desktop and API development, model integration, structured memory, permissions, release integrity, and web platform engineering. Ecological research provides a practical direction for these tools: inspectable analysis, reproducible workflows, and eventually field observation.
Three systems, explicit boundaries
Elysia Ecobotics
02 · Developer environment
Codev
Repository inspection, proposals, and reviewed changes in VS Code.
03 · Public platform
Elysia Ecobotics Online
Research resources, add-on discovery, and community participation.
Private local state ≠ public online account
An online sign-in does not grant access to local memories, files, credentials, logs, or machine state. A selected export or connection is a separate, explicit action.
Elysia — Local-First AI
Elysia runs through a Python runtime and local FastAPI bridge, with a React and TypeScript interface inside a Tauri desktop shell. Ollama supplies local model execution. Role-based routing supports multiple installed models and configured local alternatives; it does not silently fall back to a cloud model.
Structured memory and continuity
The Memory Fabric organizes local records with ownership, revisions, provenance, and explicit sharing rules. Identity, authentication sessions, profile context, and ordinary memory have separate responsibilities.
Memory changes and sharing have visible consequences. Attached files and generated artifacts are not automatically promoted into persistent memory.
Useful tools with bounded access
Current development supports approved file inspection, bounded calculations, data summaries, and local artifacts. Model requests, tools, and higher-risk operations pass through policy and approval services.
Local operation is the default. Optional downloads and outward research require their own configuration and permission boundaries.
Engineering evidence: automated account and memory tests exercise clean initialization, session revocation, account separation, deliberate sharing, and refusal of stale approvals. These checks target state transitions and access boundaries, rather than relying only on interface labels.
Codev — Governed Developer Environment
Codev is the first-party VS Code extension connected to local Elysia. Workspace trust and explicit repository approval are separate requirements. Inspection starts with bounded metadata; reading selected files and applying changes require the appropriate local authority.
- InspectSelect and approve a repository, then inspect permitted context and file information.
- Propose and reviewPrepare a change plan and inspect the proposed patch in VS Code’s native diff view.
- Approve and applyAuthorize the specific change. Source and plan checks bind execution to the reviewed state, with receipts and recovery information.
Bounded developer authority
The extension delegates actions to the local API instead of treating a chat request as unrestricted machine permission. A bounded command catalog and explicit approval control supported checks.
Current planning responses are constrained. General autonomous coding reasoning remains a development direction, not a capability claimed for the released extension.
Release and supply-chain integrity
Codev’s VSIX packaging normalizes archive metadata for reproducible bytes and checks which files belong in a distributable package.
Across the ecosystem, the online Developer Forge adds manifest validation, declared permissions, package checksums, and review records. Package integrity, review approval, and local execution permission remain distinct decisions.
Elysia Ecobotics Online
The public platform provides downloads, research discovery, developer resources, and account-based collaboration. It uses React, TypeScript, and Vite, with Supabase authentication and Postgres, Cloudflare Pages hosting, and Workers/R2 services for selected account and storage workflows.
Research and collaboration
The Living Library provides searchable scientific resources with source, access, and reuse context. Commune and Commons Circle provide community, profile, and participation workflows.
Developer Forge and Marketplace
The Forge supports manifest editing, permission declarations, selected-package inspection, export, and checksum verification. Submission creates a review snapshot; it does not automatically publish or install an add-on.
Accounts, review, and trust
Authentication, profiles, participation gates, role-based review, moderation tools, and legal resources support the platform. Public browsing and privileged actions have different access requirements.
Privacy, Security & Governance
Separate identity from model context
Local credentials and sessions do not become ordinary memory or tool context. Online profiles are managed independently, preventing account linkage from becoming an implicit data export.
Make permission specific
Approval is tied to a selected resource and operation. A proposal, trusted workspace, or published add-on listing does not confer blanket authority over a computer.
Keep changes inspectable
Revision history, provenance, operation receipts, and controlled state transitions help explain what changed and under whose authority. Tests cover rejection paths as well as successful actions.
Separate review from execution
Static scans and checksums provide evidence; they are not guarantees of safety. Online review and public distribution remain separate from local validation, installation, and permission decisions.
Ecological Computing & Embodied Systems
My environmental research shapes the long-term purpose: tools for examining geospatial and remote-sensing material, following data provenance, and making ecological analysis reproducible. The software foundation can support researchers before any physical platform is ready.
Current work: bench-stage R&D
Hardware work includes Arduino bench-node firmware for identification, status, and heartbeat signals, alongside Raspberry Pi and microcontroller integration plans. This is early commissioning and interface work.
Direction: field observation
Sensor integration, edge computing, computer vision, and robotic observation are research directions. Companion and Surveyor concepts explore how local intelligence could support ecological data collection; they are not presented as flight-ready or autonomous field products.
My Role
As founder, architect, and developer, I lead Elysia Ecobotics through EcoSyneva Commons LLC. My work connects the local application, developer extension, and online platform, with particular attention to how they exchange information and where their authority stops.
- AI systems
- Local model integration, routing, structured memory, and context boundaries.
- Software engineering
- Python services, desktop/API integration, React, and TypeScript interfaces.
- Platform engineering
- Account workflows, research resources, web routes, and deployment architecture.
- Developer tooling
- Repository review, governed changes, manifests, packaging, and validation.
- Security and qualification
- Permissions, isolation, provenance, test design, and release verification.
- Environmental computing
- Research workflow design and early sensing/embodied-system integration.
Project Media
An empty-memory qualification view from the local application and signed-out views of the public platform. Select any image to inspect the full screenshot.
Local memory controls
Clean qualification profile showing memory stewardship and user-controlled settings.
Public platform
The live entry point for releases, resources, and online participation.
Developer Forge
Add-on preparation and review are presented separately from local installation authority.
Living Library
Research discovery organized around scientific questions and source context.
Technical Stack
- Local application
- Python · FastAPI · Tauri · React · TypeScript · Vite
- AI and memory
- Ollama · local model routing · structured local storage · provenance and access policies
- Developer environment
- VS Code extension API · TypeScript · Git inspection · reviewed patches · reproducible VSIX packaging
- Online platform
- React · TypeScript · Vite · Supabase Auth/Postgres · Cloudflare Pages, Workers, and R2
- Embodied R&D
- Arduino bench firmware · Raspberry Pi integration planning · sensor and edge-system interfaces
Development Status
Public releases and current development are distinct. Elysia and Codev have published v1.0 releases; the capabilities discussed here also reflect ongoing work in their current development codebases.
- Elysia · released, actively developed
- Public Linux v1.0 release available. Memory, governed tools, and local workflows continue to evolve.
- Codev · released, bounded scope
- Public v1.0 extension available. Approved repository work is functional; broader coding intelligence remains in development.
- Online · live, actively developed
- Public resources, accounts, Forge, and Marketplace review surfaces are available. Feature availability and access remain specific to each surface.
- Embodied systems · active R&D
- Bench firmware and hardware integration plans; field autonomy remains a future research objective.