Repository navigation
BPO: Build Palantir Ontology for Toybox - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Builds a Palantir-style ontology layer for
sonoxo/toyboxwithout rewriting the existing curated README.Added
ONTOLOGY.mdarchitecture and Foundry mappingontology/schema.jsonwith object types, shared properties, interfaces, link types, object group, and governed action typesontology/seed.jsonwith platform, stamp, policy, and provenance seed objectsscripts/ingest_readme.pyto materialize README categories/tools as graph-ready JSONscripts/validate_ontology.pyto enforce schema/data integrity.github/workflows/ontology.ymlfor CI validationOntology primitives
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.