Skip to content

Latest commit

 

History

History
16 lines (11 loc) · 1.29 KB

File metadata and controls

16 lines (11 loc) · 1.29 KB

Overview

Formalize each and every tag in Stacks project. Each section should be in a separate file. For example, Section 4.2 with tag 0013 should be named S4_2_0013.ard. The stacks project is mostly self-contained, but if some preliminary is required (e.g., basic facts about groups), put the file under the Foundation directory.

Naming convention

Follow the naming convention of arend-contrib.

Comments

Each tag in Stacks project should be discussed. Use -- tag(1234) on a separate line to mark corresponding parts in the source. When referring to a tag in a comment, use @tag(5678). If some items are not applicable (e.g., automatic in the type-theoretic setting), explain why no code is needed in comments.

If the formalization is notably different from the set-theoretic setting, explain how hPOV simplifies or complicates things with comments starting with "hPOV:". We currently do not distinguish the more precise cause (constructivity, infinite hierarchy of universes, or the homotopy interpretation of path types).

If there is some space for improvement on the Arend side, mark them with comments starting with "Arend:" and report issues on their GitHub repository.