The Semantic Layer
Source-grounded pack with Business Term Definition Map, Meaning to Infrastructure Brief, and Metric Semantic Audit, plus 1 more.
Get this packGrounded in the complete The Semantic Layer series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 4 usable skills · reviewed Jul 2026
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.
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 specification
Return a business term map with operating_scope, entity_definitions, source_and_identity, dimensions_and_segments, permissions_and_uses, custody, and reconciliation_decisions.
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 specification
Return a meaning-to-infrastructure brief with priority_concepts, semantic_contract_schema, implementation_bindings, delivery_and_permissions, agent_context_contract, validation_and_observability, and pilot_and_migration.
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 specification
Return a metric semantic audit with decision_metric_scope, metric_contracts, custody_and_lineage, duplicate_comparison, discrepancy_classification, operating_impact, and repair_priorities.
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 specification
Return a semantic change plan with change_contract, semantic_diff, business_data_contract, impact_map, history_and_reconciliation, migration_and_validation, and change_log_and_communication.
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.