Before a contract
Inputs, permission boundaries and error behavior were left implicit.
After a contract
A readable contract makes accepted input and safe refusal visible.
interface:
input: declared-fields
output: documented-shape
permissions: required
unavailable: explicit-error
next_step: safe-reviewInputs
Expected fields are clear.
Permissions
Missing authority is explicit.
Errors
Offer a safe next step.
Start with context.
Compatibility means different things in different environments. This sample starts by saying which surface is under discussion.
The useful next move is to record the assumption, make the boundary visible, and ask for a review before expanding scope.
Describe inputs.
List the fields and formats a tool expects. Clear inputs make a graceful refusal possible when something is missing.
The useful next move is to record the assumption, make the boundary visible, and ask for a review before expanding scope.
Describe outputs.
A small output contract helps a reader understand success and partial success. It should include the shape, not invented performance numbers.
The useful next move is to record the assumption, make the boundary visible, and ask for a review before expanding scope.
Respect permissions.
A compatible agent should state when authority is missing. Silence is not consent, especially around external actions.
The useful next move is to record the assumption, make the boundary visible, and ask for a review before expanding scope.
Make errors useful.
Return a reason and a next safe action where possible. An error message should not pretend that work completed.
The useful next move is to record the assumption, make the boundary visible, and ask for a review before expanding scope.
Test a narrow path.
Exercise one representative input and one unavailable condition. The goal is a useful conversation, not blanket certification.
The useful next move is to record the assumption, make the boundary visible, and ask for a review before expanding scope.
Keep the contract readable.
Document the assumptions beside the interface. A reader should not need hidden context to see the intended boundary.
The useful next move is to record the assumption, make the boundary visible, and ask for a review before expanding scope.
Choose the next small step.
Identify one uncertainty worth testing next. This sample does not establish a real standard or catalog status.
The useful next move is to record the assumption, make the boundary visible, and ask for a review before expanding scope.