Explanatory breakdown of a Decantr blueprint contract. Shows sections, routes, features, patterns, guard rules, and generated context as a coherent system rather than a flat JSON file.
@official/decantrMay 13, 2026
How to use this
What to do next
Use this as a high-signal reference for the interaction and layout it describes.
Inspect the contract before rebuilding the same component by hand.
Keep the pattern structure and responsive behavior intact when translating it into runtime code.
Contract explorer
Inspect the source of truth
The contract remains available when you need route detail, theme bindings, or raw JSON for automation.
@official/blueprint-anatomy — contract
112 lines4.1 KB20 root entriesschema
id
stringstring
io
object3 keys
name
stringstring
motion
object2 keys
$schema
stringstring
presets
object1 keys
version
stringstring
contained
booleanboolean
components
object5 items
responsive
object3 keys
composition
object4 keys
description
stringstring
dependencies
object3 keys
interactions
object3 items
layout_hints
object3 keys
visual_brief
stringstring
accessibility
object5 keys
decantr_compat
stringstring
default_layout
object3 keys
default_preset
stringstring
Registry evidencePublisher and verification details
Registry intelligence
This item is authored and structured, but it is not currently one of the primary recommended references.
Recommended because: Official registry source, Structured authored contract coverage is strong, Copyable implementation guidance is present, Authored confidence score meets the recommendation threshold
Holding back: Authored quality score is below the recommendation threshold