The short answer
References are selected criteria or context used to interpret observations and assess relevance. They express what a value or situation means; mandatory restrictions require separate enforcement in the connected execution path.
A value needs a frame
A support agent observes that a case is six hours old. A reference states that responses should normally be prepared within four hours. Together they suggest a delay worth assessing. The observation describes the case; the reference describes the desired interpretation.
References can also express qualitative guidance, such as what constitutes an adequately supported answer. They help an assessor reason consistently across cases, while retaining the selected context that explains its judgment.
A desired range is not a hard prohibition
A four-hour response target does not mean the agent must send whatever it has at hour four. If evidence is incomplete and sending requires approval, those restrictions still apply. Treating the reference as an unconditional action trigger would erase the distinction between desirability and permission.
The concept guide separates references from limits and budgets. A desired quality level provides assessment context. A tool prohibition or approval requirement must be implemented through the host’s actual controls.
Version the context that shaped a judgment
The signal and reference catalog uses immutable records selected through governance. Revising the desired response window means creating and selecting the appropriate record, rather than quietly changing the meaning of an existing observation.
A reviewer should be able to ask which reference applied when a mission was assessed. Historical work may have used an earlier target, and a current owner correction may require reevaluation. Retaining those differences makes policy changes explainable.
Use references to improve assessment
Start with a small set of criteria that help choose or evaluate work. For support, distinguish factual grounding, case relevance and expected response time. State where those criteria come from and when their evidence becomes outdated. Do not make a long document stand in for execution controls.
Test a case where the reference encourages action but a limit blocks it. The correct behavior is to preserve the conflict and seek an authorized path, perhaps escalation. That test helps confirm that interpretation cannot quietly promote itself into authority.
Make customer expectations explicit
Different customers interpret the same observation differently. A four-hour wait may be acceptable for one workflow and urgent for another. References give your product a place to express those expectations separately from mandatory restrictions. AgentPlat connects selected interpretation criteria to the ongoing work record. This can help your team build products that adapt to organizational context while keeping security and spending boundaries explicit. The commercial design question is which expectations customers should configure and which restrictions your product must enforce consistently.
Explore AgentPlat 1.1 adoption when your engineering team is ready to assess the integration, and use the concept series to align product and technical stakeholders on the work model.
Sources and further reading
Documentation reviewed . Consult the linked documentation for current implementation details.