Skip to content

Move the templates to relationalai 2.1.1 - #110

Open
chriscoey wants to merge 31 commits into
mainfrom
coey/templates-relationalai-2.1
Open

chriscoey wants to merge 31 commits into
mainfrom
coey/templates-relationalai-2.1

Conversation

@chriscoey

@chriscoey chriscoey commented Nov 13, 2026 •

Copy link
Copy Markdown
Member

Moves the templates from their current pins (0.13.3 through 1.27.1) to relationalai 2.1.1, fixing mainly what 2.1.1 refuses and two notebooks that were already broken at their pins. Results at the current pins and at 2.1.1 are compared below, and match except where noted. This is the base for moving the templates to deploy mode, which follows as a stacked PR.

Supersedes #108 (its energy_grid_planning fix is included here).

What changed

Template Change Why
all relationalai==2.1.1 in every pyproject.toml and notebook install cell; READMEs and runbooks name 2.1.1 Notes saying a feature first appeared in some release keep that minimum.
demand_planning_temporal, network_flow_planning, supply_chain_resilience, supply_chain_transport Objectives add separately summed cost terms instead of summing a model.union 2.1.1 refuses an aggregate over a union. A term that can be empty (no orders in the horizon; no supplier flagged at the configured risk thresholds, or no operation into a site with a centrality score; no site with a positive fixed cost) defaults to 0.0.
demand_planning_temporal Drops the demand_bound constraint It repeated the variable's own upper bound.
supply_chain_transport, retail_planning (both scripts) Sums name the keys that identify their members 2.1.1 refuses a sum whose members are bound only in where.
book_slate_recommendation Path patterns (model.path(...).exists(), .all().count()) replace all_paths() / PathTraversal; per-user constraints name their group 2.1.1 requires the group keys and deprecates all_paths(). The printed problem has the same variables and objective on both releases.
bom-reachability, cybersecurity-attack-paths, energy_grid_planning, it-dependency-mapping, memory_supply_allocation, telco_network_recovery .all().paths() instead of .all_paths(), in code and docs 2.1.1 deprecates all_paths().
transaction_screening_local deployment.public_schema and identity.internal_schema 2.1.1 requires these fields.
sample-template Model("Template") without use_lqp=False 2.1.1's Model has no use_lqp argument.
commercial_underwriting RiskTier_Standard excludes Preferred in its own rule; premiums are summed per insured entity in the model The report's pandas sum over an integer column failed on 2.1.1. The tiers now partition entities in the model.
datacenter_compute_allocation SOLVER = "highs"; populated scenario cells are labelled FEASIBLE unless the solve proves optimality Its comment and README name HiGHS as the default; "gurobi" fails on an engine without a Gurobi licence. HiGHS stops at the 240 s limit, where the old labels called every populated cell OPTIMAL.
financial_index_replication HiGHS time limit 240 s → 300 s HiGHS proves the basket optimal in 204 s at the pin and 213-218 s on 2.1.1, close to the old limit.
rai-agent-scaffold Removed It is built on the Cortex agent (relationalai.agent), which relationalai 2.0 removed. Removed with its author's agreement; a replacement can follow on 2.x, where a Cortex Agent uses a deployed model's semantic view as a tool.
energy_grid_planning Capacity constraint weights each upgrade and request by its own variable; a substation with no upgrade options adds no capacity From #108. Optimum 1,579,200,000 → 1,562,600,000; README and runbook updated.
simple-start.ipynb Graph(..., node_concept=Station); source table created with change tracking on At its pin (1.0.14) the edge query cell failed with a type error.
fraud_detection_rules.ipynb Declares the CreditCard, Phone and Email concepts and has_* relationships the rule cells read Failed at the template's pin (1.27.1): the cells read relationships the model never declared.

Results

Pinned release vs 2.1.1.

