An implementation of modal UDT

by Benya_Fallenstein1 min read11th Feb 2015No comments


Ω 3

Personal Blog
Crossposted from the AI Alignment Forum. May contain more technical jargon than usual.

One of the great advantages of working with Gödel-Löb provability logic is that it's possible to implement an evaluator which efficiently checks whether a sentence in the language of GL is true. Mihaly and Marcello used this to write a program that checks whether two modal agents cooperate or defect against each other. Today, Nate and I extended this with an implementation of modal UDT, which allows us to check what UDT does on different decision problems---see Program.hs in the Github repository. No guarantees for correctness, since this was written rather quickly; if anybody is able to take the time to check the code, that would be very much appreciated!

The implementation of UDT is rather pleasing, I think. Here's the informal definition of modal UDT, using PA + :

  • For every possible outcome , from best to worst:
    • For every possible action , in order:
      • If it's provable in PA + that "UDT takes action " implies "the universe returns outcome ", then take action .
  • If you're still here, return a default action.

Here is the corresponding Haskell code:

udt :: (Enum a,Ord b,Show b,Enum b)
    => Int -> ModalProgram b a -> b -> ModalProgram b b
udt level univ dflt = modalProgram dflt $
  mFor $ \a ->
    mFor $ \b ->
      mIf (boxk level (Var b %> univ a)) (mReturn b)

Being able to write modal UDT like this makes it very easy to implement and try small variations on the code.

We used this code to check what modal UDT would do in a version of Newcomb's problem where Omega uses proofs in PA (rather than simulations) to decide whether to put the money in the box; that is, it will put a million dollars in the first box if and only if it can prove that you will one-box. If our code is correct, it turns out that in this case, modal UDT will do whatever its default action was.

Earlier, we thought we had proved a different result on the whiteboard, but after the code disagreed with us, we went over it again and found a bug in our proof. After fixing that bug, we now have a manual proof that UDT will end up taking its default action in this scenario (which I'll write about some other time). So looks like this can be a useful tool for figuring out this sort of thing!


Ω 3

New Comment