Review Packet PDF Layout Planning

Purpose

This page defines the proposed future packet order, print structure, layout rules, redaction reminders, and approval gates for a staff/privacy review packet. It is planning-only and creates no generated artifact.

No PDF, ZIP, export file, download, approval, decision record, protected API, protected live route, database access, data-writing path, or live workflow is created here.

Current PDF/Export Boundary

Proposed Packet Page Order

Layout Rules

• Prefer stacked cards over wide tables for decision sections.
• Use wide tables only as secondary appendix material.
• Avoid splitting a decision card across pages.
• Avoid splitting a status box across pages.
• Keep current no-go status near the top of every major packet section.
• Keep evidence summaries concise.
• Move long route inventories to appendix.
• Keep blocked capability chips deduped.
• Keep recommended next phase current.
• Keep safety boundaries visible but not repeated excessively.
• Use short route labels where possible.

Print Readability Rules

• Use readable line length.
• Avoid dense wall-of-text safety paragraphs.
• Use grouped boundary cards for long safety notes.
• Use section summaries before detailed tables.
• Avoid tables with more than five visible columns in primary print view.
• Use card layout for review decisions and staff/privacy questions.
• Keep Operator diagnostics out of the main review packet unless requested.
• Keep Recovery/news diagnostics out of staff/privacy review packet exports.

Page-Break Rules

• Keep cover/no-go status on its own opening page when a future PDF is approved.
• Keep each decision card together.
• Keep status boxes and their labels together.
• Start appendices on fresh pages when possible.
• Avoid page breaks between a section heading and its first summary card.
• Allow long route references to continue only in appendix sections.

Table/Card Rules

• Cards are primary for decision sections, staff/privacy questions, and safety boundaries.
• Tables are acceptable for route references, planning artifact inventories, and approval gates.
• Primary packet tables should use five or fewer visible columns.
• Appendix tables may be wider only if they remain secondary/reference-only.
• Table labels must not imply approval, submission, launch, or export action.

Blocked-Chip Rules

• Deduplicate blocked chips within each rendered list.
• Group similar blocked capabilities before appendix expansion.
• Keep no-go, not-recorded, and not-generated states visible near blocked chips.
• Do not use blocked chips as action controls.
• Do not repeat the same safety chip in both primary and appendix sections unless the appendix is clearly secondary.

Recommended Section Summaries

Redaction Reminders

• Exclude identity details, raw Access claims, JWTs, tokens, and headers.
• Exclude real draft bodies and private feedback.
• Exclude staff review notes and staff-only private context.
• Exclude medical, legal, trauma, and resident substance-use disclosures.
• Exclude attendance, participation, analytics, scoring, ranking, compliance, and resident performance metrics.
• Verify every future packet section is static planning content only.

Prohibited PDF Content

Required Gates Before Future PDF Generation

• staff/privacy approval
• PDF scope approval
• redaction policy approval
• distribution policy approval
• versioning policy approval
• retention policy approval
• audit policy approval
• no-sensitive-content verification
• no-identity-content verification
• no-live-data verification

What Remains Blocked

Recommended Next Phase