Add contest book (#6)

Add initial book and a workflow to build / deploy the book. I also created a few other configurations that we were missing.

Co-authored-by: Jaisurya Nanduri <91620234+jaisnan@users.noreply.github.com>

.github/CODEOWNERS

@@ -0,0 +1,4 @@
+# Copyright Kani Contributors
+# SPDX-License-Identifier: Apache-2.0 OR MIT
+
+*   @model-checking/kani-devs

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+> Please add a description of your PR.
+> If this is a solution to an open challenge, please explain your solution.
+>
+> Don't forget to check our book to ensure your solution satisfy the overall
+> requirements as well as the challenge success criteria.
+>
+
+Resolves #ISSUE-NUMBER
+
+By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

.github/dependabot.yml

@@ -0,0 +1,11 @@
+# Copyright Kani Contributors
+# SPDX-License-Identifier: Apache-2.0 OR MIT
+
+# https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/book.yml

@@ -0,0 +1,53 @@
+# Copyright Kani Contributors
+# SPDX-License-Identifier: Apache-2.0 OR MIT
+name: Build Book
+on:
+  pull_request:
+    paths:
+      - 'doc/**'
+  push:
+    paths:
+      - 'doc/**'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Install mdbook
+        run: cargo install mdbook --version "^0.4" --locked
+
+      - name: Install linkchecker
+        run: cargo install mdbook-linkcheck "0.7" --locked
+
+      - name: Build Documentation
+        run: mkdbook build doc
+
+      - name: Upload book
+        uses: actions/upload-pages-artifact@v4
+        with:
+          path: book/html
+          retention-days: "2"
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    if: ${{ github.event_name == 'push' && startsWith('refs/heads/main', github.ref) }}
+
+    # Grant GITHUB_TOKEN the permissions required to make a Pages deployment
+    permissions:
+      pages: write      # to deploy to Pages
+      id-token: write   # to verify source
+
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4
+
+

.gitignore

@@ -0,0 +1,54 @@
+# Copyright Kani Contributors
+# SPDX-License-Identifier: Apache-2.0 OR MIT
+
+## File system
+.DS_Store
+desktop.ini
+
+## Editor
+*.swp
+*.swo
+Session.vim
+.cproject
+.idea
+*.iml
+.vscode
+.project
+.favorites.json
+.settings/
+*.orig
+*.rej
+
+## Build
+/book/
+/build/
+/target
+*.rlib
+*.rmeta
+*.mir
+
+## Temporary files
+*~
+\#*
+\#*\#
+.#*
+
+## Python
+__pycache__/
+*.py[cod]
+*$py.class
+
+## Node
+node_modules
+package-lock.json
+
+# Tools
+## Kani
+*.out
+
+
+# Added by cargo
+#
+# already existing elements were commented out
+
+#/target

doc/book.toml

@@ -0,0 +1,25 @@
+# Copyright Kani Contributors
+# SPDX-License-Identifier: Apache-2.0 OR MIT
+[book]
+title = "Verify Rust Std Lib Contest"
+description = "Contest Rules and Challenges"
+authors = ["Kani Developers"]
+language = "en"
+multilingual = false
+
+[build]
+build-dir = "../book"
+
+[output.html]
+site-url = "/verify-rust-std/"
+git-repository-url = "https://github.com/model-checking/verify-rust-std"
+edit-url-template = "https://github.com/model-checking/verify-rust-std/edit/main/doc/{path}"
+
+[output.html.playground]
+runnable = false
+
+[output.linkcheck]
+
+
+[rust]
+edition = "2021"

doc/src/SUMMARY.md

@@ -0,0 +1,15 @@
+# Verify Rust Std Lib
+
+[Introduction](intro.md)
+
+- [General Rules](./general-rules.md)
+  - [Challenge Template](./template.md)
+
+- [Verification Tools](./tools.md)
+  - [Kani](./tools/kani.md)
+
+
+---
+
+# Challenges
+- [Coming soon](./todo.md)

doc/src/general-rules.md

@@ -0,0 +1,81 @@
+# General Rules
+
+## Terms / Concepts
+
+**Verification Target:** [Our repository](https://github.com/model-checking/verify-rust-std) is a fork of the original Rust repository,
+and we kept a copy of the Rust standard library inside the `library/` folder that shall be used as the verification target for all our challenges.
+We will periodically update the `library/` folder to track newer versions of the [official Rust standard library](https://github.com/rust-lang/rust/).
+NOTE: This work is not officially affiliated, or endorsed by the Rust project or Rust Foundation.
+**Challenges:** Each challenge will be documented in the contest book in the Challenges chapter, and they will have a
+tracking issue where participants can add comments and ask clarification questions.
+You can find the list of [open challenges here](https://github.com/model-checking/verify-rust-std/labels/Challenge).
+
+**Solutions:** Solutions to a challenge should be submitted as a single Pull Request (PR) to the contest repository.
+The solution should run as part of the CI.
+See more details about [minimum requirements for each solution](general-rules.md#solution-requirements).
+
+
+## Basic Workflow
+
+1. A challenge will be published in the contest book with details of the challenge,
+   and a tracking issue labeled with “Challenge” will be opened, so it can be used for clarifications and questions,
+   as well as to track the status of the challenge.
+2. Participants should create a fork of the contest repository where they will implement their proposed solution.
+3. Once they are to submit their solution for analysis, participants should create a PR against the contest repository for analysis.
+   Please make sure your solution meets [the minimum requirements described here](general-rules.md#solution-requirements).
+4. Each contribution will be reviewed on a first come, first served basis.
+   Acceptance will be based on a unanimous affirmative vote from the review committee.
+5. Once approved by the review committee, the change will be merged into the repository.
+
+## Solution Requirements
+
+A proposed solution to a contest will only **be reviewed** if all the minimum requirements below are met:
+
+* Each contribution or attempt should be submitted via a pull request to be analyzed by the committee.
+* By submitting the solution, participants confirm that they can use, modify, copy, and redistribute their contribution,
+  under the terms of their choice.
+* The contribution must be automated and should be checked and pass as part of the PR checks.
+* All tools used by the solution must be in [the list of accepted tools](tools.md#approved-tools),
+  and previously integrated in the contest repository.
+  If that is not the case, please submit a separate [tool application first](todo.md).
+* There is no restriction on the number of contributors for a solution.
+  Make sure you have the rights to submit your solution and that all contributors are properly mentioned.
+* The solution cannot impact the runtime logic of the standard library unless the change is proposed and incorporated
+  into the Rust standard library.
+
+Any exception to these requirements will only be considered if it is specified as part of the acceptance criteria of the
+challenged being solved.
+
+## Call for Challenges
+
+The goal of the contest is to enable the verification of the entire Rust standard library.
+The type of obstacles users face may depend on which part of the standard library you would like to verify. Thus, our challenges are developed with the target of verifying a specific section of the standard library or strengthening existing verification.
+
+Everyone is welcome to submit new challenge proposals for review by our committee.
+Follow the following steps to create a new proposal:
+
+1. Create a tracking issue using the Issue template [Challenge Proposal](todo.md) for your challenge.
+2. In your fork of this repository do the following:
+    1. Copy the template file (`book/src/challenge_template.md`) to `book/src/challenges/<ID_NUMBER>-<challenge-name>.md`.
+    2. Fill in the details according to the template instructions.
+    3. Add a link to the new challenge inside `book/src/SUMMARY.md`
+    4. Submit a pull request.
+3. Address any feedback in the pull request.
+4. If approved, we will publish your challenge and add the “Challenge” label to the tracking issue.
+
+## Tool Applications
+
+Solutions must be automated using one of the tools previously approved and listed [here](tools.md#approved-tools):
+
+* Any new tool that participants want to enable will require an application using the Issue template [Tool application](todo.md).
+* The tool will be analyzed by an independent committee consisting of members from the Rust open-source developers and AWS
+* A new tool application should clearly specify the differences to existing techniques and provide sufficient background
+  of why this is needed.
+* The tool application should also include mechanisms to audit its implementation and correctness.
+* Once the tool is approved, the participant needs to create a PR that creates a new action that runs the
+  std library verification using the new tool, as well as an entry to the “Approved Tools” section of this book.
+* Once the PR is merged, the tool is considered integrated.
+* The contest repository will be updated periodically, which can impact the tool capacity to analyze the new version of the repository.
+  I.e., the action may no longer pass after an update.
+  This will not impact the approval status of the tool, however,
+  new solutions that want to employ the tool may need to ensure the action is passing first.

doc/src/intro.md

@@ -0,0 +1,14 @@
+# Verify Rust Standard Library Contest
+
+The Verify Rust Standard Library contest is an ongoing contest that targets the verification of the [Rust standard library](https://doc.rust-lang.org/std/). The goal of this contest is to provide automated verification that can be used to verify that a given Rust standard library implementation is safe.
+
+The contest will contain several challenges that can be solved by participants. These challenges can take on one of many forms such as:
+
+1. Contributing to the core mechanism of verifying the rust standard library
+2. Creating new techniques to perform scalable verification
+3. Apply techniques to verify previously unverified parts of the standard library.
+
+
+We encourage everyone to watch this repository to be notified of any changes.
+
+In this book you can find more details about the contest such as: General Rules, Challenges, Verification Tools.

doc/src/template.md

@@ -0,0 +1 @@
+# Challenge Template

doc/src/todo.md

@@ -0,0 +1,3 @@
+# 🚧 Under Construction 🚧
+
+This section is still under construction. Please check it back again soon and we’ll have more details for you.

doc/src/tools.md

@@ -0,0 +1,18 @@
+# Verification Tools
+
+The verification tool ecosystem for Rust is rapidly growing, and we welcome the usage of different tools to solve our challenges.
+In this chapter, you can find a list of tools that have already been approved for new solutions,
+what is their CI current status, as well as more details on how to use them.
+
+If the tool you would like to add a new tool to the list of tool applications,
+please see the [Tool Application](general-rules.md#tool-applications) section.
+
+## Approved tools:
+
+| Tool      | CI Status |
+|-----------|-----------|
+ | Kani     | TODO      |
+
+
+
+

doc/src/tools/kani.md

@@ -0,0 +1 @@
+# Kani Rust Verifier