Copy it as-is, or use Open in Long Prompt Splitter to load it pre-filled and customize it with your own context.
CHUNKED CONTEXT PACKAGE
DELIVERY INSTRUCTIONS
- Send each chunk below as ONE message, in order, starting with Chunk 1.
- Wait for the model's acknowledgement ("Received chunk i of 3") before sending the next chunk.
- Do not edit the chunk contents — the markers and the content are designed to travel together.
CHUNK STRATEGY
- Content: 28,598 characters, ~6,500–7,944 tokens (Prose).
- Target model: GPT-5 (400,000-token window; verified June 2026).
- Chunk budget: ~4,000 tokens (14,400 characters max per chunk) → 3 chunks.
- Delivery mode: AI Reading Mode — Strict reading mode — the model is told to wait for every part and is forbidden from early analysis.
- Boundary quality: 2 section breaks, 0 paragraph breaks, 0 line-level breaks, 0 hard cuts.
===== CHUNK 1 of 3 =====
- This content arrives in 3 parts. The parts form ONE continuous document, in order.
- Do NOT respond, summarize, or analyze yet — not after this part, and not after any part except the final one.
- Wait until the final part explicitly announces that all chunks are delivered.
- After reading, reply ONLY: "Received chunk 1 of 3." Then wait for the next chunk.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
----- END OF CHUNK 1 of 3 — do not respond yet; chunk 2 follows -----
===== CHUNK 2 of 3 =====
- Chunk 2 of 3 — part of the same continuous content. The earlier rules still apply.
- After reading, reply ONLY: "Received chunk 2 of 3." Then wait for the next chunk.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
----- END OF CHUNK 2 of 3 — do not respond yet; chunk 3 follows -----
===== CHUNK 3 of 3 =====
- Chunk 3 of 3 — part of the same continuous content. The earlier rules still apply.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
## Data Retention Policy
Customer records are retained for the lifetime of the account plus twenty-four months, after which they enter a staged deletion pipeline. Backups age out on a rolling ninety-day schedule, and legal holds suspend deletion for named accounts only — never for whole cohorts.
## Access Controls
Production data access requires a time-boxed grant tied to a ticket. Standing access exists only for the on-call rotation, is read-only, and every query is logged to an immutable audit stream reviewed weekly by the security team.
===== ALL 3 CHUNKS DELIVERED =====
- All 3 chunks are delivered — the waiting rule ends now.
- Respond using the COMPLETE content across all chunks; do not answer from the final chunk alone.
TASK
[Describe what the AI should do with the full content]
NOTE
- Chunk budgets use character-based token estimates, not tokenizer output; model windows verified June 2026.