Files
openprose__prose/packages/std/ops/README.md
dan 012650a201 [codex] Prepare OpenProse 0.12.0 responsibility runtime release (#57)
* Document native runtime skill semantics

* Rename native runtime to responsibility runtime

* Add responsibility runtime compiler skeleton

* Add responsibility compilation IR

* Compile Forme manifests into repository IR

* Serve static repository IR

* Tighten responsibility runtime review gaps

* Introduce OpenProse root model

* Harden OpenProse root resolution

* Add responsibility judge activation

* Add responsibility pressure fulfillment path

* Add repository status inspection

* Make triggers concrete gateway registrations

* Add live responsibility trigger adapters

* Refine responsibility runtime validation

* Harden responsibility runtime freshness

* Tighten responsibility runtime guardrails

* docs: replace skill examples with native repositories

* chore: release v0.12.0

* fix: tighten release review gaps
2026-05-04 09:26:26 -07:00

27 lines
1.5 KiB
Markdown

# std/ops
Operational utilities for debugging, profiling, and validating OpenProse systems. These are the developer tools of the language -- the equivalent of `git status`, `cargo check`, and `go vet`. Each system maps to a `prose` CLI command.
## Systems
| System | CLI Command | Description |
|---------|-------------|-------------|
| `lint.prose.md` | `prose lint <file>` | Validate structure, schema, shapes, and contract matching |
| `preflight.prose.md` | `prose preflight <file>` | Check that dependencies are installed and environment variables are set |
| `wire.prose.md` | `prose run std/ops/wire` | Run Forme wiring to produce an execution manifest |
| `status.prose.md` | `prose status` | Show recent runs with system name, duration, and pass/fail status |
| `diagnose.prose.md` | `prose run std/ops/diagnose` | Diagnose why a run failed -- root cause analysis with fix recommendations |
| `profiler.prose.md` | `prose run std/ops/profiler` | Profile a run for cost, tokens, and time using actual API session data |
## Two categories
**Source-file tools** operate on system `*.prose.md` files before execution:
- `lint` -- validates that the system is well-formed
- `preflight` -- validates that the runtime environment is ready
- `wire` -- produces the execution manifest (Forme wiring)
**Run-artifact tools** operate on completed runs in `<openprose-root>/runs/`:
- `status` -- lists recent runs and their outcomes
- `diagnose` -- investigates a failed run to find the root cause
- `profiler` -- breaks down cost, time, and token usage from actual session data