Greenways · open foundations
Durable tools, open standards, and public infrastructure for anyone building on the web.
Hara
A precise language and runtime for symbolic, portable systems.
Hestia
Signed identity, recovery, private rooms, and agent receipts.
Hoplite
A compact application server for building and deploying web services.
Historia
Git-native collection and retrieval for AI conversation history.
Hodos
A modular Hara kernel and browser-native code environment.
Greenways OS
A sovereign-first local application launcher for the browser.
Visual Language
Shared mosaic marks, themes, components, and integrity checks.
01 · Open Source Charter · 1.0
Greenways builds durable tools in public. The charter defines what people can expect when a project carries the Greenways Open Source signature.
Qualifying projects publish their source in a public repository under an explicit, recognised open-source licence. The exact licence is stated by each repository; the Greenways signature never replaces or obscures it.
People may inspect, run, modify, redistribute, and use the work commercially according to its stated licence. Public source that cannot be meaningfully used is not enough.
Greenways publishes material architectural decisions, compatibility changes, release notes, and security channels. Maintainers may lead decisively while keeping the reasoning inspectable.
Protocols, formats, and compatibility boundaries are documented. Where conformance matters, Greenways works toward executable specifications and public test suites rather than relying on branding alone.
Changes are reviewed in the open whenever security and privacy permit. Contribution requirements should be documented, technically relevant, and applied consistently. Contributors retain visible credit for their work.
Greenways may sell hosting, integration, support, certification, or managed experiences. Commercial services do not reduce the rights already granted by a project’s open-source licence.
Software licences govern the covered work. Greenways and project names, logos, certification marks, and claims of official compatibility remain subject to their own policies. Forks are welcome; misleading endorsement is not.
The signature
This phrase means the project has public source, an explicit
open-source licence, visible stewardship, and a maintained
relationship to this charter. It does not mean every Greenways
project uses the same licence. The repository’s
LICENSE file is always authoritative.
