Review an export before engineering handoff
Check infrastructure, evidence, and package identity before using your deployment process.
Establish which design you are reviewing
Record the project, saved revision, export identifier, and infrastructure format. Review the package identity shown on the export page. This helps your team discuss the same generated result even after someone changes the project draft.
Inspect the package in layers
- Review generated infrastructure and its required inputs.
- Compare the diagrams with the intended architecture.
- Read validation evidence and distinguish successful checks from checks that did not run.
- Inspect semantic and file changes where available.
- Review generated or user-owned application source separately from infrastructure.
Do not treat infrastructure-only evidence as proof that an application was built or tested. Optional AI source is a draft requiring engineering review; its presence does not establish a successful Lambda build.
Prepare your deployment handoff
Your organization controls credentials, infrastructure state, environment-specific values, approval, planning, deployment, and rollback. Cloud Markup generates reviewable artifacts and does not deploy them into your AWS account. Keep generated files and their accompanying instructions together when handing them to another engineer. Explain any limitations that remain unresolved.
Ask a precise export question
Identify the file, resource, expected output, and stage where the issue appears. A redacted excerpt with the revision and export identifiers is usually enough to begin. Separate a generation problem from an error that occurred later in your own deployment workflow.
Include this guide and what you tried in your ticket so we can pick up from there.
Contact support