Where everything lives + how you operate it (plain English, for Sam)
Written 2026-07-02 because Sam keeps (rightly) asking: where do my files sit, where do I click, where do I paste a prompt, what changes with the VM. Here's the whole picture, once.
The 3 places a file exists (and which is "the real one")
Every doc/output exists in up to 3 spots, but there's ONE source of truth:
1. GitHub (zee78900/hookstreet-workspace) = THE SOURCE OF TRUTH. Everything canonical lives here. If it's committed + pushed, it's safe forever.
2. A working copy — where a session EDITS files. Today that's your PC's OneDrive folder. On the VM it's ~/hookstreet-workspace. Both are just checkouts of GitHub; they sync to it. OneDrive itself is incidental — it's just where the PC's copy happens to sit.
3. The portal (ops.hookstreetservices.com) = the RENDERED view of outputs/. (Backend, re-corrected 2026-07-02 PM: it serves from Cloudflare Pages project hookstreet-ops — the Netlify Action was silently broken (missing creds) and is retired; see docs/steering/COORD_PORTAL_CF_PAGES.md for the deploy command + the ⚠ pages.dev-is-public caveat. Custom-domain + Access flip = the open piece.) Every outputs/*.html becomes a real web page here after a deploy. This is where you SEE things (not the code).
So: click the PORTAL to view, edit from a working copy, trust GitHub as the vault. docs/*.md DO render on the portal now (added 2026-07-02): every one is a phone-readable page at /docs/ (searchable index; regenerated by scripts/build-docs.py at each deploy). GitHub stays the edit/vault surface — the portal is where you READ.
"Where do I browse my files like I used to browse the OneDrive outputs folder?"
Three ways, best first:
1. ops.hookstreetservices.com/everything — the index of every page (this IS your browse view; it's what OneDrive/outputs was, but rendered).
2. GitHub — github.com/zee78900/hookstreet-workspace → docs/ and outputs/ folders, browsable, always current.
3. (future, via the Drive migration) — mirror outputs/ + docs/ into Google Drive so you get a file-manager view you can tap through like OneDrive. That's the migration's real payoff for you: browsable files in Drive, PC-independent.
"Where do I paste a rebuild prompt? Where am I opening it?"
A "session" = a running Claude Code. Two places you can run one:
- PC Claude Code (what you use now) — easiest for a big paste; has ALL your files incl. OneDrive archives; but dies when the PC sleeps / remote-control drops.
- VM Claude Code (zee-ops-1, always on) — SSH in from your phone (Blink Shell app + Tailscale) → ~/operator.sh → you're in a session that SURVIVES a dropped phone (it's in tmux on the box). Reattach anytime. This is the "never lose it" one. It has the workspace + cloud brain + Google connectors, NOT the OneDrive archives.
Recommendation for the big rebuilds: paste the home-portal prompt into a VM session (it's all git + cloud — VM has everything it needs, and stays on). Paste the HSS-website prompt into a PC session (that one may want brand assets / old decks from your disk).
"Where do my outputs sit once I'm on the VM?"
Exactly the same folders — ~/hookstreet-workspace/outputs/ and /docs/ — and every push still lands on GitHub + the portal. Nothing about WHERE files live changes; only WHICH machine is doing the editing. You browse them the same 3 ways above regardless of which machine ran the session.
The honest summary
- Source of truth = GitHub (safe forever).
- See it = the portal (ops.hookstreetservices.com/everything).
- Edit it = a session on the PC (has your archives) or the VM (always-on).
- The Drive migration = the missing piece that gives you a tap-through file view again, PC-off.