Debugging playbook

Spec Contract Mismatch

Use when Spec validation, conformance, diff, generation, or release-gate spans fail.

Linked toolsok
4
Source: playbook registry
Updated: 5/25/2026, 5:11:10 PM
Evidence/query
Commandsok
2
Source: playbook registry
Updated: 5/25/2026, 5:11:10 PM
Evidence/query
SpecEvalsDocsTrace
Symptoms
  • spec span failed.
  • Contract evidence reports mismatch.
  • Release gate blocks downstream work.
Likely Causes
  • Route output does not match OpenAPI or platform contract.
  • Discovery files disagree.
  • Schema changed without regenerating docs.
Checks
  • Open Spec validation evidence.
  • Validate /openapi.yaml and /llms-index.json.
  • Compare route response shape to { ok, data } or JSON-RPC.
Evidence To Collect
  • spec validation ID
  • route
  • schema
  • diff summary
platphormctl Commands
platphormctl site inspect trace
platphormctl policy inspect trace