{% extends "base.html" %} {% block title %}PhysCom — Physical Combinatorics{% endblock %} {% block content %}

Physical Combinatorics

An innovation discovery engine that explores the combinatorial space of physical systems — generating, constraining, scoring, and ranking entity combinations against real-world physics.

Run Pipeline View Results

How It Works

PhysCom takes entities from different dimensions, forms their Cartesian product, then filters and scores every combination through a 5-pass pipeline.

1

Constraint Resolution

Each entity declares physical dependencies — what it requires, provides, or excludes. Incompatible combinations are blocked before any estimation begins.

Spaceship requires vacuum_or_thin atmosphere — Human Pedalling requires none fuel infrastructure
2

Physics Estimation

Surviving combinations get raw metric estimates — speed, cost, safety, range — via heuristic stubs or an LLM provider that reasons about the physical properties of each pairing.

Bicycle + Human Pedalling → speed: 20 km/h, cost: $0.01/km
3

Scoring & Ranking

Raw estimates are log-normalized against domain-specific bounds, then combined into a single composite score via weighted geometric mean. Combinations are ranked within their domain.

Domain urban_commuting weights: speed 25%, cost 25%, safety 25%, availability 15%, range 10%
4

LLM Review

Top-scoring combinations are sent to a language model for plausibility and novelty assessment — catching physically valid but practically absurd pairings.

"Train + Solar Sail: structurally valid constraints, but solar radiation pressure cannot overcome rail friction at ground level."
5

Human Review

The final pass surfaces results for expert evaluation. Reviewers can approve, flag, or annotate each combination with domain knowledge that no model captures.

Core Concepts

Entities

The building blocks. Each entity belongs to a dimension (e.g. platform, actuator, energy_storage) and carries typed dependencies that define its physical properties and constraints.

Car Lithium Ion Battery Solar Sail Teleporter
Browse entities →

Domains

The evaluation lens. A domain defines which metrics matter and their normalization bounds — the same combination scores differently under "urban commuting" vs "interplanetary travel."

urban_commuting interplanetary_travel
Browse domains →

Dependencies

The physics layer. Typed key-value constraints (requires, provides, excludes, range_min, range_max) that gate which combinations are physically possible.

requires provides excludes range

Metrics

Quantitative axes like speed, cost, safety, and range. Each metric has a domain-specific weight and normalization range. Some are inverted — lower cost is better.

speed cost_efficiency safety range_fuel
{% if stats %}

Current Data

{{ stats.entities }}
Entities
{{ stats.dimensions }}
Dimensions
{{ stats.domains }}
Domains
{{ stats.combinations }}
Combinations
{% endif %} {% endblock %}