ontology-objecttype

/ontology-objecttype - ObjectType Definition Assistant

Version: 3.0.0 | Model: opus

---

Overview

---

Cross-Skill Integration

---

Commands

---

Detection Patterns

---

Interactive Workflow (Phase 1-4)

Phase 1: Context Clarification

Purpose: Clarify source type and business domain

AskUserQuestion(questions=[
    {
        "question": "What is your source for this ObjectType definition?",
        "header": "Source Type",
        "options": [
            {"label": "Existing source code", "description": "Python, Java, TypeScript"},
            {"label": "Database schema", "description": "SQL DDL, ORM models"},
            {"label": "Business requirements", "description": "Requirements documents"},
            {"label": "Manual definition", "description": "New domain model"}
        ]
    }
])

Validation Gate: source_validity

Phase 2: Entity Discovery

Purpose: Extract entities + PK strategy + Property type mapping

1. Scan source code for entity candidates
2. Select Primary Key strategy (single_column / composite / composite_hashed)
3. Map Python types to Foundry DataTypes

Validation Gates: candidate_extraction, pk_determinism

Phase 3: Link Definition

Purpose: Detect relationships and define cardinality

Validation Gate: link_integrity

Phase 4: Validation & Output

Purpose: Final validation and YAML generation

Validation Gate: semantic_consistency

---

Validation Gates

---

PK Strategy Options

---

DataType Mapping

---

Output Format

L1 - Candidate Summary

Found 12 Entity Candidates
  ObjectType candidates (8): Employee, Department, Project...
  Review needed (2): DTO/Mixin patterns
  Excluded (2): Helper/Config classes

L2 - Per-Class Analysis

entity_name: Employee
pk_strategy: single_column
pk_column: employee_id
properties:
  - api_name: employeeId
    data_type: STRING
    required: true
    is_pk: true

L3 - Full YAML Definition

# objecttype-Employee.yaml
api_name: Employee
display_name: Employee
primary_key:
  source_columns: [employee_id]
  strategy: single_column
properties:
  - api_name: employeeId
    data_type: STRING
    required: true
links:
  - link_type_name: EmployeeToDepartment
    target_object_type: Department
    cardinality: MANY_TO_ONE

---

Session State

{
  "session_id": "obj-a1b2c3",
  "target_path": "/home/palantir/my-project",
  "current_phase": "phase_2_entity",
  "phase_results": {
    "phase_1_context": { "status": "completed" },
    "phase_2_entity": { "status": "in_progress" },
    "phase_3_link": { "status": "pending" },
    "phase_4_output": { "status": "pending" }
  }
}

---

Reference System

Local Reference (ontology-definition package)

/home/palantir/park-kyungchan/palantir/Ontology-Definition/
├── ontology_definition/types/    # Type definitions
├── ontology_definition/core/     # Enums, base classes
└── tests/                        # Usage examples

External References (WebSearch/WebFetch)

Trusted sources only:

• palantir.com/docs/* (Official documentation)
• github.com/palantir/* (Official repositories)
• Palantir case studies and conference materials

---

Error Handling

---

Version History

End of Skill Definition