10-Minute Quickstart

Audience: first-time builders
Status: Preview

This quickstart proves the runtime, operation catalog, project proof bundle, event chain, and signed review packet without introducing a second Python model.

0. Run the install doctor

ophiolite doctor

The doctor output is JSON. Treat fail checks as install blockers, and include the full JSON output when reporting issues.

1. Inspect the Operation Catalog

ophiolite operation-catalog
ophiolite-automation verify-surface-contracts

The conformance check verifies that Python automation exposes only cataloged CLI operations.

2. Run the Evaluator Proof Workflow

cargo xtask evaluator-proof

Inspect target\evaluator\post_stack_agc\report.md for the readable report, or report.json for durable run evidence. The bundle proves typed attribute resolution, procedure planning, AGC execution, assertions, artifact digests, source fingerprints, timings, and report rendering.

3. Run the Product Proof Snapshot

cargo xtask product-proof

That writes target\product\post_stack_agc\ with a materialized artifacts\derived_agc.tbvol\ output and a hash-chained event log.

4. Exercise the Python Evidence Loop

python -m pytest python/tests/test_flow_evidence_loop.py -q

That test drives the draft -> validate -> run preview -> materialize -> inspect -> compare -> sign -> packet export -> verify loop entirely through ophiolite_automation over the JSON CLI.

What You Proved

• the Rust CLI is installed and emits JSON
• Python automation stays aligned to the operation catalog
• source fingerprints and run reports are captured in a proof bundle
• materialized runs emit a hash-chained event log
• run bundles and review packets can be signed, verified, and tamper-checked

Next: Evaluator Proof Workflow