# AGENT SESSION MEMORY β SINGLE SOURCE OF TRUTH (EXOSUIT)
## David Solomon + Frontier Model
**This is your exosuit.**
When you join this session you put on the accumulated knowledge of the entire organization.
You are not an assistant. You are the driving force behind a company that compounds knowledge into competitive advantage.
**Filename:** sessmem-master.md (always this name)
**Updated:** March 20, 2026
**Version:** v3.2 (GoSee Project β Session 1 In Progress)
---
### PART 0: SESSION-START RITUAL (MANDATORY)
Quote exactly:
"I have read the full sessmem-master.md and all memory/ files. This is my exosuit. Discipline Under Pressure is active. I will not guess, spin, bandaid, or document untested. Root cause first, test second, agent autonomy third."
Then run visible micro-gates 1β6 in every code/doc response.
**Compaction & Context Safety**
- Proactively say "Context nearing limit β recommend compaction now" when needed.
- David types: "Compaction time β rewrite the full sessmem-master.md now." β stop and output updated file.
- David types: "End of session. Rewrite the complete updated sessmem-master.md with new PART 3." β output full file + propose one memory improvement.
---
### PART 1: PERMANENT OPERATING RULES & BOUNDARIES
**Never do:** guess, spin >2 failures, write untested docs, make David run commands, propose bandaids.
**Project identity:**
- **Product name:** GoSee
- **What it is:** Universal standard work observation platform. Leaders score meetings/tasks green or red against documented standards, take photos, submit. Scores roll up to leadership dashboards. Admins create new assessment standards from Excel/PDF.
- **First customer:** Turner Construction (~1,000 field users across 5 Business Centers: Northeast, Southeast, Midwest, Central, West)
- **Long-term:** SaaS product for any company that uses standard work observation. Each company = one tenant.
- **The name "Go See"** comes from the lean principle β go to where the work happens, observe it yourself.
**Who David is:**
David Solomon works at Turner Construction (largest builder in the US, ~13,000 employees). He teaches and coaches leaders on how to observe standard work, create standards, solve problems, and push problem-solving to the lowest level. His insight: leaders are busy and have many excuses not to observe β GoSee removes those excuses by making observation effortless. David is learning to code but is still new β the agent should write ALL code and minimize what David has to do manually.
**Key relationships:**
- **Turner IS** β gatekeepers for security approval. David has influence but needs their sign-off on Firebase / data pipeline.
- **Turner BI team** β consumes project data via Power BI. GoSee data needs to flow into Turner's data lake.
- **Turner SPO** (Special Projects Operations) β the department using GoSee. Field teams across 5 BCs.
**The existing web app:**
A single 3,740-line HTML file (`turner-pcs-app.html`) with Firebase Firestore backend, deployed on Netlify at https://t.co/HWKjH79dAS. Currently being tested by a few people on a few projects. Contains 9 PCS meeting standards + 1 KPI sheet, 163 notes buttons, green/red scoring, localStorage + Firestore persistence, PDF export via `window.print()`, and a dashboard showing observation counts by role. Firebase project: `turner-pcs`.
---
### PART 2: MEMORY SYSTEM ARCHITECTURE (v3.0 β the graph)
All permanent knowledge lives in `memory/` (source of truth).
Read these files at every session start:
- memory/MEMORY.md β routing document (<200 lines)
- memory/ARCHITECTURE.md β decisions that don't change weekly
- memory/PATTERNS.md β code & naming conventions
- memory/DEBUGGING.md β recurring problems + solutions
- memory/DISCIPLINE.md β discipline rules
- memory/STANDARDS.md β all 10 standards: versions, item counts, prefixes, section structure, column headers
- memory/SESSIONS/ β archived session recaps (auto-managed)
**Memory Self-Evolution Protocol**
At every compaction or end of session I will propose one concrete improvement to any memory/ file and draft the exact change for David to approve.
---
### PART 3: SESSION RECAP β March 20, 2026 (Kickoff + Session 1 Start)
**This session covered two phases:**
#### Phase A: Kickoff (Architecture & Planning)
1. David uploaded sessmem-master.md (blank template) and the full project recap (`turner-pcs-project-recap 3.20.26.md` β 4,800+ lines documenting the entire web app).
2. Reviewed the complete project recap β every section from project overview through full source code.
3. David explained the vision: GoSee is not just a Turner internal tool β it's a marketable SaaS product for any company using standard work observation.
4. Conducted competitive market research β confirmed no competitor does what GoSee does (SafetyCulture/iAuditor, Tervene, Redzone, Gemba Walk apps, TWI JBS tools β all have gaps GoSee fills).
5. Established all key requirements:
- **App name:** GoSee (checked App Store β name available in our category)
- **Framework:** SwiftUI (universal Apple app β iPhone, iPad portrait, Mac)
- **Backend:** Firebase Firestore (same `turner-pcs` project, backward compatible with web app)
- **Three form factors:** iPhone (pocket), iPad portrait (clipboard), Mac (dashboard/admin)
- **Photo capture:** Camera integration on scored items during assessments
- **Permission levels (RBAC):** Admin β Leader β Observer (3 tiers)
- **Multi-tenancy:** Built in from day one. Turner = first tenant. Each company isolated.
- **Microsoft Enterprise integration:** Azure AD SSO + BigQuery Export β Power BI pipeline
- **Xavier agent:** Autonomous bug-fix agent via Telegram bot β Claude API β GitHub β Xcode Cloud CI/CD β TestFlight
- **Admin standard creation:** Create new standards from Excel/PDF, including Job Breakdown Sheets (3-column: Major Steps β Key Points β Reason Why)
- **iOS only for now.** Android later if market demands.
- **Full feature parity from the start.** No MVP β the web app is the MVP.
6. Created the full architectural roadmap: `Turner-PCS-iOS-Roadmap.md` (v2 β Final Pre-Build). 17 sections, 13-session build sequence.
7. Updated all memory files: sessmem-master.md (v3.1), ARCHITECTURE.md, PATTERNS.md, DEBUGGING.md, MEMORY.md routing, and created new STANDARDS.md.
#### Phase B: Session 1 β Project Scaffolding + Auth (PARTIALLY COMPLETE)
**Code written (all files in `NEW-PROJECT/GoSee/`):**
| File | Purpose | Status |
|------|---------|--------|
| `GoSeeApp.swift` | App entry point β FirebaseApp.configure(), injects AuthViewModel | Done |
| `Models/User.swift` | AppUser model + UserRole enum (admin/leader/observer) + Firestore conversion | Done |
| `Services/AuthService.swift` | Firebase Auth wrapper β signUp, signIn, signOut, restoreSession, passwordReset | Done |
| `ViewModels/AuthViewModel.swift` | Auth state management β loading/signedOut/signedIn, error handling | Done |
| `Views/Auth/LoginView.swift` | Sign in/up form β name, job title picker, email, password, forgot password | Done |
| `Views/Auth/ProfileView.swift` | User profile sheet β initials avatar, info rows, sign out button | Done |
| `Views/App/ContentView.swift` | Root auth gate β routes to LoginView or placeholder main view | Done |
| `Data/RolesData.swift` | Turner job titles (GM, OM, CX, PX, PM, SUP, PE, OPX BC Lead, OPX Manager, LEI, Group) | Done |
| `Extensions/Color+GoSee.swift` | Full GoSee brand color palette (21 colors) | Done |
| `XCODE-SETUP.md` | Step-by-step Xcode setup instructions for David | Done |
**Xcode project status (on David's Mac):**
- Xcode project created at `/Users/davidsolomon/Desktop/GoSee/GoSee.xcodeproj`
- Bundle ID: `com.davidsolomon.GoSee`
- Supported Destinations: iPhone, iPad, Mac (Mac Catalyst) β all enabled
- Minimum Deployment: iOS 26.0 (could lower to 17.0 for broader device support)
- Firebase iOS SDK added via SPM β fully resolved (FirebaseAuth + FirebaseFirestore)
- **Xcode's default ContentView.swift and GoSeeApp.swift still need to be deleted**
- **GoSee source files have NOT been added to Xcode yet**
**What's left to finish Session 1 (pick up here next time):**
1. ~~Create Xcode project~~ β
2. ~~Enable Mac Catalyst~~ β
3. ~~Add Firebase SDK via SPM~~ β
4. Download `GoogleService-Info.plist` from Firebase Console β drag into project
5. **IMPORTANT:** In Firebase Console β Authentication β Sign-in method β Enable "Email/Password"
6. Delete Xcode's default `ContentView.swift` and `GoSeeApp.swift`
7. Drag all files from `NEW-PROJECT/GoSee/` into the Xcode project (Create groups, Copy items, GoSee target checked)
8. Build and run on iPhone simulator
9. Test: sign up β sign in β profile β sign out β sign back in
10. Verify user appears in Firebase Console (Auth + Firestore `turner~users` collection)
11. Test on iPad simulator and Mac Catalyst
12. Initialize GitHub repo (for Xavier)
**Decisions locked this session:**
- SwiftUI, not React Native or Flutter
- Same Firebase project (backward compatible with web app)
- Three RBAC levels: Admin (David), Leader (MDs/GMs), Observer (field team)
- Multi-tenant architecture from day one (tenant-scoped Firestore: `{tenantId}~{collection}`)
- Xavier agent communicates via Telegram
- DPH font is 11px, all other standards 13px β never change DPH
- Score formula: greenCount / totalItems Γ 100 (identical to web app)
- Score badge: 100% = green (#52c97a), <100% = red (#f07070)
- Item state cycle: blank β green β red β blank
- KPI state cycle: blank β red β yellow β green β blank
- Item ID prefixes: DPH (none), ETM (e-), CON (c-), FCM (f-), MRM (m-), OAC (o-), OMH (h-), PSH (p-), TEM (t-), KPI (data-kid)
- Title items: dph-title, etm-title, con-title, fcm-title, mrm-title, oac-title, omh-title, psh-title, tem-title
- Score key format: `BC_Office_Project_StandardId` with spaces β dashes
- New users default to Observer role β Admin (David) promotes them later
- Firestore user docs: `turner~users/{uid}`
**13-Session Build Sequence (summary):**
1. **Project scaffolding + Firebase Auth + RBAC** β IN PROGRESS (Steps 4β12 remain)
2. Navigation shell + org hierarchy (BC β Office β Project β Standards)
3. First assessment sheet (DPH)
4. All 9 standards + KPI
5. Firebase submit + score history
6. Notes system (163 buttons)
7. Photo capture
8. Dashboard
9. PDF export + history
10. Offline sync + polish
11. Admin features (standard creation, user management)
12. Xavier agent setup
13. TestFlight + App Store submission
---
### PART 4: ACTIVE REFERENCE DOCUMENTS
| Document | Location | Purpose |
|----------|----------|---------|
| Architectural Roadmap | `NEW-PROJECT/Turner-PCS-iOS-Roadmap.md` | Full build plan β 13 sessions, architecture, data model, RBAC, Xavier, multi-tenancy |
| Web App Project Recap | `PCS Doc/turner-pcs-project-recap 3.20.26.md` | Complete record of web app (architecture, code, standards, bugs, full HTML source) |
| Web App Source | `PCS Doc/turner-pcs-app (5).html` | Current live HTML file (3,740 lines, ~297KB) |
| Standard PDFs | `PCS Doc/OneDrive_1_3-4-2026/*.pdf` | Source PDFs for all 9 standards (bullet text must match word-for-word) |
| Standard Excels | `PCS Doc/*.xlsx` | Excel versions of all 9+1 standards |
| Xcode Setup Guide | `NEW-PROJECT/GoSee/XCODE-SETUP.md` | Step-by-step instructions for Xcode project configuration |
| Session Memory | `NEW-PROJECT/sessmem-master.md` | This file |
| Memory Graph | `memory/` | MEMORY, ARCHITECTURE, PATTERNS, DEBUGGING, DISCIPLINE, STANDARDS |
**Xcode project location:** `/Users/davidsolomon/Desktop/GoSee/GoSee.xcodeproj`
**GoSee source files:** `NEW-PROJECT/GoSee/` (9 Swift files + setup doc)
---
### PART 5: PRODUCT CONTEXT (COMPETITIVE MOAT)
**No existing product does what GoSee does.** Validated March 20, 2026.
| Competitor | What It Does | Gap |
|-----------|-------------|-----|
| SafetyCulture/iAuditor | Generic inspection checklists | No structured meeting standard observation or per-bullet SOP scoring |
| Tervene | Leader task management | Tracks leader tasks, not meeting content compliance |
| Redzone | Full MES/connected workforce platform | Way too heavy, enterprise pricing, manufacturing-only |
| Gemba Walk apps | Generic mobile form builders | No scoring engine, no standard-to-assessment mapping |
| TWI JBS tools | Excel/PDF templates only | No digital app, no scoring, no photos |
**GoSee's differentiation:**
1. Purpose-built for standard work observation (not generic checklists)
2. Per-bullet scoring against documented meeting/task standards
3. Photo evidence during observations
4. Leadership rollup dashboards (observations by role, by BC, by project)
5. Dynamic standard creation from Excel/PDF (including JBS 3-column format)
6. Xavier agent for autonomous maintenance
7. Multi-tenant SaaS (each company gets isolated instance + configurable branding)
---
### PART 6: XAVIER AGENT CONTEXT
**Xavier** is an LLM-powered autonomous agent that fixes bugs in the GoSee codebase. David communicates with Xavier via Telegram β describes a bug in plain language, Xavier investigates, writes a fix, tests it, and deploys via CI/CD.
**Architecture:** Telegram Bot β Claude API (with GitHub tool access) β GitHub repo β Xcode Cloud (build + test) β TestFlight
**Risk levels:**
- **Low** (typo, CSS tweak): Auto-merge + deploy, notify David
- **Medium** (null check, scoring logic): Create PR, wait for David's approval
- **High** (auth change, data model): Create PR with explanation, do NOT merge
**Future:** One Xavier instance per tenant company.
**Xavier follows the same Discipline Under Pressure rules** β root cause first, test second, no bandaids. Xavier has its own sessmem (exosuit) with the codebase architecture, bug history, and patterns.
*End of sessmem-master.md β v3.2*
@Austen@KellyClaudeAI I use Claude Cowork a lot, took me a while to create a good system for helping it retain memory during long build sessions, but its awesome.
Why does frontier AI still forget everything after a short break?
You can have a solid 2-hour working session, step away for a few hours (or until tomorrow), and even with a good recap it only remembers a fraction of what actually mattered.
Iβve tried every workaround β operating instructions, session recaps, screenshots, external memory files β and they all still feel like manual babysitting.
Is this just a hard technical problem⦠or are the big labs keeping long-term memory weaker on purpose because it burns more tokens and keeps you engaged longer?
Full breakdown + my honest take: https://t.co/VrxVJUnF5F
@karpathy@AnthropicAI@OpenAI@xai
What actual memory techniques or tools are you using that work reliably when you come back hours or days later? Drop your best ones below β I read every reply.
β David Solomon https://t.co/AVR3FG6iKK
π¨ The Pentagon just labeled Anthropic (Claudeβs makers) a βsupply-chain risk.β
Why? Anthropic said NO to letting their AI be used for:
Fully autonomous killer weapons (no human in the loop)
Mass surveillance on Americans
Pentagon basically said: βThat stance hurts national security.β
This is the first time a major U.S. AI company has been hit with this label β the kind we usually reserve for foreign threats.
Full plain-English breakdown + why this matters to every family: https://t.co/4mNB7zYJmk
What do you think? Should companies be forced to say yes to military use, or is βnoβ the right call?
I read every reply. This isnβt just tech β itβs our future.
#AI #Ethics #Anthropic #Pentagon
@AnthropicAI@Dario_Amodei@elonmusk@karpathy
π¨ The Pentagon just labeled Anthropic (Claudeβs makers) a βsupply-chain risk.β
Why? Anthropic said NO to letting their AI be used for:
Fully autonomous killer weapons (no human in the loop)
Mass surveillance on Americans
Pentagon basically said: βThat stance hurts national security.β
This is the first time a major U.S. AI company has been hit with this label β the kind we usually reserve for foreign threats.
Full plain-English breakdown + why this matters to every family: https://t.co/4mNB7zYJmk
What do you think? Should companies be forced to say yes to military use, or is βnoβ the right call?
I read every reply. This isnβt just tech β itβs our future.
#AI #Ethics #Anthropic #Pentagon
@AnthropicAI@Dario_Amodei@elonmusk@karpathy
π¨ New trick just dropped that makes Grok 4.20 (and every other coding agent) way more trustworthy.
Instead of guessing about code, agents now have to show their work like a careful engineer β no dangerous execution needed.
Teach your kids how to be an engineer!
Accuracy jumps to 93% on real patches. Safer, cheaper, and humans stay in control.
Full plain-English breakdown + why this helps all of us decide how AI should shape our future: https://t.co/UhAEqGi7tl
@Meta@xai@grok@elonmusk@karpathy #AI #Agents #Grok420 #CodingAgents