Feature-Freeze Policy (Beta / Release-Candidate)

During release-candidate preparation, Karkain operates under a temporary feature freeze. The goal is to harden the Beta stable core by removing unnecessary churn, while still fixing genuine problems.

Scope of the freeze

The freeze covers the Beta stable core and the release-candidate readiness surface only. A freeze does not prevent work on the roadmap; it controls what is allowed into the stable line before RC.

What is not allowed (during freeze)

  • No new major language features.

  • No unnecessary syntax changes.

  • No broad standard-library redesign.

  • No compiler architecture rewrite.

  • No speculative refactoring that could change semantics.

  • No new Implemented / Experimental items added to the stable core without a documented justification and a dedicated gate.

What is allowed

  • Bug fixes that restore documented behavior.

  • Security fixes (see SECURITY.md).

  • Documentation corrections.

  • Release tooling and packaging fixes.

  • Developer-experience fixes (clarity of diagnostics, correctness of explain codes, clean-up of help text).

  • Compatibility fixes (engine parity, target-model correctness, workspace dependency resolution).

  • Deterministic-correctness fixes (correctness of checked operations, precision of runtime error: diagnostics).

Gate discipline during freeze

Any change allowed by this policy must still:

  1. Keep the Phase 117 regression baselines green (conformance 59/59, probes 11/11, example parity 49/49, verify-examples 49 pass / 0 fail).

  2. Pass the Phase 118 release-candidate gate (pkg/cli/phase118_rc_test.go).

  3. Pass strict Sphinx + linkcheck.

  4. Not introduce new *.exe, *.c / *.c23 or docs/build pollution.

Deprecation during freeze

During feature freeze, deprecation of stable APIs is handled as follows:

  • Document the deprecation in the relevant module documentation

  • Add deprecation warnings where feasible (future @deprecated attribute)

  • Maintain deprecated APIs for the current release

  • Schedule removal for the next MAJOR version

See Semantic Versioning Policy (SemVer) for the full deprecation process and versioning rules.

How long does the freeze last?

The freeze lasts from the start of RC preparation through the RC decision. If RC is deferred, the freeze continues until the next RC decision point or until 1.0 enters active development, whichever comes first.

Unfreezing

When the project moves into 1.0 active development, the freeze is lifted and the new development conventions are documented in Roadmap and the updated release notes.

See also

Release-Candidate Scope — the release-candidate scope. Compatibility Policy — the compatibility policy during freeze. Release Engineering — the release engineering process. Release-Candidate Checklist — the acceptance checklist that gates RC declaration.