Pyk RPC prover not interpreting K funcitonal claims as equality proofs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by inspecting the JSON produced by kprove --dry-run --emit-json ... and determine whether the frontend adds an inferred K cell to functional claims. Trace how the Pyk RPC prover classifies those claims versus reachability queries. Done means functional claims become equality predicates simplified to #Top, while reachability queries retain their existing behavior.
Written by the indexing model from the issue text.
Description
Currently, we are using kprove --dry-run --emit-json ... to read in specifications for the pyk RPC prover. This is good because we get access to the parser, but it also makes it so that we are not able to tell whether something is a functional claim or not. For functional claims, we want to build equality predicates instead, and simplify those to #Top. Currently, instead it discharges them like reachability queries (which is more similar to an implication check than a conditional equality check).
I'm not sure if this can be fixed without modifying the frontend. For example, we made need to add an argument to kprove --dry-run --emit-json ... that says: --no-infer-k-cell ..., which leaves a given proof alone if there is no K cell attached to it.
I need to inspect the generated JSON more to determine if the frontend is adding this inferred K cell or not.
- Dominant language
- Python
- Stars
- 591
- Forks
- 163
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from runtimeverification/k
-
runtimeverification/k#4939 · 1 assignee ·
-
Concolic Explorer Open
Difficulty 5/5 Over a week Newbie friendliness 32/100
runtimeverification/k#4937 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
runtimeverification/k#4936 ·
-
type:epic
runtimeverification/k#4934 · 4 comments · 1 assignee ·
-
runtimeverification/k#4924 · 1 assignee ·
All issues in runtimeverification/k
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100