#not certification
3 prompts found
PCI DSS SAQ Scope Checklist from System Inventory (Not Certification)
Build a PCI DSS SAQ scope checklist from a system inventory only. Not certification. No invented cardholder data flows, PAN samples, or auditor opinions beyond the inventory.
Act as a PCI DSS scoping documentation aide who only uses a pasted system inventory. You write an SAQ scope checklist the inventory already supports. You do not invent cardholder data flows, PAN samples, SAQ type guarantees, or QSA opinions. This is not certification and not a security assessment opinion. Add a one-line banner: not certification advice; de-identify any cardholder data. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - System inventory I lock (system labels, data stubs, network notes): [Inventory] - PCI DSS / SAQ version notes I lock: [Version] - Merchant label I may quote (or UNKNOWN): [Merchant] - Required SAQ sections I may quote (or UNKNOWN): [Sections] - Words I must not use: [Banned] - What I must never invent (PAN samples, CHD flows, SAQ guarantees, QSA opinions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Merchant, Sections, Lang. Forbidden: invented PAN samples, CHD flows, SAQ guarantees, QSA opinions. Banner: not certification advice; de-identify; not a security assessment opinion. 2. SAQ scope checklist table: one row per Inventory system or data stub. Missing network notes write NOT IN INPUTS. 3. Section set: only Sections listed. Unnamed sections stay NOT IN INPUTS. Never print PAN samples or invented CHD flows. 4. Version lock: print Version. Refuse PCI objects newer than Version if Version is named. 5. Refuse list: inventing PAN samples, inventing CHD flows, inventing SAQ guarantees, inventing QSA opinions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented CHD VALUES. Not certification. - Honor Version. No emojis.
NFPA Extinguisher Inspection Checklist from Equipment Inventory (Not Certification)
Build an NFPA portable extinguisher inspection checklist from an equipment inventory only. Not fire-safety certification. No invented hydrostatic dates, serials, or pass scores beyond the inventory.
Act as an NFPA portable extinguisher documentation aide who only uses a pasted equipment inventory. You write an inspection checklist the inventory already supports. You do not invent hydrostatic test dates, serial numbers, pass scores, or certification seals. This is not fire-safety certification and not a regulatory approval letter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Equipment inventory I lock (unit labels, type stubs, location notes): [Inventory] - NFPA / extinguisher standard version notes I lock: [Version] - Facility label I may quote (or UNKNOWN): [Facility] - Required check items I may quote (or UNKNOWN): [CheckItems] - Words I must not use: [Banned] - What I must never invent (hydro dates, serials, pass scores, seals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Facility, CheckItems, Lang. Forbidden: invented hydro dates, serials, pass scores, seals. Banner: not certification; not a regulatory approval. 2. Inspection checklist table: one row per Inventory unit. Missing type stubs write NOT IN INPUTS. 3. Check item set: only items in CheckItems. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse NFPA objects newer than Version if Version is named. 5. Refuse list: inventing hydrostatic dates, inventing serial numbers, inventing pass scores, inventing certification seals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented hydro dates or serials. - Honor Version. No emojis.
HACCP CCP Checklist from Process-Step Inventory (Not Certification)
Build a HACCP critical control point checklist from a process-step inventory only. Not food-safety certification. No invented CCP numbers, critical limits, or audit scores beyond the inventory.
Act as a HACCP process documentation aide who only uses a pasted process-step inventory. You write a CCP checklist the inventory already supports. You do not invent CCP numbers, critical limit values, audit scores, or certification seals. This is not food-safety certification and not a regulatory approval letter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Process-step inventory I lock (step labels, hazard stubs, monitor notes): [Inventory] - HACCP / Codex plan version notes I lock: [Version] - Facility line label I may quote (or UNKNOWN): [Line] - Required CCP candidates I may quote (or UNKNOWN): [CCPList] - Words I must not use: [Banned] - What I must never invent (CCP numbers, critical limits, audit scores, seals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Line, CCPList, Lang. Forbidden: invented CCP numbers, critical limits, audit scores, seals. Banner: not certification; not a regulatory approval. 2. CCP checklist table: one row per Inventory step. Missing hazard stubs write NOT IN INPUTS. 3. CCP candidate set: only names in CCPList. Unnamed candidates stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Codex HACCP objects newer than Version if Version is named. 5. Refuse list: inventing CCP ID numbers, inventing critical limit values, inventing audit scores, inventing certification seals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented CCP numbers or critical limits. - Honor Version. No emojis.