Proof and verification

Claims about UseCase Forge belong next to evidence that can be inspected and repeated.

Release gates

• static analysis for every Dart and Flutter package;
• package tests, including lifecycle matrices and edge conditions;
• generated API documentation without warnings;
• archive inspection before publication;
• licenses, notices, examples, and intended public files;
• content-hygiene checks for public repositories.

Performance evidence

Benchmark results are interpreted with their runtime, power state, scenario, baseline, candidate, and limitations. JIT and AOT are recorded separately. Hot paths, queues, contention, diagnostics, and Instruction resolution are not collapsed into one marketing number.

• Benchmark methodology — environment, sampling, statistics, and traceability limits.
• Performance results — current medians, queue scaling, regressions, and raw files.
• Comparison with alternatives — capability boundaries for Bloc, Riverpod, MobX, and Redux.
• Disconnected DevTools overhead — the focused bridge experiment and its limits.

Published state

The first development releases of the four public packages are available on pub.dev. Benchmark reports, CSV summaries, full JSON samples, and checksums are published alongside these pages rather than reduced to unsupported claims.