Describe the work
Provide the recurring problem, rules, desired output, and permitted or anonymized samples. Identify business and IT contacts.
Know what to prepare, how the result will be checked, and who is responsible after launch.
Provide the recurring problem, rules, desired output, and permitted or anonymized samples. Identify business and IT contacts.
Confirm access, network conditions, accounts, and permitted actions before implementation. Agree the first task, fees, and acceptance criteria.
Deployment depends on the solution. Hosting, private deployment, or local execution is not assumed from a product name or subscription.
Identify where work runs and information is read, copied, transmitted, stored, or processed. Include models, document processing, and third-party services.
Confirm access, credentials, retention, logs, backup, and recovery responsibilities. Local execution does not itself mean all information stays on the customer network.
Agree outputs and acceptance in advance. Test normal work, missing information, differences, failed access, human waiting, and recovery within the included work.
Check completed and unfinished items against source records. Verify unclear external results before deciding whether to retry.
Confirm instructions, readiness, and handover before operation.
The agreement identifies channels, service hours and time zones, severity, escalation, updates, and maintenance.
Define responsibilities for YuanLite work, customer systems, networks, and third parties. Initial response, business restoration, and final resolution are separate commitments.
Service-level targets require agreed definitions, measurement boundaries, and supporting operating arrangements.
Assess changes to systems, records, rules, volumes, or actions. Agree the update, any fees, and validation before introducing it.
Confirm renewal or termination, access removal, data return or export, retention, and deletion as applicable. AI agent subscription terms are agreed separately where relevant.