projectsetup

To set up an F* and Pulse verification project, you need a scaffold that structures directories for specifications, implementations, and tests, alongside a Makefile for checking modules and C extraction. This provides a separation of code and generated artifacts.

An F* and Pulse codebase directory layout separates pure specifications, machine-width implementations, tests, and generated artifacts. This verification-friendly structure ensures clean module checking and organizes extraction outputs effectively.

Yes, KaRaMeL is required for C extraction in an F* verification project. The project scaffold uses KaRaMeL-aware conventions to generate output and defines when to use .fsti interfaces for extracted APIs.

Yes, you can run OCaml spec tests in a new F* and Pulse project. The scaffold includes an optional workflow for OCaml spec testing, allowing you to validate pure specifications alongside C extraction.

The best way to structure an F* project for verification and C extraction is using a scaffold that separates pure specifications from machine-width implementations. It includes a Makefile flow for module checking and KaRaMeL output generation.

You should use .fsti interfaces in an F* and Pulse codebase when defining extracted APIs. The scaffold establishes KaRaMeL-aware conventions to separate pure specifications from implementations that require interface files.