Skip to content
VelsicsTraceLodger

Technical docs

Boundaries And FAQ

Public claim rules, unsupported states, and evaluator questions.

Safe claim pattern

TraceLodger reviews supported AI-related artifacts from local evidence directories, writes deterministic case artifacts for review, keeps gaps visible, and packages provenance for downstream handoff.

  • Say what retained evidence shows.
  • Keep review leads separate from conclusions.
  • Keep source-native review primary.
  • Describe broad support with supported or where supported.
  • Keep local-first posture clear unless another deployment model is explicitly implemented.

Do not claim

Public docs should not describe TraceLodger as surveillance software, data-loss prevention software, a live endpoint monitor, autonomous decision system, or direct raw-image ingestion tool.

  • Do not say the product confirms upload unless retained evidence directly supports that state.
  • Do not say browser share-style activity by itself establishes content transmission.
  • Do not say enterprise records replace endpoint artifacts.
  • Do not say legal, HR, or examiner review is replaced.

Synthetic demo case

The Asterion Circuit Works demo is synthetic. It should show the source-code helper scenario, direct source match, agent-assisted browser follow-on, mobile continuity cues, enterprise corroboration, unsupported upload evidence, and an enterprise retention gap.

  • Case ID: TL-DEMO-IR-001.
  • Company: Asterion Circuit Works.
  • Employee label: Lena Marrow, Senior Release Engineer.
  • Bounded window: 2026-04-08T14:03:11Z to 2026-04-08T14:08:56Z.