Palantir SDK Boundary and Client Patterns

Overview

Keep application-specific Ontology access in the generated OSDK and broader platform operations in the Platform SDK. Wrap transport concerns without hiding the generated entity contract, OAuth authority, request identifiers, or Action validation.

Prerequisites

• Identify the application job, language, required Ontology entities or Platform API operations, write behavior, and owner.
• Select the target Developer Console application or current official Platform SDK package and pin its version.
• Read references/official-docs.md, generated application documentation, and relevant migration guide.
• Define request deadlines, page bounds, retryable statuses, idempotency, telemetry, and secret storage.

Current Contract

• OSDK packages are generated for selected Ontology resources and support application-specific typed access.
• Official Python and TypeScript Platform SDKs wrap Foundry/AIP REST APIs for broader platform operations.
• Authentication authority is the intersection of OAuth scope, Developer Console restrictions, and principal permissions.
• Generated OSDK versions can change call syntax; migration guides are part of the upgrade contract.