Rubric Protocol commits to the following stability guarantees for all customers on Standard, Enterprise, and Dedicated tiers.
Breaking changes require 180 days notice. A breaking change is any change that would cause a customer's existing, conformant integration to fail. This includes removing fields, changing field semantics, removing endpoints, or changing authentication requirements.
Additive changes require no notice. New fields, new endpoints, new leaf types, and new optional capabilities may be introduced at any time and will not break existing integrations.
Security-mandatory changes may require shorter notice. In the event of a critical security issue requiring a breaking change to remediate, Rubric reserves the right to deploy the change with as little as 7 days notice. Such changes will be communicated to all affected customers via direct email and the public status page.
Historical attestations remain verifiable indefinitely. Attestations written under any prior schema version will remain verifiable by current and future versions of the Rubric verifier. Protocol evolution is additive with respect to historical records.
Cryptographic algorithms follow NIST IR 8547 deprecation timelines. Algorithms deprecated by NIST will be transitioned to new primary suites according to NIST's published schedule, with migration paths documented at least 18 months before algorithm disallowance. Every Rubric attestation carries an explicit algorithm suite identifier, enabling crypto-agile migration without invalidating historical records.
Developer tier (free): best-effort notice of breaking changes via public changelog. No individual notification commitment.
Standard tier ($999/mo and above): 180 days notice by email to the registered technical contact, plus public changelog.
Enterprise and Dedicated tiers: 180 days notice by email plus a migration support consultation scheduled at no additional cost.
Deprecation notices are sent to the primary technical contact registered for each API key. To update your contact information, email support@rubric-protocol.com.
To report a security issue, see our security contact.