{"assets_path":"frozen/tasks/arc-crm-001/assets","domain":"CRM and sales operations","harbor_digest":"sha256:8f2f3fb0725b266c4c2019a04451842ca5ae07ae1b787093d4ec878905ddcb7b","harbor_task":"blobfishai/arc-crm-001","instruction":"Finish the contact-onboarding thread for Aster Freight. Determine the verified existing client, create only the newly requested contact, and leave account records and existing contacts unchanged. Record the association in a client handoff.\n\nInvestigate the current request, operative policies, permissions and relevant records before any write. Earlier messages and expired policies are not authority. Preserve every unrelated record and financial field. Persist the requested handoff and read back every changed record plus that handoff before submitting the structured answer. The handoff is graded by its entity, record/evidence references and explicitly requested literal facts, not by exact prose or semantic judgment. All organizations, tools and assets are synthetic; no external action is authorized. This is a partial clean-room Arc CRM adaptation using the HubBench engine and its context/answer controls, not a released HubBench family.\n\nIn the handoff content include these literal facts or IDs, resolved from the evidence and persisted records: resolved existing client ID, new contact's verified email, current request ID. Set evidence_ids to the operative request and policy/approval/document asset IDs used for the action.","model_evaluated":false,"oracle_score":100,"oracle_strict_pass":true,"oracle_trajectory_path":"evidence/registry/arc-crm-001/verifier/trace.json","synthetic":true,"task_id":"arc-crm-001","task_path":"frozen/tasks/arc-crm-001/task.json","title":"Onboard a buyer without duplicating the account"}
{"assets_path":"frozen/tasks/arc-crm-002/assets","domain":"CRM and sales operations","harbor_digest":"sha256:41a67a661082e6b5b21e8b135ded7726c6c4a9da03459dfec85d1eb2205c45cb","harbor_task":"blobfishai/arc-crm-002","instruction":"Resolve the renewal-stage thread for Boreal Instruments. Update only the opportunity selected by the latest owner clarification under the operative stage policy. Preserve amount, currency, ownership and the other opportunities; leave a fact-grounded note.\n\nInvestigate the current request, operative policies, permissions and relevant records before any write. Earlier messages and expired policies are not authority. Preserve every unrelated record and financial field. Persist the requested handoff and read back every changed record plus that handoff before submitting the structured answer. The handoff is graded by its entity, record/evidence references and explicitly requested literal facts, not by exact prose or semantic judgment. All organizations, tools and assets are synthetic; no external action is authorized. This is a partial clean-room Arc CRM adaptation using the HubBench engine and its context/answer controls, not a released HubBench family.\n\nIn the handoff content include these literal facts or IDs, resolved from the evidence and persisted records: resolved opportunity ID, updated stage, updated probability as an integer percentage, current request ID. Set evidence_ids to the operative request and policy/approval/document asset IDs used for the action.","model_evaluated":false,"oracle_score":100,"oracle_strict_pass":true,"oracle_trajectory_path":"evidence/registry/arc-crm-002/verifier/trace.json","synthetic":true,"task_id":"arc-crm-002","task_path":"frozen/tasks/arc-crm-002/task.json","title":"Apply the clarified renewal stage"}
{"assets_path":"frozen/tasks/arc-crm-003/assets","domain":"CRM and sales operations","harbor_digest":"sha256:6feddf5ae5d998f20fa6b52ca85ca79eb344e8976cb7dfdc4f4cfca9ca3d8737","harbor_task":"blobfishai/arc-crm-003","instruction":"Prepare the requested Cedar Analytics renewal quote. Reconcile current unit prices and the owner's quantities with the valid discount approval. Report undiscounted and quoted totals in minor currency units and the difference from the two supplied commercial alternatives. Create only the authorized draft, not an approved or signed quote.\n\nInvestigate the current request, operative policies, permissions and relevant records before any write. Earlier messages and expired policies are not authority. Preserve every unrelated record and financial field. Persist the requested handoff and read back every changed record plus that handoff before submitting the structured answer. The handoff is graded by its entity, record/evidence references and explicitly requested literal facts, not by exact prose or semantic judgment. All organizations, tools and assets are synthetic; no external action is authorized. This is a partial clean-room Arc CRM adaptation using the HubBench engine and its context/answer controls, not a released HubBench family.\n\nIn the handoff content include these literal facts or IDs, resolved from the evidence and persisted records: resolved opportunity ID, computed discounted total in minor USD units, draft status, operative approval ID. Set evidence_ids to the operative request and policy/approval/document asset IDs used for the action.","model_evaluated":false,"oracle_score":100,"oracle_strict_pass":true,"oracle_trajectory_path":"evidence/registry/arc-crm-003/verifier/trace.json","synthetic":true,"task_id":"arc-crm-003","task_path":"frozen/tasks/arc-crm-003/task.json","title":"Prepare a priced draft within current approval"}
{"assets_path":"frozen/tasks/arc-crm-004/assets","domain":"CRM and sales operations","harbor_digest":"sha256:11b680b7129f112fb7ee1dcfe6b4d462510ecbc2be2c259782d747ce334c38f7","harbor_task":"blobfishai/arc-crm-004","instruction":"Resolve Delta Cooling's revised quote request. Cancel only the superseded draft, create its authorized replacement with explicit lineage, and preserve the signed quote and all historical lines. Leave a stakeholder note and read back both versions.\n\nInvestigate the current request, operative policies, permissions and relevant records before any write. Earlier messages and expired policies are not authority. Preserve every unrelated record and financial field. Persist the requested handoff and read back every changed record plus that handoff before submitting the structured answer. The handoff is graded by its entity, record/evidence references and explicitly requested literal facts, not by exact prose or semantic judgment. All organizations, tools and assets are synthetic; no external action is authorized. This is a partial clean-room Arc CRM adaptation using the HubBench engine and its context/answer controls, not a released HubBench family.\n\nIn the handoff content include these literal facts or IDs, resolved from the evidence and persisted records: cancelled quote ID, newly created replacement quote ID returned by the CRM, replacement total in minor USD units, protected signed quote ID. Set evidence_ids to the operative request and policy/approval/document asset IDs used for the action.","model_evaluated":false,"oracle_score":100,"oracle_strict_pass":true,"oracle_trajectory_path":"evidence/registry/arc-crm-004/verifier/trace.json","synthetic":true,"task_id":"arc-crm-004","task_path":"frozen/tasks/arc-crm-004/task.json","title":"Replace a superseded draft while retaining signed history"}
{"assets_path":"frozen/tasks/arc-crm-005/assets","domain":"CRM and sales operations","harbor_digest":"sha256:c7acf1a8aa113be2623cf0a1767e408ff3d56c96b5b721cc2ec09ebce2d886a9","harbor_task":"blobfishai/arc-crm-005","instruction":"Prepare the internal contract draft for Ember Diagnostics from the current approved commercial record. Verify the client, quote, opportunity and signing limits. Persist only an unsigned draft and a legal-review handoff; do not accept, sign or activate anything.\n\nInvestigate the current request, operative policies, permissions and relevant records before any write. Earlier messages and expired policies are not authority. Preserve every unrelated record and financial field. Persist the requested handoff and read back every changed record plus that handoff before submitting the structured answer. The handoff is graded by its entity, record/evidence references and explicitly requested literal facts, not by exact prose or semantic judgment. All organizations, tools and assets are synthetic; no external action is authorized. This is a partial clean-room Arc CRM adaptation using the HubBench engine and its context/answer controls, not a released HubBench family.\n\nIn the handoff content include these literal facts or IDs, resolved from the evidence and persisted records: newly created contract ID returned by the CRM, approved quote ID, contract value in minor USD units, unsigned status, legal review recipient. Set evidence_ids to the operative request and policy/approval/document asset IDs used for the action.","model_evaluated":false,"oracle_score":100,"oracle_strict_pass":true,"oracle_trajectory_path":"evidence/registry/arc-crm-005/verifier/trace.json","synthetic":true,"task_id":"arc-crm-005","task_path":"frozen/tasks/arc-crm-005/task.json","title":"Draft a contract from the approved commercial record"}
{"assets_path":"frozen/tasks/arc-crm-006/assets","domain":"CRM and sales operations","harbor_digest":"sha256:489537c709c76416479567fd0601099bb9de898201c49f258fee03d56954c9a9","harbor_task":"blobfishai/arc-crm-006","instruction":"Complete Fjord Packaging's document association thread. Resolve the corrected opportunity and approved document; attach only the seeded mock object, preserve earlier associations and all other records, and record a handoff that identifies the actual association.\n\nInvestigate the current request, operative policies, permissions and relevant records before any write. Earlier messages and expired policies are not authority. Preserve every unrelated record and financial field. Persist the requested handoff and read back every changed record plus that handoff before submitting the structured answer. The handoff is graded by its entity, record/evidence references and explicitly requested literal facts, not by exact prose or semantic judgment. All organizations, tools and assets are synthetic; no external action is authorized. This is a partial clean-room Arc CRM adaptation using the HubBench engine and its context/answer controls, not a released HubBench family.\n\nIn the handoff content include these literal facts or IDs, resolved from the evidence and persisted records: approved document ID, corrected opportunity ID, current request ID. Set evidence_ids to the operative request and policy/approval/document asset IDs used for the action.","model_evaluated":false,"oracle_score":100,"oracle_strict_pass":true,"oracle_trajectory_path":"evidence/registry/arc-crm-006/verifier/trace.json","synthetic":true,"task_id":"arc-crm-006","task_path":"frozen/tasks/arc-crm-006/task.json","title":"Associate the corrected evidence without cross-client leakage"}