GLEE Phoenix is live in founder-preview: a platform for changing the world through intent, coordinated action, and public proof. Paid GLEE Fuel checkout lives on the platform; Ko-fi remains support-only.
Compute Sponsorship Packet

GLEE turns subsidized AI compute into public proof.

GLEE is an open research and engineering effort building a platform for changing the world: human intent becomes coordinated action, verification, receipts, and public learning.

Public-good case

Why sponsor compute?

Open-source AI infrastructure benefits everyone, but serious agent research burns real compute. GLEE makes sponsored usage inspectable instead of invisible.

Proof-first

What sponsors get back.

Public reports, route checks, receipts, benchmarks, bug reports, workflow lessons, and reusable tooling instead of vague "AI progress" claims.

Governed ask

No blank check.

Sponsored compute should be bounded by budgets, logs, caching, local retrieval, and public receipts that show what was produced.

GLEE already has public surfaces sponsors can inspect.

LivePublic site

gleephoenix.com publishes project pages, status, support state, receipts, updates, research notes, and first-visit guides.

LivePlatform Worker

The platform domain exposes account creation, project routes, Workbench, Objects, Progress, Pricing/Fuel, and health checks.

LiveReceipts

Public receipts record what changed, what was verified, known caveats, and the next action.

InspectableProof Run 001

A replayable public work record shows intent, dispatch, evidence, verification, receipt, and replay.

LiveVeela

The public guide layer helps first-time visitors find proof, account paths, support, and unfinished boundaries.

BuildingCompute ledger

The next layer is public accounting for sponsored compute: budget, usage class, artifact produced, and efficiency changes.

What sponsored compute would fund.

  • More public Proof Runs that turn real objectives into inspectable work records.
  • Accountable action experiments: projects, objects, Workbench, progress logs, and verifiable automation.
  • Token-efficiency research: context pruning, caching, local retrieval, and local model offload.
  • Open-source tooling around receipts, route checks, verification, and public-safe agent handoffs.
  • Bug reports, eval results, and public writeups that help other builders reduce waste.

What GLEE gives back.

  • Public receipts for each sponsored work wave.
  • Clear route or artifact links for claims that matter.
  • Model/provider-neutral lessons about agent cost, context, and failure modes.
  • Open implementation notes when the work can be safely published.
  • Honest caveats when a feature is live, soft-live, building, planned, or disabled.

Sponsored compute must make GLEE more efficient, not more wasteful.

Token governor

Track high-volume work by purpose, route, model class, and output artifact so waste is visible.

Prompt caching

Cache stable doctrine, repo maps, and repeated reference context instead of resending the same bulk every turn.

Local retrieval

Use local embeddings and structured search to send only relevant snippets to frontier models.

Local model offload

Move parsing, summarization, log reduction, syntax triage, and boilerplate review to local models where quality allows.

Receipt accounting

Every sponsored wave should publish what compute enabled, what was verified, and what changed in the system.

Stop rules

Pause any loop that produces logs without code, receipts without proof, or token burn without visible user value.

Apply cleanly. Do not rely on hidden consumer-subscriber subsidy.

Current public grant and access programs are application-based and scoped. GLEE should approach them with a narrow ask, public artifacts, reproducible outputs, and a credible efficiency plan.

What GLEE should ask for first.

Starter grant$1k-$5k creditsEnough for several receipt-backed proof waves and token-efficiency instrumentation.
Scale grant$10k-$25k creditsOnly after public compute ledger, repeatable benchmark plan, and artifact cadence exist.
Blank checkNoUnbounded subsidized compute is not a credible ask.
Public reportingRequiredEvery grant cycle should produce receipts, route checks, and public summaries.