[Epistemic status, can't spot a mistake, but am not confidant that there isn't one, if you find anything please say so. Posting largely because the community value of a new good idea is larger than any harm that might be caused by a flawed proof. ]

Suppose you have an automatic proof checker. Its connected to a source of statements that are sometimes correct proofs, and sometimes not. The proof checker wants to reject all false proofs, and accept as many of the true proofs as possible. It also wants to be able to update its own proof framework.

Define $S$ to be a set of statements in a particular formalism, say those that are grammatically well defined in PA. Let $B$ be any sequence from some alphabet of symbols. Let

and $V\subset L$ be the set of programs that have the property that

In other words, $V$ is the set of all programs that never prove false statements. We should never leave $V$ or need to talk about any program not in it.

For $v\in V$ write $v\left[s\right]$ to mean $\exists b\in B:v(s,b)$. Ie $v$ proves $s$

A simple setup would consist of a starting program $p_1\in V$ and a rule that says,

If $p_1\left[p_2\right[s]⟹s]$ then you can add $p_2$ to your list of trusted provers. If $p_1$ proves the soundness of $p_2$, then you can accept any statement when given a proof of it in $p_2$.

The lobian obstacle is that $p_2$ must be strictly weaker than $p_1$, in that $p_1$ can prove any statement that $p_2$ can, but $p_1$ can prove the soundness of $p_2$ and $p_2$ can't prove its own soundness. This means that each trusted prover has to be strictly weaker than the one that generated it. You could start with PA+3^^^3 and say that a few weakenings aren't a problem, but that isn't an elegant solution.

Note: You can't get around this problem using cycles. Suppose

This would imply

So any cycle could be shrunk by 1, and inductively, shrunk to a self trusting system.

I propose instead that you use the rule.

If $p_1\left[p_2\right[s]⟹p_1[s\left]\right]$ then accept any future proofs that are accepted by $p_2$, and give $p_2$ all rights given to $p_1$, including taking $p_2[p_3⟹p_2]$ to mean that $p_3$ is accepted, and so on recursively. If $p_1$ is sound, then $p_1\left[p_2\right[s]⟹p_1[s\left]\right]⟹\left(p_2\right[s]⟹p_1[s\left]\right)$ so anything that is proven by $p_2$ can be proven by $p_1$. If $p_1$ isn't sound, it can prove anything anyway.

Note that if $p_2$ is a straightforward isomorphism of $p_1$ then they are easily proven equivalent. However, if $p_2$ says "run Turing machine $T$ for $length\left(b\right)$ steps, if it doesn't halt, check if $b$ is a valid proof of $s$, if $T$ does halt, return $\top$" then it could be equivalent to $p_1$ from a second order logic perspective, but $p_1$ can't prove that $T$ never halts.

Still, this rule allows us to prove anything provable in $p_1$ and only things provable in $p_1$, while also allowing the user to add shorthands and semantic sugar.

Note that the "proof" $b$ could just be the number of processor cycles you want to run a proof search for before giving up. In fact, this framework lets you swap and mix between hand proved results, and automatically proved results (with search time cut off) as you see fit.

This formalism allows a any system containing a proof checker to automatically upgrade itself to a version that has the same Godelian equivalence class, but is more suited to the hardware available.