Entry scripts and notebooks (59)
Script Pinned release 2.1.1
datacenter_compute_allocation/datacenter_compute_allocation.py TIME_LIMIT 666,359,880 TIME_LIMIT 664,676,160
demand_planning_temporal/demand_planning_temporal.py 26,137.5, 30,863.5, 34,768 26,137.5, 30,863.5, 34,768
energy_grid_planning/energy_grid_planning.py 1,579,200,000 1,562,600,000
financial_index_replication/financial_index_replication.py 0.0313955 0.0313955
hospital_staffing/hospital_staffing.py 0, 0, 0, 0, 0, 0, 336 0, 0, 0, 0, 0, 0, 336
memory_supply_allocation/memory_supply_allocation.py 46,141,534,331, 41,097,625,117, 29,411,218,728 46,141,534,331, 41,097,625,117, 29,411,218,728
portfolio_balancing/portfolio_balancing.py 64,553.84, 588, 111,037.64, 68,807.95, 75,113.5, 83,113.86, 92,864.07, 76,954.7, 87,752.76, 97,541.96, 93,674.66, 72,872.43, 103,593.93, 82,181.75 64,553.84, 588, 111,037.64, 68,807.95, 75,113.5, 83,113.86, 92,864.07, 76,954.7, 87,752.76, 97,541.96, 93,674.66, 72,872.43, 103,593.93, 82,181.75
telco_network_recovery/telco_network_recovery.py 1,181,491,236 1,181,491,236
ad_spend_allocation/ad_spend_allocation.py 9,740 9,740
bom-reachability/bom_reachability.py ok ok
book_slate_recommendation/book_slate_recommendation.py TIME_LIMIT 564 TIME_LIMIT 557
campaign_roi/campaign_roi.py 3,151.1 3,151.1
cell_tower_coverage/cell_tower_coverage.py 90,000 90,000
cicd_runner_allocation/cicd_runner_allocation.py 10.175, 9.622, 9.526, INFEASIBLE 10.175, 9.622, 9.526, INFEASIBLE
commercial_underwriting/commercial_underwriting.py ok ok
cybersecurity-attack-paths/cybersecurity_attack_paths.py ok ok
defect_root_cause/defect_root_cause.py 46.32 46.32
demand_forecasting/demand_forecasting.py ok ok
diet/diet.py 35.4866 35.4866
disease-outbreak-prevention/disease_outbreak_prevention_network.py ok ok
entity_resolution/entity_resolution.py 927,000 927,000
factory_production/factory_production.py 200,000 200,000
fraud-detection/fraud_detection_local.py 60,618,861 60,618,861
fraud-detection/fraud_detection_rules.ipynb fails ok
fraud-detection/fraud_detection.py 1,730,555,729 1,730,555,729
humanitarian-aid-supply-chain/humanitarian_aid_supply_chain.py ok ok
it-dependency-mapping/it_dependency_mapping.py ok ok
money_laundering_motif_detection/motif_butterfly.py no objective no objective
money_laundering_motif_detection/motif_kyc_burst.py no objective no objective
money_laundering_motif_detection/motif_smurf_army.py SOLUTION_LIMIT SOLUTION_LIMIT
network_flow_planning/network_flow_planning.py 5,280 5,280
patient_cohort_recruitment/patient_cohort_recruitment.py fails no objective
planogram_optimization/planogram_optimization.py 1,656 1,656
pod_placement/pod_placement.py 12 12
product_configurator/product_configurator.py no objective no objective
production_planning/production_planning.py 44,735 44,735
retail_markdown/retail_markdown.py 23,374.65 23,374.65
retail_planning/retail_planning_local.py 62,042.64, 8,931.92 62,477.99, 9,488.61
retail_planning/retail_planning.py could not run could not run
shift_assignment/shift_assignment.py no objective no objective
shipment_compliance/shipment_compliance.py ok ok
simple-start/simple-start.ipynb fails ok
smoker_status_prediction/smoker_status_prediction_local.py ok ok
smoker_status_prediction/smoker_status_prediction.py ok ok
sprint_scheduling/sprint_scheduling.py INFEASIBLE, 112, 112 INFEASIBLE, 112, 112
subscriber_retention/subscriber_retention.py ok ok
supplier_reliability/supplier_reliability.py 4,850, 6,750, 5,150 4,850, 6,750, 5,150
supply_chain_resilience/supply_chain_resilience.py 1,865, 3,515, 1,865 1,865, 3,515, 1,865
supply_chain_transport/supply_chain_transport.py 1,444 1,444
synthetic_eligibility_records/synthetic_eligibility_records.py no objective no objective
synthetic_order_lifecycle/synthetic_order_lifecycle.py no objective no objective
test_data_generation/test_data_generation.py 18,000 18,000
transaction_screening_local/transaction_screening_local.py ok ok
traveling_salesman/traveling_salesman.py 8.5 8.5
underwriting_audit/underwriting_audit.py no objective, no objective, INFEASIBLE no objective, no objective, INFEASIBLE
warehouse_allocation/warehouse_allocation.py 13,713.29 13,713.29
water_allocation/water_allocation.py LOCALLY_SOLVED 853.392 LOCALLY_SOLVED 853.392
wildlife-conservation-network/wildlife_conservation_network.py ok ok
sample-template/template.py fails ok

