[OCaml] High Intensity Training Online
docs state agent process rules
Changed files
.kiro/steering/ocaml.md
@@ -7,8 +7,8 @@
7
7
- The `.mli` files are the specification. They have a higher authority than
8
8
the tests.
9
9
- If an interface and a test do not agree, correct the test.
10
Removed:
- A change to an interface is a design decision. Tell the user about it. Do
11
Removed:
not change an interface without an announcement.
10
Added:
- A change to an interface is a design decision. You can change an interface.
11
Added:
Continue the work. Name each changed interface in your summary.
12
12
13
13
## Style
14
14
.kiro/steering/workflow.md
@@ -12,6 +12,8 @@
12
12
change, use Browser Mode and the web-verify skill to capture rendered
13
13
evidence. If Browser Mode is unavailable, tell the user to turn it on.
14
14
Do not report the change as complete before you capture the evidence.
15
Added:
- If the change touches `lib/core` or a training rule in any layer, run the
16
Added:
doctrine-check skill. Resolve each conflict, or report it to the user.
15
17
2. The touched files are formatted with `ocamlformat --inplace`. Do not use
16
18
`dune fmt` (see Build directory safety).
17
19
3. The documentation agrees with the change.
@@ -82,6 +84,8 @@
82
84
- Keep OCaml documentation short and idiomatic.
83
85
- When a change makes a document stale or redundant, correct or remove the
84
86
document in the same change.
87
Added:
- If you find a stale fact in the steering, do not edit the steering. Tell the
88
Added:
user the fact and the correction.
85
89
- Interface comments state the intention, not the implementation. If one line
86
90
is sufficient, write one line.
87
91
- A module header states the purpose of the module and the invariant that it