The model is told to schedule a follow-up when needed, but the app needs deterministic action data before it can touch a calendar. Consumer need -> schema -> validator -> ADR The common trap is asking for JSON without deciding what the next system is allowed to execute. A parseable object can still be unsafe, ambiguous, or impossible to validate. Name the consumer The backend calendar service needs a request object, not a sentence: customer_id, reason, proposed_time, evidence, and confirmation flag. The consumer defines the contract. The model does not get to invent whatever shape feels natural. Define schema Use…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in