Implementation Coverage

Implementation coverage shows which requirements have implementation evidence and which still need work. It is separate from verification roll-up: coverage proves that an implementable obligation is connected to code, tests, proof evidence, reports, or other artifacts.

Scope

Implementation coverage is scoped to requirements. Capabilities are not directly implementation-covered because capability intent should remain implementation-independent; capability coverage is understood through the requirements that specify the capability.

Included: requirement elements.
Excluded: capability elements as direct implementation targets.
Reported by the same reqvire coverage command that also reports verification coverage.

Coverage Sources

direct_satisfied

The requirement has direct satisfiedBy relation links to implementation or evidence artifacts.

contract_satisfied_via_contract_bindings

The requirement owns a contract and a directly satisfied requirement reuses that contract.

contract_satisfied_via_child

The requirement owns a contract and a derived descendant requirement is directly satisfied.

uncovered

The requirement has no direct satisfaction, no contract-bindings coverage, and no child coverage path.

Linking Implementation

Requirements link to implementation artifacts with satisfiedBy. Multiple artifacts can satisfy one requirement when the implementation is spread across modules, tests, generated fixtures, or proof reports.

#### Relations
  * satisfiedBy: [auth_middleware.rs](../src/auth_middleware.rs)
  * satisfiedBy: [test_access_token.rs](../tests/test_access_token.rs)

Contract Fulfillment

Contract Bindings can make one subgraph depend on a requirement-owned contract from another subgraph. The contract binding is the dependency edge; fulfillment comes from satisfied requirements, descendant requirement coverage, and verification evidence.

The binding requirement declares the contract obligation for its requirement subtree.
Child requirements and contracts can provide the detailed implementation route.
Coverage and change-impact reports keep the bound contract visible for review and hardening.

Report Shape

Text output summarizes totals, covered and uncovered counts, coverage percentage, and source counts. JSON output exposes the same data for CI, dashboards, and assistant workflows.

reqvire coverage
reqvire coverage --json --output coverage.json

total_requirements_in_scope
covered_requirements
uncovered_requirements
implementation_coverage_percentage
coverage_sources