lfglabs-dev / lfglabs-dev/verity
Effects: strengthen generated annotations into execution frame theorems
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 148
- Forks
- 20
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 29
Description
Problem
#1729 has landed a useful effect surface (view, modifies, no_external_calls, generated _is_view, _no_calls, _modifies, _frame facts), but the remaining work is proof strengthening.
Today the generated theorems are mostly model-flag and frame-predicate facts. The next milestone should connect effect annotations to execution/spec frame-condition theorems that users can rely on when composing contract proofs.
Scope
- Define the execution-level meaning of
view,modifies, andno_external_calls. - Strengthen generated theorems from model metadata facts to source/interpreter preservation facts where possible.
- Make unsupported effect surfaces fail fast or emit explicit proof obligations.
- Add tests/examples that demonstrate a consumer proof using the stronger frame theorem.
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.
Research direction
Start with the effect surface introduced by #1729, including the generated view, modifies, no_external_calls, _is_view, _no_calls, _modifies, and _frame facts. Trace how execution and specification frame conditions are represented, then define done as explicit effect semantics, fail-fast handling or proof obligations for unsupported surfaces, and a consumer proof test or example.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100