Business objects with scope, sources and time.

Guide

Use this before you automate the work.

Step 1

15 objects from one canonical model

This versioned view extracts the existing Company Twin definitions rather than introducing a second ontology. The download records the ontology version and exact source hash.

• Organization, Person, Lead, Opportunity and Quote
• Order, Contract, Invoice, Payment and Product
• Service, Project, WorkItem, Appointment and Asset

Step 2

Use the binding for your stack

The ZIP includes JSON Schema 2020-12, TypeScript types, Pydantic 2 models, typed Zod 4 schemas and a Python validator CLI. The README includes installation and usage commands.

• Required, optional and nullable fields remain distinct.
• Money fields use integer minor units; currency is never inferred.
• 100 synthetic fixtures cover valid records, provenance, scope, timestamps, unknown fields, confidence and integer money.

Step 3

Understand the crosswalks and limits

Five existing mappings cover HubSpot, QuickBooks, Stripe, Shopify and Zendesk with source hashes and official documentation URLs. The README explains conceptual alignment with schema.org, UBL, OCEL 2.0 and CloudEvents.

• Mappings preserve transformations and describe their source shape; they are not complete vendor schemas.
• Schema validation proves structural shape, not authentic evidence, tenant authorization or permission to act.
• Lifecycle and relationship legality remain governed by the existing runtime contracts.

Questions

Before you hand this off