NAV-CL-E003 PUBLICATION-PACKET LIMITATIONS

NAV-CL-E003 prepares a deterministic publication derivative only. NAV-CL-E001 remains the evidence-register authority, NAV-CL-E002 remains the structural and risk validator, AUDIT-CL-001 remains the audit authority, and the implementation kits retain their own bodies. The packet is not an audit, attestation, signature, evidence repository, legal opinion, privilege determination, compliance decision, privacy or security certification, provider score, maturity grade, or proof that any underlying claim is true, independent, complete, current, lawful, confidential, or suitable for publication.

The first-party browser script reads selected files only after explicit user action, makes no fetch, XMLHttpRequest, beacon, WebSocket, WebTransport, EventSource, form submission, cookie, localStorage, sessionStorage, IndexedDB, Cache API, service-worker, BroadcastChannel, SharedWorker, remote-font, CDN, telemetry, or third-party-code call, and releases application object URLs and references on replacement, reset, page hide, and completed download when technically safe. Browser extensions, endpoint monitoring, swap, backups, print systems, download history, user-selected storage, and garbage collection remain outside the proof.

The builder never includes either selected original in any supported profile. Returning to the unchanged local source is the only way to recover omitted values. Removed values are represented only by field identity, classification, action, and reason; their content and value hashes are not copied into the packet.

The builder preserves report diagnostics, category states, contradictions, unavailable evidence, and critical uncertainty without changing severity, suppressing unfavorable findings, computing a hidden score, or converting human_review_required into favorable language. A packet with unresolved critical, contradicted, unavailable, unreviewed, or structurally invalid state says so in the validation summary, manifest, unresolved-issues file, and sign-off worksheet.

Additional limitations:
- Structural and deterministic packet construction does not establish evidence truth, independence, completeness, currency, legal sufficiency, confidentiality, privilege, privacy, security, provider conduct, or publication suitability.
- Pattern screening is conservative and incomplete; a lack of a warning does not mean a value is safe or non-identifying.
- The safe profile minimizes fields but cannot prove that a controlled identifier, date, or version is non-sensitive in every context.
- The advanced profile requires accountable line-by-line human review and remains unable to export excluded-by-default fields or selected originals.
- Download handling, archive viewers, operating systems, extensions, endpoint controls, backups, print systems, and subsequent publication are outside the runtime proof.
