{ "edition": "R1", "language": "en", "criteria": [ { "id": "POC-01", "title": "One question and one route", "applies_to": [ "retained-run", "conditional-existing-operator", "planning" ], "expected": "One bounded question, one route, a supported input or a clearly pending use case, and a reviewer are recorded.", "how_to_check": "Write what decision the result will inform. For the audit route use CREATE_AUDIT_ARTIFACT with the exact intent create audit artifact; for reading identify the retained record.", "evidence": "Planning worksheet; agreed scope and input reference.", "source_url": "/guides/poc/deployment.html#scenario" }, { "id": "POC-02", "title": "An eligible installation and operating handoff", "applies_to": [ "conditional-existing-operator" ], "expected": "The operator confirms the exact release, matching client/service, supplied endpoint, operation permission, unused approved key and report access before submission.", "how_to_check": "Record non-secret references and the responsible contact for every handoff item. Mark missing items open; a retained run cannot fill them.", "evidence": "Delivery and administrator confirmations; approved procedure and request references.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-handoff" }, { "id": "POC-03", "title": "Baseline and unknowns are visible", "applies_to": [ "retained-run", "conditional-existing-operator" ], "expected": "Reproduction records both status and health exits plus relevant component states and reasons. Reading records the published baseline and explicitly identifies observations that were not published.", "how_to_check": "Keep the same supplied service/account context. Copy actual states and reasons; assign any required unknown or non-ready prerequisite to its owner before a new submission.", "evidence": "Baseline observation reference; status/health exits and relevant literal reasons.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-baseline" }, { "id": "POC-04", "title": "One Work stays identifiable", "applies_to": [ "retained-run", "conditional-existing-operator" ], "expected": "The saved returned Work ID agrees with the inspected list, show and selected report; no replacement execution is used to resolve uncertainty.", "how_to_check": "Compare each Work ID and the selected report revision. If no ID was returned, preserve the original request and use the support reconciliation route.", "evidence": "Original request reference, Work ID and same-Work comparison notes.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-reconcile" }, { "id": "POC-05", "title": "The product outcome is copied accurately", "applies_to": [ "retained-run", "conditional-existing-operator" ], "expected": "Execution count, validation, final result, retry/replay fields and closure are recorded as returned, including pending human acceptance.", "how_to_check": "Read the selected canonical report and returned result together. Leave unavailable fields unobserved; do not replace them with example values.", "evidence": "Literal selected report/result fields and their source reference.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-report" }, { "id": "POC-06", "title": "Report files match the selected Work", "applies_to": [ "retained-run", "conditional-existing-operator" ], "expected": "Reproduction verifies readable JSON/PDF, same Work/revision and matching file hashes. Reading identifies what file verification the public record reports without claiming a new file check.", "how_to_check": "Compare JSON with json_file_sha256 and PDF with pdf_sha256; report_sha256 is a different digest. Review the PDF against the same JSON.", "evidence": "File comparison observation or the cited historical comparison statement; private paths remain local.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-files" }, { "id": "POC-07", "title": "Usefulness receives a human review", "applies_to": [ "retained-run", "conditional-existing-operator", "planning" ], "expected": "The reviewer records a decision against the original question, criterion results and remaining limits separately from product acceptance.", "how_to_check": "Use MET, NOT_MET, NOT_RUN, BLOCKED or NOT_APPLICABLE with an explanation for each criterion. These are manual worksheet labels. Write the human decision and next action; copy product acceptance separately if observed.", "evidence": "Criterion review rows and a separate final human-review record.", "source_url": "/guides/poc/deployment.html#first-work" }, { "id": "POC-08", "title": "Cost and elapsed time have an evidence basis", "applies_to": [ "retained-run", "conditional-existing-operator", "planning" ], "expected": "For each relevant cost/time item, record the agreed limit and measured value with period/source, or Not measured/Not applicable with a reason.", "how_to_check": "Distinguish software offer, compute, AI/provider, storage/backups and elapsed time. Compare observed values with agreed limits manually; an unread bill is not zero.", "evidence": "Budget owner/limit; billing or timing reference, or an explicit measurement limitation.", "source_url": "/guides/poc/deployment.html#prepare" }, { "id": "POC-09", "title": "Every used resource has a closeout decision", "applies_to": [ "retained-run", "conditional-existing-operator", "planning" ], "expected": "Each used resource has an owner, intended final state, retention decision, observed final state and continuing-charge disposition, or an explicitly open item.", "how_to_check": "List only resources actually used. For reading record that no product/cloud resource was created by that route; for operations obtain the supported procedure and verify each authorized transition.", "evidence": "Resource closeout rows, retention references and unresolved lifecycle items.", "source_url": "/guides/poc/deployment.html#retire" }, { "id": "POC-10", "title": "Open items have an owner and a resume condition", "applies_to": [ "retained-run", "conditional-existing-operator", "planning" ], "expected": "Every unresolved item names a responsible role/contact, next action, evidence needed and the condition for continuing the affected step.", "how_to_check": "Prepare a sanitized handoff with version, stage, expected/observed result and original Work/request reference when available. Distinguish request reconciliation, service restart and a new submission.", "evidence": "Issue handoff rows and the agreed next-owner/resume record.", "source_url": "/guides/poc/deployment.html#support" } ], "failure_cases": [ { "id": "F-01", "symptom": "Fresh r232 customer cannot obtain the first product administrator", "check": "Confirm the exact delivered version and whether the supported initial-admin procedure has been supplied.", "owner": "Delivery contact and product administrator; supplier support for the missing procedure.", "evidence": "Version, stage reached and missing-procedure request reference.", "resume_when": "The supported procedure for the delivered version is supplied and required product access is confirmed. Planning and reading can continue meanwhile.", "avoid": "Do not use the isolated Admin demonstration candidate or a test initializer as customer bootstrap.", "source_url": "/guides/poc/deployment.html#admin" }, { "id": "F-02", "symptom": "Client is missing or the service cannot be reached", "check": "Check the supplied client path, exact release, local endpoint and account context against the handoff.", "owner": "Service operator; delivery contact for installation mismatch.", "evidence": "Failed command reference, exit, sanitized transport reason and target/release reference.", "resume_when": "The operator confirms the intended endpoint/service and the same-context baseline can be observed.", "avoid": "Do not invent a service startup, change accounts to bypass a denial or treat a desktop path as an appliance connection.", "source_url": "/docs/headless-operations-guide-en.html#headless-troubleshoot" }, { "id": "F-03", "symptom": "Health is nonzero or a required component is UNKNOWN", "check": "Read each relevant state and reason; identify which prerequisites the intended operation requires.", "owner": "Component owner with the product administrator and service operator.", "evidence": "Status/health exits and literal component reasons; affected prerequisite.", "resume_when": "The owner resolves the applicability and required readiness/authority is confirmed for that operation.", "avoid": "Do not repeat the retained lab exception by assumption or restart automatically because health is nonzero.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-baseline" }, { "id": "F-04", "symptom": "Preparation is rejected or the request is denied", "check": "Read the nested reason as well as the outer error. Check supplied intent/operation and authority; establish whether a Work was created.", "owner": "Product administrator for permission; supplied-interface owner or support for input/preparation.", "evidence": "Original request reference, complete sanitized reason and same-context reconciliation result.", "resume_when": "The original attempt is reconciled and the responsible owner confirms the exact supported input and any authority needed for a permitted next action.", "avoid": "Do not replay the historical failed wording as a test, assume no persisted metadata or bypass a denial.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-submit" }, { "id": "F-05", "symptom": "Submission times out, is interrupted or returns no Work ID", "check": "Preserve the original key and request context; inspect saved responses and reconcile the original installation/principal with support.", "owner": "Work owner and product support.", "evidence": "Original key reference, observation time, exit/response state and minimal request reference.", "resume_when": "The original attempt has a resolved disposition and the exact authorized next action is documented; an execution_retry_allowed false result still forbids automatic retry.", "avoid": "Do not create a new key or repeat work run as recovery. An empty scoped list alone does not prove that no Work exists.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-reconcile" }, { "id": "F-06", "symptom": "Work/report identity differs, show is denied or outcome is FAILED/PARTIAL", "check": "Compare the saved ID, account/installation scope, selected revision and literal outcome/closure fields.", "owner": "Work owner and product support; administrator for a binding denial.", "evidence": "Mismatching references or literal failure, selected revision and sanitized reason.", "resume_when": "The same-Work result and permitted next action are reconciled by the responsible owner. Any repair or new execution requires its own supported procedure and authority.", "avoid": "Do not substitute another report, switch principals to evade a denial or call a failed/partial result unchanged state.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-report" }, { "id": "F-07", "symptom": "JSON/PDF is missing, unreadable or has a file-hash mismatch", "check": "Use the returned paths or supplied approved copies, same Work/revision and the correct file-hash fields.", "owner": "Service operator and product support.", "evidence": "Work/report reference, expected and observed file-hash comparison, access failure reason; keep private paths local.", "resume_when": "The correct selected artifacts are available and the discrepancy is resolved with retained evidence.", "avoid": "Do not regenerate silently, substitute another report or compare raw file bytes with report_sha256.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-files" }, { "id": "F-08", "symptom": "Resource owner, retention effect or restart outcome is unclear", "check": "Identify the exact resource and in-flight Work; compare intended and observed state with the supplied lifecycle procedure.", "owner": "Service operator for service state; cloud/data owner for resources, retention and charges.", "evidence": "Before/after states, resource reference, pending Work, retention decision and remaining-charge question.", "resume_when": "The responsible owner confirms the exact lifecycle action and retained-data effect; after an authorized restart, required health/readiness is checked before dependent work.", "avoid": "Do not equate closing a GUI with service stop, VM stop with zero charges, or restart with permission to resubmit a Work.", "source_url": "/guides/poc/deployment.html#restart" } ], "scenarios": [ { "id": "retained-run", "title": "Read one recorded Work", "question": "Can I explain how one supported audit operation is traced to its report and pending human acceptance?", "available_now": "Available now as a read-through of the public retained local R234 record.", "inputs": [ "The six-step recorded-run reader", "Blank input, observation and run-record worksheets", "The evaluation criteria below" ], "expected_output": "A completed reading record with cited product facts, a separate human assessment and an owner handoff for any proposed reproduction.", "limits": "No installation is needed to read. The historical operation does not establish customer access, AI quality or a new file/runtime check.", "source_url": "/docs/headless-worked-run-en.html#reader" }, { "id": "conditional-existing-operator", "title": "Reproduce the supported local audit operation", "question": "On this eligible installation, can one approved CREATE_AUDIT_ARTIFACT Work be followed to readable, matching JSON/PDF reports?", "available_now": "Conditional: an already authorized operator must confirm the exact matching installation and all operation prerequisites first.", "inputs": [ "Supplied client path, local endpoint and exact service release", "Operation permission, one unused approved key and private output directory", "Exact operation CREATE_AUDIT_ARTIFACT and intent create audit artifact", "Approved report access, reviewer and lifecycle/cost owners" ], "expected_output": "Your own returned Work/result observations, same-Work comparison, readable file checks and a separate reviewer decision; success is not prefilled.", "limits": "This operation creates a structured local audit artifact. It does not analyze an arbitrary business attachment or validate a customer AI/provider setup.", "source_url": "/docs/headless-operations-guide-en.html#headless-tutorial-submit" }, { "id": "planning", "title": "Prepare a new-customer AI evaluation", "question": "Which supported task, input, quality measure, cost limit and customer setup proof are needed to answer our business question?", "available_now": "Planning is available now. Fresh r232 administrator-dependent use stops at C7; customer AI/storage/lifecycle procedures and matching proof remain prerequisites.", "inputs": [ "One business question and approved non-confidential sample description", "Requested supported task/model/location and expected deliverable", "Proposed quality/time/cost criteria with named owners", "Exact delivery and missing-procedure request references, or explicit unknowns" ], "expected_output": "A scoped evaluation brief, proposed measurable criteria and a missing-prerequisite handoff. Operational observations stay blank until a supported, authorized customer route is proven.", "limits": "No runnable AI payload or customer setup is supplied by this audit workbook. Obtain the supported version-specific procedure and validate its result before claiming business value.", "source_url": "/guides/poc/deployment.html#ai" } ] }