# Published CLI consumer inputs

For installation and evaluation commands, follow the
[first-result guide included in the source archive](../../../../docs/first-result.md).
The reader also exports these files as `consumer-inputs.zip`; use the
[published guide](https://mmkolpakov.github.io/robotics-runtime/docs/first-result.html#install-and-obtain-the-inputs)
with that standalone download. Its `manifest.json` records the source revision
and per-file SHA-256. PyPI installation alone does not install the examples.

`scenario-input.json` is an authored synthetic scenario; `runtime-template.json`
contains explicitly synthetic runtime facts. `produce.py` uses public contracts
writers and the upstream MCAP writer to create the scenario, runtime, run
context, synthetic OTLP JSON-lines stream, one UInt64 MCAP recording, recording
summary and finalized evidence index. It has no repository or test support imports.

```bash
python produce.py --output inputs
```

Choose a new output directory per production. The producer refuses an existing
directory. Evidence links use absolute paths to the generated source files; retain
those files in place for evaluation. File sizes and digests are derived from the
generated bytes rather than supplied placeholders.

The expected offline outcome is `incomplete`, exit `1`, with JSON and JUnit; the
guide lists the coverage a live `passed` verdict needs. The synthetic runtime
identities and graph declarations qualify no live execution, image or simulator.
See the guide for all commands, file ownership, missing coverage and a
byte-integrity refusal.
