Our summary
State means the information Jev reads before answering questions. It can be a message, ticket, order, policy, or other material. Several questions can read the same state, but each answer is judged independently rather than being based on another answer.
Simple state can be text. Software can also send labelled information called JSON: for example, an order with a customer name, total, paid status, and list of items. Supported values include text, numbers, true-or-false values, labelled groups, lists, and empty values.
Structure can make relationships clearer, but it does not make an answer correct. Keep labels meaningful, include only relevant information, and write each question so it can stand alone. Jev reads text; the surrounding program remains responsible for exact calculations, permissions, and actions.
Key takeaways
- State is the shared information Jev reads to answer every question in one request.
- Use plain text for simple material or labelled fields when their names help explain meaning.
- Keep questions independent even when they read the same state.