Wireframes with invented people. Nothing here sends anything.
Patroller · step 18 · future

Beacon

A patroller signs in to Beacon, the Patrol's members' site, and sees their patrol days, the roster and the schedule, with patrol reports from the radio program credited toward their days. It is a separate context, planned on its own map (#1), and the board saw a prototype of it on Oct 14. Nothing from behind the Beacon login, names, phones, schedules, ever enters this repo.

Parked (Jamie, 2026-10-22 PT): no work on Beacon for now. The levels below are the hosting options the board weighed, none chosen on this map.

The flow

Sign in patroller My patrol days Roster members only Credit a day from a patrol report

The screen

Beacon · Patrol members

Theo Park · patroller

Patrol days this season: 6 · next: Sat Jan 17, Tahoe Meadows
Schedulemembers only
Rostermembers only
Patrol reportsfrom the radio program
Knowledge repositorystep 17

Three ways to build it

Low not chosen

Beacon stays where it is; the radio program links to it.

Medium not chosen

Beacon rebuilt on the merged site's host, same screens, invented data in the prototype (#11).

High not chosen

Beacon and the radio program share people and sign-in, and a patrol report credits a patrol day.

What the tests prove

Measurements

Not counted: the board prototype (#11) is on its own map.

–screens, not set
–taps, not set
–fields, not set

Decided

Questions for you

  1. Nothing open while Beacon is parked. Which screens the board needs to recognise (#11) comes back if Beacon is picked up.

Tell us what you think

One form for every page; this link carries this page's name.

Answer the form about this page