FREE · prove

Knowledge Coverage Check

Compare the observed system inventory with current knowledge and turn missing coverage into focused review work.

01 · THE SITUATION

“Documentation exists, but you cannot tell which delivered surfaces are uncovered or stale.”

Documentation exists, but its presence does not reveal which delivered surfaces remain uncovered or stale.

REPOSITORY → ACTION → ARTIFACT → OUTCOME

02 · WHAT IT READS

acme-support-agent/fictional fixture

outputs/blueprint.jsonThe surfaces currently visible inside the boundary.
outputs/bindings.jsonWhich current knowledge items cover each identity.
repo/docs/ + outputs/answers.jsonRunbook material and approved reusable answers.
outputs/freshness.json + outputs/coverage-boundary.mdEvidence state and observation limits applied to coverage.

03 · WHAT THE FDE DOES

cliVerified public-main primitive

                      adopt coverage recompute --system acme-support-agent --json

Available deterministic coverage primitive; the visual gap workflow is planned.

workbenchIllustrative planned interaction

Planned local interface — illustrative.

04 · WHAT GETS PRODUCED

outputs/gaps.jsonIllustrative fixture

Coverage and gap table

A deterministic view of covered, uncovered, and observation-limited identities with next-owner suggestions.

05 · WORK AVOIDED

You spend scarce subject-matter-expert time correcting missing areas instead of reviewing everything.

06 · CREDIBILITY BOUNDARY

Completeness is relative to the observed inventory and declared boundary, never a claim that the whole real-world system is documented.

07 · NEXT STEP

Use the fictional repository demo to inspect the whole free-layer sequence before touching a real project.