Final Release Discipline

release/final-discipline.tsv is the release-readiness inventory for the

production roadmap. It lists the gates that must pass before a release may claim

production readiness for its covered surface.

This document and make final-release-discipline-check are bounded source

checks. They do not run the heavy final gates. The heavy gates remain explicit

release operations because they can compile, self-host, run app suites, verify

release hashes, and consume enough resources to affect this host.

Required Areas

The final discipline inventory must cover:

• type system gates;
• runtime memory and host-effect gates;
• framework runtime gates;
• package registry and resolver gates;
• backend coverage and compatibility matrix gates;
• ABI source, layout, and executable compatibility gates;
• Index and Kukulkan app runtime gates;
• release schema, helper, package-layout, source-audit, and compatibility gates;
• ADR/RFC governance;
• public docs acceptance, release, drift, and completion gates;
• security and performance evidence;
• self-host and release verification.

Upgrade, Downgrade, And Rollback

Every release must identify the supported compatibility window and rollback

artifacts:

• release manifests and SHA256SUMS for compiler artifacts;
• release/manifest-schema.tsv for manifest compatibility;
• compat/abi-matrix.tsv for ABI/object/archive/linker compatibility;
• package registry yanks, checksums, and rollback metadata;
• Index and Kukulkan rollback manifests;
• public docs static-site rollback bundles and smoke evidence.

Downgrade support is not implicit. A release can claim downgrade support only

when the final discipline gate references a rollback artifact that

has an executable check.

Security

Security release evidence includes:

• make runtime-host-security-check for denied host effects and runtime

capability boundaries;

• make apps-security-reliability-production-check for app threat-model,

incident-drill, dependency outage, and hardening evidence;

• public disclosure, advisory, key rotation, and dependency trust docs before

external publication claims are made.

Performance

Performance release evidence includes:

• make memory-check for release compiler and runtime memory reports;
• make rss-limit-check for the bounded RSS report contract;
• app performance budgets and generated summaries for Index/Kukulkan release

candidates.

Public Documentation

Public docs must be release-blocking when public behavior, domains, packages,

or rollback guidance changes. The final discipline inventory includes

make public-docs-milestone-10-check, make public-docs-drift-check, and

make documentation-impact-check so the support matrix, release checklist,

redirects, static bundles, search index, completion evidence, and behavior-docs

review remain truthful.

Completion Rule

Passing make final-release-discipline-check means the final release contract

is complete and synchronized. It does not mean production readiness has been

achieved. A release can claim production readiness only after every required

row in release/final-discipline.tsv has been executed and the release notes

name any remaining gaps.