# Handoff Transfer — Codex to Claude Code

Generated: 2026-05-19, America/New_York
Workspace: `C:\Users\ztrei\OneDrive\2. Hook Street\05. 2026 BH`
Purpose: paste this into one Claude Code session so it knows what Codex did, what remains, and what to avoid redoing.

## One-Line Status

Codex cleaned the BOS mortgage proof trail, corrected one live BOS sheet routing cell, documented the remaining Shellpoint proof gap, and committed the repo-side cleanup locally. The recommended next focused session is **Start Here v0.1 / action-spine setup**, with Shellpoint payment verification as the first proof-required card.

## What Codex Did

### BOS / STR mortgage cleanup

- Found May 15 portal screenshots for Selene and Shellpoint under `STR-Operations/`, viewed them, and moved them into:
  - `STR-Operations/mortgage-proof/2026-05/9312_selene_finance_2026-05-15.png`
  - `STR-Operations/mortgage-proof/2026-05/9332_shellpoint_2026-05-15.png`
- Added `STR-Operations/mortgage-proof/2026-05/README.md` summarizing the proof.
- Added `.gitignore` rule so raw mortgage portal PNGs stay local/private:
  - `STR-Operations/mortgage-proof/**/*.png`
- Updated stale mortgage numbers in:
  - `docs/OBLIGATIONS.md`
  - `docs/MORTGAGE_ROUTING.md`
  - `docs/MAY_AUTOPAY_PREFUND_2026-05.md`
  - `docs/MAY_2026_OPENING_SNAPSHOT.md`
  - `docs/SCOPE_BACKLOG.md`
- Created local commit:
  - `cf47351 docs: refresh STR mortgage routing proof`

### Live BOS Google Sheet

Target sheet:

- Spreadsheet: `Monthly Obligations`
- ID: `1L_rxCSOncM6WtqCYaEbooNdxiXbfOi_Sfm7k0IAAsBo`
- Tab: `Monthly Obligations`

Readback found:

- Row 6: `Shellpoint - 9332 Mortgage`
  - Amount already correct: `$3,161.51`
  - Due date: `6/15/2026`
  - Pay From Account currently: `9312 - 6651`
  - Codex did **not** change this because the Shellpoint screenshot does not show the funding account.
  - Added note to `Monthly Obligations!J6`: payment account needs proof before changing.
- Row 7: `Selene Finance - 9312 Mortgage`
  - Amount already correct: `$3,379.91`
  - Due date: `6/15/2026`
  - Pay From Account was wrong: `9332 - 2528`
  - Corrected `Monthly Obligations!J7` to `9312 - 6651`
  - Added note citing the Selene portal screenshot payment method: Checking Account (6651).

### Gmail / handoff scan

Codex reviewed recent Gmail drafts only for context. It did **not** send, delete, archive, or label anything.

Important draft findings:

- Multiple May 13-15 Mildred drafts overlap heavily.
- May 15 Mildred weekly briefing says Daily Tracker remains the source of truth.
- May 4 BOS audit draft says BOS core is working; visible problems are mostly data quality, not code.

### GitHub / issues

- Checked `zee78900/hookstreet-bos-sheets` open issues via `gh issue list`; no open issues were returned.
- Earlier MIS work was done in the local `MIS` repo:
  - Latest local MIS commit: `a9157e4 fix MIS issue diagnostics and position review output`
  - MIS branch is ahead, but direct push was blocked because the local history includes a private broker screenshot commit (`a83cc3c data: 4 broker screenshots`).
  - Do **not** direct-push MIS `master` unless private screenshot history is intentionally accepted.

## What Not To Redo

- Do not re-correct Selene in the BOS sheet. `Monthly Obligations!J7` is already `9312 - 6651`.
- Do not change Shellpoint routing based on intuition. Its row may be wrong, but the screenshot does not prove the funding account.
- Do not commit or push raw mortgage screenshots unless Sam explicitly wants those private portal images in git.
- Do not treat old `$3,853.33` Shellpoint or `$3,450.00` Selene figures as current. The verified STR mortgage subtotal is now `$6,541.42`.
- Do not send or delete the Gmail drafts without Sam explicitly approving.
- Do not direct-push MIS `master`; create a code-only branch if publishing MIS fixes.

## Recommended Next Session

### Primary focus: Start Here v0.1

Use the untracked file:

- `START_HERE_EXECUTION_LAYER_CLAUDE_CODE_MASTER.md`

The file defines the next action-spine direction. Start with its acceptance-test seed cards, especially:

- `Shellpoint payment verification`
- `Lock Mildred weekly schedule`

Recommended next steps:

1. Decide where Start Here v0.1 lives: existing BOS sheet tabs, a new local scaffold, or a dedicated action sheet.
2. Seed exactly the five acceptance-test cards from `START_HERE_EXECUTION_LAYER_CLAUDE_CODE_MASTER.md`.
3. Make Shellpoint the first proof-required action:
   - Title: `Shellpoint payment verification`
   - Required proof: portal or bank evidence showing whether payment posted and which account funded it.
4. Do not build a full app yet. First prove the action-card loop:
   - create card
   - mark done
   - add proof
   - defer with date
   - filter Mildred-safe vs sensitive

### Secondary focus: Shellpoint proof

Sam should capture or provide one of:

- Shellpoint portal screenshot showing payment method / bank account
- Chase transaction showing the Shellpoint debit and last four of the account
- confirmation screen/email with payment method

Only after that should Claude Code update `Monthly Obligations!J6`.

### Optional MIS publishing path

If Sam wants MIS fixes published:

1. In `MIS`, create a code-only branch from `origin/master`.
2. Cherry-pick the code commits only:
   - `5b029d0 MIS P0 fixes #6 + #7: PORTFOLIO_OVERLAP gate + REDUCE/EXIT graduation`
   - `a9157e4 fix MIS issue diagnostics and position review output`
3. Exclude private screenshot commit:
   - `a83cc3c data: 4 broker screenshots`
4. Push the code-only branch and open a draft PR.

## Current Repo State After Codex

Workspace repo:

- Branch: `master`
- Ahead of `origin/master` by 1 commit:
  - `cf47351 docs: refresh STR mortgage routing proof`
- Still untracked:
  - `START_HERE_EXECUTION_LAYER_CLAUDE_CODE_MASTER.md`

Raw mortgage PNGs are present locally but ignored by git.

## Recommended Opening Prompt For Claude Code

```text
Read outputs/2026-05-19_handoff_codex-to-claude-code.md and START_HERE_EXECUTION_LAYER_CLAUDE_CODE_MASTER.md.

Do not redo the BOS mortgage cleanup. Selene is already corrected in the live BOS sheet. Shellpoint routing is still proof-gated.

Focus this session on Start Here v0.1: seed the acceptance-test cards, make Shellpoint payment verification the first proof-required card, and keep Mildred-safe vs sensitive boundaries explicit. Do not build a full web app yet.
```