Differences, and what I could not run

  • energy_grid_planning: the Fix energy_grid_planning's substation capacity constraint #108 fix (above). Revenue is the objective, so where several upgrade sets earn the same revenue the net value depends on which set the solver returns; the README now says so.
  • retail_planning_local: the GNN's demand predictions differ between the two runs, so the plans differ (62,042.64 / 8,931.92 → 62,477.99 / 9,488.61). With demand fixed to the same values, the original code at its pin and the edited code at 2.1.1 give the same optimum for both problems ($115,524.69 revenue, $108,685.87 cost).
  • book_slate_recommendation stops at its 180 s limit on both releases (TIME_LIMIT, objective 564 → 557). The README says the bundled slice solves to OPTIMAL in a few seconds; that predates this PR.
  • datacenter_compute_allocation: with HiGHS, both releases stop at the 240 s limit with near-equal incumbents: 16 of 24 scenario cells get a plan and 8 none. A 1,800 s limit gives the same 16 and 8, so the limit stays. The README shows the HiGHS output.
  • patient_cohort_recruitment fails at its pin (1.1.0) with a type error in problem.display() and runs unchanged on 2.1.1. transaction_screening_local fails on a fresh install at its pin, which now resolves duckdb 2.0; with duckdb 1.5.6 it runs, and its output matches 2.1.1. sample-template fails on a fresh install at its pin (0.13.3) under Python 3.11 and 3.14.
  • retail_planning.py needs the full H&M tables and a GPU, so I could not run it; it shares the sum change with retail_planning_local, which I ran.
  • fraud_detection.py reads PaySim tables that were not available to me, so I ran a copy on the template's bundled paysim_mini sample, on CPU: both releases give the same results.
  • telco_network_recovery, subscriber_retention, simple-start ran against a separate database instead of the one named in the scripts.

The capacity constraint bound the upgrade and approval variables in its
where clause, outside its sums over the substation's upgrades and
requests. For each substation and investment level it therefore compared
the sum of the upgrade variables times the sum of the upgrade capacities
with the sum of the approval variables times the sum of the requested MW.
Each upgrade's capacity and each request's MW is now weighted by its own
variable.

Listing InvestmentLevel in the objective's sum makes it say what the
solver already computes, one term per request and level.

The optimum moves from 1,579,200,000 to 1,562,600,000. The knee stays at
$300M, now with 6 data centers, 1,530 MW and $252M net value: Google
Metroplex and Lambda Labs at Dallas-Fort Worth are approved from $300M,
and xAI Colossus at no budget. The README and runbook state the new
results.
@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

The templates docs preview for this pull request has been deployed to Vercel!

✅ Preview: https://relationalai-docs-53nd9eo0k-relationalai.vercel.app/build/templates
🔍 Inspect: https://vercel.com/relationalai/relationalai-docs/DnoxrH4avm4dvvA7nEQeBaxXGQUm

relationalai 2.x refuses sum(model.union(...)) objectives: a union keeps one
copy of equal values while the solver adds every term. The objective now adds
the production, holding and unmet-demand totals, each summed over its own rows,
with a zero default on the unmet total, which is empty when no order falls in
the horizon. The unmet-demand bound duplicated the variable's own upper bound
and is removed.
relationalai 2.x refuses an aggregate over model.union, since the union
keeps one copy of equal values while the solver takes every arm's
members. The objective now adds sum(Lane, ...) and sum(Site, ...), each
naming the concept whose members it totals, and the README describes
the objective that way.
relationalai 2.x renamed deployment.schema to deployment.public_schema
and requires deployment.identity.internal_schema. The local DuckDB
config sets both (main and main_internal); README and runbook describe
the three settings.
…ium from the model

