des-serving-layer-design

What problem does it solve?

des-serving-layer-design prevents AI agents from designing data products that consumers cannot safely use by defining how Gold outputs and semantic objects are delivered through trusted serving channels with clear access, freshness/quality visibility, performance expectations, and feedback/usage monitoring.

Core Features & Use Cases

• Serving Layer Specification design: produce a complete serving blueprint covering scope, non-scope, consumer/persona mapping, channel inventory, and Gold/Semantic-to-serving mappings.
• Trust, security, and experience alignment: document access control/security model, freshness and quality visibility, performance/latency expectations, and caching/materialization expectations.
• Consumer-safe validation artifacts: create Phase 17 support plan, evidence pack, artifact revision notes, Done Gate decision, and Phase 17→18 handoff requirements (without implementing dashboards/APIs/pipelines).

Quick Start

Use the des-serving-layer-design skill to create the serving specification for your Phase 17 scope by routing Phase 17 based on your Phase 16 semantic model specification and Phase 16 handoff.