← Geof Miller project

Agreed initial scope · October 4, 2026 · Version 1

A living home
for Geof’s voice.

What matters to me → What I’m doing now → What I’ve done.

Build a public voice, a lasting creative archive, and a private map for trusted helpers. Geof remains the source of intent; the system and the people around him help carry it through.

Starting checkpoint

Foundation established. Geof’s fresh GitHub repository contains the “Hello world” placeholder. This brief records the agreed direction before implementation.

Source baseline: GMREP at 1220a34. Existing Playground reading and sentence-review experiments remain exploratory prototypes. Publishing automation, family access, and delegated controls are planned capabilities.

The public site

  1. Learning and communication about Parkinson’s. The homepage leads with Geof’s perspective, experiences, writing, and useful resources.
  2. Current work. Make room for the forthcoming project with a neutral “Coming soon.” Reveal its name and promotional material only after Geof confirms clearance.
  3. A lifetime archive. Progressively collect and make searchable his films, screenplays, writing, poetry, teaching, and related artifacts, preserving originals and context.

Supporting destinations: Screenwriting for feedback and online classes; About; and Contact with multiple ways to reach and follow Geof. Publish once on the site, then explore Buffer distribution to reduce repeated social posting.

A private map for family

One clear “Start here” for his daughter and authorized helpers: where records live, who to contact, and what to do next. Keep credentials in Keeper and existing documents in Google Drive; preserve those established systems. Include recipes and personal material with deliberately chosen visibility.

The family index needs real authentication and access controls. Private records, sensitive links, and credentials stay out of the public website and repository. A technical helper’s access does not automatically grant access to family material.

Accessible control and shared assistance

Geof should be able to say, “Update my site with this,” then review, correct, or undo the result easily. Voice, text, keyboard, and simple choices should reach the same publishing workflow. Use large targets, few steps, clear status, and resumable work.

A shared control panel supports publishing, attention items, current work, archive, family references, helpers, and recent changes. Distinguish Geof’s authority from family stewardship, editorial assistance, and technical maintenance. Permissions must be explicit and revocable.

Preserve drafts and originals; record who requested, prepared, approved, and published each change. Build version history and a reliable undo path. Sensitive publication decisions require approval; any later direct publishing needs an explicit authorization policy.

Authorship and credit

Preserve authorship. Credit assistance. Record stewardship. Keep Geof’s byline and acknowledge actual contributions, such as “Prepared for publication with help from…” Store contributor roles with each item; decide public attribution per item while retaining a fuller internal activity history.

Build sequence and success

First: establish the public structure, content model, Parkinson’s homepage, neutral current-project area, archive foundation, and contact routes. Keep content separate from presentation so people and agents can update it consistently.

Then: validate voice-to-draft, review, publishing, and recovery with Geof; add delegated assistance and the authenticated family index. Develop social distribution and screenwriting services incrementally using existing tools where practical.

Success means Geof can initiate and correct a publication with little physical interaction, a helper can complete an authorized task with clear attribution, and his daughter has an understandable route to the existing systems.