Introduction

Scenario: Your defense team already uses Foundry to manage mission data, and leadership wants a plain-language brief on where Gotham fits — how the Foundry-managed Ontology powers Gotham and what Gotham is positioned to do from the operations center to the tactical edge.

This unit positions Gotham at a high level inside the Palantir portfolio. You are not configuring Gotham or building anything — you are producing a literacy-level brief that a non-technical stakeholder can read and trust. The center of gravity for this orientation is one verified mechanism: type mapping enables a unified representation of the Ontology across Foundry and Gotham, managed within Foundry's Ontology Manager, so Gotham can query Foundry object types and their metadata. That single fact is the bridge between what you already know (Foundry as the data operations platform and the Ontology as its semantic layer) and Gotham as a decision-making environment built on top of that shared semantic foundation.

Why this matters for the mission: Gotham is marketed as 'the operating system for defense decision-making' — an AI-ready environment meant to help operators see, understand, and act in the modern battlespace from operations centers out to the tactical edge. Treat that framing as POSITIONING, not as a load-bearing technical claim. The marketing page that carries that wording is client-rendered and was cited at partial confidence, so your brief should present it as Palantir's positioning and explicitly flag it as 'confirm against Gotham product docs.' What you can state with higher confidence is the integration mechanism (type mapping) and Gotham's published security principles, which come from Gotham's own security documentation.

On security, Gotham's architecture is documented around zero trust, least privilege, and defense-in-depth, blending mandatory and discretionary controls, with markings as mandatory controls applied to data and resources that need special protection — the same family of marking concepts you met in the classification unit. Throughout this unit, keep AIP in the picture: AIP is the generative-AI layer that brings governed AI to both Foundry and Gotham. One honest caveat to carry through every step — Gotham has its own separate documentation and API surface and is OUTSIDE the Foundry read APIs this platform uses, so there is no demo artifact to inspect here; this unit is entirely self-attested reading and diagramming.

Capability focus: Gotham positioning (high level); Foundry-Gotham type mapping (unified ontology); Gotham security principles. · Artifact: A Gotham positioning brief + a diagram annotation (Ontology → Gotham, AIP spanning both).

Key concepts

Companion video

1. 1

   Read the Foundry-Gotham type-mapping page

   Read the 'Enable Gotham integration' page on Foundry-Gotham type mapping and self-attest that you can restate the mechanism in plain language. The load-bearing, higher-confidence fact is this: type mapping enables a unified representation of the Ontology across Foundry and Gotham, managed within Foundry's Ontology Manager, so Gotham can query Foundry object types and their metadata. Note the two constraints the docs call out — once enabled, type mapping cannot be disabled, and only one Foundry Ontology per Gotham install can have it enabled. Because Gotham's broader positioning is partial-confidence, mark any claim that goes beyond this documented integration mechanism as 'confirm against Gotham product docs.'

   not startedself-attested

   Mark complete

   Self-attested: you can state that type mapping gives a unified ontology across Foundry and Gotham.

2. 2

   Explain Gotham's mission purpose

   Write a one-paragraph brief stating Gotham's mission purpose at a high level. Use Palantir's own framing — Gotham positioned as 'the operating system for defense decision-making,' an AI-ready environment to help operators see, understand, and act from the operations center to the tactical edge. Critically, label this as POSITIONING: the wording comes from a client-rendered marketing page cited at partial confidence, so your brief must present it as Palantir's positioning and explicitly flag it for verification against Gotham product documentation rather than asserting it as an established technical fact. Keep the brief literacy-level: what Gotham is for, who uses it, and how it relates to the Foundry data you already understand.

   not startedself-attested

   Mark complete

   Self-attested: your brief states Gotham's role at a high level (positioning, partial-confidence — flag).

3. 3

   Annotate the diagram: Ontology → Gotham, AIP spanning both

   Sketch a diagram annotation that shows the relationship between the platforms, and self-attest that it reads correctly. The annotation should show the Foundry-managed Ontology powering Gotham via type mapping (an arrow from the Foundry Ontology into Gotham), and AIP spanning both Foundry and Gotham as the governed generative-AI layer on top of the shared Ontology. There is no read API to check here — Gotham configuration is not in scope for this enrollment's Foundry read APIs — so this is a diagramming deliverable. Keep the arrows faithful to the one documented mechanism (Ontology -> Gotham via type mapping) and avoid drawing connections the docs do not support.

   not startedself-attested

   Mark complete

   Self-attested: your annotation shows the Foundry-managed Ontology powering Gotham, AIP spanning both.

4. 4

   Identify Gotham's security principles

   Identify and self-attest Gotham's published security principles. From Gotham's security overview you should be able to name zero trust, least privilege, and defense-in-depth, and state that Gotham blends mandatory and discretionary controls with markings as mandatory controls applied to data and resources needing special protection — the same marking concept you met earlier in the course. Note explicitly that Gotham maintains its own separate docs and API surface, distinct from the Foundry read APIs this platform's runner uses, which is why this step is manual recall rather than a machine-verified check. Treat the security principles (sourced from Gotham's own security docs) as higher-confidence, and keep any broader Gotham positioning flagged as partial-confidence.

   not startedself-attested

   Mark complete

   Self-attested: you can name zero trust, least privilege, and defense-in-depth (flag as positioning).