Real operational evaluation · authorised, non-personal, non-confidential case facts only · no uploads, pasted documents, screenshots or private links · Read the data boundary
OSE Obligation Satisfaction Engine

Restricted evaluation terms

Information for the separately restricted OSE evaluation environment.

Evaluation use and information boundary

Access is private and approval-based. You may evaluate OSE against genuine operational situations using only information that your organisation authorises and that is non-personal and non-confidential. Enter actual obligations in neutral language, actual dates, permitted conditions, measurements and outcomes where those facts do not identify a person or disclose confidential commercial information. If a case needs confidential wording or identifying detail to make sense, do not enter it.

Do not enter personal case data, confidential business or commercial information, verbatim contract text, person/customer/supplier names, non-public order/shipment references, confidential thresholds, contact details or credentials. Do not upload files, import workspaces, paste document or screenshot contents, or enter private document links. Use text-only facts with generic source categories and neutral case labels. Recognisable URLs and email addresses are rejected in case text, but this check cannot identify every name, sensitive fact or copied document; users remain responsible for checking their entries.

File upload, workspace-file import and source-file download routes are disabled in this profile. Assessment-data exports remain available to organisation owners and contain the text entered; keep them within the same information boundary.

OSE records the facts supplied by users and applies its supported rules. It does not interpret the customer's contract, inspect or authenticate source documents, or make legal, financial or irreversible commercial decisions. Results require human review.

The 14-day evaluation begins when the invited organisation owner activates access. Access expires server-side; expiry restricts workspace routes but does not automatically erase records or create a payment, renewal or paid entitlement. Continued service requires a separate agreement and approved provisioning.

These evaluation terms are a draft and require owner/legal approval before external access is opened.