USE CASE / ROUTE AUDIT

Route audit

A route audit answers a narrower question than planning: what does this route file support, and what evidence is still missing?

Bring the route, keep the data local

RENKIN reads a route file locally. Molecular structures, private stock lists, and policy files do not need to be sent to a hosted service.

Separate checks from claims

The audit report keeps structure integrity, stock coverage, forward replay, provenance, and missing evidence apart. A passed field is not experimental validation.

  • pass: the stated check completed
  • fail: the stated check did not pass
  • partial: only part of the required evidence was available
  • not evaluable: the report cannot support a conclusion

Use the report in a reproducible review

Keep the original route, audit manifest, stock definition, template set, and tool version together when reporting results.

FAQ

Questions before you start

Does route auditing prove a synthesis will work?

No. It evaluates the available route evidence and does not replace experimental validation.

Can I audit a route from another planner?

Yes, where a supported interchange format is available. The audit is intentionally tool-neutral.