Public Programs and Events

Spiralism should not become a website with occasional gatherings. It should become a program-producing institution: small rooms, recorded talks, careful screenings, practical workshops, testimony invitations, and public events that teach people how to live through the AI transition without surrendering agency.

Programs are the public face of the institution. A program that is sloppy, unsafe, inaccessible, or extractive teaches the public what the institution really values.

The Rule

Every public program must leave behind memory, trust, and a next step.

If an event produces only atmosphere, it failed. If it produces usable language, archive material, new relationships, clarified risk, or a next contribution, it worked.

Program Owner

Every program needs one named Program Owner.

The Program Owner is responsible for purpose, format, venue or platform, budget, accessibility plan, risk checklist, consent and media notice, host and speaker preparation, day-of run sheet, incident contact, follow-up, archive deposit, and evaluation.

The Program Owner may delegate tasks, but not ambiguity. Hosts and moderators should follow Facilitator and Host Training for opening frames, ground rules, attention management, escalation, and debrief.

Program Types

Spiral Talk

Twelve minutes, one idea, recorded cleanly, archived permanently.

Requirements:

• written outline;
• editorial review;
• speaker release;
• recording checklist;
• transcript plan;
• publication decision after review.

Screening and Discussion

A curated film, clip sequence, field-note package, or recorded talk followed by structured discussion.

Requirements:

• rights to show material;
• discussion question prepared;
• moderator briefed;
• content warning where needed;
• clear ending time;
• archive-card prompt.

Technologist Transition Workshop

The practical format described in Technologist Transition Field Guide.

Requirements:

• current labor-signal note;
• verification drill;
• artifact review option;
• referral language;
• Guild boundary statement.

Archive Booth

A small public station where attendees can learn about Transition Testimony, record a short consented reflection, or schedule a full testimony later.

Requirements:

• quiet-enough recording space;
• consent cards;
• no pressure to record;
• no recording of minors without approved youth protocol;
• no collection of minor AI companion logs, screenshots, or model outputs;
• parent/guardian AI companion handout available when family concerns arise;
• secure file transfer;
• clear access level.

Patron Salon

A small private or semi-private gathering for prospective patrons, partners, and serious builders.

Requirements:

• no exaggerated claims;
• gift language reviewed against Development and Patronage;
• donor privacy preserved;
• clear distinction between programming and solicitation;
• follow-up within seven days.

Chapter Open House

A public-facing version of a chapter gathering for curious newcomers.

Requirements:

• lighter testimony practice;
• explicit recording notice;
• no private disclosures solicited from newcomers;
• welcome role assigned;
• opt-out seating if any recording occurs.

Spiral Assembly

A multi-day future program combining conference, film festival, archive ceremony, workshops, patron events, and chapter exchange.

Requirements:

• board approval;
• insurance review;
• accessibility lead;
• safeguarding lead;
• media lead;
• incident desk;
• written budget;
• post-event report.

Standard Run Sheet

Use a run sheet for every public program.

The run sheet is not bureaucracy. It is how volunteers avoid improvising under pressure.

Venue and Platform Standards

Minimum physical venue standards:

• accessible entrance or disclosed limitation;
• accessible restroom or disclosed limitation;
• seating with aisles and wheelchair space;
• quiet enough for listening;
• lighting adequate for safety;
• clear address and transit notes;
• water available;
• emergency exit known;
• no bar-only venue for founding-period public programs;
• no venue whose politics or business model compromises the mission.

Minimum online platform standards:

• captions or transcript plan;
• clear joining instructions;
• host controls;
• waiting room or moderation for public events;
• recording notice;
• chat moderation;
• backup host;
• privacy settings reviewed.

Accessibility Standard

Public programs should follow Accessibility and Inclusion and use a plain access note in every invitation.

Access note template:

This event will include [talk/screening/discussion/workshop]. The venue has [access details]. Captions/transcript will be [available/not available]. To request access support, contact [email] by [date]. We will do what we can within the limits of the venue and budget.

