nx_landed_cost.nx

nx_landed_cost.nx -- SOVEREIGN LANDED-COST ENGINE for the import/export corridor program. The API/MCP/agentic tier of the /trade.html calculator (operator: "an emitting calculator for these import exports ... we want to do it with russia and lots of other countries ... it needs to scale"). The HTML page prices ONE shipment for a human; THIS organ prices ANY shipment for an AGENT or WORKFLOW -- one tools/call returns the full 2026 US duty stack as structured JSON, so a workflow can fan out over a whole supplier catalog x many corridors and rank by margin. INTEGER-EXACT, NO FLOAT (sovereign law): money in CENTS, duty rates in BASIS POINTS (1% = 100bps), fees in PPM, margins in PERMIL. Every figure is a pure integer transform of the inputs -- no rounding drift, reproducible, gate-checkable against hand arithmetic. REGIME LAYER (the researched, stable part -- 2026-07, verify before a real transaction): * PNTR/NTR status picks Column 1 vs Column 2. Belarus + Russia = PNTR SUSPENDED = Column 2 (punitive) + they are the only col2 corridors here. All others = Column 1. * EXIM Country Limitation Schedule: CLOSED for Belarus + Russia; open elsewhere. * Section 122 (the 10% global surcharge) EXPIRED 2026-07-24 by operation of law -> default OFF; pass s122=1 only to model a replacement surcharge. Section 232/301 are product-specific inputs. The PRODUCT duty rates (col1/col2/232/301 bps) are INPUTS -- they are HTS-line-specific and must come from a licensed broker; the organ supplies the regime logic + fee math around them. VERBS: nx_landed_cost calc <cc> <fob_c> <freight_c> <ins_c> <units> <col1bps> <col2bps> <s232bps> <s301bps> <unitprice_c> <ocean01> <s122_01> <pref01> <other_c> -> JSON nx_landed_cost selftest -> known-value gate (Belarus + Central-Asia reference shipments) -> VERDICT license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0