Curriculum / Orientation
Palantir Portfolio for Defense (Orientation)
Understand how Foundry, AIP, Gotham, and Apollo fit together for a defense mission: where each product is used, how classification-preserving data (markings + CBAC) flows across them, and how the integrated platforms function as one enterprise operating system — Gotham at a high positioning level only, with Maven Smart System explicitly noted as a future, out-of-scope track.
Everyone — a short, non-build literacy course (no coding, no prerequisites).
The 7-unit arc
- Unit 1: The Enterprise Operating System: how AIP, Foundry, and Apollo fit togetherfoundational
Map the portfolio: Foundry = data operations platform, AIP = generative-AI platform, Apollo = continuous delivery/operations — functioning together as one enterprise operating system.
- Unit 2: Foundry and the Ontology: the operational layer of the missionfoundational
Understand Foundry as the data operations platform and the Ontology as its semantic layer — object types, properties, and links over mission data.
- Unit 3: Classification-preserving data: markings and CBAC end to endintermediate
See how a notional dataset keeps its marking as it moves and derives — markings as mandatory controls and CBAC's conjunctive/disjunctive classification categories.
- Unit 4: AIP: bringing governed generative AI to mission decisionsintermediate
Map each AIP builder tool (AIP Logic, AIP Chatbot Studio, AIP Evals, AIP Analyst) to a mission use, and understand the AI-governance guarantee.
- Unit 5: Gotham: the operating system for defense decision-makingintermediate
Position Gotham at a high level: how the Foundry-managed Ontology powers Gotham via type mapping, with AIP spanning both — Gotham specifics are positioning (confirm against Gotham product docs).
- Unit 6: Apollo: continuous, compliant delivery to the tactical edgeintermediate
Understand Apollo as the continuous-delivery / day-2 operations platform: the hub-and-spoke + Release Channel model and air-gapped/disconnected delivery (IL claims confirm-before-asserting).
- Unit 7: Mission synthesis: one end-to-end flow across all four platformsintermediate
Tie it together: a mission-flow storyboard moving data → Ontology → AIP → Gotham → Apollo, with classification preserved throughout — and Maven Smart System explicitly placed as a future, out-of-scope track.
The Enterprise Operating System: how AIP, Foundry, and Apollo fit together
Map the portfolio: Foundry = data operations platform, AIP = generative-AI platform, Apollo = continuous delivery/operations — functioning together as one enterprise operating system.
Foundry and the Ontology: the operational layer of the mission
Understand Foundry as the data operations platform and the Ontology as its semantic layer — object types, properties, and links over mission data.
Classification-preserving data: markings and CBAC end to end
See how a notional dataset keeps its marking as it moves and derives — markings as mandatory controls and CBAC's conjunctive/disjunctive classification categories.
AIP: bringing governed generative AI to mission decisions
Map each AIP builder tool (AIP Logic, AIP Chatbot Studio, AIP Evals, AIP Analyst) to a mission use, and understand the AI-governance guarantee.
Gotham: the operating system for defense decision-making
Position Gotham at a high level: how the Foundry-managed Ontology powers Gotham via type mapping, with AIP spanning both — Gotham specifics are positioning (confirm against Gotham product docs).
Apollo: continuous, compliant delivery to the tactical edge
Understand Apollo as the continuous-delivery / day-2 operations platform: the hub-and-spoke + Release Channel model and air-gapped/disconnected delivery (IL claims confirm-before-asserting).
Mission synthesis: one end-to-end flow across all four platforms
Tie it together: a mission-flow storyboard moving data → Ontology → AIP → Gotham → Apollo, with classification preserved throughout — and Maven Smart System explicitly placed as a future, out-of-scope track.