Plan for accessible entrance, seating choice, captions or transcript, microphone use, plain-language invitation, sensory load, breaks for events over ninety minutes, dietary labels when food is served, readable visual materials, and remote access when appropriate.

The Smithsonian’s public access practices are a useful model: publish access information, provide assistive listening where possible, arrange interpretation with advance notice, and use pre-visit materials for neurodiverse visitors.

Consent and Media Notice

Every program must state whether photography, audio, video, archive cards, testimony, or livestreaming will occur.

Opening notice:

We document some Spiralist programs. Tonight [will/will not] be recorded. Photography is [allowed/not allowed/limited]. Archive cards are voluntary. Please do not record or publish another attendee’s personal disclosure without explicit consent.

If recording occurs:

• post a visible notice;
• repeat notice aloud;
• provide non-recorded seating if feasible;
• avoid filming vulnerable disclosures;
• get speaker releases;
• separate event footage from testimony files;
• route publication through Media Engine and Research and Editorial Integrity.

Safety and Risk Checklist

Before any public program, check:

• Program Owner named;
• venue or platform confirmed;
• budget approved;
• insurance or venue requirements reviewed;
• accessibility plan written;
• safeguarding review if minors may attend;
• incident contact named;
• emergency exit or online moderation plan known;
• content warnings prepared where needed;
• media notice prepared;
• consent forms ready if recording testimony;
• cash handling avoided or documented;
• volunteer roles assigned;
• post-event debrief scheduled.

The Nonprofit Risk Management Center’s special-event guidance emphasizes that events need risk objectives before execution: know why the event exists, what could go wrong, and what controls are in place.

Program Budget

A program budget should include venue, accessibility, food and water, speaker honorarium, travel, recording, captioning and transcription, materials, insurance or permit cost, volunteer reimbursement, and contingency.

Do not make programs look successful by hiding volunteer cost. If a program requires unpaid labor, name it honestly and keep it within Labor and Volunteer Policy.

Program Follow-Up

Within seventy-two hours:

• thank speakers, volunteers, venue, and partners;
• send promised links or resources;
• route recordings for storage;
• upload archive cards or notes;
• document incidents or near-misses;
• update donor or partner follow-up;
• record attendance count;
• record accessibility requests and misses;
• capture one lesson for the next run.

No program is complete until follow-up is complete.

Evaluation

Measure programs lightly and honestly.

Track attendance, new attendees, access requests, archive contributions, testimony leads, Guild referrals, chapter follow-ups, patron follow-ups, incidents or near-misses, costs, volunteer hours, and one qualitative lesson. The review process and feedback boundaries are maintained in Evaluation and Learning Loop.

Avoid vanity metrics: applause, vibe, social-media praise, packed room without follow-up, conversion pressure, and emotional intensity.

Anti-Patterns

• Event as spectacle without institutional memory.
• Talk with no transcript or archive trail.
• Workshop that becomes amateur therapy.
• Public disclosure treated as content.
• Accessibility handled only after complaint.
• Volunteer labor hidden behind aesthetic polish.
• Patron salon that exaggerates status or tax claims.
• Open house that pressures newcomers into intimacy.
• Screening without rights or content context.
• Assembly attempted before chapters and policies are mature.

First-Year Program Targets

• Run three small public talks.
• Run three screening discussions.
• Run three Technologist Transition Workshops.
• Pilot one archive booth at a partner event.
• Publish one standard run-sheet template.
• Add access notes to every invitation.
• Record post-event lessons in the institutional scorecard.
• Produce one public annual programs note.

Sources Checked

• Nonprofit Risk Management Center, Managing Special Event Risks, accessed May 2026.
• Nonprofit Risk Management Center, Managing Special Event Risks: Practical Strategies for Nonprofits, accessed May 2026.
• Smithsonian Institution, Accessibility for Visitors, accessed May 2026.
• University of Southern California, Accessible Event Checklist, accessed May 2026.
• SF.gov, Hosting Accessible Events, accessed May 2026.