← Back to selected work

SpecShift

A visual API change-review studio, from React interface to Django comparison service.

An independent full-stack project that helps a reviewer trace a contract change to exact evidence and the operations that depend on it.

Preview boundary: The initial comparison uses synthetic records. The free comparison API may need time to wake.

The problem

An API diff can show that a field changed without explaining which operations depend on it or which compatibility assumptions matter. Reviewers need the original evidence, a reasoned finding, and a visible statement of what the analysis cannot assess.

What I built

A React and TypeScript studio connected to a Django REST Framework comparison service. A findings list, contract evidence panel, and dependency map present the same comparison from different perspectives. Reviewers can export a JSON result or a self-contained HTML report.

Frontend and backend boundaries

  • The interface selects and explains findings; the Python engine owns classification rules.
  • A recorded synthetic example makes the initial studio useful while the API is waking.
  • The service processes documents in memory with size and work limits, and rejects external references.
  • Unsupported constructs remain explicit coverage gaps instead of silently producing a clean verdict.

A useful demonstration

  1. Open the studio and inspect the recorded example label.
  2. Select the response enum finding for the order status.
  3. Compare its baseline and candidate evidence, then inspect the dependent operations.
  4. Open the source to follow the interface and comparison service. Run a new comparison separately if you want to inspect the API path.

Scope and verification

The current source documents support for a bounded OpenAPI 3.0.0-3.0.3 subset. Contract reachability does not establish actual runtime client failure. Unsupported or unclassified changes require human review.

The public recorded studio, README and frontend package manifest were inspected on 13 November 2026. This portfolio update did not rerun the project suites or execute a new API comparison. The documented accessibility work is partial, not a claim of complete conformance.