Native product contract

Published baseline: v0.11.1.

This page is the entry point for the current native product contract. It maps each required operator, integrator, and reviewer topic to current guidance and executable evidence. It does not turn controlled engineering evidence into independent review or live-title compatibility.

Published release and current source

The downloadable baseline is v0.11.1, source 6b071dc2c5ca6dd6f8f56bdcd28f70b7e986b22b. Documentation that must match installed bytes should follow that release identity.

The v0.11.1 bytes include the direct route and the S203 through S206 route and evidence fixes in addition to prior published corrections. The retained documentation and package-evidence lineage begins with S154 and includes the S158 Windows observation corrections. Installed-product failures return as version-specific issues. Publication does not convert implementation-authored evidence into independent acceptance.

Contract map

The version-two registry at docs/audits/native-documentation-coverage.v2.json binds all thirteen topics to exact current pages, required headings, example authorities and non-ignored executable tests. cargo xtask docs check refuses missing, duplicate, unknown, unsafe, historical-as-current, absent, ignored, feature-inapplicable or out-of-order authorities.

Executable example authority

Every current fragcap invocation in the README and nonhistorical site pages passes through the production command parser without dispatch under the applicable command trees. Retired Deep Capture consent switches remain rejected. Parser acceptance proves the command shape, not that an installed command ran or that its target is compatible.

Committed manifest specimens pass through the versioned product reader. Packet pcapng and JSON Lines examples remain exact generated goldens. Application, HAR, process, proxy, cleanup, correlation and stable API examples use controlled product tests when a shortened standalone specimen would omit lifecycle or authority facts. JSON syntax alone is never accepted as product authority.

Engineering completeness and explicit non-claims

Deep Capture is native and shipped for known-compatible stored targets. The current source has controlled protocol, routing, launch, evidence, cleanup, recovery, packaging, API and documentation contracts. It does not claim universal decryption, certificate-pinning bypass, compatibility with an unmeasured title, or that an independent security audit has been performed.

Current source also carries requested inspection scope, effective scope, middleware handling, and policy identity through calibration, authorization, stored facts, artifacts, Targets, and Doctor. Launcher-mediated auto selects exact-game inspection with blind middleware relay. Scope-specific repository and package checks establish the implemented contract; installed-product observations follow release.

Green CI, package certification, hosted replay, bot review and this closed inventory are engineering evidence, not proof of universal live-title compatibility or independent security acceptance. Optional operator and reviewer observations are not standing implementation-completion conditions.

Reconciliation point

Later field or independent-review findings amend the current contract at the page and executable authority that owns the affected fact. They are not inferred in advance. Each observed failure becomes a concrete defect against the affected active release, with reproduction or evidence, expected and actual behavior, remediation and regression coverage as applicable.

Optional installed reproduction uses digest-verified published bytes and records the actual operator decision for any trust or game launch effect. Installation, version output and controlled package tests do not establish real-title compatibility. Consent, scoped routing, reversible exact cleanup and retained administrator control remain unchanged. The MSI and fragcap executable are unsigned; the bundled WinDivert driver has separate upstream signing evidence.