Status: Active OpenSpec proposal; not implemented or deployed. The source under
openspec/changes/is authoritative.
Context
The repository is greenfield. This change must cross the real CLI, parser, obligation model, reporting, and exit boundary without implying broad MVP coverage.
Goals / Non-Goals
- Goals: one deterministic Rust
i32/zero path; all three obligation states; guidance/gate behavior; immutable source files. - Non-goals: other numeric boundaries or types, return assertions, reachability inference, diff scoping, JSON/SARIF, Vampiro input, or unsupported frameworks.
Test Shape
Integration fixtures provide a Cargo workspace, one explicit free-function
i32 parameter, and zero, non-zero, or runtime-computed arguments in built-in
#[test] functions. Tests assert diagnostics, obligation state, and exact exit
status. Parser/unit tests cover classification precedence.
Decisions
- Parse Rust statically; never compile or execute the analyzed workspace.
- A literal
0direct argument covers the obligation. Only definite non-zero literals make it uncovered. A runtime-computed argument with no literal-zero match makes it indeterminate; a definite zero match takes precedence. - Human output has one stable line per obligation, sorted by file, line, function, parameter, and boundary. Uncovered lines are findings; indeterminate lines are diagnostics.
- Guidance always exits zero after a successful scan. Gate exits with the policy-failure code only for an uncovered tracer finding. The implementation shall separately document and test numeric policy and operational exit codes.
Risks / Trade-offs
- The narrow syntax can look like general Rust support. Help and diagnostics must label it a tracer and report encountered unsupported constructs.
- Adding a parser dependency shapes later architecture. Keep parsing behind a front-end interface and avoid exposing parser types in the obligation model.
Approval Gate
Implementation SHALL NOT begin until a human approves this proposal and the normative EARS source.