You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The role assignment in buildExpr (binder type → input, body → output, operands → input, etc.) is currently a design choice, not a proven-correct one. There is no theorem that the hypergraph "means the same thing" as the Expr.
Goal
Define a reference semantics — what does a proof hypergraph mean? (e.g. an interpretation back into a logical/type-theoretic object).
Prove the conversion preserves meaning — ⟦exprToProofHypergraph e⟧ = ⟦e⟧ under that semantics.
Notes
This is a research / design issue: it cannot be stated as a theorem until the reference semantics is defined. Blocked on that definition.
Context
The role assignment in
buildExpr(binder type →input, body →output, operands →input, etc.) is currently a design choice, not a proven-correct one. There is no theorem that the hypergraph "means the same thing" as theExpr.Goal
⟦exprToProofHypergraph e⟧ = ⟦e⟧under that semantics.Notes
Part of the verification roadmap (see #81).