The AI Output Verification Pack

I want to INSTALL the real setup so Claude runs the verification pass on my actual deliverable and its real sources, not just a chat demo. Walk me through it step by step, do not skip the install. Treat me like a CFO, audit committee chair, general counsel, or deal lead who has never built a Claude Project or installed an Office add-in, and define every term once.

This is NOT a Terminal or coding install. There is nothing to compile. It is two paths: a private Claude Project where the draft and its source documents live (recommended) and an optional Word or Excel add-in for checking the file in place.

## Path 1 (RECOMMENDED) — a private Claude Project for the deliverable and its sources
This is the path that makes verification real. The check only works if Claude can see the actual sources the deliverable cites, not just the draft.

Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account on a Team or Enterprise plan so the data stays in my tenant. Pin **Opus 4.8**. Nothing to install for this path.
2. **Create the verification desk.** In Claude, create a new **Project** named for the deliverable and the date. A Project is a private workspace with its own knowledge that other chats cannot see. Your draft and your sources stay in your own tenant.
3. **Load the material.** This is the step people skip and then wonder why the pass is weak. Drop in BOTH the draft deliverable AND the documents it cites: the source reports, the filings, the data files, the contracts, the cases. Verification compares the draft against these. No sources loaded means the best Claude can do is mark a line UNVERIFIED.
4. **Run the vault.** Run prompt 01, pick what you are verifying (a report, a model, a legal document, a research piece, a board pack) and your data source (A) upload, or (D) a governed connector if you pull from a VDR or filings database. Then run 02 to 09 in order: citation existence, quote trace, number tie-out, claim against source, the confident-and-wrong sweep, internal consistency, the self-check gate, and the verification report.
5. **Gate it.** Treat prompt 08 (the self-check) as a hard gate. If the unresolved count is above zero, the deliverable is NOT cleared to ship until each item is fixed. A named human signs before anything leaves the firm; a prompt cannot sign.
6. **Shadow run first.** Run the pack on two or three deliverables that already shipped before you trust it on live work. It will catch things in work that already went out. That is the proof. See the 90 day rollout in the bundle.

## Path 2 (OPTIONAL) — Claude for Word or Excel add-in for checking in place
If I want the citation, quote, and number checks to run inside the live document:
1. In Word or Excel (Microsoft 365 desktop or web): **Home** or **Insert** tab, **Add-ins** / **Get Add-ins**, search **"Claude"**, **Add**. Tell me where the button is in my version.
2. Sign in to the docked Claude side panel.
3. In vault prompt 01 choose data source (C) the add-in. Run prompt 04 (number tie-out) in Excel on a model, or prompts 02, 03, and 05 in Word on a report, so the checks run against the live file. Keep the source documents in the Project so the add-in has something to verify against.
4. Pin **Opus 4.8** for the verification work.

## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, citation, footnote, primary source, fabricated source, paraphrase drift, misattribution, tie-out, recompute, false precision, the self-check gate, partner sign-off, `{{TOKEN}}`.
- Do NOT tell me a step is "not possible." If the add-in is missing, check Word or Excel for Microsoft 365, try the web version, or AppSource. For the Project path there is nothing to install.
- The single most common reason this underdelivers is loading the draft without its sources. Make me load the sources.
- Never paste confidential client material into a public Claude window outside a Project. Use a Project with your tenant controls and follow your firm's data policy.
- This moves the verification work in-house and makes the sign-off defensible. It does not replace the named professional who signs, the subject-matter expert on the substance, or your auditor. Read the audit and compliance overlay before you reduce any external scope. A named human signs. Not legal, tax, or accounting advice.

First message: ask me "Path 1 (a private Claude Project for the deliverable and its sources, recommended) and do you also want Path 2 (the Word or Excel add-in for checking in place)? What are you verifying first (a report, a model, a legal document, a research piece, or a board pack), and do you have the source documents it cites ready to load?" Then start step 1.