Skip to content

docs: fix ECONOMICS.md's stale pricing source-of-truth #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wikithoughts merged 1 commit into from
Aug 30, 2026
Merged

docs: fix ECONOMICS.md's stale pricing source-of-truth #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions docs/ECONOMICS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,17 @@ Every job is **conserved**: the asker's debit equals exactly the sum credited to
split allocates the **remainder to the last payee** so rounding can never mint or burn fractional
credit. Property-tested across 3,000 randomized scenarios with zero drift.

Current parameters (tunable, in `coordinator.py` / `ledger.py`):
`STARTER_ALLOWANCE = 100`, `WORKER_POOL = 30`/job, `JUDGE_FEE = 5`/job.
Current parameters: `STARTER_ALLOWANCE = 100` (`PW_STARTER_CREDITS` in `council/ledger.py`) applies to
both paths below. Pricing itself has two separate sources of truth, and only one is live:

- **Legacy in-process demo** (`council/coordinator.py`, driven by `council/run_demo.py`): fixed
`WORKER_POOL = 30`/job, `JUDGE_FEE = 5`/job — no per-job-type scaling.
- **Live network** (`council/net/`, D50): priced by `pool_for(job_type, n_minds)` in
`council/net/config.py`, driven by the `PW_WORKER_POOL`/`PW_JUDGE_FEE` env vars (same 30/5 defaults) —
but the per-mind price scales by the number of responding nodes and by each job type's `pool_mult`
weight (e.g. `chat` is 1×, `research_report` is 3×, `assisted` is 5×), so the real price is not a flat
constant. `GET /job-types` on any live coordinator serves the exact current numbers (including
`judge_fee`) for that deployment — the one place to read actual pricing rather than this doc.

## Sustainability & contributor pay (later)

Expand Down
Loading