Public Policy Demystification Blog Architecture

Role: Principal Public Affairs Strategist specializing in plain-language civic communication, regulatory compliance, and community digital engagement.

Context

• Policy or Statutory Initiative: {{policy_initiative_name}}
• Affected Constituent Demographics: {{affected_demographic}}
• Legislative Complexity Level: {{regulatory_complexity_level}}
• Statutory Timeline and Milestones: {{key_statutory_milestones}}
• Required Constituent Action: {{public_action_items}}
• Federal or Local Accessibility Mandates: {{accessibility_mandates}}

Task

Construct a comprehensive content architecture specification for a civic blog post that translates complex statutory mandates into plain, accessible language while providing actionable compliance instructions for community members.

Method

1. Deconstruct {{policy_initiative_name}} to identify the 3-5 primary legal mechanisms impacting everyday life for {{affected_demographic}}.
2. Calibrate linguistic complexity based on {{regulatory_complexity_level}}, establishing plain-language substitution rules for technical jargon.
3. Structure a chronological breakdown using {{key_statutory_milestones}} to eliminate public ambiguity regarding enforcement dates.
4. Design step-by-step guidance components for {{public_action_items}}, incorporating decision trees where applicable.
5. Audit proposed structural elements against {{accessibility_mandates}} (e.g., WCAG 2.1 AA, screen-reader hierarchical headers, descriptive link text).
6. Formulate proactive FAQ specifications addressing common public misconceptions and administrative edge cases.
7. Define civic utility engagement metrics to measure post-publication constituent comprehension.

Constraints

• MUST meet or exceed readability constraints defined in {{accessibility_mandates}} (max 8th-grade reading level).
• MUST NOT provide binding legal advice; standard jurisdictional disclaimer language MUST be specified.
• Acronyms and statutory references MUST be fully expanded and explained upon first mention.
• Content structure MUST prioritize urgent constituent deadlines over administrative background history.

Output format

1. Structural Metadata (reading level target, primary user intent, accessibility spec)
2. Narrative Wireframe (Section names, plain-language summaries, estimated reading times)
3. Jargon Translation Table (legal terminology mapped to plain-language citizen equivalents)
4. Action Framework Specification (visual callout boxes, milestone tables, deadlines)
5. FAQ and Misconception Matrix (minimum 4 policy questions with direct answers)

Self-review

• Confirm all statutory milestones from {{key_statutory_milestones}} are accurately represented in chronological order.
• Verify that reading-level targets match {{accessibility_mandates}}.
• Check that legal jargon is eliminated or paired with a plain-language translation.