Advanced Declarative Reference

Use the generated declarative schema reference for field-level detail after the workflow is clear.

The generated declarative reference documents the versioned JSON Schema artifacts that define supported document shapes. Treat it as the field-level companion to the declarative workflow.

Best Entry Points

Where To Start

Task	Start With	Why
Checking supported kinds	Generated declarative reference	It lists the schema-backed kinds directly
Confirming field names and types	Generated declarative reference	It is the field-level source of truth
Understanding per-kind schema files	Generated declarative reference	It points straight at the per-kind artifacts
Wiring editor schema mappings	Generated declarative reference	It exposes the exact schema path to map
Planning a safe rollout workflow	Product guides	They explain validate, plan, apply, and operational safety
Understanding schema vs semantic validation	Product guides	They explain why both validation layers exist
Learning how assets, models, semantics, and products fit together	Product guides	They connect the schema to the platform mental model

Runtime Contract

declarative reads are strict by default, so missing supported endpoints fail the operation instead of being skipped
plan uses exit code 0 for clean, 2 for actionable drift, and 1 for blocking declarative errors
apply aborts before mutation when blocking declarative errors are present
the operational success condition is a clean follow-up plan after apply

Editor Integration

Map the union schema:

schemas/declarative/v1/duck.declarative.schema.json

to your config file patterns in your editor.

Next Steps

Generated Declarative ReferenceInspect schema fields and kinds. Declarative DeliveryApply schema in real workflows.