RiskTier_Standard now excludes RiskTier_Preferred in its own rule, so
the four tier concepts partition InsuredEntity as the README says,
instead of the report subtracting Preferred after the query. The
premium-by-tier rollup reads Policy.total_premium from the model and
merges it on the entity id, rather than looking each id up in the
policies CSV.
relationalai 2.x refuses a sum that does not identify each member, since
PyRel counts equal members once while the solver counts one per row, and
refuses an aggregate over model.union. Each constraint and cost sum now
names its keys, the objective adds its four cost terms, and the two LTL
cost terms are each one sum over (segment, period). The segment refs are
defined once and reused.
READMEs and runbooks named each template's previous pin (1.0.14 through
1.27.1). Requirement and install lines now state 2.1.1, the version every
pyproject.toml pins. Notes giving the release a feature first appeared in
keep that minimum.
…ls read

The rule cells read User.has_address, has_credit_card, has_phone and
has_email, and the model text describes CreditCard, Phone and Email
concepts, but the model cell declared only flat properties. The notebook
now declares those concepts (identified by their value, so users sharing
a card, phone or email link to the same node) and relationships, loads
them with User.new, and assigns each user's weakly connected component
through a rule, since the component of the full graph spans every node
type.
relationalai 2.x refuses an aggregate over model.union: the union keeps
one copy of equal values, while the solver takes every arm's members.
Both objectives now add their separately summed cost terms. None of the
terms can be empty for these templates, so none takes a default. The
network_flow_planning README explains the two sums instead of the union.
The graph was built without a node concept, so Graph generated its own
Node concept and the edge query read Station's id from nodes that have
none. Graph(..., node_concept=Station) makes Station the graph's Node.
The notebook also creates its source table with change tracking on,
which the model needs to read it, uses Station.lookup for the edge
endpoints, and drops a stray copy of the centrality introduction that
sat before the setup cells.
relationalai 2.x refuses a sum that does not identify each member, since
PyRel counts equal members once while the solver counts one per row. The
revenue, salvage and cost sums name their keys in both scripts.
…roups

relationalai 2.x replaces all_paths() and PathTraversal with path
patterns that name their endpoints: the candidate rule uses the walk
pattern's .exists() and the walk count its .all().count(). Each per-user
constraint names its group keys in its where clause, which 2.x requires
for a constraint with one instance per group. The problem has the same
variables, constraints and objective as before.
…rollup

The rollup summed one row per policy, so an entity with several policies
would be counted once per policy. It now sums Policy.total_premium per
InsuredEntity in the model, keeping one row per entity. The bundled data
has one policy per entity, so the report is unchanged.
relationalai 2.1.1 deprecates path(...).all_paths() and warns on every
call. bom-reachability, cybersecurity-attack-paths, energy_grid_planning,
it-dependency-mapping, memory_supply_allocation and telco_network_recovery
now write .all().paths(), which returns the same paths, and their READMEs
and runbooks name it. Results are unchanged.
…t upgrades

The capacity constraint holds for every substation with a request. At a
substation with no upgrade options its upgrade sum has no value, which
makes the constraint, and so every investment level, infeasible. The
upgrade sum now defaults to 0.0. The bundled data has upgrades at every
requested substation, so results are unchanged (1,562,600,000); with a
request added at a substation without upgrades the plan is feasible.

The README notes that revenue is the objective, so where several upgrade
sets earn the same revenue the reported net value depends on the set the
solver returns.
The already-read exclusion is explained where it is defined; the
candidate rule now points to it.
The risk surcharge sums flow from watch-level suppliers only. With
thresholds that flag no supplier, a case the README describes, the sum
is empty and 2.1.1 leaves the objective without a value. Default the
term to zero, as the union objective did by dropping it.

Also point the memory_supply_allocation runbook at the path module's
README under its current name.
rai-agent-scaffold is built on the Cortex agent (relationalai.agent),
which relationalai 2.0 removed, so its pin and README stay at 1.0.14.

