Parallel mining sessions — paste-able prompts¶

Purpose: Self-contained menu of research topics that can be farmed out to separate parallel Claude sessions. Each numbered topic below has a one-line description plus a paste-able prompt that bootstraps a fresh session with full context. Drop any of these into a new chat and Claude will execute autonomously.

These topics were sized after the 2026-05-08 session that stood up the external-data connectors (Gmail, M365 multi-tenant, Synology). With the connectors in place, the FP&A workflow can mine concrete dates, decisions, and counterparty status directly from email / SharePoint / Teams / files rather than relying on Austin to summarize.

For session opener: the first message in any new session should link back to this file (https://gitea.austinrenfroe.com/austin/renfroe-holdings/src/branch/main/todo/parallel-mining-sessions.md) so the cold session can read the full bootstrap + topic context.

Bootstrap (paste into every new session)¶

"We're working in the renfroe-holdings repo. Bootstrap by reading these in order: CLAUDE.md, context/discovery-summary.md, context/entities.md, context/people.md, decisions/log.md (last 5 entries), todo/parallel-mining-sessions.md (this file). Then execute the topic below.

Working dir: ~/projects/renfroe-holdings on claude-code-01.

External-data tooling (read-only by script-level enforcement; full setup in scripts/inboxes/README.md):
export BW_SESSION="$(cat ~/.config/bw/session)"
cd ~/projects/renfroe-holdings

# Microsoft 365 — both tenants. cm = Casa Moksha, rfh = Renfroe Holdings.
python3 -u scripts/inboxes/m365.py mail <cm|rfh> --top 50 --q "<keyword>"
python3 -u scripts/inboxes/m365.py message <cm|rfh> <message-id>
python3 -u scripts/inboxes/m365.py files <cm|rfh> --path "/Documents/<subfolder>"
python3 -u scripts/inboxes/m365.py sites <cm|rfh>
python3 -u scripts/inboxes/m365.py events <cm|rfh> --days 30
python3 -u scripts/inboxes/m365.py teams <cm|rfh>
python3 -u scripts/inboxes/m365.py chats <cm|rfh> --top 100

# Gmail ([email protected]) — IMAP + iCal feed
python3 -u scripts/inboxes/gmail.py search 'FROM "@portilla.com.mx" SINCE 1-Jan-2026'
python3 -u scripts/inboxes/gmail.py fetch <uid>
python3 -u scripts/inboxes/gcal.py upcoming --days 14

# Synology /volume1/cloud (read-only, mounted on proxmox; not natively in this LXC)
ssh proxmox 'sudo find /mnt/synology-cloud -maxdepth 3 -type d' | head
ssh proxmox 'sudo ls "/mnt/synology-cloud/SP (Moksha)/Accounting"'
ssh proxmox 'sudo cat "/mnt/synology-cloud/<path>"'
Conventions for findings: - Write substantive output into legal/, accounting/, context/, or tax/ as appropriate. Make NEW files for new topics; update existing for incremental data. - Append decisions/log.md if a substantive decision lands. - Update todo/for-austin.md or todo/for-advisors.md with concrete asks if you surface them. - Don't dump verbatim email content into the repo — paraphrase tightly. Multi-page email transcripts are noise; what's worth keeping is dates, who-said-what, and decisions. - Don't double-write what's already documented. Cross-check context/, legal/, accounting/, tax/, decisions/log.md before adding to avoid duplication. - Flag anything that affects active mandates (Cindy removal, Pearce 2025 filing, JME deliverable, Mita price reconciliation). - Commit + push frequently — small, focused commits per finding rather than one giant commit at end of session.

Read-only enforcement: the M365 app is consented for read+write delegated permissions, but m365.py only requests read scopes. Never bypass this — if a task requires writing to mail/files/Teams, surface it back to Austin first.

Session etiquette: end-of-session, leave a clean working tree (everything committed), update todo/for-next-session.md if you've left work in flight, and surface to Austin anything that needs his decision."

Topics¶

1. Mita Garden Hills purchase-price reconciliation¶

The Sales Contract Financial Plan lists ¥760M, but Austin paid more due to property changes during build-out. Repo flags Mita basis as TBD until reconciled.

Reconcile the true Mita Garden Hills 1009 purchase price + basis. Read the full Closing Documents folder at /mnt/synology-cloud/Business/Renfroe Holdings GK (Mita Garden Hills)/Closing Documents/ via ssh proxmox, including the Special Changes Addendum, all wire confirmations, ownership change agreement, and assignment paperwork. Cross-reference with M365 mail in both tenants (search "Mita", "Mitsui Fudosan", "Pinnacle", "Tokyo Star", "TSB") for any wires or addenda not in the Synology share. Produce accounting/mita-purchase-price-reconciliation.md with a definitive line-item buildup of the actual amount paid, broken down by land / building / consumption tax / closing fees / property-change additions. Update context/entities.md and downstream tax / banking / legal files with the reconciled number. Until this lands, no Mita dollar figure should be cited in advisor-facing output.

2. Pearce Bevill 2025 filing prep — actual state vs. the 19-item agenda¶

The repo has a 19-item agenda for Pearce in tax/2025-filing-prep.md. Mining email will say what's already been addressed.

Mine all RFH-tenant mail (and personal [email protected] if relevant) for traffic with Pearce, Bevill, Leesburg, Moore (search "Pearce", "Bevill", "Leesburg", any @pearcebevill.com or related domain). Pull the substantive threads from 2025 to present. Reconcile against the 19-item agenda in tax/2025-filing-prep.md: which items has Pearce already addressed? Which are open? What's Pearce's read on PFIC / GILTI / 5471 / FBAR / NOL / Augusta rule / Renfroe Innovation entity form? Update tax/2025-filing-prep.md with the actual status of each item and append tax/pearce-bevill-thread-summary.md with a chronological summary of what Pearce has weighed in on. Flag any positions that conflict with what's currently in the repo.

3. JME Contadores integration — what monthly deliverables actually exist¶

The repo treats "JME monthly deliverables" as pending. Mining mail will say what's actually been delivered.

Mine all CM-tenant mail (and RFH if relevant) for traffic with JME Contadores / JME Contador / Grupo Consultor JUA / minfante / any Mexican CPA-related domain. Pull every monthly deliverable that has actually arrived (TBs, GLs, P&Ls, CFDI exports, IMSS / ISR confirmations). Cross-reference with source-data/jme/ to see what's already in the repo vs. what's been emailed but not pulled in. Identify any month where JME's package has arrived but isn't in source-data/. Update accounting/moksha-rollup-plan.md and todo/remaining-work-summary.md with the actual JME deliverable status. Surface any answers JME has given to questions in todo/jme-questions-2026-04-29.md.

4. Casa Moksha SharePoint live ↔ Synology replica audit¶

The Synology has /volume1/cloud/SP (Moksha) mirroring CM SharePoint. We need a directory map and divergence list.

Build a directory-by-directory comparison between (a) live Casa Moksha SharePoint via M365 Graph (m365.py sites cm enumerates 8 sites: Accounting, Marketing, mgmt, hr, Legal, guestrelations, MokshaMaintenance, root) and (b) the Synology replica at /mnt/synology-cloud/SP (Moksha)/ accessed via ssh proxmox. Produce source-data/casa-moksha-sharepoint-index/README.md mirroring the pattern of source-data/synology-documents-index/README.md — for each top-level area, list what's there, when it was last updated, and whether the live site has files the replica doesn't (or vice versa). Highlight anything that suggests the replica is stale or the live site has post-replica activity worth mining.

5. Casa Moksha Teams chat archives — operational context¶

22.9MB of Teams Chat Files in RFH OneDrive replica, 24.3MB in CM OneDrive replica. Ground-truth ops context lives there.

Read the Teams Chat Files dumps under /mnt/synology-cloud/OneDrive (Moksha)/Microsoft Teams Chat Files/ and /mnt/synology-cloud/OneDrive (GMail)/Microsoft Teams Chat Files/ via ssh proxmox. Cross-reference with live Teams chats via m365.py chats cm --top 100 and m365.py teams cm to enumerate channels. Produce source-data/casa-moksha-teams-chat-summary.md capturing: (a) which threads / channels exist, (b) what topics dominate (e.g. Cindy era, vendor decisions, guest issues), © any ops decisions or commitments not already documented elsewhere in the repo. Don't dump verbatim chat content; paraphrase tightly. Flag anything that affects active mandates (Cindy removal, Pearce filing, JME catchup).

6. Renfroe Innovation — entity scoping from email¶

Repo currently has Renfroe Innovation as a Xero tracking option only. The actual entity story is murky.

Mine all email across both M365 tenants and Gmail for "Renfroe Innovation". Surface: (a) any formation discussions (LLC? S-corp? not yet formed?), (b) what IP it's intended to hold, © what activity has been tagged to it (CONLEY ROSE legal $1,500 was retagged 2026-04-20; what else?), (d) any related counterparties (other patent firms, licensing parties, IP attorneys). Produce context/renfroe-innovation-scope.md with a "what we know" doc so Pearce can advise on entity form. Update the Renfroe Innovation entry in context/entities.md with whatever firms up.

7. Withers London litigation portfolio¶

Three matters: Rodrigo Ponce de Leon recovery (~$100K, partly recovered), HyperRealms equity, Gilette Studios equity. Financial impact unknown.

Mine email (RFH tenant primarily, CM if relevant, [email protected] personal) for traffic with Withers London (any @withers-related domain), and for "HyperRealms", "Gilette" (or "Gillette") + "Studios", and "Rodrigo Ponce de Leon". Surface: (a) status of the $100K Rodrigo recovery (paid back? still owed? partial?), (b) HyperRealms equity dispute — what equity exactly, suit posture, expected timeline, financial expectations, © Gilette Studios equity — same questions. Produce legal/withers-london-portfolio.md with a matter-by-matter timeline + status. Update the HyperRealms entry in entities.md Investment positions with concrete dispute status. Reconcile against the Synology folder /mnt/synology-cloud/Legal Matters/Rodrigo Ponce de Leon/ if it has supporting evidence.

8. Casa Moksha guest revenue history — fill the unidentified gaps¶

CO DASH LLC, Richard Rosenblum, Inner Warrior, Secluded Serenity, NVIO Jose Pablo Gonzalez Deleze are all unidentified in the repo.

Mine email across both tenants + Gmail for Casa Moksha guest revenue counterparties: "CO DASH", "Richard Rosenblum", "Uri Metsarme", "Inner Warrior", "Secluded Serenity", "Ariella Laden", "Jose Pablo Gonzalez Deleze" / "NVIO". Pull booking confirmations, retreat agreements, payment confirmations. Update context/people.md "Casa Moksha guest-side counterparties" table with concrete identification (corporate retreat? individual guest? recurring? one-off?). Cross-reference with PayPal exchange history if email surfaces it. Build out accounting/casa-moksha-guest-revenue-ledger.md for 2024+2025 channels (Brex Dep, Santander MXN, PayPal, Wells Fargo 6248 historical).

9. Five Points / 1006 20th St S / SBA / Edgewood — full operational reconstruction¶

Bankruptcy / foreclosure / SBA-PG structure is documented but the operational thread (Edgewood property mgmt, SBA correspondence, AFR amortization) lives in email.

Mine RFH-tenant mail for Five Points BHM, 1006 20th St S, Edgewood Partner, ServisFirst Bank (legacy), SBA EIDL, and AFR loan to Austin's parents. Surface: (a) Edgewood's monthly cadence — what bills do they actually pay, when do they spike (the Apr 2026 $1,563 vs. monthly $500), (b) SBA correspondence — any modifications, deferrals, payoff discussions on the $7,965/mo PG Austin pays personally, © AFR loan paperwork — any signed promissory note, amortization schedule, interest payments going to parents, (d) any post-foreclosure 1006 cleanup items. Produce accounting/five-points-1006-sba-narrative.md with the full story including dollars and dates. Update entities.md Five Points BHM section + banking/jpmorgan-chase.md with anything new.

10. Portilla billing reconciliation across entities¶

The 2026-04-17 DEBIT NOTES email is the canonical billing record. Reconcile against the ledger.

Mine CM-tenant mail for all Portilla invoices and debit notes (search "DEBIT NOTES", "factura", "invoice", "[email protected]"). Pull every billing event from 2024 to present. Reconcile against the existing accounting/vendor-mappings.md Portilla entry and the Brex transaction history (Primary + Casa Moksha Ops). Produce accounting/portilla-billing-reconciliation.md with: (a) every Portilla invoice/debit note ever sent, (b) which entity paid each (Primary vs. Casa Moksha Ops vs. unpaid), © which mandate each charge relates to (RHG conversion / Cindy consignation / Cindy share return / general corporate / other). Surface any invoices billed but not paid; any payments not matched to an invoice; any entity-allocation problems for the intercompany agreement.

Possible later additions (not yet sized into prompts)¶

"Return of RHG Shares - Formal timestamp" thread — interleaved with Cindy consignation but distinct; substantive share-return paperwork. Read and merge with legal/cindy-consignation-timeline.md.
Yuriko Kato GK departure paperwork — the Aug 22, 2025 Legal Affairs Bureau acknowledgment is in the Synology share; mine Withers Japan / Yamashita Law correspondence for the surrounding context.
HHR Stock Trust → Hunter disbursement — pull mail re: trustee duties, disbursement plan, Plaid feed disconnect timing.
Tokyo Star Bank ongoing operations — mortgage statements, FX flows, GK rental income; mine Withers Japan + TSB correspondence for ongoing posture beyond the closing story.
W 3603 renovation status — DW Residential active billing, Augusta rule planning, RENFROE rental setup.