Skip to content

CLAUDE.md takes the pricing rules economicspace kept; README's used-in-space price says PLUS #2

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
loggger101 merged 1 commit into from
Oct 26, 2026
Merged

CLAUDE.md takes the pricing rules economicspace kept; README's used-in-space price says PLUS #2

Show file tree
Hide file tree
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
18 changes: 15 additions & 3 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,21 @@ and `spacevalue/quotes/` the recorded metal quotes. Rules:
`spacevalue quotes record`. `SHA256SUMS` holds every file, and the CSVs are
CRLF by rule (`.gitattributes`), because that is what the sums hash.
- **The judgement tables are judgement.** `IN_SPACE_UTILITY` and its overrides
are engineering estimates. Overrides only run downward; `gto` takes `geo`'s
profile by reference (asserted). Every commodity needs a `_COMMODITY_CLASS`
entry (asserted at import), and every in-space destination a demand row.
are engineering estimates. Overrides only run downward; `mars_orbit`'s empty
override is deliberate (README, "The judgement in it"); `gto` takes `geo`'s
profile by reference (asserted). `_UTILITY_FAMILIES` holds each family at
one level at every destination (asserted). Every commodity needs a
`_COMMODITY_CLASS` entry (asserted at import), and every in-space
destination a demand row: a missing row once meant an unbounded market.
- **A price used in space is the Earth price PLUS** `in_space_utility x` the
launch cost avoided, less processing (`in_space_price_usd_per_kg`). Never
replace the Earth price with the launch cost: v1.3.0 did, and threw the
material away. Shipped home it is the Earth price less the downleg, so a
commodity no depot wants is still worth something there.
- **`annual_market_kg` is routed**: world production bounds a commodity flown
home, the depot's import budget one sold there. `_DEMAND_SHARE_BY_CLASS`
splits that budget; its bulk classes sum to 1 (asserted) and `trace` sits on
top of them.
- **The library is quiet.** No printing, installing or directory creation at
import; progress goes through spacecost's `say()`. Printed strings are ASCII
(Windows gives a redirected stdout cp1252). `tests/test_rules.py` holds both.
Expand Down
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,9 +75,10 @@ far more. `tests/test_docs.py` holds this table to the code.
At Earth's surface a commodity is worth its market price. Anywhere else it is
worth the better of two fates:

- **used there**: the launch cost avoided, times how good a substitute it is
for the same mass launched from Earth (its *in-space utility*, 0 to 1), less
what it costs to process on site; or
- **used there**: its Earth price plus the launch cost it avoids, the launch
cost scaled by how good a substitute it is for the same mass launched from
Earth (its *in-space utility*, 0 to 1), less what it costs to process on
site; or
- **shipped home**: its Earth price, less the cost of the trip down.

Every row says which fate won (`value_route`) and, at a depot, how much of it
Expand Down
Loading