Palantir Local and In-Platform Development Loop

Overview

Keep pure logic fast and local while treating Foundry preview, checks, and builds as separate evidence. A local mock can verify application logic, but it cannot prove Foundry permissions, lineage, transactions, or full-data behavior.

Prerequisites

• Identify the Code Repository or Developer Console application, language, branch, data sensitivity, and target environment.
• Install the supported Palantir VS Code extension or use an in-platform workspace as appropriate.
• Read references/official-docs.md and the repository's generated in-platform documentation.
• Prepare lightweight unit fixtures without production data and a sandbox branch.

Current Contract

• Foundry Code Repositories support sandbox branches, automatic checks, unit tests, previews, pull requests, and full builds.
• Preview can use sample or subset data; a full build runs on platform data and commits pipeline output.
• The VS Code extension can preview, debug, synchronize, and initiate Foundry builds from a local workspace.
• Local tests should isolate business logic and avoid relying on live external resources.