NAV-CL-E006 ARTIFACT-CONTINUITY LEDGER LIMITATIONS

NAV-CL-E006 records deterministic processing of explicitly selected bytes and consistency of relationships required by current E004 and E005 contracts. It does not establish authorship, signer identity, legal custody, possession history, publication date, trusted time, authenticity, provenance truth, semantic equivalence, institutional approval, legal admissibility, privacy, security, evidence truth, or publication fitness.

Files are read only after explicit activation and parsed as inert bounded bytes. No server upload, application network request, account, analytics, cookie, service worker, browser database, persistent setting, remote notary, signing service, timestamp authority, identity provider, blockchain, or public ledger is used. Reset releases page-held references and generated object URLs as far as the browser permits.

The accepted v1.20.0 site archive remains unavailable. E006 records artifact relationships inside this v1.22.0 WIP tree but does not repair or erase that release-lineage discontinuity.

Additional limitations:
- A reproduced hash or receipt identity proves only agreement among explicitly selected bytes and current deterministic contracts.
- Source-declared timestamps are untrusted metadata and do not prove existence, observation, signing, receipt, custody, or publication at any time.
- Disconnected components, missing materials, contradictory bindings, and release divergence remain visible and are never bridged by inference.
- Fresh E004 verification is structural and cannot evaluate evidence truth, provenance quality, legality, privilege, confidentiality, privacy, security, or publication fitness.
- Duplicate selected bytes are repeated observations, not independent corroboration or proof of separate custody.
- Human reviewers must separately decide source identity, authority, current validity, substantive equivalence, legal effect, retention, and publication.
