The Semantic Layer
Source-grounded pack with Business Term Definition Map, Meaning to Infrastructure Brief, and Metric Semantic Audit, plus 1 more.
Use this pack when
Choose this pack when the work touches The Semantic Layer and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Included workflows
Choose the job in front of you.
4 source-grounded skills. Load one workflow at a time.
Business Term Definition Map
Use this workflow when business entities, terms, lifecycle states, dimensions, or segments such as customer, account, ARR, active user, pipeline, implementation, severity, or risk mean different things across teams, systems, dashboards, workflows, and decisions.
Output Return a business term map with operatingscope, entitydefinitions, sourceandidentity, dimensionsandsegments, permissionsanduses, custody, and reconciliationdecisions.
Meaning to Infrastructure Brief
Use this workflow when governed business definitions must become reusable, versioned, machine-readable infrastructure for metrics, dashboards, workflows, APIs, operating reviews, and permissioned AI or agent context without duplicating meaning in every consuming surface.
Output Return a meaning-to-infrastructure brief with priorityconcepts, semanticcontractschema, implementationbindings, deliveryandpermissions, agentcontextcontract, validationandobservability, and pilotandmigration.
Metric Semantic Audit
Use this workflow when important metrics disagree across dashboards, decks, spreadsheets, SQL, models, workflows, or teams and need audit of underlying entities, business definition, formula, scope, owner, source, freshness, exceptions, approved uses, comparability, and operating-review impact.
Output Return a metric semantic audit with decisionmetricscope, metriccontracts, custodyandlineage, duplicatecomparison, discrepancyclassification, operatingimpact, and repairpriorities.
Semantic Layer Change Plan
Use this workflow when pricing, product instrumentation, lifecycle states, revenue rules, territories, ownership, schemas, or business policy changes the meaning of entities, metrics, dimensions, or segments and downstream comparisons, workflows, reports, and agents must be reconciled safely.
Output Return a semantic change plan with changecontract, semanticdiff, businessdatacontract, impactmap, historyandreconciliation, migrationandvalidation, and changelogandcommunication.
Human review
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.
Source and files
Grounded in the complete The Semantic Layer series.
10 source essays · 4 usable skills · reviewed Jul 2026