Many failures attributed to the model originate in poor inputs. A prompt input contract defines accepted data, validity conditions and what happens when prerequisites are unmet.
Specify required and optional fields
Every field needs a name, type, permitted length and example. Missing required information should stop the workflow rather than trigger a silent assumption.
Preserve provenance and time
Connect each input to its source system, owner and update time. Correct information that is no longer current can produce equally incorrect outputs.
Check permission to use the data
Record whether processing, sending to the provider and retention are permitted. The contract should reject content that violates the data policy.
Normalise formats
Convert dates, units, languages and codes into a consistent representation. Consistency reduces ambiguity and makes evaluation repeatable.
Provide a clear validation report
A rejection should explain which field failed and how to fix it. This makes the contract a collaboration tool rather than an invisible barrier.
This framework is DigitalNow's original editorial methodology.