Carry the work forward.

1. Start with the right context

Use this guide before a meeting, beside the four reports, or after handover. It is reusable guidance, not an engagement record. Keep your actual documents and client information in the environment approved by your organization. Library does not receive them.

• Before the engagement: name the mission outcome, scope, decisions needed, available source material and people who can explain it. Record missing information rather than filling gaps with guesses.
• During the engagement: use the report map below to prepare questions and distinguish a proposed action from a decision already made.
• After handover: start with the accepted package and its recorded date. Review changes with the receiving owners before reusing an earlier recommendation.

A living foundation is maintained by its receiving team. Preserve the issued snapshot, name an owner for working copies, and record changes and review decisions. Library guidance does not automatically update your engagement or provide continuous monitoring.

AI is optional. Use only an AI service and data handling arrangement your organization has approved for the material concerned. Public availability of this prompt does not permit uploading client information. When no approved AI is available, use the same questions as a meeting checklist.

Using your Markdown and prompt packs with approved AI

• Confirm the receiving environment with your designated security and data owners: exact government tenant or endpoint, permitted information, intended use, upload features, connectors, retention and sharing settings. Do not substitute a consumer account with the same model name.
• Preserve the issued package. Make a working copy of only the Markdown reports, selected worksheets and prompt pack needed for this question; retain filenames, dates, source references and handling markings. Markdown is readable text, not redaction or declassification. Do not upload the whole consultant workspace or raw evidence by default.
• If the approved tool supports file upload, attach only the permitted files. Otherwise paste a permitted excerpt with its filename, date and section. Ask the AI to list what it actually received before using the prompt; if a format or file is unsupported, keep using the human-readable package.
• Start with a reading task: summarize an unresolved decision, compare documented alternatives, or draft a review agenda. Require file and section citations, distinguish facts from recommendations and unknowns, and prohibit actions or changes to recorded decisions.
• Check the answer against the source documents. Record any accepted change in a separate working copy with its reviewer and date; an AI answer does not validate a reading, accept risk, authorize implementation or reissue the package. Without approved AI, use the same prompt as a meeting checklist.

Approval belongs to an exact service offering, deployment, region and feature set—not a model name. A provider’s IL5 provisional authorization does not authorize your mission system or permit every data type or use. FedRAMP is not a DoD impact level. IL5 does not cover classified IL6 work; IL6 requires its own approved environment and handling path.

DoD service examples — reviewed 2026-10-14. Recheck the exact offering before use.

• Google — defense AI and GenAI.mil
• Navy — GenAI.mil enterprise designation, 28 January 2026
• Microsoft — Azure OpenAI IL4/IL5 authorization
• AWS — model-specific Bedrock authorization scope

Public Ask CW is for public reference guidance; it is not an IL5 service for engagement data. Library and its public prompts do not grant permission to upload documents. These dated examples are starting points for verification, not an approved-products list or a procurement recommendation.

2. Read the four reports together

The reports are connected views of one engagement record. They are not four independent assessments. Their recommendations and jumpstarts support local decisions; they do not authorize implementation.

Read the Leadership decision brief for direction, the Cloud foundation and readiness plan for context, the Transition and transformation plan for sequencing, and the Operating handover and evidence package for continuing ownership. If two views conflict, record the discrepancy and refer it to the engagement owner; do not silently choose one.

The method connects 51 readiness positions with a 53-workstream backbone. A position is not a document request, and a workstream is not automatically required. Use the selected scope and recorded consultant judgment. Where the package shows levels, preserve its readings and validation status.

8. Distinguish requirements from guidance

NIST publications, cloud guidance and standards become applicable through the relevant policy, contract or system context; do not label every cited practice mandatory. A reusable image, package, reference architecture or another program’s use does not transfer authorization.

3. Prepare the next decision

Start with one decision. Keep proposed ownership and timing separate from agreed ownership and timing. Carry the result into the client’s existing decision and change processes.

6. Compare architecture alternatives

Use the existing approved estate as the starting point. More products or more automation are not outcomes on their own.

Before comparing totals or scores, agree the decision criteria and who can accept the trade-offs. Do not turn unsupported estimates into apparent precision.

7. Make operating ownership explicit

Confirm coverage hours, escalation, recovery expectations and the handoffs between mission teams, shared services and security operations. Technical capability is not delegated authority. Keep unresolved responsibilities visible rather than treating a diagram or role label as an agreement.

4. Plan the first 30 / 60 / 90 days

These are optional review windows, not delivery promises. Replace them with the client’s agreed dates, capacity and operating cadence. Start from accepted actions, then identify proposals that still need a decision.

A meeting is useful when it leaves a recorded decision, an owned follow-up or an explicit unknown. Keep the review small enough that owners can maintain it without a new platform.

5. Keep the posture current

Revisit the affected part of the record when a workload, boundary, provider service, owner, dependency, requirement or operating practice changes. An incident or missed recovery objective can also trigger a review. A trigger means investigate; it does not by itself prove a lower readiness level.

Keep a dated baseline and a reviewed change log. A newer Library guide is general guidance; it does not automatically supersede an issued client report or change the requirements that applied to it.

9. Go deeper only where needed

These are separately scoped options, not four mandatory stages. Carry forward the specific question, relevant report sections, known sources, affected positions or workstreams, unresolved gaps and proposed receiving owners. Agree scope, handling, responsibilities and acceptance before beginning deeper work. Equivalent reviewed prior work can provide the starting context.

10. Try a fictional handover discussion

Fictional teaching example — no real engagement or authorization claim. The handover says a shared service is proposed for an application, but its recovery owner is not yet agreed. The roadmap lists that agreement as a dependency before migration planning can proceed.

The useful result is a better question and a traceable human decision. The prompt, worksheet and generated answer remain jumpstarts to review, not the answer by themselves.