sample-template passed use_lqp=False to Model, an argument 2.1.1's Model
no longer takes.
@chriscoey chriscoey changed the title Move every template to relationalai 2.1.1 Move the templates to relationalai 2.1.1 Nov 13, 2026
@chriscoey
chriscoey requested a balanced review from Copilot November 13, 2026 22:09

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The objective becomes undefined for networks with no positive-fixed-cost sites because the empty fixed-cost sum is not defaulted to 0.0.

1 open issue
What changed in this PR

Migrates 53 of 54 templates to RelationalAI 2.1.1 as a foundation for the later deploy-mode migration. The agent scaffold remains on 1.x because its Cortex agent API was removed in 2.0.

Changes:

  • Updates dependency pins and corresponding README and runbook guidance.
  • Adapts aggregates, path queries, model construction, and local deployment configuration for 2.1.1.
  • Repairs two notebooks and underwriting reporting, and incorporates #108’s energy-grid capacity fix with updated results.
File Description
wildlife-conservation-network/​README.md Documents SDK 2.1.1.
wildlife-conservation-network/​pyproject.toml Pins SDK 2.1.1.
water_allocation/​README.md Documents SDK 2.1.1.
water_allocation/​pyproject.toml Pins SDK 2.1.1.
warehouse_allocation/​README.md Documents SDK 2.1.1.
warehouse_allocation/​pyproject.toml Pins SDK 2.1.1.
underwriting_audit/​README.md Documents SDK 2.1.1.
underwriting_audit/​pyproject.toml Pins SDK 2.1.1.
traveling_salesman/​README.md Documents SDK 2.1.1.
traveling_salesman/​pyproject.toml Pins SDK 2.1.1.
transaction_screening_local/​transaction_screening_local.py Updates DuckDB deployment schema configuration.
transaction_screening_local/​runbook.md Updates version and deployment guidance.
transaction_screening_local/​README.md Explains updated local deployment configuration.
transaction_screening_local/​pyproject.toml Pins SDK 2.1.1.
test_data_generation/​pyproject.toml Pins SDK 2.1.1.
telco_network_recovery/​telco_network_recovery.py Migrates path enumeration calls.
telco_network_recovery/​README.md Documents SDK 2.1.1.
telco_network_recovery/​pyproject.toml Pins SDK 2.1.1 with GNN support.
synthetic_order_lifecycle/​README.md Updates version and reinstall guidance.
synthetic_order_lifecycle/​pyproject.toml Pins SDK 2.1.1.
synthetic_eligibility_records/​pyproject.toml Pins SDK 2.1.1.
supply_chain_transport/​supply_chain_transport.py Adds aggregate keys and separate cost sums.
supply_chain_transport/​README.md Documents SDK 2.1.1.
supply_chain_transport/​pyproject.toml Pins SDK 2.1.1.
supply_chain_resilience/​supply_chain_resilience.py Adds cost totals with an empty-risk fallback.
supply_chain_resilience/​README.md Documents SDK 2.1.1.
supply_chain_resilience/​pyproject.toml Pins SDK 2.1.1.
supplier_reliability/​README.md Documents SDK 2.1.1.
supplier_reliability/​pyproject.toml Pins SDK 2.1.1.
subscriber_retention/​README.md Documents SDK 2.1.1.
subscriber_retention/​pyproject.toml Pins SDK 2.1.1 with GNN support.
sprint_scheduling/​README.md Documents SDK 2.1.1.
sprint_scheduling/​pyproject.toml Pins SDK 2.1.1.
smoker_status_prediction/​README.md Documents SDK 2.1.1.
smoker_status_prediction/​pyproject.toml Pins SDK 2.1.1 with GNN support.
simple-start/​simple-start.ipynb Fixes graph typing, lookups, and change tracking.
simple-start/​README.md Clarifies station-node graph construction.
simple-start/​pyproject.toml Pins SDK 2.1.1.
shipment_compliance/​README.md Documents SDK 2.1.1.
shipment_compliance/​pyproject.toml Pins SDK 2.1.1.
shift_assignment/​README.md Documents SDK 2.1.1.
shift_assignment/​pyproject.toml Pins SDK 2.1.1.
sample-template/​pyproject.toml Pins SDK 2.1.1.
sample-template/​model/​schema.py Removes the unsupported model argument.
retail_planning/​retail_planning.py Names members of objective aggregates.
retail_planning/​retail_planning_local.py Applies matching aggregate-key changes locally.
retail_planning/​README.md Documents SDK 2.1.1.
retail_planning/​pyproject.toml Pins SDK 2.1.1 with GNN support.
retail_markdown/​pyproject.toml Pins SDK 2.1.1.
production_planning/​pyproject.toml Pins SDK 2.1.1.
product_configurator/​README.md Documents SDK 2.1.1.
product_configurator/​pyproject.toml Pins SDK 2.1.1.
portfolio_balancing/​README.md Documents the updated SDK pin.
portfolio_balancing/​pyproject.toml Pins SDK 2.1.1.
pod_placement/​README.md Updates version and troubleshooting guidance.
pod_placement/​pyproject.toml Pins SDK 2.1.1.
planogram_optimization/​README.md Updates version and reinstall guidance.
planogram_optimization/​pyproject.toml Pins SDK 2.1.1.
patient_cohort_recruitment/​README.md Documents SDK 2.1.1.
patient_cohort_recruitment/​pyproject.toml Pins SDK 2.1.1.
network_flow_planning/​README.md Explains separately summed objective costs.
network_flow_planning/​pyproject.toml Pins SDK 2.1.1.
network_flow_planning/​network_flow_planning.py Replaces the union aggregate with separate sums.
money_laundering_motif_detection/​pyproject.toml Pins SDK 2.1.1.
memory_supply_allocation/​runbook.md Updates path API examples and reference path.
memory_supply_allocation/​README.md Updates SDK and path-enumeration guidance.
memory_supply_allocation/​pyproject.toml Pins SDK 2.1.1 with GNN support.
memory_supply_allocation/​memory_supply_allocation.py Migrates dependency-path enumeration.
it-dependency-mapping/​runbook.md Updates path-enumeration examples.
it-dependency-mapping/​README.md Updates SDK and path API guidance.
it-dependency-mapping/​pyproject.toml Pins SDK 2.1.1.
it-dependency-mapping/​it_dependency_mapping.py Migrates downstream-path enumeration.
humanitarian-aid-supply-chain/​README.md Documents SDK 2.1.1.
humanitarian-aid-supply-chain/​pyproject.toml Pins SDK 2.1.1.
hospital_staffing/​README.md Documents SDK 2.1.1.
hospital_staffing/​pyproject.toml Pins SDK 2.1.1.
fraud-detection/​README.md Documents the updated SDK pin.
fraud-detection/​pyproject.toml Pins SDK 2.1.1 with GNN support.
fraud-detection/​fraud_detection_rules.ipynb Repairs entity relationships and component assignment.
financial_index_replication/​README.md Documents the updated SDK pin.
financial_index_replication/​pyproject.toml Pins SDK 2.1.1.
factory_production/​README.md Documents SDK 2.1.1.
factory_production/​pyproject.toml Pins SDK 2.1.1.
entity_resolution/​README.md Documents the updated SDK pin.
entity_resolution/​pyproject.toml Pins SDK 2.1.1.
energy_grid_planning/​runbook.md Updates frontier results after the capacity fix.
energy_grid_planning/​README.md Updates results, allocation explanations, and SDK guidance.
energy_grid_planning/​pyproject.toml Pins SDK 2.1.1 with GNN support.
energy_grid_planning/​energy_grid_planning.py Fixes capacity weighting and migrates path calls.
disease-outbreak-prevention/​README.md Updates SDK and reproducibility guidance.
disease-outbreak-prevention/​pyproject.toml Pins SDK 2.1.1.
diet/​pyproject.toml Pins SDK 2.1.1.
demand_planning_temporal/​README.md Documents separately summed objective costs.
demand_planning_temporal/​pyproject.toml Pins SDK 2.1.1.
demand_planning_temporal/​demand_planning_temporal.py Revises cost sums and removes a redundant constraint.
demand_forecasting/​README.md Documents SDK 2.1.1.
demand_forecasting/​pyproject.toml Pins SDK 2.1.1 with GNN support.
defect_root_cause/​pyproject.toml Pins SDK 2.1.1.
datacenter_compute_allocation/​pyproject.toml Pins SDK 2.1.1 with GNN support.
cybersecurity-attack-paths/​README.md Documents SDK 2.1.1.
cybersecurity-attack-paths/​pyproject.toml Pins SDK 2.1.1.
cybersecurity-attack-paths/​cybersecurity_attack_paths.py Migrates attack-path and route enumeration.
commercial_underwriting/​README.md Documents SDK 2.1.1.
commercial_underwriting/​pyproject.toml Pins SDK 2.1.1.
commercial_underwriting/​commercial_underwriting.py Partitions tiers and sums premiums per entity.
cicd_runner_allocation/​README.md Updates SDK and reproducibility guidance.
cicd_runner_allocation/​pyproject.toml Pins SDK 2.1.1.
cell_tower_coverage/​README.md Documents SDK 2.1.1.
cell_tower_coverage/​pyproject.toml Pins SDK 2.1.1.
campaign_roi/​README.md Documents SDK 2.1.1.
campaign_roi/​pyproject.toml Pins SDK 2.1.1.
book_slate_recommendation/​README.md Explains path existence and walk counting.
book_slate_recommendation/​pyproject.toml Pins SDK 2.1.1.
book_slate_recommendation/​book_slate_recommendation.py Migrates path queries and names constraint groups.
bom-reachability/​runbook.md Updates assembly-path enumeration examples.
bom-reachability/​README.md Updates path-depth guidance for the new API.
bom-reachability/​pyproject.toml Pins SDK 2.1.1.
bom-reachability/​bom_reachability.py Migrates assembly-path enumeration.
ad_spend_allocation/​README.md Documents SDK 2.1.1.
ad_spend_allocation/​pyproject.toml Pins SDK 2.1.1.

