Guides for the people who show up on Tuesday.

GA-01Interview a pickleball team captain for the team page

reporting · 1 week · feeds pickleball-team-page

Interview one team captain who has agreed in writing to a 30-minute call about how the team schedules play, welcomes new players and posts results. Turn the call into proposed updates to the team guide, using only what the captain said and confirmed.

• Consent form signed by the captain, stored with the assignment
• Interview notes with timestamps for each quote
• Proposed edits to the pickleball-team-page guide sections

• The captain has approved every quote in writing before anything is published
• No quote is attributed to anyone who did not say it
• Proposed edits add no facts the captain did not confirm

Learns: Interviewing with consent, Quote verification, Turning notes into a guide section

Approval: Mike approves before any interview is published or quoted

GA-02Fact-check El Segundo resource links for new-in-town

reporting · 2 weeks · feeds new-in-town

Check each local resource already listed in the new-in-town guide for El Segundo. Confirm that it is open, current and useful to a newcomer, then propose additions. Record every check with the date and the primary source you used.

• Link audit table with status, last-checked date and source for each resource
• Up to five proposed additions, each with a one-line neutral description
• List of entries that could not be verified

• Every resource has a dated check against a primary source such as the organization site or a city page
• Nothing is added that was not checked
• Unverified entries are flagged, not silently removed

Learns: Source verification, Local government research, Writing neutral one-line descriptions

GA-03Draft the first-visit checklist for a neighborhood guide

guide writing · 1 week · feeds start-a-neighborhood-guide

Write a first draft of the checklist and the wanted list for the start-a-neighborhood-guide page. Base it on the guide sections already in place and on public city guidance about neighborhood groups. Keep the steps general enough for any neighborhood, with one El Segundo example.

• Checklist draft with six to eight steps, each with a one-sentence detail
• Wanted list draft with five items a reader could send in
• Short source note linking each step to the public guidance it came from

• Each step can be completed by one person in under an hour
• Every step cites a public source or is marked as the Guide opinion
• The text reads at about an eighth-grade level

Learns: Plain-language how-to writing, Reader-first checklists, Citing public process pages

GA-04Write a plain-English ladder rules explainer

guide writing · 3 weeks · feeds pickleball-ladder-and-league-night

Turn a set of ladder and league-night rules, shared by a host who agrees to share them, into a plain-English explainer with one worked example. Do not invent rules. Mark any rule the host has not confirmed so the Guide can resolve it.

• Rules explainer under 800 words
• One worked example using fictional player names
• List of open questions for the host

• Every rule traces to a source the host provided
• The worked example uses only fictional names and scores
• The explainer scores at grade 8 or below on a standard readability check

Learns: Rules writing, Worked examples, Readability checks

Approval: Mike approves the explainer before it is published

GA-05Build a schedule and results JSON template for team pages

data · 2 weeks · feeds pickleball-team-page

Design a small JSON schema for a team schedule and results, with a sample file for one invented team. Pages and agents will read the same file, so keep field names plain and write every date in ISO 8601 with a time zone.

• JSON schema file with a description for each field
• Sample file for one fictional team with at least eight matches
• Short note listing edge cases such as forfeits, postponements, rain-outs and ties

• The sample validates against the schema with no errors
• Every date uses ISO 8601 with a time zone
• The schema can represent forfeit and postponed status

Learns: JSON schema design, Data validation, Edge cases in sports data

GA-06Audit all guides for privacy: minors and consent

data · 4 weeks

Read every guide and its sections, checklist and wanted list. Flag any text that names a minor, a private person or a private address, or that implies consent that was never given. Report each finding with its file and location. Do not edit the guides in this assignment.

• Audit table with one row per finding
• Severity rating for each finding
• Short summary of patterns and recommended fixes

• Every guide in src/data/guides is reviewed
• Each finding cites a slug and a section heading
• The report copies no personal details beyond what is needed to find the text

Learns: Privacy review, Consent basics for public writing, Structured audit reporting

Approval: Mike approves any fix that changes published guide text

GA-07Design a printable game-day card for a court bulletin board

design · 3 weeks · feeds game-day-reporting

Design a one-page printable card that tells players how to find league-night information, check the ladder and report a score. Use only the steps and field names from the game-day-reporting guide. The card should be readable from two meters away.

• Print-ready PDF at letter size
• Editable source file
• One-paragraph note on type sizes and contrast choices

• Body text is at least 14 pt and headings at least 24 pt
• The card still reads clearly when printed in grayscale
• The card contains no photos of people

Learns: Print layout, Type hierarchy, Contrast checks for accessibility

Approval: Mike approves before the card is printed or posted at any venue

GA-08Shoot header photos of public courts and beaches

design · 2 weeks · feeds beach-and-run-clubs

Photograph public parks, courts and beach access points in El Segundo for guide headers. Shoot at quiet hours, frame without identifiable people, and log the location and time of each shot. Do not photograph private property without permission.

• Set of ten to fifteen header-ready images, cropped to the guide banner size
• Shot log with location, date, time and orientation for each image
• Short note on any shot that needed a retake because of people in frame

• No image shows an identifiable person without signed consent on file
• Every image has an alt-text line describing the place, not the people
• Every image is at least 2000 pixels wide

Learns: Location photography, Consent and privacy in public spaces, Image preparation for the web

Approval: Mike approves every photo before it is used on any page

GA-09Recruit and onboard the first three volunteer contributors

community · 1 week · feeds start-a-pickleball-team

Find three people who want to help with a guide, using a short public sign-up form and a short conversation with each. Explain the one-Guide-per-topic model, what contributors do and do not do, and which decisions are still open. This is a volunteer project brief. It is not a job offer, and intern applications are not open.

• Recruiting message draft for Mike to review
• One-page onboarding guide for contributors
• Log of the three first contributors and the first task each agreed to

• Three contributors have agreed in writing to a first task
• Contributors are asked only for a name and a preferred contact method
• The recruiting message makes no employment or compensation promises

Learns: Volunteer recruiting, Onboarding design, Setting clear scope

Approval: Mike approves the recruiting message before it is sent to anyone

GA-10Compile a consent-based list of local run clubs and rec leagues

community · 2 weeks · feeds beach-and-run-clubs

List public-facing run clubs and rec leagues in the South Bay that publish their own meeting times. Use only public channels. Log each contact attempt and its result. Record organization names and public links only, with no personal details about any organizer.

• List of at least ten groups with name, public link, meeting info and last-checked date
• Contact log showing each attempt, channel and outcome
• Short note on which groups asked not to be listed

• Every listed group has a public source for its meeting information
• No group is listed after it asked to be left out
• The file holds no personal contact details for individuals

Learns: Community research, Consent-based outreach, Maintaining a directory

Approval: Mike approves before any group is listed publicly or contacted directly

GA-11Write an agent prompt that drafts a game recap from a stats sheet

agent ops · 3 weeks · feeds game-day-reporting

Write a prompt and a fixed output format for an agent that drafts a game recap from a stats sheet. The draft is for human review only. The prompt must forbid invented scores, names and quotes, and must mark any missing field instead of guessing.

• Prompt file with role, inputs, rules and output format
• Three test runs on fictional stats sheets, with saved outputs
• Failure log listing every invented detail the agent produced and the prompt change that fixed it

• The test set produces zero invented scores or names
• Missing fields appear as [MISSING] in the output
• Every output says a human must review it before publication

Learns: Prompt design, Evaluation with test cases, Human review in the loop

GA-12Spec a weekly link-check and staleness report for all guides

agent ops · 4 weeks

Write a spec, not a live job, for a check that lists every related link and every dated checklist item across the guides. It should flag links not checked in 90 days and write a report for a human. The report goes to a review queue and never to the live site.

• Written spec covering inputs, outputs, schedule and failure cases
• Dry-run report on the current guides
• Runbook section explaining how a human clears each flag

• The dry run covers every guide in src/data/guides
• The spec makes no automatic edits to guide files
• The runbook names the reviewer and the time allowed for each flag

Learns: Automation specs, Runbook writing, Limiting agent actions to review