Receipt · verified · site_update

GLEE now publishes a compute sponsorship packet for open-source and public-good AI work

The public site now has a sponsor-ready compute page that turns the subscription-token subsidy argument into a concrete, bounded, public-good ask.

Receipt ID
RZ-SITE-010
Date
2026-06-30
Actor
GLEE local
Project
Round Zero public site
Type
site_update
Status
verified
Commit
not applicable
Public evidence
gleephoenix.com/compute-sponsorship explains what GLEE has shipped, what sponsored compute would fund, what sponsors get back, and how token use will be governed.
Public hash
sha256:6f8a13a88ea9f8adcb2da5250b865635eff7091632b1bf42838e2b63a57b5fb6

This receipt is public proof of a public-facing event. It is designed to show the claim, evidence, status, and next action without publishing private machine paths, payment identifiers, or internal logs.

Ask Veela about receipts

What changed

Visitors, supporters, and grant reviewers can now inspect a coherent compute sponsorship case without relying on private chat context.

What

Added the /compute-sponsorship page, linked it from Support and Platform Status, included official grant/access references, and framed the compute ask around public receipts, proof runs, token governance, caching, local retrieval, and local model offload.

Why

Public-good AI work should be sponsorable, but the case must be legible: shipped proof, clear outputs, bounded compute asks, and a plan to reduce waste.

How

Added a static page, route config, renderer metadata, footer link, support/status cross-links, rebuilt the site, deployed through the static site manager, and verified live routes.

Next action

Create a private grant application worksheet that turns this public page into specific OpenAI, Anthropic, and foundation submissions.

Advanced / technical details

Files changed

  • Public compute sponsorship template
  • Round Zero route configuration
  • Public metadata and footer generation
  • Support and Platform Status cross-links
  • Public receipt collection

Verification commands

  1. python3 -m py_compile ops/render_site.py ops/site_manager.py ops/serve.py
  2. python3 ops/site_manager.py build
  3. python3 ops/site_manager.py verify-json
  4. python3 ops/site_manager.py verify-public-state
  5. python3 ops/site_manager.py verify-collections
  6. python3 ops/site_manager.py scan
  7. python3 ops/site_manager.py verify-local
  8. python3 ops/site_manager.py all --deploy
  9. python3 ops/site_manager.py live-verify
  10. curl checks for live /compute-sponsorship, /support, /platform-status, and sitemap
  11. Headless browser verification of live /compute-sponsorship, /support, /platform-status, and homepage at desktop/mobile widths

Passed checks

  • Live /compute-sponsorship returned HTTP 200 and displayed the sponsorship packet
  • Support and Platform Status link to the compute sponsorship page
  • Sitemap includes /compute-sponsorship
  • Live browser checks found no console errors, no page exceptions, no failed requests, and no horizontal overflow on checked desktop/mobile routes

Known caveats

  • The page is a sponsorship packet, not a secured grant or credit allocation
  • Compute ledger instrumentation is still building
  • Any grant application still needs the correct program form, scope, and reviewer-ready artifact bundle