No description
  • JavaScript 83.8%
  • HTML 14.8%
  • Shell 1.4%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Xaver Emmerling 6b3e01d049 Add Tilo to fund 9447
A scripted company at the first Demo Day of seed 9447: the model ranks
it last (small, crowded market, no proven path) and passes; it trades
sideways for twelve years, then in Spring 2039 it is worth $10T. It is
added after the batch is generated and rolls its own dice, so every
other company's fate in that seed is unchanged (1,012 of 1,012 events
identical over 15 years). Money now formats in trillions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 14:22:23 -07:00
fonts Serve the Unicorn Fund game at vc.tilo.coffee 2026-10-24 12:12:49 -07:00
k8s Deploy without CI: no image, no registry, no token 2026-10-24 12:32:05 -07:00
ascii.js Serve the Unicorn Fund game at vc.tilo.coffee 2026-10-24 12:12:49 -07:00
deploy.sh Deploy without CI: no image, no registry, no token 2026-10-24 12:32:05 -07:00
engine.js Add Tilo to fund 9447 2026-10-24 14:22:23 -07:00
game.js Fix pro-rata and cap follow-ons at a third of the round 2026-10-24 12:42:04 -07:00
index.html Show how much of each company you own in the portfolio 2026-10-24 12:20:01 -07:00
model.json Serve the Unicorn Fund game at vc.tilo.coffee 2026-10-24 12:12:49 -07:00
nginx.conf Send the security headers on every page 2026-10-24 12:35:35 -07:00
profiles.json Serve the Unicorn Fund game at vc.tilo.coffee 2026-10-24 12:12:49 -07:00
README.md Deploy without CI: no image, no registry, no token 2026-10-24 12:32:05 -07:00

Unicorn Fund

Run a $50M seed fund through endless generated YC batches, at https://vc.tilo.coffee.

Static files (index.html, game.js, engine.js, ascii.js, model.json, profiles.json, fonts/), copied from the game/ folder of the unicorn-predictor project, where the model and profiles are built.

  • Play locally: python3 -m http.server 8777, then open http://127.0.0.1:8777 (?seed=… replays a shared fund).
  • Deploy: push to main, then run ./deploy.sh. It writes k8s/site.yaml with @REVISION@ set to that commit onto the deploy branch, which Argo CD syncs. There is no CI and no image of our own: the pods download that commit's archive from Forgejo on start and serve it with stock nginx (nginx.conf). deploy.sh refuses to run unless gitleaks finds nothing in the repo's history.