Pass 4's plausibility review only ever saw normalized scores, never the raw physical estimate behind them -- confirmed via live testing this was exactly what caused a real misfire (gemma2:27b cited a real cyclist's correct 5 W/kg, log-normalized to "0.159" against a car's power scale, as grounds for rejecting an ordinary bicycle). review_plausibility now takes raw_metrics + normalized_scores + metric units, and the prompt explicitly instructs reasoning from the raw value first. Verified live against phi4: it now cites the actual raw number and correctly explains why a low normalized score doesn't mean the estimate or concept is bad. Repository write methods used in the pipeline's hot path now take an optional commit=False, and Pipeline defers commits during the fast/ deterministic passes (1, 3, and 2 without an LLM), flushing every 200 combos and on any exit path (finally block covers normal completion, cancellation, and any other exception). LLM-involving calls (pass 2 with an LLM, all of pass 4) still commit immediately -- those are slow and crash-prone and worth protecting per-write; the deterministic passes aren't, and recomputing them is now measured at under a second for the full domain rather than worth 8,000+ individual fsync'd commits. Full 2,970-combination domain run: multiple minutes -> 0.91s. Test suite: ~70s -> ~15s. Also fixes two more issues found while auditing the estimator for a real run: CARGO_KG_PER_STRUCTURAL_KG was 500 (no real vehicle carries 500x its own structural mass in cargo -- a magnitude bug, not a modeling choice), corrected to 2.5. And space/rocket platforms' range_fuel now reports the domain's ceiling instead of an arbitrary placeholder constant -- vacuum coast isn't resistance-limited, so "distance before running out of fuel" isn't a meaningful question for these the way it is for ground/air/water vehicles; the real constraint is delta-v budget, a different metric this pass doesn't model. Validated with a live full-domain run (phi4, real Ollama calls): 115 reviewed, 0 malformed/null reviews, 0 verdict-vs-status mismatches. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Applied Combinatorics
Innovation via Attribute Mixing
This is an experimental repo which uses lists of physical attributes and recombines them to form new objects. These objects are then reviewed for comprehensibility and viability.
Example:
Let's identify some methods of getting from here to there:
- Car
- Airplane
- Train
- Bicycle
- Walking with your legs
- Wheelchair
- Scooter
- Spaceship
- Teleportation or beaming technology
To build object 'car' you must select a power source. Power sources include:
- Gas/Internal Combustion Engine
- Lithium Ion Batteries
- Hydrogen Combustion Engine
- Human pedalling
- Modular Nuclear Reactor
- Coal/steam locomotion
- the Sun via Solar Sail
- Cannonfire Recoil
- Pushed by a friend
Putting together lists 1 and 2 we can create 81 mostly novel forms of transportation, such as trains powered by solar sails or walking powered by tiny cannon recoil. Obviously some of these concepts are not as viable as others. While being pushed by a friend might work for those in a wheelchair, it is too slow for those in a car. Speed is therefore a target metric. Let's list some target metrics:
- Speed
- Cost efficiency
- Availability
- Safety
- Range (by fuel)
- Range (by platform degredation or maintenance)
Using these metrics this experiment intends to sift vaguely reasonable concepts from nonsense. Its shortlist may include concepts that sound bizarre but may be technically plausible. Bicycles, motorcycles, and e-bikes all had their turn. Why not hydrogen-bikes?
Setup
Docker (recommended)
docker compose up web
Then open http://localhost:5000.
Seed the database with the transport example:
docker compose run cli seed transport
Local development
pip install -e ".[dev,web]"
python -m physcom init
python -m physcom seed transport
python -m physcom_web
Then open http://localhost:5000.
Run tests:
python -m pytest tests/ -q
LLM integration (optional)
By default the pipeline uses stub estimation. To enable Gemini:
pip install -e ".[gemini]"
export LLM_PROVIDER=gemini
export GEMINI_API_KEY=your_key_here
# export GEMINI_MODEL=gemini-2.0-flash # optional, this is the default
physcom run urban_commuting --passes 1,2,3,4
Copy .env.example to .env and fill in your key for persistent configuration.
a few notes: the thin atmosphere and the sun are obvious dependencies to the solar sail power source. Dependencies would include things such as scale of force (nuclear reactor vs pedalling obviously has an important force differential) and geographic requirements (walking requires ground and gravity). The project should include on every entity a list of dependencies. The viability tester will need to pull in all of these dependencies to ensure they do not contradict.
Additionally, metrics are expected to be extremely close to full points or none at all. The speed of a person pushing a car is effectively zero in its domain whereas a rocket powered car would easily reach the limits of speed in the domain. The resulting multiplication between metrics to get the viability score will be heavily logarithmic. This is expected and is intended to be a filter to eliminate technically plausible but completely pointless in practice concepts. Metric weights are therefore dependent on domain, which will also need to be defined.
First pass viability is physics such as force output, possibly generalized by LLM, last passes can include LLM and human review of social factors.
Attributes themselves are real (quality proven) and are thusly not garbage in the 'garbage in garbage out' risk - that risk is measured in how much nonsense the dimensional explosion generates that makes it past heuristic filters.