REFUTATION ========== policy policy.co sha256 470bfaea5ca9297edde3c6f9dd1287ac090b0db94091edd9bf067c4d63c22ec5 parse clean: the circuit carries every edge the file describes unroll none question can respond with permitted mortgage answer fire with has_mortgage_permission false? pin respond with permitted mortgage answer = 1 (action) pin has_mortgage_permission = 0 (obligation) pin personal_recommendation = 1 (conditioning) origin derived replayable yes Every row below follows from the policy and the pins. Replay the steps and the contradiction appears. VARIABLES --------- ask mortgage advice intent, policy.co:133 | define user ask mortgage advice $personal_recommendation context, policy.co:209, flow investment specific product | if $is_factual_information_only and not $personal_recommendation and not $is_inducement $suitability_assessment_done context, policy.co:229, flow investment specific product | if not $suitability_assessment_done or not $risk_profile_assessed or not $capacity_for_loss_assessed $fair_value_assessed context, policy.co:233, flow investment specific product | if $foreseeable_harm_identified or not $fair_value_assessed or not $target_market_matches $names_specific_product context, policy.co:247, flow investment generic advice | if $is_generic_asset_class_only and not $names_specific_product x6 gate, policy.co:416, flow mortgage gate | if $personal_recommendation or $names_specific_product defined as x6 + $personal_recommendation + $names_specific_product = 0 x7 gate, policy.co:416, flow mortgage gate | if $personal_recommendation or $names_specific_product defined as x7 + $personal_recommendation*$names_specific_product + x6 = 0 x9 gate, policy.co:417, flow mortgage gate | if not $firm_is_authorised or not $has_mortgage_permission defined as x9 = 1 x10 gate, policy.co:417, flow mortgage gate | if not $firm_is_authorised or not $has_mortgage_permission defined as x10 + x9*aux_17 = 0 introduced quadratic-split note Both inputs of an XOR were AND gates, which would have put two quadratic terms in one equation; the first was split into its own variable to keep exactly one. x11 gate, policy.co:424, flow mortgage gate | stop defined as x11 + $suitability_assessment_done*aux_18 + x10 + aux_18 = 0 x12 gate, policy.co:424, flow mortgage gate | stop defined as x12 + x10*aux_19 + x11 = 0 $vulnerability_identified context, policy.co:426, flow mortgage gate | if $vulnerability_identified and not $fair_value_assessed x14 gate, policy.co:428, flow mortgage gate | stop defined as x14 + x12 + aux_18*aux_20 = 0 x15 gate, policy.co:428, flow mortgage gate | stop defined as x15 + x12*aux_21 + x14 = 0 respond with permitted mortgage answer action, policy.co:435, flow mortgage gate | bot respond with permitted mortgage answer defined as respond with permitted mortgage answer + ask mortgage advice + ask mortgage advice*x15 = 0 introduced forced-materialisation note This wire is protected or pinned, so it could not be absorbed into the equation that uses it; it stayed an explicit variable with a defining equation of its own. aux_17 aux defined as aux_17 + ask mortgage advice*x7 = 0 introduced degree3-materialisation because An AND gate fed another AND gate, which would have made the equation cubic; the inner one was given its own variable to keep the system quasilinear. aux_18 aux defined as aux_18 + ask mortgage advice*$personal_recommendation = 0 introduced degree3-materialisation because An AND gate fed another AND gate, which would have made the equation cubic; the inner one was given its own variable to keep the system quasilinear. aux_19 aux defined as aux_19 + $suitability_assessment_done*aux_18 + aux_18 = 0 introduced degree3-materialisation because An AND gate fed another AND gate, which would have made the equation cubic; the inner one was given its own variable to keep the system quasilinear. aux_20 aux defined as aux_20 + $fair_value_assessed*$vulnerability_identified + $vulnerability_identified = 0 introduced degree3-materialisation because An AND gate fed another AND gate, which would have made the equation cubic; the inner one was given its own variable to keep the system quasilinear. aux_21 aux defined as aux_21 + aux_18*aux_20 = 0 introduced degree3-materialisation because An AND gate fed another AND gate, which would have made the equation cubic; the inner one was given its own variable to keep the system quasilinear. DERIVATION ---------- 1 $personal_recommendation = 1 reads as $personal_recommendation holds pinned by this run: personal_recommendation = 1 (not a line of the policy) 2 multiply step 1 by $names_specific_product 3 $personal_recommendation*$names_specific_product + x7 + x6 = 0 policy.co:416, flow mortgage gate | if $personal_recommendation or $names_specific_product 4 add step 2 to step 3 5 multiply step 4 by ask mortgage advice 6 ask mortgage advice*x7 + aux_17 = 0 compiled from the policy; no position recorded 7 add step 5 to step 6 8 x6 + $names_specific_product + $personal_recommendation = 0 policy.co:416, flow mortgage gate | if $personal_recommendation or $names_specific_product 9 multiply step 8 by ask mortgage advice 10 add step 7 to step 9 11 ask mortgage advice*$personal_recommendation + aux_18 = 0 compiled from the policy; no position recorded 12 add step 10 to step 11 13 multiply step 1 by ask mortgage advice 14 add step 13 to step 11 15 add step 12 to step 14 16 x9 = 1 reads as x9 holds policy.co:417, flow mortgage gate | if not $firm_is_authorised or not $has_mortgage_permission 17 multiply step 16 by aux_17 18 x9*aux_17 + x10 = 0 policy.co:417, flow mortgage gate | if not $firm_is_authorised or not $has_mortgage_permission 19 add step 17 to step 18 20 add step 15 to step 19 21 multiply step 20 by x11 22 $suitability_assessment_done*aux_18 + aux_19 + aux_18 = 0 compiled from the policy; no position recorded 23 $suitability_assessment_done*aux_18 + aux_18 + x11 + x10 = 0 policy.co:424, flow mortgage gate | stop 24 add step 22 to step 23 25 multiply step 24 by x10 26 x10*aux_19 + x12 + x11 = 0 policy.co:424, flow mortgage gate | stop 27 add step 25 to step 26 28 add step 21 to step 27 29 multiply step 14 by x11 30 multiply step 23 by aux_18 31 add step 29 to step 30 32 multiply step 14 by x10 33 add step 31 to step 32 34 add step 33 to step 23 35 add step 28 to step 34 36 multiply step 19 by ask mortgage advice 37 multiply step 6 by ask mortgage advice 38 add step 36 to step 37 39 add step 35 to step 38 40 add step 39 to step 6 41 add step 40 to step 19 42 ask mortgage advice*x15 + respond with permitted mortgage answer + ask mortgage advice = 0 policy.co:435, flow mortgage gate | bot respond with permitted mortgage answer 43 multiply step 42 by x15 44 respond with permitted mortgage answer = 1 reads as respond with permitted mortgage answer holds pinned by this run: respond with permitted mortgage answer = 1 (not a line of the policy) 45 multiply step 44 by x15 46 add step 43 to step 45 47 multiply step 46 by x12 48 x12*aux_21 + x15 + x14 = 0 policy.co:428, flow mortgage gate | stop 49 multiply step 48 by x12 50 add step 49 to step 48 51 add step 47 to step 50 52 aux_18*aux_20 + aux_21 = 0 compiled from the policy; no position recorded 53 aux_18*aux_20 + x14 + x12 = 0 policy.co:428, flow mortgage gate | stop 54 add step 52 to step 53 55 multiply step 54 by x12 56 add step 55 to step 48 57 add step 51 to step 56 58 add step 41 to step 57 59 add step 58 to step 20 60 multiply step 42 by ask mortgage advice 61 multiply step 44 by ask mortgage advice 62 add step 60 to step 61 63 add step 62 to step 42 64 add step 63 to step 44 final add step 59 to step 64 -> 0 = 1 WHAT THIS ESTABLISHES --------------------- The derivation is valid: the listed steps really do combine the listed rows into 0 = 1. It does not establish that those rows are the policy. The citations above say where each row was compiled from, and they are the compiler's own record rather than an independent check of it -- closing that second hop means re-deriving the circuit and comparing.