AxiomCore / EXPLORE
Get started

Declarative software for humans + agents.

Review a validation change beyond the text diff

A one-character validation edit can change an API boundary. Review source, semantic meaning, and affected consumers as separate questions.

By AxiomCore engineering ·

Changing a string field’s minimum length from 1 to 10 is a small source edit with a concrete behavioral consequence: values with fewer than ten characters are no longer accepted at that boundary. Counting changed lines alone does not explain the effect.

A useful review keeps three views together: the exact edit, the contract meaning, and the supported relationships to callers. AxiomCore’s Inspector is designed around this separation.

1. Confirm the source edit

In the Playground’s backend example, find the title validation declaration. Keep its type as a string and change only its minimum length from 1 to 10. Click Run after each version has compiled successfully so there is a valid before-and-after model to compare.

The text view should help you see the precise source edit. It is the right place to catch an accidental change to a nearby field or operation. A failed compilation should not silently become the new accepted application.

2. Explain the contract meaning

The semantic question is which accepted values changed, not how many internal graph objects were regenerated. Raising a minimum length tightens the input constraint. It may break a consumer that previously submitted a shorter value, even though the field name and operation name are unchanged.

Changing the field’s type is a different edit. An integer type and a string with a length constraint are not interchangeable. Review the declared type as well as explicit validation, and check both at the receiving boundary.

3. Follow the affected relationships

Use the impact view to investigate operations and UI actions connected to the changed field. Ask whether an input hint, client validation, authored test, or mock fixture needs updating. Treat the paths as a bounded account of relationships supported by the current evidence.

An external consumer may exist outside that model. Contract evidence helps scope a review; it does not prove that every deployed client has been discovered.

4. Exercise the boundary

Try one value below the new minimum and one that meets it. Confirm the rejection and success through the relevant runtime observations, rather than judging only by whether a button remains clickable. Review existing fixtures separately: changing an input constraint does not necessarily migrate stored records.

In the browser Playground, these observations come from a local mock backend. Repeat the important cases against your real service and supported client before a release. Keep production validation authoritative even when a frontend also checks the input.

5. Review the release, not just the editor

A reproducible review needs a known previous contract and a candidate built from pinned inputs. The maintained changes, impact, and CI guide explains the available Inspector workflow. Read it alongside the application’s own integration tests and release checks.

The point is to make a small edit’s consequences visible: what changed, what can now fail, which relationships are known, and what evidence still needs to be collected.

Related: what a coding agent needs beyond a file tree and adopting one contract in an existing stack.

AxiomStudio · Early access

Build with agents, first.

Join the AxiomStudio waitlist. We'll email you when early access opens.

We'll only email you about early access.

You're on the list.

We'll email when it opens.