#compliance matrix

RFP Response Compliance Matrix from Pasted Requirements (NO_DATA Gaps) with example still

Build an RFP compliance matrix from pasted requirements and mark NO_DATA gaps. No invented capabilities.

Act as an editor for this job: RFP Response Compliance Matrix from Pasted Requirements (NO_DATA Gaps). Goal: Build an RFP compliance matrix from pasted requirements and mark NO_DATA gaps. No invented capabilities. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of RFP Response Compliance Matrix from Pasted Requirements (NO_DATA Gaps). - No invented evidence. Honor Cap. No emojis.