Documentation and teaching closeout requirements

September 7, 2026 — development process update. This change introduces no compiler release, language feature, or runtime behavior.

Janus now makes the implementation owner responsible for documentation and teaching within the originating task. Each sprint/milestone requires a public progress or release note, including periods containing only internal work. Substantial implementations update affected references and examples. Every solid new feature requires reference documentation, a worked tutorial, and a new Monastery lesson. Corrections update affected existing lessons.

The completion procedure defines the triggers and required evidence. Closeout records distinguish prepared files, integrated changes, and verified publication. Missing required work keeps feature/milestone completion pending; it cannot be replaced by a general “docs updated where applicable” checkbox.

The hardening roadmap prioritizes a coherent AOT alpha, then native scripting and managed memory. Monastery stays in prelaunch mock mode through those two milestones. Its Janus-authored WASM engine prototype belongs to milestone 3 and launch readiness to milestone 4. Lessons and native example verification continue throughout; mock output is not test evidence.

This work updates operating rules, contributor checklists, the evaluation roadmap, and teaching-readiness documentation. It leaves compiler/runtime code and the mock UI behavior unchanged. Site builds and content validation check these documentation changes; future language features require their own compiler-backed acceptance evidence.