# rvt-inspect
`rvt-inspect` is the support-facing command for a quick file health and export
readiness answer. It avoids reverse-engineering terminology in the default text
output and writes a stable JSON report with `--json`.
The diagnostic terms used here are defined in
[Diagnostic Semantics](diagnostic-semantics.md). The important distinction is
that opening and inspecting a file can succeed even when model conversion is
partial or scaffold-only.
```bash
rvt-inspect model.rvt
rvt-inspect model.rvt --json
```
The report answers:
| `failure_mode` | Stable user-facing classification such as `unsupported_revit_version`, `unsupported_model_layout`, `incomplete_model`, `partial_decode`, or `scaffold_only_export`. |
| `file` | File opened, Revit version/build, verified version range, stream count, schema parse status. |
| `decoded` | Class count, validated elements, diagnostic candidates, ArcWall records, geometry count. |
| `export` | IFC readiness level, score, building element counts, unsupported features. |
| `warnings` | User-facing caveats from the export diagnostics sidecar. |
| `next_steps` | Short actions appropriate for the current readiness level. |
| `export_diagnostics` | The full diagnostics payload also used by `rvt-ifc --diagnostics`. |
## Reading The Result
`rvt-inspect` treats metadata/schema inspection as useful work. A report can
therefore be successful while still warning that no validated elements or
geometry were decoded.
| `failure_mode.kind` is `corrupt_file` | The input could not be opened as a readable Revit OLE/CFB container. |
| `failure_mode.kind` is `unsupported_revit_version` | The file opened, but its Revit version is outside the verified support range. |
| `failure_mode.kind` is `unsupported_model_layout` | The file is in a supported container/version range, but decoded records did not meet the production model confidence bar. |
| `failure_mode.kind` is `incomplete_model` | Model elements were exported, but `export_diagnostics.confidence.unexported_element_records` records use an element-record layout whose ElementId this release cannot locate (RE-30), so the IFC is missing them. The readiness score is scaled down by the exported share. |
| File/schema fields present, no export warnings | Inspection succeeded and no obvious export caveat was reported. |
| `export.level` is `scaffold` | The IFC path can write a valid framework, but no validated building elements were decoded. |
| `decoded.diagnostic_candidates` is greater than zero | Research scans found low-confidence candidates that are not production model elements. |
| `decoded.geometry_elements` is zero | Geometry workflows are not supported for this file yet. |
| `warnings` is non-empty | Read the warnings before relying on exported IFC/glTF/SVG output. |
## JSON Schema
`schema_version` is currently `1`. Additive fields may be introduced in minor
releases. Incompatible changes must increment this number.
By default, paths are redacted so the output is safer to share in bug reports.
Use `--no-redact` only for private/local diagnostics where original paths are
needed.