Check reference

Check declared interface coverage

A service boundary needs a contract that both sides can review. interface_coverage checks the declared interface structure for missing coverage and broken references.

What the check observes

The analyzer uses the project's requirement and interface records to find components without interface specifications, interfaces without covering requirements, and broken component references. Structured interface metadata distinguishes participants, including external parties. A component that genuinely has no interface may carry a reasoned no_interface attestation in its variables file. That attestation addresses the no-interface finding only; it does not excuse broken references or an uncovered declared interface.

Example: a leaf analysis component has no boundary

Illustrative case. An internal data model is consumed within one analysis stage and exposes no cross-component contract. An explicit attestation is more informative than an invented interface requirement with no real behavior.

# Component .vars.yaml excerpt
no_interface:
  declared: true
  reason: "Internal data model consumed only within the analysis stage; no cross-component boundary."

Resolve the finding

Inspect the named component pair or nearest-match diagnostic. Check names and structured interface fields before creating new requirements.
For a real boundary, write its inputs, outputs, assumptions, failures, and responsible participants, then connect its requirement coverage.
Use an attestation only for a genuinely absent boundary. Declare external parties explicitly rather than creating internal requirements for software the project does not own.

Run and interpret

proof audit --check interface_coverage --verbose

The current implementation reports specification-stage warnings. The interface gap analysis reads the project's requirement corpus. A selected spec in the gaps command does not confine covering candidates to that spec, because interface requirements and their covering requirements often live at different levels.

Coverage is relative to the interfaces and components represented in the analysis. It does not discover every production network call or prove protocol compatibility. An attestation has a reason-length validation rule, but satisfying that rule does not establish that the architectural claim is true.

Continue from here

Allocate each internal participant's responsibility. Detect implementation drift after review.

Bring one service boundary with unclear coverage or ownership. Bring a change to Proof.