Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Alethe
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Admin message
Pour rappel, le service sera inaccessible ce lundi 05/05/25 midi pour raison de mise à jour.
Show more breadcrumbs
veriT
Alethe
Commits
0c8d4fb3
Commit
0c8d4fb3
authored
1 year ago
by
Hans-Jörg
Browse files
Options
Downloads
Patches
Plain Diff
Start defining contexts
parent
d8008d63
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
althelf/README.md
+18
-5
18 additions, 5 deletions
althelf/README.md
althelf/alethe.smt3
+10
-8
10 additions, 8 deletions
althelf/alethe.smt3
with
28 additions
and
13 deletions
althelf/README.md
+
18
−
5
View file @
0c8d4fb3
...
...
@@ -5,7 +5,7 @@ fulfill some restrictions (For example, all conclusions must be printed),
and use a specific signature. The signature collects the Alethe proof rules.
To avoid confusion, this document refers to Alethe as "Alethe Classic".
An Althe Classic consumer should be able to use the AltheLF proofs, by only
An Al
e
the Classic consumer should be able to use the AltheLF proofs, by only
changing its parser.
## Changes
...
...
@@ -13,7 +13,20 @@ changing its parser.
*
We assume that AletheLF is extended with a
`:match-conclusion`
feature
that captures the conclusion of the step. This is very useful for Alethe
Classic proofs, since they allow us to avoid extra arguments.
*
`cl`
is not unary, instead
`(cl)`
is the term
`false`
. Hence, a the simple
`false`
term should be parsed as the empty clause, and
`cl false`
is the
clause containing the literal
`false`
.
*
Sharing doesn't use
`!named`
, but instead uses
`define`
statements.
*
`cl`
cannot be used without arguments. To write
`(cl)`
AletheLF uses the term
`false`
. Hence, a the simple
`false`
term should be parsed as the empty
clause, and
`cl false`
is the clause containing the literal
`false`
.
*
Sharing doesn't use
`! .. :named`
, but instead uses
`define`
statements.
## Contexts
Alethe Classic has a notion of contexts used to reason about binders. Contexts
are lists of variable assignments and shadowings (self assignments). In AletheLF
a context is represented as a conjunction of equalities
`= x t`
where
`x`
is a
variable and
`t`
a term.
Since context are scoped, we use AletheLF's context mechanism. The extended
context become assumptions of the scope and premises of steps that use contexts.
Hence, the equivalent to an
`anchor`
is an
`assume-push`
. The
context-manipulating rules are rules with
`:assumption`
that check that the
assumption is the appropriately extended context.
This diff is collapsed.
Click to expand it.
althelf/alethe.smt3
+
10
−
8
View file @
0c8d4fb3
...
...
@@ -43,10 +43,10 @@
:match-conclusion CL
)
% TODO
(declare-rule subproof ()
:
arg
s ()
:conclusion
true
(declare-rule subproof ((F Bool) (G Bool))
:assumption F
:
premise
s (
G
)
:conclusion
(=> F G)
)
% TODO: side condition
...
...
@@ -76,10 +76,12 @@
:match-conclusion CL
)
% TODO
(declare-rule bind ()
:args ()
:conclusion true
% TODO: side conditiion
(declare-rule bind ((ctx Bool))
:assumption ctx
:premises ((cl (= phi phi')))
:requires ((check_bind ctx xs ys) true)
:match-conclusion (cl (= (forall xs phi) (forall ys phi')))
)
% TODO
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment