Choose one supported task, obtain its exact handoff, follow the bounded steps and keep the result with its next owner. These five cases distinguish preparation, observation, report verification, an authorized configuration change and AI planning.
Prepare an input
Prepare one integration source document
Describe a status.read operation and identify what the supported target package must supply.
Available now for local document preparation and reading published results. A complete customer Helper request package is still a separate prerequisite.
Apply only the approved log_level WARN change and distinguish its action receipt, stored value and effective behavior.
Conditional on a provisioned, authorized Admin installation and a separately approved change. The recorded repaired local candidate does not supply fresh r232 bootstrap.
Make model, identity, data, budget and setup dependencies concrete enough for their owners to resolve.
Planning is available now. A controlled product/provider call remains dependent on the supported customer setup, exact runtime binding and explicit operation authority.
“Custom” means a task for your supplied environment. It does not mean arbitrary code execution or a new product contract.
Use a documented interface only with its matching delivered version, established access and permitted task. Record any files or configuration outside the frozen image that it changes.
The connected Admin demonstration used an isolated repaired candidate. Its source repair is historical demonstration context, not an instruction to modify Golden r232.
Fresh r232 administrator-dependent use remains blocked at C7. Missing delivery or supported setup belongs in the owner handoff.
Helper preparation, GAPE projection reading and AI connection planning have distinct inputs and completion points. A successful preparation stage does not establish live connectivity.
The expected observations describe what to check. Enter only your own observations in the blank workbook.
No task matches. Clear the filters or choose another term.
Prepare an inputPrepare one integration source document
Current route
Available now for local document preparation and reading published results. A complete customer Helper request package is still a separate prerequisite.
Goal
Describe a status.read operation and identify what the supported target package must supply.
Changes to expect
Creates or edits caller-owned local documents only. No product registration, runtime configuration or provider request.
Evidence scope
JSON syntax and source-field review can be completed here. Published DISCOVER PASSED establishes local source discovery; NORMALIZE DENIED / CONTRACT_INCOMPATIBLE leaves target compatibility open.
Bring these inputs
A non-secret operation brief and an owner for the service description.
The public status-document.json source example and its field reference; keep the original and edit a copy.
Record the supplied tool/build and target references, or mark them unknown; the recorded macOS Helper build identity is unproven.
1. Describe the source
Use the brief to name the read operation, input service:string and output service:string plus healthy:boolean. Keep declared shapes separate from actual request values or a live reply.
Expected observation
One reviewable operation description with no claimed service call.
Keep
Operation brief, data owner and approved non-secret sample reference.
If it does not match
If the intended service or data use is unclear, return the description to its owner.
Follow the CUSTOM_API field table: retain protocol revision 1, primitive property types and consistent required lists. Use the published JSON syntax check if Python 3 is available. Keep notes in the brief, not unsupported JSON fields.
Expected observation
A readable JSON source document; syntax success is recorded separately from product validation.
Keep
Original/source-copy references, intended edits and any actual syntax result.
If it does not match
Fix only the identified format error in the copy. Do not add invented contract or credential fields.
List the supplier-owned contract/adapter IDs and revisions that are still needed. The source belongs in draft.source of a matching complete request; do not combine public fragments into a claimed valid request or pass the source directly to r2-discover.
Expected observation
A concrete missing-deliverable list for a complete versioned request, supported target and installation route.
Keep
Supplied target references or explicit unknowns; responsible supplier contact.
If it does not match
No complete matching package means stop before product preparation commands.
Read the published DISCOVER and NORMALIZE excerpts together. Record each operation, request_id, status, reason and lifecycle_stage. Both excerpts contain the same historical request ID; this is a record to inspect, not a key for reuse. R2 semantic denial can return process exit 0; read the JSON result.
Expected observation
Discovery success and normalization denial remain distinct; the next owner receives the missing target/package question.
Keep
Cited excerpts and a separate interpretation/next-action note.
If it does not match
Do not claim normalized, registered or connected execution from DISCOVER PASSED.
A source copy, any actually performed syntax result, a correctly interpreted retained result and a named missing-deliverable handoff are recorded.
Close or hand off
Keep the original and edited copy under the data owner’s retention choice. No service needs stopping in this preparation route. Continue product preparation only after the supplier supplies the matching complete package and scope.
Follow the supplied baseline block using the same client/socket/account. Record each exit immediately and preserve status.json and health.json privately.
Expected observation
Two query observations and their own exit codes, or the exact unperformed/failed stage.
Keep
Observation time, command reference, exits and sanitized source references.
If it does not match
Transport failure is not a reason to start or restart the service automatically.
Copy literal liveness, readiness, authority/runtime states and relevant reasons. Keep UNKNOWN visible and ask the affected component owner whether it blocks the intended next task.
Expected observation
An observation summary that separates service presence from task-specific readiness.
Keep
Literal states/reasons and the next-owner question.
If it does not match
Do not apply the historical lab’s exception to this installation or infer permission from exit 0.
The intended target and actual query results are recorded; unanswered readiness questions have an owner.
Close or hand off
Retain sanitized observations and leave the supplied service unchanged. Record that no Work was submitted. Any later service or Work action follows a separately supported authorized route.
Read the published example now. Actual file checks require authorized access to your own selected Work/revision and its report files.
Goal
Check that the delivered JSON and PDF belong to the same selected Work and match their reported file hashes.
Changes to expect
Reads selected records and files; may save local review notes. It creates no new Work or replacement report.
Evidence scope
Reading a historical comparison proves what the publication reported. A fresh match requires your own file observations; validation and human acceptance are separate.
Bring these inputs
An existing saved Work ID and selected report revision, supplied by the authorized operator or matching read query.
Actual returned JSON/PDF paths or approved copies with an attributable handoff.
An approved local viewer and file verifier for your platform; raw reports remain private.
1. Bind the selected record
Compare the saved Work ID with list/show/selected report references where available, preserving the same installation/account context. Record the chosen revision.
Expected observation
One attributable Work and report revision, or an explicit mismatch.
Keep
Work/report/revision references and same-identity observations.
If it does not match
A missing selected report or identity mismatch stops the file-completion claim.
Copy execution_count, validation_results, final_result, receipt/closure and returned retry/replay fields. Keep human_acceptance null or pending exactly as returned.
Expected observation
Literal outcome and product acceptance are recorded separately from reviewer judgment.
Keep
Selected report fields and their source reference.
If it does not match
Do not fill unavailable values from the recorded example.
Use the returned paths or approved copies. Compare JSON bytes with json_file_sha256 and PDF bytes with pdf_sha256; remove the sha256: prefix only for comparison. Open the PDF and compare its Work/result with JSON.
Expected observation
Readable same-revision files with observed hash comparisons, or an identified access/mismatch issue.
Keep
Expected/observed file hashes and readability/identity observations; keep private paths local.
If it does not match
report_sha256 is not a raw-file checksum. Missing files or mismatch go to the service operator; do not regenerate silently.
The review states exactly which selected-file checks were performed and the product’s literal acceptance state. A reading-only exercise is labeled as such.
Close or hand off
Keep raw files under the data owner’s retention decision and share only approved references. Record missing delivery or verification with its owner; this task does not stop services or accept Work.
Use an eligible installationReview one approved logging change
Current route
Conditional on a provisioned, authorized Admin installation and a separately approved change. The recorded repaired local candidate does not supply fresh r232 bootstrap.
Goal
Apply only the approved log_level WARN change and distinguish its action receipt, stored value and effective behavior.
Changes to expect
May change the registered log_level setting after authorization. The visible {"log_level":"WARN"} fragment is not a complete request; no service restart is required by this configuration contract.
Evidence scope
An applied decision, mutation flag, revision and audit reference prove the recorded action within scope. The general projection withholds values; effective WARN needs the installation’s supported observation.
Bring these inputs
Exact organization/appliance/installation, current administrator/grant references and the supplied connection profile.
The change owner’s exact approval, current-state review and the supported configuration payload/procedure.
A retention/recovery disposition and a supported stored/effective-value observation if that proof is needed.
1. Connect and capture the baseline
Follow the supplied Admin connection checklist. Confirm returned target identity, then Refresh and record appliance state revision and configuration revision separately.
Expected observation
A current authorized target and a baseline attributable to that target.
Keep
Target, grant/reference, observation time and both revisions; retain private profile values locally.
If it does not match
Target mismatch or missing Admin provisioning stops the change path.
Open Appliance → Update configuration. Compare Target and Expected revision with the current appliance state revision, then compare Requested change with the owner-approved log_level WARN change. Cancel a mismatch; submit once only within the supplied approval.
Expected observation
The actual decision/reason, mutation flag and audit reference, not a prefilled APPLIED result.
Keep
Approved intended change, expected revision and literal action response.
If it does not match
For stale revision refresh and re-review; for an uncertain timeout preserve and reconcile the existing request before another submission.
Refresh and inspect Audit for the matching action and revision. Record stored and effective values only through the supported observation supplied by the operator; otherwise leave them unobserved. A changed revision alone is not an effective-value test.
Expected observation
Action/revision evidence plus a separate observed or unresolved stored/effective-state record.
Keep
Audit reference, post-action revisions and the source of any stored/effective observation.
If it does not match
If effect is unproven, assign the observation to the operator; do not mask the gap with a restart.
Record whether the authorized change remains applied or an explicit recovery decision is pending. Disconnect after review; saved profile fields are not a current snapshot. Use only a separately supplied and authorized recovery procedure if needed.
Expected observation
Final connection state, retained change disposition and next owner are explicit.
Keep
Minimal support record and retention/recovery procedure references.
If it does not match
Do not delete managed profiles/keys or invent an inverse change as routine cleanup.
The one approved action and matching audit/revision are recorded; stored/effective evidence is either observed through its supported path or explicitly open.
Close or hand off
Retain the approved state or hand a recovery decision to the change owner. Disconnect and preserve required history. This case performs no automatic rollback, service restart or customer bootstrap.
Planning is available now. A controlled product/provider call remains dependent on the supported customer setup, exact runtime binding and explicit operation authority.
Goal
Make model, identity, data, budget and setup dependencies concrete enough for their owners to resolve.
Changes to expect
Creates a planning worksheet only. It does not enable APIs, alter IAM, configure a runtime or call Vertex AI.
Evidence scope
A completed plan identifies who must verify the actual identity, model/location, binding, cost and data conditions. It is not connected AI or customer E2E proof. GAPE observation and assistant document review are separate from Vertex execution.
Bring these inputs
Named PoC, cloud/AI and data owners; one permitted use-case question.
Non-secret project/location/model choices or explicit unknowns, and an identity-owner reference.
Exact delivery release and supplied setup/binding procedure reference, or a recorded missing-procedure request.
1. Fill non-secret choices
Use the published AI worksheet to record project, supported location, exact model, identity owner, approved data class and budget/retry limits. Leave missing values unknown.
Expected observation
A concrete plan without tokens, keys or invented model defaults.
Keep
Worksheet and owner-confirmation references.
If it does not match
Resolve unclear data use or cost ownership before any later setup.
Ask the cloud owner to confirm API/billing, actual attached VM service identity, inference permissions/access scopes, model/location policy and network. Ask delivery for the exact supported binding/setup route. Record each as supplied, pending or unknown based on evidence.
Expected observation
Each prerequisite has a responsible owner and evidence to obtain.
Keep
Non-secret procedure, identity-owner and dependency references.
If it does not match
Fresh r232 administrator-dependent setup remains stopped at C7; do not substitute a test initializer or another platform’s authentication recipe.
Agree what a separately authorized small task would prove: actual selected model/location, whether a call was sent, returned result, product validation and measured cost. Keep expected text separate from a recorded reply.
Expected observation
A bounded future check, stop conditions and owner/resume handoff; no call has been made by this plan.
Keep
Expected result, budget/retention plan and missing-evidence list.
If it does not match
Do not infer a provider call from a selected runtime or silently change provider/model to fill a missing prerequisite.
Owners can see the proposed task, required setup proof, cost/data limits and exact conditions for a later authorized evaluation.
Close or hand off
Retain the planning record; leave actual call/result/cost fields blank. Handoff the supported setup question to delivery/cloud owners. No cloud resource or credential cleanup is implied by this plan.
The worked reading example traces a service-status Document to the published discovery result and then its normalization denial. It shows a useful owner handoff while leaving the integration unresolved.