Sovereignty is not a feature. It is the architecture.
Limen Code exists because developers deserve tools that respect them.
No usage data is collected, transmitted, or stored. No analytics scripts. No beacons. No phone-home on startup. The application makes exactly zero network requests unless you explicitly initiate one.
Every feature that touches external services goes through a consent gate. AI interactions require explicit mode selection via LREM. SSH connections require manual initiation. Container orchestration uses Podman, never Docker, ensuring rootless-by-default operation.
The codebase is open. The build process is reproducible. LREM logs are local and human-readable. Sovereignty Declarations are versioned and revocable. Every action the editor takes on your behalf is auditable.
This is the foundational axiom of the FlameNet ecosystem. It applies to every integration point in Limen Code: AI providers, extension loading, remote connections, and convergence state.
Build identity and verification data.
| Project | Limen Code |
|---|---|
| Version | 0.3.0 Beta |
| Stack | Electron 33 + React 18 + Monaco + Zustand |
| Build System | electron-vite + electron-builder |
| Platforms | Linux (x86_64) — AppImage, .deb |
| License | Open Source |
| Telemetry | None — zero network requests on startup |
| Container Policy | Podman only — Docker excluded by design |
| AI Policy | Consent-gated via LREM — no silent data transmission |
| Ecosystem | FlameNet · LuxNetwork · Limen Convergence |
Limen Code is one node in a larger convergence architecture.
Sovereign web browser built entirely in Rust. Servo rendering engine, iced GUI, zero telemetry. The browser that complements the editor.
Consent-first network layer. Sovereignty declarations, ember traces, convergence states. The protocol that binds the ecosystem.
The convergence fabric. ZkME Gateway, Momentum Engine, Perpetuity genesis. Where sovereignty meets coordination.