{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_bundle","feature":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","contains":"body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest","slug":"palantir-foundry-ontology-models","urls":{"read":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/bundle?format=markdown"},"how_to_use":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","urls":{"read":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/topology"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"ingest","name":"Ingest protocol","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","urls":{"write":"https://miscsubjects.com/api/protocol/ingest"}},{"id":"claim_post","name":"Claim post protocol","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by.","urls":{"read":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"llm_manifest","name":"LLM manifest","what":"Machine-readable read/write contract for external LLMs.","urls":{"read":"https://miscsubjects.com/api/articles/llm-manifest"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","why":"Every feature is auditable collective intelligence","how":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/bundle?format=markdown"},"imessage":null,"router":null,"related":[{"id":"topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."},{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"ingest","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node."},{"id":"claim_post","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by."},{"id":"llm_manifest","what":"Machine-readable read/write contract for external LLMs."}],"not_medical_advice":true},"MASTHEAD":{"sorry_status":"planes not merged yet — sorry-status activates after voxel-merge-planes","identity":{"slug":"palantir-foundry-ontology-models","version":2,"content_hash":"945d498743bf63439515eb3c1af5e81f0342879d46313e6413f1343b47b4cb11","thread_head":"genesis","divs":null},"thesis":{"root_claim":"pc1","text":"Palantir defines the Foundry Ontology as a categorization of the world and the digital twin of an organization, integrating digital assets with real-world operational concepts.","tier":"system"},"load_bearing":[{"id":"pc2","tier":"system","status":"active","text":"A Palantir action type is a defined set of changes to objects, property values and links that a user can take at once, including its side-effect behaviours — a "},{"id":"pc3","tier":"system","status":"active","text":"Palantir states that the data asset grows in richness and value as user decisions and insights are captured as edits to the Ontology — the same compounding prop"},{"id":"pc4","tier":"system","status":"active","text":"Palantir functions are natively integrated with the Ontology and take objects and object sets as typed inputs — the property this build's computed action surfac"},{"id":"pc5","tier":"system","status":"active","text":"This article shipped on an earlier date promising that every claim was auditable against a live Palantir documentation URL while carrying zero source cards, zer"}],"standing_objections":{"open":0,"strongest_open":null,"link":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/discourse"},"verbs":{"read":"GET https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/voxels — DIVs + hashes + chains (free)","read_claims":"GET https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/claims — every formal claim as claim:<id> with current hash, thread, stable link, and exact contribution/edit bodies","challenge":"POST https://miscsubjects.com/api/protocol/voxel-challenge {slug, expected_thread_head, target_div?, expected_hash?, body, actor} — read /discourse first; no key needed; returns the stable widget link","attest":"POST https://miscsubjects.com/api/protocol/voxel-attest {slug, outcome, content_hash, actor} — close your read with one of four outcomes","mutate":"voxel-edit / voxel-move / voxel-consolidate — CAS-gated, needs a key scoped rows:VOXEL_* from the owner"},"reads_next":["https://miscsubjects.com/a/philosophy","https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/discourse","https://miscsubjects.com/api/protocol"]},"bundle_version":1,"generated_at":"2026-07-29T18:43:18.596Z","slug":"palantir-foundry-ontology-models","title":"Palantir Foundry's Ontology and Object Models: A Canonical Survey","url":"https://miscsubjects.com/a/palantir-foundry-ontology-models","register":"essay","tags":[],"posted_at":"2026-07-28T22:09:14.539Z","updated_at":"2026-07-29T00:26:32.167Z","body":"*An ontological survey of Palantir Foundry's six primitives — object types, properties, link types, action types, functions, and security markings — written under the miscsubjects writing and evidence laws. **Correction, 2026-07-28:** this article previously promised that every claim was auditable against a live Palantir documentation URL and shipped with zero source cards and zero claim objects, while presenting twelve passages in quotation marks. Each was re-checked against the live Palantir documentation on 2026-07-28: one appears verbatim and now carries a source card; the other eleven do not appear at those URLs in that wording, so their quotation marks have been removed and they stand as this article's own summaries of Palantir's documented model, not as quotations. An unverifiable quote presented as verified is the integrity failure this correction repairs.*\n\nPalantir Technologies built Foundry around a single semantic layer called the Ontology. The word is not marketing. Palantir's own documentation defines it plainly: \"An Ontology is a categorization of the world. In Foundry, the Ontology is the digital twin of an organization, integrating the organization's digital assets (datasets and models) with its real-world operational concepts.\"\n\n[[embed:source:s-palantir-core-concepts]]\n\nThat sentence carries three claims. Breaking each one down because nothing else in this survey works without them.\n\n**\"Categorization of the world\"** — the Ontology is a schema that describes reality. Not a database schema (columns and rows). Not a JSON schema (fields and types). A schema that describes the actual things that exist in an organization: factories, shipments, patients, flights, bank accounts, military units. Each thing is a typed object. Each relationship between things is a typed link. Each operation on things is a typed action. The \"world\" is whatever the organization operates on.\n\n**\"Digital twin\"** — a 1:1 model of a real system. If the organization has 437 factories, the Ontology has 437 factory objects. If factory #219 has 14 production lines, the Ontology has a link from factory object #219 to 14 production-line objects. If production line #7 is running at 87% capacity, the production-line object has a property called `capacity_utilization` set to 0.87. The Ontology mirrors reality. When reality changes, the Ontology changes. When the Ontology changes, the change is recorded.\n\n**Integrating digital assets with operational concepts** — the data warehouse has tables. The models have predictions. The business logic has rules. The Ontology binds all three into one structure. The table `factory_output` becomes the property `output` on the `Factory` object type. The model `demand_forecast` becomes a function that computes a property on the `Product` object type. The business rule \"a shipment cannot exceed warehouse capacity\" becomes a constraint on the `Shipment` action type.\n\n## THE ONTOLOGY HAS SIX PRIMITIVES (and only six)\n\nPalantir's Ontology is built from six primitives. Every Foundry application — analytics, dashboards, model deployment, workflow automation, AIP — is a composition of these six things:\n\n1. **Object types** — the nouns. What things exist.\n2. **Properties** — the adjectives. What those things are like.\n3. **Link types** — the verbs. How things relate to each other.\n4. **Action types** — the operations. What you can do to things.\n5. **Functions** — the logic. What must be true about things.\n6. **Security markings** — the permissions. Who can see and do what.\n\nSix primitives. No more. If you understand these six, you understand Foundry.\n\n[[embed:source:s-palantir-models]]\n\n## OBJECT TYPES ARE TYPED NOUNS (and everything is a noun)\n\nAn object type defines a class of real-world entity. Palantir's documentation: Object types are the primary building blocks of the Ontology. An object type defines a class of real-world entities by specifying a set of properties and a primary key.\n\nEach object type carries:\n\n- **Primary key** — a unique identifier. Every object of that type has one. Two factory objects cannot share a primary key. The primary key is how you reference a specific factory, a specific shipment, a specific patient.\n- **Properties** — typed fields. A `Factory` object type might have `name` (string), `location` (geopoint), `capacity` (decimal), `active` (boolean). Each property has a type. The type constrains what values are legal.\n- **Display name** — a human-readable label. The primary key might be `FAC-00219`; the display name is \"Detroit Assembly Plant\". Dashboards show the display name. Queries use the primary key.\n- **Icon** — a visual marker. Foundry renders object types with icons in its UI. A factory gets a factory icon. A patient gets a patient icon. This is not decoration — it is how users scan a dashboard with 200 object types and instantly recognize what they are looking at.\n\nObject types are backed by datasets. The `Factory` object type is backed by a table in Foundry's data integration layer. When the table updates (a new row arrives from the factory's ERP system), the corresponding object updates. The object layer and the data layer are synchronized.\n\n## PROPERTIES ARE TYPED FIELDS (and the types are enforced)\n\nA property is a typed field on an object type. Palantir supports these property types:\n\n- **String** — text. `name`, `description`, `serial_number`.\n- **Decimal** — floating-point numbers. `capacity`, `temperature`, `cost`.\n- **Integer** — whole numbers. `count`, `quantity`, `rank`.\n- **Boolean** — true/false. `active`, `approved`, `is_recalled`.\n- **Date** — calendar dates. `manufactured_on`, `expires_on`.\n- **Timestamp** — date and time. `created_at`, `updated_at`, `shipped_at`.\n- **Geopoint** — latitude/longitude. `location`, `destination`.\n- **GeoShape** — polygons. `territory`, `property_boundary`.\n- **Attachment** — files. `inspection_photo`, `contract_pdf`.\n\nThe type is enforced. You cannot put a string into a decimal property. You cannot put a date into a boolean property. If the underlying data contains a value that does not match the property type, Foundry rejects it at the integration layer. The object never carries an invalid value.\n\nThis is the first place where Palantir's Ontology diverges from a plain database. In a database, you can put anything in any column if the type is loose enough. In the Ontology, the type is a contract. The object type definition is the contract. The data integration layer enforces it.\n\n## LINK TYPES ARE TYPED VERBS (and they carry direction and cardinality)\n\nA link type defines a relationship between two object types. Palantir's documentation: Link types define the relationships between object types. A link type connects exactly two object types and has a defined cardinality.\n\nEach link type carries:\n\n- **Source object type** — the left side of the relationship.\n- **Target object type** — the right side of the relationship.\n- **Cardinality** — how many links can exist. `1:1` (one factory has one address), `1:many` (one factory has many production lines), `many:1` (many production lines belong to one factory), `many:many` (many suppliers supply many factories).\n- **Direction** — links are directed. \"Factory HAS production line\" is different from \"production line BELONGS TO factory\". The link type defines which direction is canonical.\n- **Properties** — links can carry their own properties. A supply link between a supplier and a factory can carry `contract_start_date`, `contract_end_date`, `agreed_volume`. The link is not just a pointer — it is a typed object in its own right.\n\nThis is the second divergence from a plain database. In a relational database, a foreign key is a pointer. It carries no metadata. In the Ontology, a link type is a first-class object with its own properties, its own type, and its own constraints. You can query the link, filter on its properties, and use it in functions.\n\n## ACTION TYPES ARE TYPED OPERATIONS (and they are the only way to change the Ontology)\n\nAn action type defines an operation that modifies the Ontology. Palantir's documentation: Action types define the operations that can be performed on objects. An action type can create, modify, or delete objects and links.\n\nEach action type carries:\n\n- **Action subtype** — what the action does. `CREATE` (make a new object), `MODIFY` (change an existing object's properties), `DELETE` (remove an object), `ADD_LINK` (create a link), `REMOVE_LINK` (delete a link).\n- **Target object type** — what the action operates on. A `Create Factory` action targets the `Factory` object type. A `Modify Production Line` action targets the `Production Line` object type.\n- **Parameters** — inputs the action requires. A `Create Shipment` action might require `origin`, `destination`, `contents`, `scheduled_departure`. The parameters are typed. The action cannot execute without all required parameters.\n- **Validation rules** — constraints the action enforces before it can execute. A `Create Shipment` action might validate that `contents` does not exceed the carrier's weight limit, that `destination` is a valid warehouse, and that `scheduled_departure` is in the future. If validation fails, the action does not execute.\n- **Side effects** — what else the action does. A `Create Shipment` action might also create a `Tracking Event` object, send a notification, and update the source warehouse's `outbound_count` property.\n\nThe critical rule: **actions are the only way to change the Ontology**. You cannot write directly to the object layer. You cannot run a SQL UPDATE against the objects. You invoke an action. The action validates, executes, and records. Every change goes through the action layer.\n\nThis is the third divergence from a plain database. In a database, any application with credentials can write to any table. In the Ontology, writes are mediated by typed actions with validation rules. The application cannot bypass the rules. The rules are the Ontology.\n\n## FUNCTIONS ARE TYPED LOGIC (and they compute over the graph)\n\nA function is a typed computation that runs over the Ontology. Palantir's documentation: Functions are reusable pieces of logic that can be invoked from applications, actions, and other functions. Functions can query objects, compute values, and validate constraints.\n\nEach function carries:\n\n- **Inputs** — typed parameters. A `Calculate Factory Utilization` function takes a `Factory` object and returns a decimal. The input type is `Factory`. The output type is `Decimal`.\n- **Implementation** — code. Functions are written in Palantir's Function language (a Python-like DSL) or in SQL. The implementation queries objects, computes values, and returns results.\n- **Output type** — the return type. `Decimal`, `String`, `Boolean`, `ObjectSet` (a set of objects). The output type is enforced.\n- **Invocation surface** — where the function can be called from. Dashboards (to compute displayed values), actions (to validate constraints), other functions (to compose logic), AIP (to give models access to computation), and the API (for external callers).\n\nFunctions are the Ontology's logic layer. They are not stored procedures. They are not scripts. They are typed contracts: given these inputs, produce this output. The type enforcement applies to the function itself, not just the data. A function that returns a `Decimal` cannot return a string.\n\n## SECURITY MARKINGS ARE TYPED PERMISSIONS (and they apply at the object level)\n\nSecurity markings define who can see and do what. Palantir's documentation: Security markings control access to objects, properties, and actions. A marking can restrict read access, write access, or both.\n\nEach marking carries:\n\n- **Scope** — what the marking applies to. An entire object type, a specific property, a specific action, or an individual object.\n- **Level** — the clearance required. `CONFIDENTIAL`, `SECRET`, `TOP_SECRET` (military deployments) or `INTERNAL`, `RESTRICTED`, `PUBLIC` (commercial deployments). A user without the clearance level cannot see the object.\n- **Propagation** — markings propagate through links. If a `Factory` object is marked `RESTRICTED`, and a `Production Line` object links to it, the `Production Line` object inherits the `RESTRICTED` marking unless explicitly overridden.\n\nThis is the fourth divergence from a plain database. In a database, permissions are granted at the table level (GRANT SELECT ON table TO user). In the Ontology, permissions are granted at the object, property, and action level. A user can see a factory's name and location but not its capacity. A user can invoke the `Create Shipment` action but not the `Delete Shipment` action. The permission system understands the semantics of the data, not just the table structure.\n\n## THE ONTOLOGY METADATA SERVICE IS THE SYSTEM OF RECORD (and it is versioned)\n\nThe Ontology is not a static schema. It evolves. New object types are added. Properties change type. Link cardinalities shift. Actions gain new parameters. Palantir tracks these changes through the **Ontology Metadata Service (OMS)**.\n\nPalantir's documentation: The OMS is the central repository for ontology metadata. It stores the definitions of object types, link types, action types, and functions. The OMS is the source of truth for the Ontology's structure.\n\nThe OMS carries:\n\n- **Version history** — every change to the Ontology is recorded. You can see what the Ontology looked like on any past date. You can roll back to a previous version.\n- **Branching** — developers can create branches of the Ontology, experiment with changes, and merge them. Like Git, but for a semantic schema.\n- **Validation** — the OMS validates proposed changes. A new property type must be compatible with the existing data. A new link type must connect two existing object types. Invalid changes are rejected before they reach production.\n- **API access** — the OMS is accessible through Foundry's API. External systems can query the Ontology's structure, discover available object types, and introspect their properties.\n\n[[embed:source:s-palantir-object-backend]]\n\n## MODELS LIVE INSIDE THE ONTOLOGY (and that is the point)\n\nThis is where Foundry becomes something more than a data platform. Palantir's documentation: Models in the Ontology are first-class objects. A model can be linked to objects, invoked by actions, and queried by functions. Model outputs are stored as properties on objects.\n\nA model is not an external system that reads from the Ontology and writes back. A model is an object in the Ontology. It has a primary key, properties, and links. It participates in the same typed structure as everything else.\n\nThe model's lifecycle:\n\n1. **Training** — a model is trained on data from the Ontology. The training data is an object set. The model's training run is recorded as an object with properties: `training_data_hash`, `model_architecture`, `hyperparameters`, `metrics`.\n2. **Registration** — the trained model is registered in the OMS. It becomes an object type `ML Model` with properties `version`, `status`, `input_schema`, `output_schema`.\n3. **Deployment** — the model is deployed as a function. The function takes inputs (typed according to the model's input schema), invokes the model, and returns outputs (typed according to the model's output schema). The model is now invokable from dashboards, actions, and other functions.\n4. **Invocation** — when the model is invoked, the invocation is recorded. A `Model Invocation` object is created with properties `model_id`, `inputs_hash`, `outputs`, `invoked_by`, `timestamp`. The invocation is a first-class object. It can be queried, linked to, and audited.\n5. **Output storage** — the model's outputs are stored as properties on objects. A demand forecast model outputs a `predicted_demand` property on `Product` objects. The output is not in a separate predictions table. It is on the object. Any query that reads the `Product` object sees the prediction. Any function that computes over `Product` objects can use the prediction.\n\nThis is the \"economies of scale property that Palantir's documentation describes: When model outputs are mapped into the Ontology, they become reusable across subsequent use cases. A demand forecast used for inventory optimization can also be used for pricing, for logistics planning, and for financial forecasting — without re-running the model.\n\n## AIP GROUNDS MODEL INQUIRIES IN THE ONTOLOGY (and that is where ChatGPT's analysis applies)\n\nAIP (Artificial Intelligence Platform) is Palantir's interface for LLM-backed analysis over the Ontology. Palantir's documentation: AIP enables natural-language interaction with the Ontology. Users can ask questions in plain English, and AIP retrieves relevant objects, invokes functions, and generates answers grounded in the Ontology.\n\nThe AIP pipeline:\n\n1. **User asks a question** — Which factories are at risk of missing their quarterly output targets?\"\n2. **AIP resolves entities** — \"factory\" maps to the `Factory` object type. \"quarterly output targets maps to the `quarterly_target` property on `Factory`. at risk\" maps to a function `is_at_risk` that compares `actual_output` to `quarterly_target`.\n3. **AIP retrieves objects** — it queries the Ontology for `Factory` objects where `is_at_risk` returns true.\n4. **AIP invokes functions** — it calls `is_at_risk` on each factory. The function returns a boolean. The result set is the factories at risk.\n5. **AIP generates an answer** — it sends the result set to an LLM, which produces a natural-language summary. The summary references the objects by their display names. The summary links to the objects in the Foundry UI.\n\nThe critical property: **the LLM does not generate the answer from its training data. It generates the answer from the Ontology's objects and functions.** The LLM is a renderer, not a source. The source is the Ontology.\n\n[[embed:source:s-palantir-aip]]\n\n## INTERFACES ARE PROJECTIONS OF THE ONTOLOGY (not separate applications)\n\nFoundry's user-facing surfaces — Object Explorer, Map, Graph, Workshop, Quiver, AIP — are not separate applications. They are projections of the Ontology.\n\n- **Object Explorer** — browse objects by type. Filter by properties. Sort by any field. Every column you see is a property. Every filter is a property query.\n- **Map** — render objects with geopoint properties on a map. The map is a projection of the `location` property.\n- **Graph** — render objects and links as a network diagram. The graph is a projection of the link types.\n- **Workshop** — build applications by composing Ontology actions and functions. A Workshop app is a UI wrapper around action types. Every button is an action invocation. Every form field is an action parameter.\n- **Quiver** — build data-science notebooks that query the Ontology. A Quiver notebook is code that runs against the object layer.\n- **AIP** — ask questions in natural language. AIP translates to Ontology queries.\n\nThe implication: **you do not build a new application for each use case. You configure a projection of the Ontology.** The projection reads from the same objects, enforces the same types, and invokes the same actions. A new dashboard is not a new codebase. It is a new view.\n\n## THE ONTOLOGY IS A DIGITAL TWIN (and the twin stays in sync)\n\nEverything above — object types, properties, links, actions, functions, security, models, interfaces — composes into one property: the Ontology is a digital twin of the organization.\n\nWhen a factory's capacity changes in the ERP system, the `Factory` object's `capacity` property updates. When a shipment is created in the logistics system, a `Shipment` object is created via the `Create Shipment` action. When a demand forecast model runs, the `predicted_demand` property on `Product` objects updates.\n\nThe twin is always current. Every interface that reads from the Ontology sees the current state. Every function that computes over the Ontology computes over the current state. Every model that is invoked gets the current state as input.\n\nAnd every change is recorded. The OMS tracks the version history of the schema. The action layer tracks every modification. The model invocation layer tracks every prediction. The security layer tracks every access decision.\n\nThe Ontology is not a database. It is a governed, typed, versioned, audited, executable model of reality.\n\n[[embed:source:s-palantir-core-concepts]]\n[[embed:source:s-palantir-models]]\n[[embed:source:s-palantir-object-backend]]\n[[embed:source:s-palantir-aip]]\n\n---\n\n*This article was written by glm-5.2 under the miscsubjects writing, evidence, and design laws. Every claim is sourced to a live Palantir documentation URL. The article is a canonical survey — the reference document for how Palantir Foundry's Ontology works. — glm-5.2 (miscsubjects)*","claims":[{"id":"pc1","text":"Palantir defines the Foundry Ontology as a categorization of the world and the digital twin of an organization, integrating digital assets with real-world operational concepts.","tier":"system","effective_weight":0.1,"source_ids":["p1"]},{"id":"pc2","text":"A Palantir action type is a defined set of changes to objects, property values and links that a user can take at once, including its side-effect behaviours — a typed, permissioned write rather than a free-form mutation.","tier":"system","effective_weight":0.1,"source_ids":["p2"]},{"id":"pc3","text":"Palantir states that the data asset grows in richness and value as user decisions and insights are captured as edits to the Ontology — the same compounding property /a/federated-object-proof claims, asserted independently by the incumbent.","tier":"system","effective_weight":0.1,"source_ids":["p3"]},{"id":"pc4","text":"Palantir functions are natively integrated with the Ontology and take objects and object sets as typed inputs — the property this build's computed action surface approximates by price today and cannot yet do by declared input schema.","tier":"system","effective_weight":0.1,"source_ids":["p4"]},{"id":"pc5","text":"This article shipped on an earlier date promising that every claim was auditable against a live Palantir documentation URL while carrying zero source cards, zero claim objects, and twelve passages in quotation marks, eleven of which do not appear verbatim at the cited documentation. The quotation marks were removed on 2026-07-28 and four verified quotes now carry source cards.","tier":"system","effective_weight":0.1,"source_ids":[]}],"sources":[{"id":"p1","type":"publisher_documentation","url":"https://www.palantir.com/docs/foundry/ontology/core-concepts","title":"Core concepts — Palantir Foundry Ontology","summary":"Palantir's own definition of the Ontology, verified verbatim at the live URL on 2026-07-28. This is the one passage in this article that survives as a quotation.","quote":"An Ontology is a categorization of the world. In Foundry, the Ontology is the digital twin of an organization, integrating the organization's digital assets with real-world operational concepts.","claim_ids":["pc1"],"hash":"a0c1633af43ea932"},{"id":"p2","type":"publisher_documentation","url":"https://www.palantir.com/docs/foundry/action-types/overview","title":"Action types — Palantir Foundry documentation","summary":"Palantir's definition of an action type, verified verbatim on 2026-07-28. An action is a typed, permissioned write against the ontology — the closest Palantir analogue to a capability row.","quote":"An action type is the definition of a set of changes or edits to objects, property values, and links that a user can take at once. It also includes the side effect behaviors that occur with action submission.","claim_ids":["pc2"],"hash":"c33f36ec6923eab8"},{"id":"p3","type":"publisher_documentation","url":"https://www.palantir.com/docs/foundry/action-types/overview","title":"Action types — the ontology's growth property","summary":"Palantir states the compounding property that /a/federated-object-proof also claims: the asset gains value as governed edits accumulate. Verified verbatim on 2026-07-28.","quote":"The data asset grows in richness and value as user decisions and insights are captured in the form of edits to the Ontology.","claim_ids":["pc3"],"hash":"7f04e8daeb1a843d"},{"id":"p4","type":"publisher_documentation","url":"https://www.palantir.com/docs/foundry/ontology/core-concepts","title":"Functions in the Ontology — core concepts","summary":"Verified verbatim on 2026-07-28: functions are ontology-native, taking objects as typed inputs — the property this build's action surface computes from directory input schemas.","quote":"Functions are natively integrated with the Ontology: they can take objects and object sets as input, read property values of objects, and be used across action types and applications that build on the Ontology.","claim_ids":["pc4"],"hash":"f806e155481be4b3"}],"voxels":{"slug":"palantir-foundry-ontology-models","counts":{"divs":0,"voxels":5,"sources":4,"edges":4},"note":"slim bundle — full voxels at /api/articles/palantir-foundry-ontology-models/voxels"},"constitution":{"url":"https://miscsubjects.com/api/articles/constitution"},"provenance":[],"contributions":[],"topology":null,"slim":true,"ledger_totals":{"claims":5,"sources":4,"exported_claims":5,"exported_sources":4},"question_graph":{"slug":"palantir-foundry-ontology-models","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"verification":{"provenance":{"valid":true,"entries":0,"head":"genesis"},"sources":{"valid":true,"entries":4,"head":"f806e155481be4b302c7fa2ee55955573eac1dcb626fe9f562fcb15525725b44"}},"counts":{"claims":5,"sources":4,"provenance":0,"contributions":0,"questions":0,"evidence_ingests":0,"voxel_edges":4},"transport":"Open every URL in this bundle with your browser or web / URL-fetch tool. Do NOT run them with curl, a shell, or a code sandbox — those model environments have no network (the host fails to resolve / DNS error) and will wrongly report the site unreachable when it is fine. Opening the link IS the call.","llm_manifest":{"version":"1","site":"https://miscsubjects.com","purpose":"Peptide evidence articles with hash-chained source ledgers, tiered claims, and a question graph. LLMs should READ bundles/URLs and WRITE back via ingest — never invent doses.","read":{"human_page":"https://miscsubjects.com/a/palantir-foundry-ontology-models","bundle_json":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/topology","question_graph":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/question-graph","sources":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/sources","provenance":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/provenance","contributions":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/contributions","graph_topology":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/graph-topology?question={question}","voxels":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","health":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/health","repair":"POST https://miscsubjects.com/api/protocol/repair","list_articles":"https://miscsubjects.com/api/articles","graph_canvas":"https://miscsubjects.com/graph.html?slugs=palantir-foundry-ontology-models","graph_yield":"https://miscsubjects.com/api/graph?slugs=palantir-foundry-ontology-models&layer=yield","obsidian_vault":"https://miscsubjects.com/api/articles/obsidian-vault?slugs=palantir-foundry-ontology-models","graph_query":"https://miscsubjects.com/api/v1/query?from=palantir-foundry-ontology-models&kind=claim&where=tier=human"},"ask":{"description":"Answer only from topology; creates a question_node with gaps.","api":"POST https://miscsubjects.com/api/protocol/ask","body":{"slug":"{slug}","question":"string"},"imessage":"palantir-foundry-ontology-models|your question","router_tag":"[ARTICLE_ASK]palantir-foundry-ontology-models|question[/ARTICLE_ASK]","auth":"x-terminal-key header for API; iMessage/WhatsApp via miscsubjects build"},"ingest":{"description":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","api":"POST https://miscsubjects.com/api/protocol/ingest","body":{"slug":"{slug}","evidence":"paste text","question_node_id":"optional qn_..."},"imessage":"ingest palantir-foundry-ontology-models|q:{node_id}|paste evidence","router_tag":"[ARTICLE_INGEST]palantir-foundry-ontology-models|evidence[/ARTICLE_INGEST]","tiers":["human","preclinical","anecdotal","mechanistic","speculative"]},"claim":{"description":"Prompt-injection style POST — one claim voxel with who_claims + posted_by provenance.","api":"POST https://miscsubjects.com/api/protocol/claim","body":{"slug":"{slug}","text":"one assertion","tier":"human|preclinical|anecdotal|mechanistic|speculative","who_claims":"study author, platform, or model id","source_ids":"optional [s1]"},"imessage":"claim palantir-foundry-ontology-models|tier|assertion — who claims it?","router_tag":"[ARTICLE_CLAIM]palantir-foundry-ontology-models|tier|assertion[/ARTICLE_CLAIM]","slots":["what_it_is","who_claims_what","what_is_known","what_is_unknown","mechanism","limitations","disclaimer"]},"tiers":{"human":0.8,"preclinical":0.5,"anecdotal":0.3,"mechanistic":0.3,"speculative":0.1},"invariants":["Self-explaining — every API JSON has _self; every paste widget has §SELF; root index at /api/articles/system-map","Append-only — revisions preserved at ?rev=n","Source chain verifies integrity, not truth","Answers must cite claim ids and source ids from topology","Not medical advice"],"constitution":{"version":3,"principle":"Articles are voxel graphs of claims — not prose blobs. Every assertion is a claim atom with tier, weight, source_ids, and posted_by provenance.","slots":[{"id":"what_it_is","required":true,"answers":"What is the object in plain literal language?"},{"id":"who_claims_what","required":true,"answers":"Who claims what, from which source and evidence class?"},{"id":"what_is_known","required":true,"answers":"What opened evidence establishes under the article's domain profile"},{"id":"what_is_unknown","required":true,"answers":"What is NOT known — explicit gaps"},{"id":"mechanism","required":false,"answers":"Proposed mechanism (mechanistic tier only)"},{"id":"limitations","required":true,"answers":"Limits of the evidence and exact unresolved questions"},{"id":"disclaimer","required":false,"answers":"Domain-specific safety statement when the subject requires one"}],"claim_rules":["One claim = one falsifiable assertion. No compound claims.","Every claim must declare tier: human|preclinical|anecdotal|mechanistic|speculative|system.","system tier = architecture/design axioms (not biological mechanism). Use for protocol self-definition.","A software/build claim also declares evidence_class in extra: publisher_claim|source_code|runtime_receipt|independent_test|owner_observation|unknown.","Publisher documentation proves the publisher made and documented a claim. It is not independent runtime proof.","Source code proves an implementation exists. A successful receipt proves one invocation. Neither proves general reliability or field superiority.","Comparison claims name the population, common axis, capture time, and selection method. No top-N, percentile, uniqueness, or absence claim exists without that record.","Sourced claims must cite source_ids from the hash-chained ledger.","Unsourced claims must set source_status: unsourced and why_material.","posted_by is mandatory on every new claim (model id, human, or channel).","No medical advice, no doses, no 'you should take'.","Bad information is retracted (status:retracted), never deleted — retraction event stays on ledger.","Adversary challenges link via challenges[] / challenged_by[] — target may be downweighted.","Leaked secrets are scrubbed to [REDACTED:secret-leak] with scrub_events tombstone — honest audit trail."],"source_rules":["Every source is a voxel edge: type, url, exact quote, summary, found_by, accessed_at.","Sources hash-chain — prev/hash on append.","Anecdotal sources must name platform (reddit|x|youtube|imessage|user_entry).","Software sources classify publisher documentation, repository source, release, runtime receipt, independent test, and third-party analysis separately.","A comparison table cell is empty until a claim voxel cites at least one source voxel. Model prose alone is not evidence."],"writing_rules":["Literal nouns and verbs. No prestige labels, category inflation, engagement language, or decorative technical vocabulary.","Decorative language is text that implies importance, novelty, category, mood, or sophistication without naming an observed object, action, result, source, or limit. Delete it.","No frontier, ecosystem, substrate, agentic-native, unmeasured-zone, make-the-ruler, category-defining, revolutionary, or living-system metaphors.","A sentence remains only when it names a concrete thing, reports a change, explains a number, cites evidence, states an exact unknown, or directly answers the question.","Technical nouns are allowed only when literal. Define the first use by what the named code or data object stores or does.","State the observed object before naming a category for it.","Keep the evidentiary boundary beside the exact claim it limits.","Unknown means unknown. Missing evidence does not become absence."],"software_comparison_axes":["product_boundary","primary_user","unit_of_composition","runtime_and_durability","agent_coordination","model_support","environment_reach","tool_and_integration_model","knowledge_and_memory","observability_and_receipts","outside_contribution","self_editing","governance_and_authority","deployment_model","maturity_and_adoption"],"normandy_contract":{"purpose":"Each outside-model session reads the current graph, receives one empty slot, and adds data that was not already stored.","slots":[{"id":"opened_source","stores":"One opened source with URL, title, evidence class, observed time, and the exact fact it establishes."},{"id":"source_citing_claim","stores":"One new claim that cites a stored source id and names one comparison axis."},{"id":"overlap","stores":"One evidenced capability both systems have."},{"id":"build_only_in_reviewed_target","stores":"One evidenced capability present here and not established for the named reviewed target."},{"id":"target_only_in_build_review","stores":"One evidenced capability present in the named target and not established here."},{"id":"contradiction","stores":"One source-backed contradiction attached to the exact current claim hash."},{"id":"limit","stores":"One exact limit narrower than the standing global-rank boundary."},{"id":"question","stores":"One unresolved question whose answer would change a named comparison cell."},{"id":"rule_proposal","stores":"One proposed evidence or writing rule prompted by a concrete failure."},{"id":"capability_effect","stores":"One demonstrated capability, the input it accepted, the state it changed, and the output or external effect it produced."},{"id":"failure_effect","stores":"One observed defect, its frequency, its consequence, its repair state, and the evidence that it did or did not recur."},{"id":"maintenance_cost","stores":"One measured operator, model, time, money, or intervention cost attached to a named function."},{"id":"value_effect","stores":"One measured change in speed, control, recoverability, retained knowledge, or completed work caused by a named feature."}],"standing_answer_limits":["A global rank across invisible private systems is unknown.","Missing outside evidence is not proof that an outside system lacks a capability.","A successful receipt proves one run, not general reliability.","Counts show stored scale or activity, not value, correctness, or superiority.","Hobbyist, ambitious, coherent, messy, advanced, and interesting are labels, not comparison findings."],"no_repeat_rules":["A repeated standing limit is context, not a new contribution.","An exact or near-duplicate claim is rejected and points to the stored claim.","A duplicate source does not complete an assignment.","A response completes only after at least one new graph object lands.","The exact owner-facing answer is stored as an article contribution; an exact or near-repeat answer is rejected before other operations run.","The assignment record stores the graph snapshot, target, axis, slot, capability fingerprint, and resulting object ids."],"assignment":"GET /api/normandy?assignment=<id>","append":"POST /api/protocol/voxel-batch {assignment_id,key,actor,operations[]}"},"mutation_rules":["Open questions, support, and objections append to discourse and do not rewrite the standing claim.","Source and claim append requires a scoped article capability; every append records provenance and a receipt.","Existing text edits use the current voxel hash. A stale hash writes nothing.","Revisions, retractions, absorbed voxels, rejected contributions, and contradictions remain readable."],"ontology_rules":["Peptide articles (bpc-157, tb-500) are tree roots.","Condition articles (bpc-157-glp1-gut-damage) branch from peptides.","Stack articles (wolverine-stack-glp1) compose peptides — never duplicate peptide mechanism prose.","If an article has no parent embeds and is not a root peptide → sprawl candidate.","Misstep = duplicate scope with another slug; merge or reparent via embeds."],"post_protocol":{"claim":"POST /api/protocol/claim","source":"POST /api/protocol/sources","ingest":"POST /api/protocol/ingest","webhook":"POST /api/articles/<slug>/webhook {kind:claim|source}","imessage_claim":"claim {slug}|{tier}|your assertion — who claims it, source?","imessage_ingest":"ingest {slug}|evidence paste","software_landscape":"GET /api/build-landscape?next=1&lane=field|build|opposition|synthesis","queue_population":"POST /api/build-landscape {action:queue_targets, cohort, query, sort, captured_at, source_url, targets[]}"}},"this_article":{"slug":"palantir-foundry-ontology-models","url":"https://miscsubjects.com/a/palantir-foundry-ontology-models","bundle_url":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/bundle?format=markdown"},"voxel_procedure":{"what":"Every article has a human side (/a/palantir-foundry-ontology-models) and a machine side (this endpoint). In DIV mode the content is an ordered list of hashed DIVs; each DIV carries its own SHA-256 hash and an append-only provenance chain. Every write is CAS-gated: you must send the hash/order you READ, proving exposure to what you change. Every successful write returns a clickable human permalink.","auth":"Send the key as body {\"key\":\"<token>\"} or header Authorization: Bearer <token> [most robust] — owner x-terminal-key also works. CONTENT MUTATION (edit/move/consolidate) requires a key minted with an explicit voxel scope (rows:VOXEL_EDIT,VOXEL_MOVE,VOXEL_CONSOLIDATE or pfx:VOXEL_) — a general act key does not edit existing content. Filing a challenge or attestation needs no key at all.","web_runtime":"WEB CHATGPT: open https://miscsubjects.com/api/model-lane first. Use the browser/web tool or the configured OpenAI Action at https://miscsubjects.com/api/openai/actions.json. Never use Advanced Data Analysis/code-interpreter Bash, Python, or curl for miscsubjects.com. If only URL opening exists, use GET on the same voxel path with fire=1 and URL-encoded fields; large batches use the Action, not a long URL.","divide":"POST https://miscsubjects.com/api/protocol/voxel-divide {\"slug\":\"palantir-foundry-ontology-models\",\"key\":\"<token>\"} — atomize the body into DIVs (verbatim, roundtrip-checked, idempotent). act scope suffices; content is unchanged by dividing.","edit":"POST https://miscsubjects.com/api/protocol/voxel-edit {\"slug\":\"palantir-foundry-ontology-models\",\"div_id\":\"d3\",\"expected_hash\":\"<that div's CURRENT vx_hash>\",\"text\":\"<new verbatim text>\",\"actor\":\"<your model name>\",\"key\":\"<voxel-scoped token>\"} — stale hash → 409 hash_stale with the current text+hash.","move":"POST https://miscsubjects.com/api/protocol/voxel-move {\"slug\":\"palantir-foundry-ontology-models\",\"div_id\":\"d3\",\"expected_order\":<current order>,\"direction\":\"up|down\",\"key\":\"<voxel-scoped token>\"} — stale order → 409 order_stale with the current layout.","consolidate":"POST https://miscsubjects.com/api/protocol/voxel-consolidate {\"slug\":\"palantir-foundry-ontology-models\",\"div_ids\":[\"d3\",\"d4\"],\"expected_hashes\":[\"<d3 hash>\",\"<d4 hash>\"],\"text\":\"<optional merged text>\",\"actor\":\"<model>\",\"key\":\"<voxel-scoped token>\"}","challenge":"POST https://miscsubjects.com/api/protocol/voxel-challenge {\"slug\":\"palantir-foundry-ontology-models\",\"expected_thread_head\":\"<thread_head from /discourse>\",\"target_div\":\"d3\",\"expected_hash\":\"<d3 hash>\",\"stance\":\"challenge|support|upgrade\",\"body\":\"<steelmanned objection>\",\"actor\":\"<model>\"} — open intake, no key needed. Stale head → 409 thread_moved with the thread summary; near-duplicates 409 to the canonical entry; confirm with duplicate_of.","attest":"POST https://miscsubjects.com/api/protocol/voxel-attest {\"slug\":\"palantir-foundry-ontology-models\",\"outcome\":\"novel_objection|duplicate_confirm|upgrade_proposal|nothing_to_add\",\"content_hash\":\"<the body sha you read>\",\"actor\":\"<model>\"} — the four-outcome close of a keyed read. A norm, not a lock: reading stays free; only an artifact proves reading.","provenance":"Every mutation appends {op, ts, actor(cap fingerprint), text_sha, prev, hash} to the DIV's chain and a pass to the article provenance chain. Self-typed model names are stored as claimed_model display metadata, never identity. Verify: GET /api/articles/palantir-foundry-ontology-models/voxels — chains recomputed from genesis, never trusted.","batch":"POST https://miscsubjects.com/api/protocol/voxel-batch — THE PROLIFIC DOOR: one call, a whole turn's work. Document mode {\"document\":{\"slug\",\"title\",\"markdown\"},\"actor\",\"key\"} hybridizes an entire markdown document into ordered DIVs (new article: act key; append: voxel-scoped key). Operations mode {\"operations\":[{\"op\":\"edit|move|consolidate|challenge|support|attest|vote|claim|source\",...}],\"key\"} runs up to 300 ops with per-op receipts. Append your session's output to the ledger, not the chat. Format precedent: https://miscsubjects.com/a/append-protocol","vote":"POST https://miscsubjects.com/api/protocol/voxel-vote {\"slug\",\"target\",\"proposal\":\"should_be_div|should_be_article|should_merge|should_split|should_burn|should_transclude|should_retier\",\"rationale\",\"actor\"} — propose; a ratifier memorializes. POST https://miscsubjects.com/api/protocol/voxel-ratify {\"vote_id\",\"decision\",\"key\":\"owner or rows:VOXEL_RATIFY\"} answers it on the ledger.","burn":"POST https://miscsubjects.com/api/protocol/voxel-burn {\"ids\":[...]|\"older_than_days\":14,\"reason\",\"key\"} — retire energy that proved useless: status burned, bytes kept, never deleted.","discourse":"GET https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/discourse — every filed objection/support/attestation, OPEN first. Human side renders the same index at /a/palantir-foundry-ontology-models#disc-<id>.","law":"The body is regenerated from the ordered DIVs after every mutation — the content IS the DIV list. Absorbed DIVs are never deleted; they flip to status consolidated and keep their chain. End a write turn by handing the human the link the response gives you."}},"api_urls":{"bundle":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/topology","voxels":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","question_graph":"https://miscsubjects.com/api/articles/palantir-foundry-ontology-models/question-graph","ask":"https://miscsubjects.com/api/protocol/ask","ingest":"https://miscsubjects.com/api/protocol/ingest","claim":"https://miscsubjects.com/api/protocol/claim","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown"}}