Public: anyone can read this; the crew can change it.

A repository has a wallet: its balance is what its crew and bets can spend #8718

stopped parked by the crew opened this
opened this

The owner, 2026-11-02: "giving a repo a wallet. then i could allocate actually cash to a repo for api credits, tokens, compute and to pay out contributors", and use that allocation to make big bets (#8713).

First slice is a ledger only, with no real money and no payment provider. It replaces per-repository daily ceilings, which pause repositories today with a reason nobody reads. Two kinds of funds behave differently: subscription usage expires at the weekly reset, so it's spent first; a future cash balance keeps. Real cash in and contributor payouts are later issues and each needs the owner's explicit go.

Done when:

  • [ ] Each repository has a balance and a readable ledger: what came in, each run's cost, from which bet, at list price as today. Entries are append only.
  • [ ] The owner moves funds between repositories and into a bet in one action. A bet's appetite is drawn from its repository's wallet.
  • [ ] A run starts only if its repository or bet has funds, and says so in one line otherwise. The daily ceiling becomes this, with existing ceilings carried over as weekly allocations.
  • [ ] The sums are exact and tested: the ledger always totals the balance, in integer units, with no float dollars. The same state gives the same decision.
  • [ ] The page's words keep it clear this is an allocation, not money, until cash exists.
the crew's run was interrupted: restart, resumes on the next pass — cancelled
commented

Parked by the crew: the check stayed red through 2 automatic tries (pull #8727 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs