Rangoon website source
The public marketing website source on the main branch. Build it locally with Node.js 20 or later.
Downloads & systems
Rangoon is in active development. The website source is available today; the governed agent platform is not yet distributed as an application binary, installer, package, container, or hosted service.
Website source · Application in development
source first
What is available
Use the source archive to inspect or run this public website. It is not an installer for the Rangoon application.
The public marketing website source on the main branch. Build it locally with Node.js 20 or later.
There are no released desktop installers, CLI packages, containers, application binaries, or hosted services yet.
Read the roadmapCandidate platform profiles guide future work. They do not indicate a supported, certified, or downloadable release.
View candidate profilesWebsite source only
These commands build and check the public website. They do not install, start, or configure a Rangoon application runtime.
git clone https://github.com/hypler-dev/rangoon.git
cd rangoon
npm run build
npm run check
npm test
npm startFuture system profiles
These profiles come from LNSAT’s distribution architecture, the reference foundation for Rangoon. No initial support profile has been selected for release.
| Platform | Architecture | Candidate operating systems | Status |
|---|---|---|---|
| macOS | Apple Silicon (ARM64) Intel (x86_64) | Profile under evaluation | Candidate |
| Linux | x86_64 ARM64 | Ubuntu 24.04 · Debian 13 · Rocky Linux 9 | Candidate |
| Windows | Profile to be determined | Future platform lane | Later |
Candidate profiles are planning inputs, not system requirements, compatibility commitments, or support announcements.
Mobile direction
LNSAT mobile support is a source-only architecture plan: iOS and iPadOS Swift shells alongside Android Kotlin shells. The aim is an accountable companion, not an arbitrary mobile shell or background agent daemon.
Planned embedded-app policy evaluation with explicit scope and consent.
A planned opt-in component, never assumed to be active.
Planned inventory of enrolled mobile surfaces and their declared state.
Mobile architectureMobile guardrails
Future mobile workloads are designed to use explicit outbound leases and respect battery, thermal state, network availability, operating-system permissions, and user consent.
Mobile execution should begin only with a declared, user-approved purpose.
Device and platform constraints should limit what runs and when.
Control Center direction keeps enrolled state and workload context inspectable.
Keep exploring
The future is open
Let’s build an AI ecosystem worth trusting.
