Native product contract
Complete current documentation authority and its boundary from published releases and external acceptance.
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.10.2, source 13c9230d1e91b1fddd34de1f279963fa0e711ef4. Documentation that must match installed bytes should follow that release identity.
The v0.10.2 bytes include S154's closed documentation inventory, S155's bounded independent-review intake and hosted replay authorities, S156's deterministic structured package-certification evidence, S157's complete documentation contract, and S158's Windows observation corrections. Publication does not convert implementation-authored evidence into independent acceptance.
Contract map
| Topic | Current authority |
|---|---|
| Architecture | Ownership, composition, trust and output boundaries |
| Setup | Installation, prerequisites and first run |
| Capture modes | File, stream and ring behavior with loss accounting |
| CLI | Commands, options, migrations and worked invocations |
| Protocols and routing | Exact supported traffic, routing and calibration |
| Refusals | Trust, pinning, scope and unsupported outcomes |
| Artifacts and correlation | Evidence authority, bounded retention and packet correlation |
| Diagnostics and recovery | Separate readiness and exact owned-resource recovery |
| Security and privacy | Consent, sensitivity and explicit sharing |
| Bounds | Finite work and observable omissions |
| Packaging and migration | Published certified packages and retained state |
| Public API | Stable facade and controlled adapters |
| Completion status | This release, source, supported boundary and active-release defect policy |
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.
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 do not remain as standing completion gates.
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 is operator-owned and uses digest-verified published bytes. Agents do not run the installed sensitive product, launch real games or mutate host trust to validate these pages. Consent, scoped routing, reversible exact cleanup, retained administrator control and unsigned-package policy remain unchanged.