Start with the contract
Choose this when your first risk is shared semantics across app layers. Stabilize events, snapshots, and invariants before wiring runtime details.

This site is the canonical public surface for Legato documentation. If guidance in a README conflicts with content here, this docs site is authoritative.
Legato gives you two layers with one goal: predictable playback integrations.
@ddgutierrezc/legato-contract defines shared semantics (tracks, snapshots, events, errors, capabilities, invariants).@ddgutierrezc/legato-capacitor adds runtime integration (audioPlayer, mediaSession, listeners, sync helpers).Start with the contract
Choose this when your first risk is shared semantics across app layers. Stabilize events, snapshots, and invariants before wiring runtime details.
Integrate with Capacitor
Choose this when your first risk is native runtime behavior. Set up plugin surfaces, playback commands, and media-session listeners with contract semantics already aligned.
Harden for production
Choose this when you need rollout confidence: capability-gated controls, upgrade checklists, and compatibility boundaries validated in your CI.
If you want an opinionated sequence, use Golden Paths.
Getting Started
Use the decision hub to pick your path and plan your first 15 minutes.
Concepts
Learn the public boundary, canonical authority rules, and where maintainer docs live.
Package Guides
Find dedicated guides for the contract and Capacitor packages.
Reference
Use public API/reference entrypoints for integration details.
Community
Get contribution and support links without maintainer-only runbook details.