Continuity pledge

Your graphs and the programs flowRS writes are yours and do not depend on flowRS staying in business.

1. Every program flowRS exports carries its own build: its Cargo.lock, flowRS's runtime crates as source under MIT OR Apache-2.0, its form contract and its software bill of materials. It builds with Rust's own tools and the public crates its lock names: no flowRS checkout, no account and no key.
2. The graph document format is published, with a schema and a conformance corpus. flowRS will keep reading every format-1 document.
3. The graph engine and the command-line tool that read, check, run and export a graph without the editor are published as source under Apache-2.0: the engine's repository, mirrored at Codeberg. A few of its crates are under MIT OR Apache-2.0, and what it carries from others keeps its own licence, named beside it.
4. If the hosted service at flowrs.openie.dev is to close, we will say so at least 90 days before, keep export of every document working until it closes, and publish the source of the editor and the server under Apache-2.0 on the day it closes.
5. We will make these promises a condition of any sale of flowRS.

These promises stand apart from the terms: changing the terms does not change them.

Check it yourself

The engine builds with nothing of flowRS's but its own source:

git clone https://git.transaction.science/Transaction-Science/flowrs-engine
cd flowrs-engine
cargo build --locked -p flowrs-cli
target/debug/flowrsc check spec/conformance/flowrs/add-two-numbers.flowrs
target/debug/flowrsc run spec/conformance/flowrs/add-two-numbers.flowrs --tier t0
target/debug/flowrsc app spec/conformance/flowrs/add-two-numbers.flowrs -o my-app