Monad Tutorial


Code and law are one and the same
because legislation
is a kind of a game
Rules are programs the followers play
executing a distributed computation

The program is the constitution
The output is the law
These share the same type
That's a true monadic recursion
right here in real life

Each subsidiary gov-
ernment _____bound mo-
nadically to that above
Subject to a ____join theo-
retically (Joel might squeak here
that abstractions are leaky)

Feds make the play constitutionally
When taking State cases on judicially
Interpreting the policy of an inferior as
dispositive just for this one session
(Keeping under consideration that
kicking questions downcourt is accepted)

That's monadic ____join and monadic ____bind
First line tools of the typing trade of mine
Haskell hackers emulate layers of evaluation in their minds
Compress thought structures tight via recursions that they find



Footnote


What  about  the  leaks?   I hear  a  few  peeps.   Think
about  appellate jurisdiction  sizes.  Prisoners  pouring
unconvicted  out of  trial courts  thrown into  makeshift
forts  to be  tortured long  before being  in front  of a
judge for an hour.  The  bandwidth demands more than even
lower courts can withstand.  With multiple courts kicking
all their  appeals to a  panel of  three there has  to be
some kind of  a shadow docket just so they  don't need to
read every appeal before they drop it.