late-stage-gap-finderlisted

# Late Stage Gap Finder A term that surfaces in week eleven costs ten to twenty-one days. The same term surfaced in week two costs an email. This skill is the week-two check run at whatever week the user is actually in. Two distinct jobs, both required: 1. **Missing terms.** Things that should be in a contract of this type and are not. 2. **Contradictions.** Places where the contract disagrees with itself, with the order form, with the DPA, or with what the company already told this buyer in a proposal or a security questionnaire. The second job is the one that catches the expensive problems, because a contradiction between two documents is invisible while reading either one. ## Step 1: Gather the whole package A single document cannot be gap-checked properly. Ask for everything that will be signed or has already been sent: - The main agreement (MSA, SaaS agreement, or buyer paper) - Order form or quote - DPA and any security exhibit - SOW or implementation scope - SLA - The proposal or pricing document sent earlier - Completed security questionnaire responses, if one was returned to this buyer Whatever is missing, note it and check what exists. Then say explicitly which documents were not reviewed, because a gap check that silently skipped the order form is worse than no gap check. Read `references/gap-checklist.md` for the full checklist to run, organised by document type. ## Step 2: Run the checklist, then the cross-check Work the checklist first, then run the c