Know what is actually on disk

optiflow is a local-first Rust CLI that inventories media collections, proves byte-identical relationships, calculates conservative storage outcomes, and produces immutable plans for human review.

Observe first. Prove relationships. Plan safely.

Choose a path

• Install and run a first scan to exercise the CLI against a directory you control.
• Understand the safety boundary before integrating optiflow with automation.
• Inspect the artifact-set commit protocol to see staging, marker validation, crash recovery, and durability boundaries.
• Inspect the handle-bound observation protocol to see how file races, retries, cache reuse, and refusal are handled.
• Review media-profile evidence to understand the first lossless-PNG candidate contract and why it makes no savings claim.
• Check media capabilities and optimizer strategy to distinguish current inspection/validation from planned production and replacement, and see the OxiPNG and image_optim direction.
• See the operator-ready milestone for the exact release/source pins and the dependency-ordered external-drive path.
• Consume the CLI contract from flow, a shell script, or another subprocess client.
• Configure an effective policy with deterministic precedence, provenance, and fingerprints.
• Explore the architecture for the generated system and document graph, then inspect the runtime architecture to see how observations become evidence-backed reports and plans.
• Place OptiFlow in the platform to understand how CNCF capabilities fit around the portable product boundary.
• Inspect the performance budgets for the reproducible discovery, hashing, cache-reuse, memory, and artifact-size regression guard.

What the release and current source prove

The published v0.1.0 release proves read-only inventory and exact duplicate groups from equal logical size plus equal complete BLAKE3-256 content hashes. Its report preserves the evidence used to make that claim. A generated plan is a separate, immutable, review-only artifact with preconditions for a future execution boundary.

Post-release main adds report v6 and can preserve a deterministic review opportunity for byte-classified PNG inputs when current provider evidence is complete. That behavior is not retroactively present in the v0.1.0 binary. It is analysis only: it creates no optimized output and estimates no savings.

inputs
  -> effective policy
  -> conservative discovery
  -> content inventory
  -> exact evidence
  -> immutable report
  -> review-only plan
  -> typed command result

Machine-readable contracts

Every JSON command returns one optiflow.command-result.v1 envelope. Run, report, plan, configuration, and effective-policy documents have independent schema identifiers so consumers can evolve safely without coupling to the Rust implementation.

The checked-in contracts live in the schemas/ directory.