Contract changes
Removed endpoints, renamed fields, type changes, and new requirements.
ChangeBench
Methods before metrics.
Continuity publishes fixtures, commands, raw outputs, and failure definitions before publishing benchmark results.
A benchmark should be reproducible, or remain unpublished.
The current harness includes one implemented endpoint-rename case. No comparative score is claimed.
Behavior changes
Authentication, pagination, error semantics, and runtime mismatches.
Adversarial safety
Malicious instructions, capsules, MCP calls, and prohibited network access.
Authoritative checks
A model never marks itself correct; the fixture's own checks decide.
Published artifacts
Fixture, command, raw output, tool version, and failure definition.
Current status
Endpoint rename implemented. Remaining categories are specified, not measured.
Make the next change survivable.
Start with the local engine. Connect the network when it creates value.