@ontoboom

Human resources: the full employee lifecycle from requisition to alumni. Covers org structure (Organization, Department, Team, CostCenter, WorkLocation), workforce (Employee, Contractor), job architecture (JobFamily, JobGrade, JobPosition), recruiting pipeline (JobRequisition, Candidate, JobApplication, Interview, JobOffer), employment and compensation (Salary, Bonus, EquityGrant, Benefit), performance management (PerformanceCycle, PerformanceReview, Goal), skills and learning (Skill, SkillAssessment, LearningCourse, LearningEnrollment), leave (LeavePolicy, LeaveRequest), and payroll (PayrollRun, Payslip). Built for agents that need to reason over people data without per-HRIS schema gymnastics.

Supply chain and logistics, aligned with GS1 Global Standards: trading partners, products and trade items (GTIN / GLN / SSCC identifiers), production batches and serial numbers, physical locations and functional zones, shipments and consignments, purchase orders and despatch/receiving advice, inventory snapshots, product certifications, and recalls. Built for agents that need to reason over supply chain data without per-ERP schema gymnastics.

Capital markets + legal entities, aligned with the EDM Council's FIBO (Financial Industry Business Ontology, MIT License). Covers legal entity types with LEI/ISIN/CUSIP/FIGI identifiers, the full instrument hierarchy (equity, debt, derivatives, money market), markets and exchanges, portfolio positions, trade execution and settlement, corporate actions, credit ratings, and market indices/benchmarks. Built for agents that need to reason over investment data without per-vendor schema gymnastics.

Telecom / CSP ontology aligned with the TM Forum SID (Shared Information/Data Model): the Party, Customer, Product, Service, and Resource domains plus catalog, order, agreement/SLA, usage, billing, and trouble-management entities. The classic Product → CustomerFacingService → ResourceFacingService → Resource decomposition is modeled explicitly, so agents can reason from a customer's product down to the network resources that realize it.

Insurance (P&C + Life), aligned with the ACORD reference model: parties and roles, policies and coverages, insurable objects, the quote→bind underwriting pipeline, premium / billing / commission, and the full claims lifecycle (loss event → claim → reserve → settlement → subrogation/salvage). Built for agents that need to reason over policy and claim data without per-carrier schema gymnastics.

Customer 360: a unified, vendor-agnostic schema for the data agents need to reason about a customer end-to-end. Identity + accounts + subscriptions + touchpoints across CRM, marketing, support, billing, product analytics, and consent. Designed to sit on top of any warehouse (Snowflake / BigQuery / Postgres) where these signals already live.

Lightweight clinical schema: patient, encounter, practitioner, observation, condition, medication, and care plan. Inspired by FHIR R5 but trimmed to the minimum agents need to reason over a single visit. NOT a HIPAA-compliant production schema and NOT for clinical decision-making — use as a starting point for non-PHI synthetic workflows.

B2B multi-tenant SaaS: workspaces, members, roles, plans, entitlements, feature flags, usage events, invitations, and billing. The schema every B2B SaaS reinvents — agents that hop between products shouldn't have to.

Banking / fintech: parties, accounts, instruments, transactions, balances, KYC status, risk scores, and counterparty resolution. Designed for agents that need to reason over payment flows + compliance signals without per-vendor schema gymnastics.

Online retail: products, variants, carts, orders, fulfilment, payments, and returns. A vendor-agnostic baseline for agents that need to reason across Shopify / WooCommerce / custom storefronts without per-stack translation.

Account-based B2B CRM: companies, contacts, deals, pipeline stages, activities, and ownership. Designed as the canonical schema for agents that need to reason over a sales pipeline without per-tenant guessing.