GenesisNode SCFDP Demo

Select Scenario

Choose a supply-chain scenario to plan. Each scenario defines customers, zones, cargo types, and vehicle constraints.

Problem Instance

Select a scenario to view the problem instance data.

Pipeline Results

View system:

Route Map

Metrics

Route Details

Proof Traces

Each route is verified against all active rules. Expand a route to see individual constraint checks.

Rule Editor

Rule Builder Help

What is a rule?

A rule is a constraint that adjusts route feasibility probability. When a route's features match a rule's condition, the rule's action modifies the ML model's probability estimate -- either reducing it (soft penalty) or capping it (hard cap). Rules encode domain knowledge that the ML model may not have learned.

Namespaces

Capacity Physics: Rules about vehicle load limits and demand vs. capacity.
Zone Routing: Rules about geographic zone compatibility and transitions.
Cargo Compatibility: Rules about mixing different cargo types on the same vehicle.
Temporal Feasibility: Rules about time windows, shift duration, and scheduling constraints.
Route Complexity: Rules about number of stops, zone transitions, and operational complexity.

Features (16 available)

Loading features...

Condition Types

Threshold: Single comparison: feature > value, feature == value, etc. Example: demand_capacity_ratio > 0.85
Range: Feature must fall between min and max. Example: demand_capacity_ratio between 0.7 and 0.95
Percentage: Feature exceeds a percentage threshold (value 0-100, internally divided by 100 for ratio features). Example: route_duration_ratio > 80%
Relative: Compare one feature against another. Example: n_stops > n_zones_in_route
List Membership: Check if a categorical value is in a list. Example: cargo_type IN [hazmat, munitions]
Compound: Combine two sub-conditions with AND or OR. Example: zone_conflict_flag == 1 OR cargo_conflict_flag == 1
F-logic Fact: Direct F-logic/constraint text for zone incompatibility, cargo incompatibility, or time window overrides.

Actions

Soft Penalty: Subtracts a delta from the probability. E.g., delta = -0.15 reduces probability by 15 percentage points. Use for "risky but not impossible" situations.
Hard Cap: Sets a maximum probability ceiling. E.g., max_prob = 0.05 means at most 5% feasibility. Use for "physically impossible or forbidden" situations.

Example Rules

1. Capacity overload (hard cap): If demand_capacity_ratio > 1.0, cap probability at 5%. The vehicle literally cannot carry the load.

2. Near capacity (soft penalty): If demand_capacity_ratio > 0.85, subtract 0.15. Route is risky but may still work.

3. Tight schedule range: If route_duration_ratio is between 0.85 and 1.0, subtract 0.10. Route is cutting it close on time.

4. Relative stops-to-zones: If n_stops > n_zones_in_route * 3, subtract 0.05. Too many stops per zone is inefficient.

5. Zone incompatibility (F-logic): incompatible_zones(2, 4). Declares that zones 2 and 4 cannot be on the same route.

Add Rule

Rule Name Namespace Description Condition Type

Action Type

Delta (penalty amount) Negative value, e.g. -0.15 = reduce probability by 15pp

Reason Author

Active Rules

Plan Diff

Infeasibility Explorer

Scan all customers for single-stop feasibility under current rules.

Certificate

Retrospective Backtest

Test a proposed rule against historical scenarios to see its impact before deploying.

SCFDP