Schema Stability Policy

Non-Breaking Changes

• Adding nullable fields
• Adding enum variants
• Adding new feed files
• Adding new manifest metadata keys

Breaking Changes

• Removing or renaming existing fields
• Changing field types
• Changing primary identifiers
• Changing route templates

Deprecation Policy

Breaking changes require a schema/interface version bump. Existing paths remain stable within the same interface version.

Before relying on a feed in production, always read /schedule.manifest.json and compare schema_version and agent_interface.version.