/**
 * The PIG schema.
 *
 * Read in this order to understand the domain:
 *
 *   ontology (in @pig/core)  the vocabulary — teams, stages, tiers
 *   identity                 who may use PIG, and as what
 *   crm                      accounts, contacts, activities — the ordinary part
 *   supply                   sites, priced inventory, capacity we have bought
 *   demand                   what customers want, and what we have sold
 *   allocations              the join between the two. The reason PIG exists.
 *   contracts                MSA, DPA, SLA, order forms, obligations
 *   compliance               export control as a predicate on the match
 *   calendar                 the one dated row type nothing else owns
 *   motion                   the reusable practice bound to the demand stages
 *   agent                    the leased task queue and evidence-bearing facts
 *   fields                   user-defined fields
 */
export * from './enums';
export * from './identity';
export * from './settings';
export * from './crm';
export * from './supply';
export * from './demand';
export * from './allocations';
export * from './contracts';
export * from './compliance';
export * from './calendar';
export * from './learn';
export * from './motion';
export * from './agent';
export * from './fields';
export * from './integrations';
export * from './imports';
export * from './google';
export * from './notion';
