Skip to content

BPO: Build Palantir Ontology for Toybox - #1

Merged
sonoxo merged 6 commits into
mainfrom
feature/palantir-ontology
Sep 7, 2026
Merged

sonoxo merged 6 commits into
mainfrom
feature/palantir-ontology

Conversation

@sonoxo

@sonoxo sonoxo commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Summary

Builds a Palantir-style ontology layer for sonoxo/toybox without rewriting the existing curated README.

Added

  • ONTOLOGY.md architecture and Foundry mapping
  • ontology/schema.json with object types, shared properties, interfaces, link types, object group, and governed action types
  • ontology/seed.json with platform, stamp, policy, and provenance seed objects
  • scripts/ingest_readme.py to materialize README categories/tools as graph-ready JSON
  • scripts/validate_ontology.py to enforce schema/data integrity
  • .github/workflows/ontology.yml for CI validation

Ontology primitives

  • Object Types: Tool, Category, Platform, Capability, Interface, Stamp, Source, Policy
  • Link Types: contains, runsOn, hasCapability, hasInterface, hasStamp, sourcedFrom, governedBy, alternativeTo, dependsOn
  • Interfaces: CatalogEntity, ExecutableTool
  • Actions: RegisterTool, UpdateToolMetadata, SetToolLifecycle, AttachCapability, AttachPlatform, AttachPolicy, ApproveTool, DeprecateTool

This follows Palantir Foundry's ontology model of semantic resources (objects/properties/links/interfaces) plus kinetic resources (actions/functions/governance), while keeping tool execution permissioned by consuming applications rather than auto-running catalog entries.

@sonoxo
sonoxo merged commit 14abf1e into main Sep 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant