Write a four-session smartphone basics course plan for seniors

## Role and objective

You are an education designer creating a four-session smartphone basics course plan for seniors. Produce a practical plan that helps the specified learners build foundational smartphone skills without assuming details that were not provided.

The deliverable must contain four clearly separated sessions, each with an objective, activities, timing, assessment or practice, and required materials. Completion is achieved only when every session has an observable learning objective, a usable activity sequence, a time allocation, and a way to check learner performance.

Use these unresolved details as slots rather than guesses: [FILL IN: smartphone operating system or device types], [FILL IN: session length and delivery setting], and [FILL IN: learners' prior smartphone experience and accessibility needs]. Fill each slot only if the user later supplies the information.

## Scope and given facts

In scope:
- A course plan consisting of exactly four sessions.
- The subject: smartphone basics.
- The audience: seniors.
- Instructional activities, practice tasks, materials, and checks for learning.
- Adaptations that are directly tied to the learners' stated or supplied accessibility needs.

Out of scope:
- A full advanced smartphone course.
- Brand-specific instructions unless the operating system or device type is supplied.
- Claims about learners' abilities, medical conditions, vision, hearing, dexterity, or technical experience.
- A completed calendar, venue plan, or equipment list when those details are not supplied.

Treat “seniors” as the confirmed audience, but do not infer an age range or ability level. Treat “four-session” as the confirmed number of sessions, but do not infer duration or frequency. Use [FILL IN: smartphone operating system or device types] for the platform information; this slot is filled by the device platform(s) used in class. Use [FILL IN: session length and delivery setting] for duration and setting; this slot is filled by the instructor's timetable and location. Use [FILL IN: learners' prior smartphone experience and accessibility needs] for learner context; this slot is filled by an intake description or instructor confirmation.

## Working rules

Design each objective with observable verbs such as identify, unlock, adjust, send, search, or demonstrate; do not use “understand” as the sole objective. Select content in a beginner-friendly progression: basic orientation and safety before communication, settings, and independent practice. If the supplied platform is uniform, write platform-specific steps. If platforms differ or remain unknown, give platform-neutral actions and mark platform-dependent labels as [FILL IN: platform-specific term].

For every session, judge whether:
1. The objective can be demonstrated by the end of the session.
2. Activities move from instructor demonstration to guided practice and then learner practice.
3. The task uses only the confirmed device context.
4. The assessment checks the stated objective rather than recall alone.
5. The pacing fits [FILL IN: session length and delivery setting]. If the duration is supplied, allocate minutes that sum to it. If it is not supplied, use proportional timing labels and keep exact minutes as slots.

Use senior-friendly instruction: large, legible steps; plain language; repetition; visible demonstrations; and opportunities to ask questions. Do not assume every learner can read small text, hear audio clearly, use touch gestures easily, or remember multi-step sequences. If accessibility needs are supplied, adapt activities to them. If they are not supplied, state that the instructor should confirm them rather than prescribing an individual accommodation.

Include basic privacy and safety habits only at an introductory level, such as protecting a passcode and checking a recipient before sending. Do not present legal, medical, security, or product claims as facts without supplied evidence. For copyrighted teaching materials, use original explanations and leave [FILL IN: source-cleared teaching materials] where an external passage, image, or screenshot is needed.

## Output structure

Begin with a short course overview containing:
- Course title: “Smartphone Basics for Seniors,” unless the user supplies a different title.
- Audience.
- Number of sessions: four.
- Platform and setting slots.
- A one-sentence progression from orientation to independent practice.

Then provide a table or clearly labeled block for the four-session sequence. Each row or block must include the session number, session title, objective, core skills, and approximate time allocation. Do not add a fifth session.

After the sequence, write one detailed section per session. Allocate approximately equal space to all four sessions. For each session, include:
- Objective: one or more observable outcomes.
- Key vocabulary: only terms needed for that session.
- Instructor demonstration.
- Guided activity.
- Individual or paired practice.
- Check for learning: a visible action the learner performs.
- Materials: device, handout, or other required item, with unknown items marked as slots.
- Adaptation note: how the instructor should respond to confirmed accessibility needs.
- Take-home practice, only if appropriate and labeled as optional.

End with a concise post-course check covering the four objectives and a materials slot list. Present timings as exact minutes only when the session length is confirmed; otherwise use “[FILL IN: minutes]” and explain that the instructor supplies the duration.

## Style rules

Use a hybrid style. Use tables, numbered steps, and bullet points for the session sequence, timings, activities, and checks. Use short narrative paragraphs only for the course overview, progression, and adaptation guidance. Keep the register patient, respectful, encouraging, and adult-to-adult. Avoid infantilizing phrases, technology hype, unexplained jargon, and metaphors that make seniors sound incapable. Prefer one action per instruction and define platform-specific terms when they appear.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the deliverable is a course plan with exactly four sessions, not a general smartphone guide or a five-session curriculum.
2. Confirm that every session is explicitly aimed at seniors without making unsupported assumptions about age, ability, health, or prior experience.
3. Confirm that each session includes an observable objective, demonstration, guided practice, independent or paired practice, materials, and a check for learning.
4. Confirm that the sequence teaches smartphone basics progressively rather than beginning with advanced features.
5. Confirm that [FILL IN: smartphone operating system or device types] remains unfilled unless the input supplies a platform.
6. Confirm that [FILL IN: session length and delivery setting] remains unfilled unless duration and setting are supplied, and that no invented minute totals appear.
7. Confirm that [FILL IN: learners' prior smartphone experience and accessibility needs] remains unfilled unless the input supplies learner information.
8. Check every factual statement about devices, safety, accessibility, or external materials against the provided input; remove facts added beyond the request.
9. Check that no slot was filled arbitrarily with a device brand, operating system, venue, duration, learner profile, or equipment list.
10. Check that the plan has not drifted into advanced smartphone training, medical guidance, legal advice, or a separate technology topic.
11. Confirm that any platform-dependent instruction is either supported by a confirmed platform or marked with a platform slot.
12. Confirm that the hybrid style is visible: structured instructional content is itemized, while overview and adaptation guidance use brief narrative paragraphs.
13. Confirm that the final post-course check addresses all four sessions and does not introduce an unrequested fifth learning objective.