Any capable AI can help you enter GLEE.
The AI may guide. The human authorizes. GLEE Cloud is the airlock; the Thousand Sunny remains private and sovereign.
Freshness-aware public state.
The site should feel alive because GLEE publishes inspectable state, not because the UI pretends to be live. Freshness is computed from status.json.
Ship signs. Fleet serves. Vela guides. MCP airlocks.
The Thousand Sunny is the sovereign command ship: private lab, root of trust, signing source, and Captain authority. GLEE Cloud is the public fleet: website, public receipts, search, onboarding, accounts, MCP, and contribution systems.
Receipts, updates, projects, public status, manifests, and released code can flow from the ship to the fleet.
The fleet may not command the Sunny, read local files, expose secrets, or run admin actions without Captain-controlled gates.
External AIs may explain GLEE, search public proof, and route users to official pages. Humans authorize account, support, and identity actions.
Joining GLEE is a state, not just a signup.
Visitor
Reads public site, receipts, projects, Vela pages, and status files. No account required.
Follower
Future account state for following projects, saving interests, and receiving updates.
Supporter
Has contribution memory through approved support rails and public/private recognition preferences.
Contributor
Submits work, issues, docs, tests, designs, research, or receipts.
Node Operator
Future state for running local GLEE tooling or contributing compute under explicit rules.
Trusted Contributor
Earned through verified work, durable receipts, and higher-trust review paths.
Low friction does not mean low consent.
A join session is short-lived. It states who is asking, what path was requested, what actions are allowed, what actions are forbidden, and when the session expires.