ForgeLessons

Adam Kane + Miguel Whitney · 9:30 a.m. HST · approximately 118 minutes

Build Miguel’s independent lesson-management workspace, starting with localization and keeping Google Sheets as the source of truth.

01 / PURPOSE

Stop Lesson Content Drift

Lesson text changes across Word, Google Sheets, and translations are getting out of sync—forcing avoidable retranslation.

The initial goal is to identify changed source text and help Miguel update localization. Broader team adoption is not a prerequisite.

02 / ARCHITECTURE

Keep One Content Authority

Google Sheets: authoritative lesson content consumed by Unity.
Supabase: supplemental step data, such as programmer notes.
Standalone app: independent development in Cursor, retaining the React/TypeScript stack.

03 / PLANNED CAPABILITIES

From Localization To Authoring

Flag changed and out-of-sync lesson text.
Create lessons; add and reorder steps.
Attach images and capture dictated site-visit notes.
Translate lesson text—not internal notes.
Support Portuguese, Spanish, and French initially, with room for additional languages.
Add glossary and admin views, including service-connection health.

04 / HANDOFF & OPEN ISSUES

Local Progress, Deployment Blocked

The standalone repository was cloned into Cursor. Local editing and Git syncing were demonstrated.

Deploy through GitHub → Vercel, not direct deployment commands.
Vercel account/GitHub authorization remained unresolved; secrets syncing also needed attention.
Database connectivity was not verified.
ForgeBot access to modify the extracted app was not established.

NEXT / AGREED FOLLOW-UP

Continue Locally; Unblock Setup Together

Miguel: continue development locally. Adam + Miguel: a time-boxed, 30-minute follow-up on September 10 to work through the remaining setup issues.

Status reflects the end of the meeting—not a current deployment audit.