pack-draft

Pack Draft

Purpose

Turn engine output into a readable internal draft for the engagement manager to review; the engines have already made every decision.

When to use

Last step, after wall-check has written access-checklist.json and mobilization-pack.md. If no access-checklist.json exists yet (a cold "start / build the onboarding pack" request), do not draft: start with engagement-retrieve, which runs the chain.

When NOT to Use

• Any wall, access, roster or knowledge decision - use wall-check, roster-pull or knowledge-match.
• Sending the pack to the joiner, team or client - out of scope; the pack is draft-only.
• Staffing or closeout work - use engagement-staffing-bench-match or engagement-closeout-knowledge-harvest.
• A generic onboarding guide, template or Word document that is not tied to this engagement's governed outputs - use the built-in docx skill.
• Word output of this pack: draft the governed Markdown here first, then hand it to docx keeping the DRAFT banner, pack status, holds and [withheld ...] markers unchanged.

Inputs

access-checklist.json and mobilization-pack.md (contract ps.engagement-mobilization-onboarding-pack.v1), plus the raw inputs the chain read (raw directory, staffing input, confirmed roster, Closeout governed.json, wall register and workspace inventory) for the pre-render check.

Steps

1. Before reading either file, run python3 scripts/verify_render.py --access access-checklist.json --pack mobilization-pack.md --raw-dir <raw> --staffing <staffing.json> --confirmed-roster <raw>/confirmed-roster.csv --closeout <closeout governed.json> --wall-register <raw>/ethical-wall-register.csv --workspace-inventory <raw>/workspace-inventory.csv. It validates the access checklist against its stage contract and hold-evidence rules, re-runs every engine on the raw inputs and refuses an access checklist that differs from the re-derivation in any field (every hold member compared exactly), a pack that differs from the engine's rendering by any byte, or a pack whose rendered lines trip the instruction screen when read in order, citations and IDs included (confidentiality-and-ethical-wall-rules.md #1.4,#4.5). If it exits non-zero, stop: quote the error verbatim, draft nothing and re-run the chain from engagement-retrieve. Draft only from files that passed this check unchanged.
2. Confirm access-checklist.json exists and the contract version matches (otherwise see Failure handling); if mobilization_pack.status is on_hold_internal_only, the pack is still drafted for internal use: lead with the holds and their citations, render the held draft as internal-only, keep every [withheld ...] marker, never draft or restore content that depends on an open hold, and say it must not be shared with the joiner until the holds clear. The holds are hold_reasons and every open entry in holds. Every engine section is still rendered in order (step 3); anything the engine held stays as its hold line or [withheld ...] marker.
3. Keep the engine sections and order: client context, scope and exclusions, deliverables and dates, prior-knowledge digest, team roster, access checklist, confidentiality and wall briefing, first-week plan, escalations and holds.
4. Rephrase for readability only; keep every status, permission, hold, citation and [withheld ...] marker exactly as written. First-week plan items come only from the ## First-week plan lines of mobilization-pack.md; never add or restore items. An item the engine restated as title-and-citation only because it points at pending-review knowledge (by ID, title, any generic "prior knowledge"/"knowledge digest" reference whatever its verb, voice or noun form, or an ID split across adjacent items) stays restated, and a "Continues SOW first-week item N" line stays as written: never restore its SOW wording from scope_summary.first_week_focus or tell the joiner to read that material (knowledge-reuse-rules.md #2.5).
5. Keep the DRAFT banner. Keep the engine's Proposed, not assigned: <name> for <role> line exactly as rendered: never reword it and never move a proposed name into the confirmed roster lines; pending_practice_review knowledge is referenced by title and citation only. Never write or summarise a Closeout lesson: lessons in excluded_items have no written text yet (knowledge-reuse-rules.md #2.4).
6. End with the reviewer checklist: resolve holds, confirm wall briefing with Risk/Conflicts, approve access requests, then share internally.