Understand the review
Identify the delivery, responsible people and review stage before following any test.
See the stages →Review one defined VibePackr delivery against Google’s published VM Marketplace process, from customer instructions to final review.
Inspect each official item
143 mapped items across five named official pages. Open an item for its applicability, procedure and evidence request.
Open the checklist →Use your own review workbook
Download blank target, observation and handoff files. Results start empty and stay private.
Get the workbook →Documentation coverage is separate from review readiness. This edition maps the declared official source set. It does not report that 143 tests passed. The customer first-administrator path and other delivery checks below remain unresolved.
The official review route
Agree the exact review target
Record the product/listing, image and deployment package version or digest, deployment route, applicable architecture, intended offer and review contacts. Keep private target identifiers in the downloaded target worksheet.
Prepare the customer journey
Follow the hosted Getting Started reference from the listing through deployment, access, configuration, health and maintenance. Record administrator credential applicability and every missing input.
Validate the package and open preview
Record successful deployment-package validation in Producer Portal and agree tester access. Use the exact preview delivery; do not substitute a local R234 demonstration.
Check the listing and deployment
Check displayed product/pricing/support/terms, default resources, ports, SSH, license association, applicable admin access and the required machine/region/clone matrix. Preserve each result.
Follow the documented next steps
Test every applicable post-deployment instruction, including the selected AI/storage route and one intended Work. Missing initial-admin or other prerequisites block dependent steps. Reconcile one result and its report; keep customer lifecycle evidence separate.
Complete component and final reviews
Track Product Details, Pricing and Deployment Package separately. Google’s review includes image deployment/uninstallation, unit tests and vulnerability scanning. After component approvals, private Publish requests final testing/review.
Publish only after reviews are approved
Record final approval before Enable public display / Make public. If an affected product component changes, re-submit its review. Maintain and monitor the product after launch. These website pages perform none of these portal actions.
Product and review baseline
VibePackr is a dedicated, single-tenant VM appliance in the customer’s Google Cloud project, operated headlessly by default. The documentation baseline is 0.1.0-r232. The exact final customer delivery version and Marketplace deployment package are pending. No successor version is assigned by this guide.
Draft for feedback. The supported first-customer-administrator path is pending policy approval, implementation and customer validation. The new-customer journey is not complete. This document is not a request to deploy or a report of successful Marketplace review.
Use the English Customer & PoC Getting Started as the primary procedure. The Developer Guide is supplemental context for integration preparation; it does not replace customer deployment instructions.
For a reader new to VibePackr, begin with the customer guide’s orientation, roles and access example and illustrative PoC. These explain the same procedure below; the example is conceptual and is not execution evidence.
Access, inputs and costs
- An agreed review scope, authorized contacts, Google Cloud project with billing, intended zone and VPC/subnet.
- Supplier-provided listing/preview access, exact deployment package/version, offer/terms and resource inventory. These final customer inputs are pending.
- Supported maintenance access and separately established product administration. Retained IAP SSH access is not product administrator issuance.
- For AI: permitted project, location, model and service identity; API, model access, network and billing conditions. Customer-VM setup remains unvalidated.
- Software charges are separate from Google Cloud infrastructure and AI-service charges. Stopping/deleting a VM may leave retained storage and related charges.
The reference sizing is e2-standard-2 (2 vCPU, 8 GiB), Debian 13 x86_64, 20 GiB boot disk, with separate 50 GiB durable-disk and 100 GiB live-object-storage planning figures. It is not a performance guarantee, universal minimum or proof that those resources are provisioned. See deployment preparation.
Official sources and coverage
The sources below define this edition’s coverage. Requirements, recommendations, conditional requirements, official procedures and Google-owned review activities remain distinct. Use the checklist for individual source passages and evidence requests.
| Official source | Mapped scope | Observed revision |
|---|---|---|
| Offering virtual machine (VM) products | Vendor entry, VM-specific requirements and lifecycle checklist. Linked specialist documents remain explicit dependencies. | 2026-09-30 Read 2026-10-04 |
| Set up your Google Cloud environment | Workspace and product setup, product details, Google Cloud-specific Getting Started, next steps and draft feedback. | 2026-09-30 Read 2026-10-04 |
| Building your virtual machine (VM) image | Image preparation, license binding, conditional visibility and credentials, image checks and maintenance notes. Build commands are not operational instructions for frozen r232. | 2026-09-30 Read 2026-10-04 |
| Testing your VM product | Preview access, listing UI, deployment flows and variants, and documented post-deployment tests. | 2026-09-30 Read 2026-10-04 |
| Submit your product | Submission prerequisites, component reviews, Google-owned VM checks, private final review, changes and public publication. | 2026-09-30 Read 2026-10-04 |
The count covers the documented review items in these five pages. Deeper pricing, open-source, payment, deployment-route and policy documents are explicit prerequisite dependencies; their full contents and private Partner Engineer requirements are not silently treated as satisfied. Record any additional requirement in the workbook with its source and owner.
Requirement interpretation: Google recommends screenshots and co-branding; its cited instructions require a hosted Google Cloud-specific Getting Started guide and testing of documented post-deployment steps. Password generation is conditional on the applicable administrator login interface. A separate Reviewer Guide or full SDK submission is VibePackr’s editorial organization, not a universal requirement established by these sources.
Read the evidence at its actual scope
| Record | How to use it | What it cannot establish |
|---|---|---|
| Published manuals and this workbook | Navigate procedures; capture target, applicability and observations | Executed customer tests or Google approval |
| Recorded local R234 Headless / GUI result | Understand same-Work readback, validation, JSON/PDF and pending human acceptance | r232 Marketplace installation or review-target equivalence |
| Separately repaired Admin candidate | Inspect the bounded Admin demonstration and its explicit version limits | Existing Golden customer bootstrap or Golden repair |
| Exact Marketplace test evidence | Bind actual observations to the agreed image, package, environment and scope | Unobserved variants or automatic Google acceptance |
| Google component / final decision | Retain the portal state or assigned contact’s dated decision reference privately | Approval inferred from website availability |
Customer procedure and retained demonstrations
| Read the shared customer procedure | Result to inspect | Current validation state |
|---|---|---|
| Preparation → Marketplace entry | Agreed contacts, costs, offer, exact listing and delivery version | Final listing/package/offer inputs pending |
| Deploy → Access | Correct VM/resources and supported SSH access | Retained bounded raw-image deployment and IAP SSH; exact customer Marketplace-package replay pending |
| Initialize / health | Base health result and separate unevaluated fields | Bounded retained evidence; not overall readiness |
| First administrator | Supported issuance and permitted product access | Policy approval / implementation / customer validation pending; stop dependent execution |
| AI → Storage | Actual customer identity/model/storage behavior | Implementation and limited prior evidence exist; exact customer setup and execution remain pending |
| Readiness → First work item | All required checks and agreed work outcome | Overall new-customer readiness and replayable first-work sequence unproven |
| Stop/restart → Retirement | Intended state transition and per-resource retention/deletion | Retained storage tests are limited; final customer lifecycle instructions pending |
Follow these links rather than a duplicate procedure. Record the observed result and stop at the first unmet prerequisite. No missing step should be treated as a successful test.
Read a concrete integration example
- Open the complete CUSTOM_API source document and its field table.
- Compare the local discovery result with the deliberately unbound-target denial. These are selected actual local fields, not a customer E2E run.
- Inspect GAPE, external-agent assistance and Vertex runtime distinctions.
- Use the remaining self-service conditions to identify what a reviewer cannot yet reproduce from downloads alone.
Read the operational surfaces
Headless covers terminal operation; PackrGUI covers the desktop client; VibePackr Admin and Packtory Admin separate management roles. Troubleshooting provides symptom-based next actions. These source-derived references do not close first-administrator setup or establish customer execution. Inspect each guide’s source/delivery scope before using a desktop screen as an appliance delivery claim.
Review a task from start to finish
Usage workflows connects the five surfaces through inputs, one submission route, same-result checks and owner handoffs. The separate Packtory library guide covers search, inspection and conditional download/derivative demonstrations. These inspected adapters use sandbox configurations; general customer production delivery is not established.
Inspect one actual Headless run
Open the six-step recorded-run reader, then the operating prerequisites and command guide. The reader connects the actual rejected input, correction, one local R234 Work, same-Work readback and report verification. It shows selected recorded fields rather than a live terminal. Validation PASSED and product human acceptance pending are separate recorded states. This local exercise is not a customer r232 Marketplace deployment.
Review workspace coverage without assuming every branch ran
The workspace menu map covers Business, all eight Engineering IDE stages and its five related tools, and all six Operations routes. The actual audit Work and additional native observations anchor the instructions. Populated source-change/build, policy administration, AI calls and human acceptance were not executed by this walkthrough. Read the stated observed result and remaining branch for each menu.
Prepare a useful review handoff
- Complete the target sheet with the submission owner. A missing version, applicable deployment route or access method stays unresolved.
- Use the checklist to identify applicable items and owners. Agree test authorization, costs, data handling and cleanup separately before operational work.
- Record each actual observation in the blank result sheet, including failures and blocked prerequisites. Link minimal private evidence; do not paste secrets, raw logs or full reports into a public issue.
- Send the draft Getting Started URL and the agreed private review handoff to the assigned Partner Engineer through the established channel. Record the response, additional requirements and required changes. This guide does not send anything.
Known product limits and feedback
Please review whether the shared customer sequence, expected results and pending conditions are clear. Comments on documentation can proceed before product readiness is established.
- Initial administrator policy is under review; issuance, successor implementation and validation remain pending.
- AI identity/setup, production storage binding, entitlement verification and complete lifecycle behavior require exact customer-path validation.
- Helper/SDK customer delivery and approved public successful-input schemas remain pending. Architecture planning does not create product authority.
- The exact Marketplace package, final delivery version, access instructions and matched customer-journey screenshots remain dependencies.
- Local HTML authoring, public URL availability, feedback submission and final customer reproduction are separate states.
Support: support@vibepackr.com. Send the version, step and sanitized error or documentation question. Do not include secrets, full logs or confidential work. No response-time commitment is made here.
New R2 examples improve source-document authoring and error interpretation. They do not supply a fully distributable Helper request envelope, a validated customer agent version, or completed Linux Vertex binding. Local source discovery, syntax checks and browser checks are separate from Marketplace product validation.
The earlier R6 documentation work retained five native views and did not submit product Work. A later isolated local R234 Headless exercise did complete one actual Work with same-Work readback and report verification. R8 integrates its selected recorded fields; this integration starts no new Work. Product acceptance was not updated by the later approval of the exercise and guide. Connected customer GUI sequences remain unproven; see the per-surface evidence table.
Inspect the actual GUI report route
R9 adds one different isolated R234 Work submitted from PackrGUI. Follow Business, Engineering, Operations and the final report guide. The PDF viewer opened the same Work report, both file hashes matched, and product human acceptance remains pending. This is local candidate evidence, not customer Marketplace delivery or Google approval.