Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Status: Active OpenSpec proposal; not implemented or deployed. The source under openspec/changes/ is authoritative.

ADDED Requirements

Requirement: Rust i32 zero obligation classification

The system SHALL statically inspect explicit i32 parameters on Rust free functions and direct calls from built-in #[test] functions, without compiling, executing, or modifying the analyzed workspace. For the built-in numeric zero boundary it SHALL classify each obligation as exactly covered, uncovered, or indeterminate according to REQ-4, REQ-6, REQ-7, and REQ-19.

Scenario: Literal zero covers the obligation

  • WHEN a built-in #[test] function directly calls the analyzed function with literal 0 for its explicit i32 parameter
  • THEN the zero obligation is covered and no coverage-gap finding is emitted

Scenario: Definite non-zero calls leave a gap

  • WHEN every direct test call passes a definite non-zero integer literal for the parameter
  • THEN the zero obligation is uncovered and one coverage-gap finding is emitted

Scenario: Runtime value is indeterminate

  • WHEN there is no definite zero match and at least one direct test call passes a runtime-computed value
  • THEN the zero obligation is indeterminate, an indeterminate diagnostic is emitted, and no coverage-gap finding is emitted

Scenario: Definite coverage takes precedence

  • WHEN one direct test call passes literal 0 and another passes a runtime-computed value
  • THEN the zero obligation is covered

Requirement: Tracer reporting and mode exits

The system SHALL emit deterministic human-readable obligation output carrying the REQ-5 fields available to this tracer: rule ID, file, line, boundary name, reachability class, and shape source. Guidance mode SHALL return success after a successful scan. Gate mode SHALL return the documented policy-failure exit only for an uncovered, reachable tracer obligation, and SHALL return success for covered and indeterminate obligations (REQ-11, REQ-12, REQ-19).

Scenario: Uncovered obligation gates

  • WHEN gate mode successfully scans an uncovered zero obligation
  • THEN it emits one reachable standalone coverage-gap finding and exits with the documented policy-failure status

Scenario: Indeterminate obligation does not gate

  • WHEN gate mode successfully scans an indeterminate zero obligation
  • THEN it emits an indeterminate diagnostic and exits successfully

Scenario: Guidance reports without gating

  • WHEN guidance mode successfully scans an uncovered zero obligation
  • THEN it emits the finding and exits successfully

Requirement: Explicit tracer scope

The system SHALL identify this capability as limited to stable Rust, built-in #[test] functions, explicit free-function i32 parameters, direct calls, and the zero boundary. Encountered unsupported languages, frameworks, or Rust constructs SHALL be reported explicitly and SHALL NOT be interpreted as evidence of covered or uncovered obligations.

Scenario: Unsupported test construct is visible

  • WHEN the scan encounters a macro-generated test relevant to a tracer candidate
  • THEN it reports the construct as unsupported and does not classify that construct as a definite match or non-match