UES · ONE GOAL · BROWSER-LOCAL · V0

ONE / GOAL.

Set it. Run the machine. Go.

A daily-action machine for the 25-mile radius.

You get one goal. You declare a daily action. You mark the day. You stop, or you continue. The page tracks the streak. The cohort sees the receipt. The ledger gains weight when the milestones land. There is no other interface.

YOUR GOAL · IF SET, IT APPEARS HERE

The machine.

No goal set on this device yet. Use the form below.

SET IT

One goal. Declare it.

All fields are stored in this browser only. Nothing leaves your device until you log a corresponding ledger entry at /commons.

FIVE LOOPS · DAILY → ANNUAL

What runs when.

  1. DAILY

    Mark the day. Either you did the daily action or you did not. One tap. No paragraph required.

    Output: A streak counter. Visible on this page. Logged in localStorage.

  2. WEEKLY

    Sunday review: one paragraph. What worked, what slipped, what is the smallest version of tomorrow's action.

    Output: One short note appended to the goal record. Optional but recommended.

  3. MONTHLY

    On the first of each month: log a give-back ledger entry at /commons crediting the streak.

    Output: A real Hours entry on the public ledger. Weight equal to days marked × 1/30 hours.

  4. QUARTERLY

    On the 30 / 60 / 90 day crossings: stop, walk, look at the goal again. Decide: continue, restart, or retire.

    Output: A horizon-check note. Status update on the goal record.

  5. ANNUAL

    On the 365-day crossing: declare the goal complete or retire it honestly. Pick the next one in the same format.

    Output: A retirement entry on the goal record. The next goal begins.

EIGHT HORIZON BANDS · WHAT EACH DAY-COUNT MEANS

The bands.

  1. Day 01 · The first tick

    You showed up once. The machine has begun.

  2. Day 07 · One week

    A week is a real cohort unit. Most goals die before week one.

  3. Day 30 · Thirty

    The first horizon. Log a Hours give-back at /commons (+1 weight).

  4. Day 60 · Sixty

    A second Hours give-back. The machine has earned its place.

  5. Day 90 · Ninety

    The second horizon. Quarterly review. Continue, restart, or retire.

  6. Day 180 · Half a year

    Custody weight crosses (+4). The cohort can credibly point at the receipt.

  7. Day 270 · Three quarters

    A third Custody weight (+4). The end horizon visible.

  8. Day 365 · One year

    The final horizon. Goal completed or honestly retired. Next one declared.

PRINCIPLES

Seven rules before any goal is set.

  1. 01

    One goal at a time. Multiple parallel goals dilute the machine. Pick the one. Park the rest.

  2. 02

    Daily action over weekly intention. The machine runs once a day or it does not run.

  3. 03

    A streak is more honest than a plan. Plans negotiate; streaks accumulate.

  4. 04

    Mark the day even when the action was small. A two-minute version of the daily action counts as a tick. A zero day breaks the streak.

  5. 05

    Three horizons: thirty, ninety, three-hundred-sixty-five. Set the day count. Cross or restart.

  6. 06

    On milestone crossings, log a ledger entry at /commons. The streak earns Hours weight; the goal earns Custody weight.

  7. 07

    When the goal is complete, declare the next one in the same format. The machine does not retire; the operator does.

FIVE SEED GOALS · COHORT INSPIRATION

What the cohort is running.

These are five real goals the Marine Layer cohort is running today. Each is paired to a UES program, has a declared trigger condition, and points toward a Commons ledger phase. Use them as inspiration; do not copy. Set your own.

  1. ARTIFACT RUNNING

    First Bench at Hilltop, built and open by 2026-08-01

    Why: The pilot. The smallest useful unit. Proves the give-back loop works at the smallest possible unit.

    Daily: Either: log a give-back at /commons, or attend a Marine Layer sit, or send one parks-department email, or move one sub-task on the bench permit forward.

    Trigger: Bench permit issued by El Segundo Parks Department + bench fabricated + installation date scheduled.

    90-day horizon · Commons + Marine Layer · cohort: Marine Layer cohort + parks-department point person · started 2026-04-21

  2. RITUAL RUNNING

    Marine Layer eight-week cycle, completed end-to-end

    Why: The minimum unit of the cohort practice. One full cycle proves the format works.

    Daily: Sit your daily ten minutes. Post the artifact within the same day.

    Trigger: Eight weekly sits completed, eight artifacts logged, next steward named at the Pier Closer.

    90-day horizon · Marine Layer · cohort: Marine Layer cohort, cap 12 · started 2026-05-09

  3. ACQUISITION SET

    PointCast Commons CLT shell entity filed with CA Secretary of State

    Why: Phase 2 vehicle. Without it, no parcel acquisition. With it, the Commons can hold land that stays common.

    Daily: Either: review one paragraph of bylaws, or send one email to pro-bono counsel, or read one prior CLT case study, or log one Expertise give-back.

    Trigger: 100 ledger weight crossed + 1 offered easement + Articles filed + Form 1023-EZ submitted + EIN issued.

    365-day horizon · Commons · Phase 2 Vehicle · cohort: Pro-bono counsel + founding board (5 names, 3 not Mike) · started 2026-05-06

  4. PUBLICATION RUNNING

    Ten UES Working Papers in Material Culture, published

    Why: The series is the institutional memory. Ten papers establish UES Working Papers as a real publication track.

    Daily: Either: write one paragraph on the active paper, or read one source, or render one specimen plate, or commit one ledger entry for the work.

    Trigger: UES-WP-2026-01 through 2026-10 all published; Codex GREEN on at least eight; the series is its own cohort.

    365-day horizon · UES Working Papers · cohort: Marine Layer cohort + Codex review · started 2026-05-02

  5. ATTENDANCE SET

    Forty civic-surface attendances logged across one year

    Why: Civic Layer literacy at scale. Forty attendances across the six surfaces is the floor for credible cohort civic competence.

    Daily: On meeting days: attend, take notes, post artifact within 24 hours. On non-meeting days: read one packet, or walk one parcel, or talk to one regular.

    Trigger: Forty attendance entries across at least four of the six surfaces (City Council, Planning Commission, Parks/Rec/Library, ESUSD, LAX Roundtable, Coastal Commission), with one prepared public comment.

    365-day horizon · Civic Layer · cohort: Civic Layer cohort (anyone in the radius) · started 2026-05-01