Skip to content

Commit 9ce3954

Browse files
Merge main into nightly-testing
2 parents ab50ad7 + 85518e6 commit 9ce3954

1 file changed

Lines changed: 6 additions & 11 deletions

File tree

CONTRIBUTING.md

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22

33
- [Contributing to CSLib](#contributing-to-cslib)
44
- [Contribution model](#contribution-model)
5+
- [The role of AI](#the-role-of-ai)
56
- [Style and documentation](#style-and-documentation)
67
- [Variable names](#variable-names)
78
- [Proof style and golfing :golf:](#proof-style-and-golfing-golf)
@@ -38,8 +39,6 @@
3839
- [Back ends for Boole](#back-ends-for-boole)
3940
- [Implementing verification paradigms](#implementing-verification-paradigms)
4041
- [Lean automation](#lean-automation)
41-
- [The role of AI](#the-role-of-ai)
42-
4342

4443
# Contributing to CSLib
4544

@@ -57,6 +56,11 @@ If you are adding something new to CSLib and are in doubt about it, you are very
5756

5857
If you are unfamiliar with CSLib as a whole and want to understand how to get started, please see [Getting started](#getting-started).
5958

59+
# The role of AI
60+
61+
CSLib in general follows the Mathlib policy on [use of AI](https://leanprover-community.github.io/contribute/index.html#use-of-ai). In particular, take note of:
62+
> If you use artificial intelligence [...] please explain this in the PR description. Explain which tool(s) you used and how you used it. This provides useful context for reviewers: tools make different mistakes than humans, so knowing this makes it easier to spot common errors.
63+
6064
# Style and documentation
6165

6266
We generally follow the [mathlib style for coding and documentation](https://leanprover-community.github.io/contribute/style.html), so please read that as well. Some things worth mentioning and conventions specific to CSLib are explained next.
@@ -322,12 +326,3 @@ The formal methods community has a wide range of verification techniques that co
322326
Since Boole back ends reduce correctness questions to Lean conjectures, automation is central.
323327

324328
We already rely on key techniques such as `grind` and `lean-smt`. Additional work on automation for conjectures generated from Boole is welcome, including domain-specific automation that remains performant and readable.
325-
326-
#### The role of AI
327-
328-
There are two primary areas where generative AI can help:
329-
330-
- generating/refining specifications (at the front-end or Boole level)
331-
- helping to prove Lean conjectures
332-
333-
Other creative uses of AI are welcome, but contributions should remain reviewable and maintainable.

0 commit comments

Comments
 (0)