I think it's good the concept that the halting problem
makes for an argument that "static analysis always halts".
What I mean by that is relating it to something like Zeno,
you show it doesn't go through, so show it never gets anywhere.
So, showing completeness results first, then makes
for that the student doesn't get left with the idea
of "give up", instead "get over it", or "get through it".
I.e. the idea is to make sure that there's completeness first,
then, to forestall the feeling locked in with absence of
free will or the conscious about it, instead, that incompleteness
is sort of framed as about "there's asymptotic freedom",
in a sense.
Either way it's sort of liberating "my Turing machine can compute"
or "the Turing machine can't compute me". Here the idea is to
make sure there's that "my Turing machine can compute", first,
then "the Turing machine can't compute me" doesn't result
"my Turing machine can't compute".
Framing these kinds of things in universals and the infinite
is sort of for "it's an open box", for the anxiety-prone of
the claustrophobic sort, vis-a-vis the agoraphobe, fear of
being closed in or wide-open spaces. I.e. for not offending
the sensibilities, is first for "here's the great part,
it's closed, out through the unbounded, each is closed",
you know, deterministic, then "here's the kicker: it's open",
so that then they can imagine it in the infinite.
(Here the subscripts are just to indicate the generator
and the instructions, about what populates the tape
then what reads the tape.)
(The, "epistemological antinomies" would probably relate
to "non-logical/properly-logical paradoxes" meaning
terms introduced above the logic, vis-a-vis "logical
paradoxes", what are just any of the usual sorts class/set
distinction issues like in set theory after expansion of
comprehension into quantifier disambiguation. Here for
example the UTM has the monad of its state, it's sort of
non-logical.)
I'm only a practicing sort of corp enterprise software
eng dev where UTM's are really academic, but formal languages
about automata more generally like state-machines are real
apropos, there are bounds, it's unbounded, then I usually
sort of describe things "survey, audit, gap", in terms of
"sensible, fungible, tractable". Got to know your "Big O".
I studied foundations for thirty years though and sort of
have a combined approach about uncountability and logical
paradox, though. Like in my youtube videos or 10,000's posts
to sci.math I demand that there are at least three continuous
domains in mathematics, including line-reals [0,1], the
complete ordered field as field-reals, and signal-reals,
about the analytic construction, and their doubling/halving spaces.
So, I would probably explore that first, ..., Zeno you know.
Yet, that's my opinion.
Like "today we're going to talk Halting Problem or Entscheidungs,
Branching Problem. Does anybody not know Zeno? Has everybody
got that Goedel has complete arithmetic then incomplete arithmetic?
Cantor's Uncountability and the Diagonal or Anti-Diagonal?
Alright, since we already have bounded-tape Turing machines,
Halting Problem is about same as Goedel incompleteness."
Otherwise I'd just kind of leave that out. It's enrichment,
vis-a-vis formal languages, accepter/rejector, automata,
states, open/closed items, in time, these kinds of things.
I'd make such notions more part of a survey in foundations
or formal systems than formal languages and formal automata
(defined, deterministic, and closed).
Russell's Antinomy, Goedel's Incompleteness, the Halting Problem,
Cantor's Paradox (the universe would be its own powerset),
these sort of go together in "a survey of confounding results".
Zeno, ....