Review effort: Balanced

@chriscoey
chriscoey marked this pull request as ready for review November 13, 2026 22:20
Site.x_open exists only for sites with a positive fixed cost, so with
none the fixed-cost sum is empty and the objective has no value.
Default that sum to 0.0.
Centrality scores exclude stores and offices, so in a network whose
operations all deliver to them the centrality sum is empty and the
objective has no value. Default that sum to 0.0.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The major SDK migration still requires maintainer runtime validation of retail_planning.py with full H&M tables and a GPU, plus datacenter_compute_allocation with its configured Gurobi solver.

No open issues 🎉

1 resolved since last review

Review effort: Balanced

The comment and README name HiGHS as the default solver, but SOLVER was
set to "gurobi", which fails on an engine without a Gurobi licence.
A populated cell was labelled OPTIMAL whatever the termination status,
so a HiGHS run that stopped at its time limit reported "16 optimal" and
persisted AllocationPlan.status OPTIMAL. Cells are now OPTIMAL or
INFEASIBLE when the solve proved optimality, and FEASIBLE or UNSOLVED
when it did not. The README shows the HiGHS output.
HiGHS proves the basket optimal in 204-218 s on relationalai 2.1.1 and at the previous pin, close to the 240 s limit, so a slower solver run would stop at the limit with an unproven basket.
The template writes this file on every run; it was committed by mistake.
…ring and runbook

The runbook gave only the Gurobi result; it now also gives the HiGHS
default (16 FEASIBLE, 8 UNSOLVED at the 240 s limit). The README no
longer says Gurobi labels the same cells, which no run has checked.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The 53-template major SDK migration leaves the full H&M/GPU retail_planning.py workflow unvalidated, requiring human confirmation of connected Snowflake and GNN compatibility.

No open issues 🎉

Review effort: Balanced

It is built on relationalai.agent, which relationalai 2.0 removed, so it
cannot move to 2.1.1 with the other templates. A replacement can follow
on the 2.x path, where a Cortex Agent uses a deployed model's semantic
view as a tool.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The SDK major-version migration leaves the full-table/GPU retail_planning.py entrypoint unvalidated, requiring a maintainer with the H&M tables and target Snowflake/GPU environment to confirm compatibility.

No open issues 🎉

Review effort: Balanced

rai-agent-scaffold was removed, so the repository root now holds 52
template directories.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants