Receipt detail pages, project cross-links, and mission feed ship on public site
Fleet v0 Wave 1 extends Round Zero with full receipt proof pages, project cross-links, and a mission feed band on the homepage.
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 Vela about receiptsWhat changed
Public site now generates receipt detail pages with actor, project link, verification fields, plus a homepage mission feed from YAML.
What
Extended public receipt schema, detail page renderer, project cross-links, homepage mission feed, and collection validation gates.
Why
GLEE's public differentiator is proof. Visitors must inspect claims, evidence, verification, and next actions without hand-edited static pages.
How
Updated receipts.yaml, projects.yaml, render_site.py, homepage template, and site_manager verify-collections. Ran local site gates.
Next action
Wave 2: artifact cards, task cards, spokesperson posts, and GitHub-linked proofs.
Advanced / technical details
Files changed
- Public receipt content collection
- Round Zero site generator
- Homepage mission feed template
- Content collection validation gates
Verification commands
- python3 ops/site_manager.py all
- curl -fsS https://gleephoenix.com/receipts
Passed checks
- verify-collections passed with extended receipt fields
- Eight or more receipt detail routes generated
- status.json lists receipt_pages and receipt_pages_count
- Homepage mission feed sections render from YAML
Known caveats
- Artifacts, tasks, and GitHub-linked proofs ship in Wave 2
- Publish pipeline from Ship remains Wave 3
- GitHub OAuth login remains honestly pending