Flow v1.0.0 is here - First stable release!

Flow 1.0.0 is now finalized.

This release is about drawing a hard line around what Flow can actually promise as stable.

The 1.0 Stable surface is now explicitly classified and machine-enforced. Anything that isn't ready for that promise is marked Experimental or Reserved. The compiler also has a self-hosted flowc production path, including bootstrap from checked-in C, compiler-source auditing, and fixed-point self-compilation checks.

The documentation was also put through a fairly brutal cleanup. There are now 594 verified ordinary Flow examples + 9 verified expected-error examples, with zero ordinary code fences left unverified.

The permanent Stable conformance suite checks the language contract independently of individual compiler implementation details, including differential execution between the reference implementation and flowc.

Linux x86-64 and macOS arm64 are the initial Tier-1 platform targets. Release qualification exercises the compiler, builds the distributable compiler, unpacks it, rebuilds it, compiles generated C and then executes a packaged Flow program.

The v1.0.0 release process also gates on version consistency, stability classification, documentation verification, conformance, fuzzing, the strict corpus and self-host auditing that normally happens before publishing.

It's important to state that 1.0 does not mean everything currently implemented in Flow is permanently frozen. Effects, dsys, the formatter, extended numerical APIs, some advanced language forms and alternate backends remain Experimental while that work continues.

More features are coming in future releases, like deeper self-hosting, overload resolution, monomorphisation, effects, numerical performance and tooling. But for now, happy to say that Flow has a stable foundational release to go off of.