Palantir Redacted Diagnostic Bundle

Overview

Collect identifiers and platform evidence that allow another operator to reproduce the failure while excluding bearer tokens, secrets, object values, dataset rows, and unnecessary logs. The bundle is an inventory and evidence manifest, not an indiscriminate archive.

Prerequisites

• Identify the failure surface, time window, owner, support case, audience, and maximum allowed data classification.
• Obtain request IDs, build IDs, repository branch/commit, module version, SDK package versions, and non-secret environment metadata.
• Read references/official-docs.md and confirm whether log access is enabled and appropriately marked.
• Create the bundle in an access-controlled temporary location with an expiration owner.

Current Contract

• Foundry build reports, debugger sessions, and metrics are distinct evidence surfaces.
• Service and trace logs can contain values from prompts, objects, or upstream systems; viewing them can require Edit permission, log access, and markings.
• A caller can record OAuth grant type and scope names without recording a bearer token or client secret.
• Python transform debugging is an interactive investigation tool; debugger values are not proof of committed output.