> For the complete documentation index, see [llms.txt](https://docs.interlynk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interlynk.io/lynkctl/evidence.md).

# Evidence & Confidence

lynkctl records, for every conclusion it reaches, where that conclusion came from and how strongly it is supported. This lets you audit an SBOM rather than take it on faith.

***

## Evidence Output

When you pass `--evidence`, lynkctl emits CycloneDX 1.6 evidence on components where it can represent the supporting records cleanly. Evidence can include identity methods, source/manifest/map occurrences, license evidence, copyright evidence, confidence values, and tool references.

```bash
lynkctl generate ./myproject --evidence -o sbom.cdx.json
```

Scope decisions and other conclusions that CycloneDX cannot directly model remain internal. They are surfaced through [diagnostics](/lynkctl/diagnostics.md) when they affect auditability.

## Confidence

Confidence lives on evidence records and CycloneDX evidence methods. Higher values mean stronger evidence. When multiple evidence records support the same conclusion, the resolver applies precedence rules first, then confidence, then a stable evidence-ID tie break.

### Score Reference

lynkctl assigns each conclusion a confidence score based on the strength of its source — explicit declarations and build commands score highest, heuristic inferences lowest. The detailed score-to-source breakdown is internal and evolves with the tool. Contact Interlynk if you need the full reference for audit or review purposes.

### Interpreting Scores

| Range       | Confidence | Guidance                                                                                                              |
| ----------- | ---------- | --------------------------------------------------------------------------------------------------------------------- |
| 0.85 – 1.00 | High       | Data comes from authoritative sources — explicit declarations, build commands, pkg-config.                            |
| 0.60 – 0.84 | Moderate   | Inferred from build structure, source scanning, or heuristic analysis. Generally reliable, but may need verification. |
| Below 0.60  | Low        | Fallback heuristics. Review recommended.                                                                              |

When multiple stages contribute evidence for the same field, individual evidence records preserve the per-source confidence and reasoning. Conflicting or low-confidence conclusions produce diagnostics with evidence IDs in verbose output.

## Overriding a Conclusion

If lynkctl gets a component wrong, or you have authoritative information it cannot derive, supply a `--overrides` YAML file. Overrides carry confidence 1.00 and take precedence over every other source. Run `lynkctl generate --help` for the override file format.

```bash
lynkctl generate ./myproject --overrides overrides.yaml -o sbom.cdx.json
```

## Related

* [Diagnostics & Exit Codes](/lynkctl/diagnostics.md) — how conflicts and low-confidence conclusions are reported


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.interlynk.io/lynkctl/evidence.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.