Repository navigation
v0.16.17
Control launch and operating cutover
- Step 3 shows each Control's actual implementation state, launch checks, and what marking it Implemented asserts.
- Prospective setup guidance now asks teams to configure and check the control before operation. Dated evidence is collected when the first scheduled cycle or event occurs.
- Policy activation, evidence source readiness, training, and event tasks use the same effective obligation rule and cutover time. Dormant event work cannot be opened early or partially.
- The generated workspace guide explains the separation between setup, cutover, and later operating proof.
Both packages are released at 0.16.17. The active data model remains v11.