Renfroe Holdings

Family-office knowledge base for Austin Renfroe — entities, accounting, decisions, and source documents in one navigable record.

Browse the entity stack → Decisions log

17 entities tracked

64 Monarch accounts

~$25M portfolio gross

7 active mandates

Hierarchy at a glance

graph TD
    Austin[<b>Austin Renfroe</b><br/>legal: Gavon Augustus Renfroe]:::owner

    Austin -->|100%| RFH[Renfroe Family Holdings, LLC<br/>US TX · disregarded SMLLC]:::active
    Austin -->|100% personal| RI[Renfroe Innovation, LLC<br/>US TX · parallel to RFH]:::active
    Austin -.personal.-> Personal[Personally held<br/>W 3603 · 210 Lavaca 2612 · Oceana 433]:::personal
    Austin -.99% personal.-> RHGmx[Renfroe Hospitality Group<br/>S.A. de C.V. → S. de R.L.<br/>Mexico · Form 5471]:::foreign

    RFH --> Subs[5 active US sub-LLCs<br/>W 3101 · ATX/Austin/Renfroe Marine · Five Points]:::active
    RFH --> Pending[3 pending US TX entities<br/>RHG-LLC · CM-LLC · CM-Holdings-LLC]:::pending
    RFH --> GK[Renfroe Holdings GK<br/>Japan 合同会社<br/>Mita Garden Hills · Form 5471]:::foreign

    classDef owner fill:#fef3c7,stroke:#92400e,stroke-width:3px,color:#000
    classDef active fill:#d1fae5,stroke:#047857,color:#000
    classDef pending fill:#fef9c3,stroke:#a16207,stroke-dasharray:5 5,color:#000
    classDef foreign fill:#dbeafe,stroke:#1e40af,color:#000
    classDef personal fill:#fce7f3,stroke:#9f1239,color:#000

Full hierarchy + Mermaid graph + per-entity profiles →

---

Active-mandates timeline

gantt
    title Active mandates — windows + projected close
    dateFormat YYYY-MM-DD
    axisFormat %b %Y
    todayMarker stroke-width:2,stroke:#ef4444,opacity:0.8

    section Cindy / RHG MX
    Service of process attempts        :crit, cindy_serve, 2026-04-20, 2026-06-30
    Court appearance / payment ack     :cindy_close, 2026-06-15, 2026-07-15

    section Mexican entity reorg
    RHG conversion S.A. → S. de R.L.   :rhg_conv, 2026-06-01, 2026-12-31
    Casa Moksha LLCs activation        :cm_act, 2026-06-01, 2026-12-31

    section Mita / Japan
    NEW GK formation (proposed, Tohyama):crit, gk_new, 2026-04-01, 2026-08-31
    Membership-interest transfer (US capgain review) :gk_xfer, after gk_new, 60d

    section IP
    Conley Rose §101 OA response       :crit, done, oa_resp, 2026-04-27, 2026-05-09
    CASA MOKSHA U.S. trademark filing  :tm_file, 2026-03-28, 2026-08-31

    section Birmingham (1006)
    Larry & Rick LOI → lease           :loi, 2026-04-15, 2026-09-30
    TX franchise forfeiture cure       :crit, ff_cure, 2026-05-09, 2026-06-30

    section US Tax
    Pearce 2025 prep + filing          :prep_25, 2026-05-09, 2026-10-15

---

What's actively in flight

Cindy Canto removal — Mexican payment-consignation proceeding. Service-of-process blocked at Mérida address (CSF typo); Portilla preparing motion for re-attempt. Projected close: late June 2026 if service completes. Timeline →

NEW Renfroe Holdings GK formation (proposed, not yet formed) — Tohyama Office (judicial scrivener Takeshima Tohru) is engaged to form a new GK that would take over Mita 1009 from the existing GK. ABS Partners cleared the Japan side 2026-04-30. Formation has NOT been executed — Tohyama is still waiting on Austin to provide forms + US-LLC existence cert + affidavit, and Austin is gating that on US capital-gain exposure analysis from Pearce + Kim & Rosado. As of 2026-05-10: still only ONE GK exists (the existing Renfroe Holdings GK). Communications dive →

RHG SA → S. de R.L. de C.V. conversion — downstream of Cindy removal. Casa Moksha LLC + Casa Moksha Holdings LLC will jointly own the Mexican entity post-conversion (≥2-member minimum). Entities →

Mita Garden Hills total economic cost reconciled — ¥835,355,900 (¥813.9M adjusted contract + ¥21.4M closing fees + ¥0.09M stamp duty). Funding traced through Brex API + Pinnacle correspondent flow. Reconciliation →

1006 LOI in flight + insurance renewed — "Larry & Rick" event-venue / restaurant tenant LOI (Bill Clements at TRC + Jay Halsey at eXp Realty as broker). Berkshire commercial insurance renewed at $7,575/yr 2026-05-02. Five Points narrative →

Conley Rose patent 4447-00106 §101 OA response — OVERDUE. 3-month deadline 2026-04-27 has passed; small-entity extensions accruing $94/mo. Examiner interview held ~Apr 30. Plus the new CASA MOKSHA U.S. trademark filing (CR 8049-00100, classes 039/041/043/044) waiting on Austin's responses to 5 info requests since 2026-03-28.

Pearce Bevill 2025 filing prep — 19-item agenda. Kickoff email sent 2026-05-09. Replies pending. Status →

📧 Two advisor-escalation emails drafted, awaiting Austin's review. Pearce + Kim & Rosado: 7 items including GK Form 8832, BOIR overdue, Form 3520/8938 → · Stuart Memory: Five Points TX forfeiture cure + AFR notes →

---

Browse by section

Entities

17-entity stack with standardized profiles + Mermaid hierarchy. Per-entity files cover timeline, people, vendors, finances, real assets, intercompany flows, open litigation, documents.

People

Principal, family, staff, and external counterparties (CPA, MX accountant, JP accountant, MX/UK/JP/US legal counsel, banking contacts).

Decisions

Append-only log of every substantive decision since 2026-04-18 — accounting system, intercompany framing, entity treatment, M365 connectivity, etc.

Accounting

Chart of accounts, vendor mappings, reconciliations (JME packets, Mita purchase price, Portilla billing, Five Points / 1006 / SBA narrative). Comprehensive Xero buildout scaffold tracks live org state, phases, runbooks.

Banking

Per-institution detail (Brex, Santander MXN, JPMorgan, Tokyo Star, Wells Fargo, Coinbase). Plus the Monarch-aggregated coverage map for personal channels.

Legal

Active matters — Cindy consignation, Withers London portfolio (Rodrigo / HyperRealms / Gilette), draft intercompany agreements, advisor contract gaps.

Tax

2025 filing prep agenda (19 items), Pearce Bevill thread summary, FBAR analysis, advisory tax-benefit areas, tax-strategies reference.

Open questions

Live list of unresolved items — what's awaiting documents, what's awaiting advisor input, what needs joint advisor review.

To-do

Action items partitioned by audience — for Austin, for advisors, for next session, mining playbooks for parallel sessions.

Source documents

Index of paper records on the Synology share — Mita closing docs, Casa Moksha SharePoint, JME packets, Brex history, Santander 15-month transactions.

---

Deep-dive findings (2026-05-09)

By-property deep dive

Comprehensive 2,595-line per-property profile. Mita Garden Hills, Casa Moksha, all four W Residences units (3101, 3103, 3603, 2612), Oceana 433, 1006 20th St S, three Lake Austin marina slips, Renfroe Innovation patents, plus a cross-cutting Block-21-HOA appendix. Each section covers identity, financials, documents, people, vendors, mandates, taxes, dates, open questions, and inconsistencies.

Communications deep dive

Matter-keyed mining of 10 active mandates from M365 + Gmail content (not just metadata). Surfaced the new-GK formation by Tohyama, the overdue Conley Rose §101 OA, the Berkshire insurance renewal on 1006, the active "Larry & Rick" LOI on the Birmingham building, Enrique Williams's Feb 2026 departure, and the 60-day forward calendar.

Per-property profile (template)

Standardized 17-section template for every entity profile. One file per entity at context/entities/<slug>.md. Sections: at-a-glance / status / purpose / timeline / people / vendors / finances / real assets / insurance / intercompany / litigation / documents / open questions / related entities / revision log. v1 — format will evolve.

Inconsistencies audit

44 findings across 9 categories: numbers, dates, status, entities, people, stale TBDs, closed-but-listed, implicit facts, missing cross-references. Severity-tagged. Top 10 priorities ranked at the bottom.

Document audit (Dive 7)

Paranoid, primary-sources-only verification pass. Every name, every date, every "see file at [path]" claim verified against a primary source. 491 lines. Top finding: GK Form 8832 deadline expired ~13 months ago. Plus 14 cross-source disagreements, 17 missing documents, 9 dated commitments past their deadline.

Tax + cap table audit (Dive 8)

Tax-filings matrix and cap-table matrix across all 16 entities. 721 lines. Captured 4 EINs not previously in repo, verified $3.4M federal NOL line-by-line, surfaced BOIR overdue across 4 entities, Form 3520/8938 apparent absence, Schedule B 7a question, RI 2017 Form 8832 history.

Open questions

Live list of unresolved items — what's awaiting documents, what's awaiting advisor input, what needs joint advisor review. Latest dives have surfaced ~30 new questions; the highest-leverage ones are at the top of the inconsistencies / document / tax audit docs.

Email drafts queue

Advisor-escalation emails drafted from audit findings, awaiting your review and send. Currently two open: Pearce + Kim & Rosado (7 items) and Stuart Memory (Five Points + AFR notes).

Master timeline

Single chronological view 2010 → present. 465 lines. Forward calendar for upcoming commitments. "Dates we don't know" section for unresolved-date items.

Flow of funds

Cross-source money picture: Monarch + Brex + Santander + Xero. Net worth (~$25M / $20M adjusted), top counterparties last 12 mo, 24 reconciliation items. Key finding: Xero org is essentially empty — Brex/Santander/TSB history not yet ingested.

People graph

50+ net-new individuals from email + chat + Synology mining. Cross-connection graphs across advisors / counterparties. 20 open identifications still to triage.

Monarch coverage map

What's already in Monarch (64 accounts, 22 institutions) vs. what's not (Tokyo Star Bank, Santander MXN). Practical query patterns at the bottom.

Tokyo Star Bank extraction

Five-path proposal for closing the TSB transaction-level gap. Manual CSV ingestion recommended as v1 — same pattern as JME monthly packets.

---

Claude instructions

For future Claude sessions working on this repo. This section describes the bootstrap pattern, the standing rules, and the tooling available. Read it once at the start of any new session.

Bootstrap (start of every new session)

# 1. Read these in order:
#    - CLAUDE.md (repo's standing rules — including the boundary with fo-stack)
#    - context/discovery-summary.md
#    - context/entities/README.md (Mermaid hierarchy + 17-entity index)
#    - context/people.md
#    - decisions/log.md (last 5–10 entries)
#    - todo/parallel-mining-sessions.md (paste-able mining prompts)
#    - context/deep-dive-findings-2026-05-09.md (synthesis from the 2026-05-09 dive)

# 2. Working dir + connector bootstrap:
export BW_SESSION="$(cat ~/.config/bw/session)"
cd ~/projects/renfroe-holdings

Standing rules

• Don't bold URLs. Wrapping URLs in **bold** markdown breaks tap-to-open in Austin's UI. (Saved as a memory.)
• The repo is records / data / decisions, not code. Build/platform code lives in ~/projects/fo-stack/. Don't cross the boundary; see CLAUDE.md § Repo boundary.
• Direct push to main is authorized for Austin's account. No PRs needed for this repo.
• Push frequently. Small, focused commits per finding rather than one big batch at end of session.
• Never dump verbatim email content into the repo. Paraphrase tightly. Source-tag every concrete claim (file path / mailbox query / Synology path / decision-log entry).
• Default to mcp__ollama__* for bulk text — summarization, classification, extraction. Free; runs against the homelab Ollama on compute-vm. No Anthropic spend.
• Use Explore agents for bulky read passes so synthesized findings come back without burning main context.
• Read-only by script enforcement. All inbox connectors (scripts/inboxes/*.py) are read-only — no write methods imported into the dispatch layer. Never bypass this without explicit Austin authorization.
• BW writes require confirmation. Ask before creating new Vaultwarden items or rotating values; reads are fine without a per-call ask.

Connector tooling

# Microsoft 365 (cm = Casa Moksha tenant; rfh = Renfroe Holdings tenant)
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 "/<path>"
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

# Monarch Money (read-only — accounts / txns / holdings / net-worth / cashflow)
python3 -u scripts/inboxes/monarch.py accounts
python3 -u scripts/inboxes/monarch.py txns --days 90 --search "<merchant>"
python3 -u scripts/inboxes/monarch.py holdings
python3 -u scripts/inboxes/monarch.py networth --limit 24

# Synology /volume1/cloud — read via ssh proxmox (LXC NFS gated)
ssh proxmox 'sudo find "/mnt/synology-cloud/SP (Moksha)" -maxdepth 4 -type d'
ssh proxmox 'sudo cat "/mnt/synology-cloud/<path>"'

Conventions for findings

• Write substantive output into legal/, accounting/, context/, or tax/ as appropriate. 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 surfaced.
• Add to context/master-timeline.md Forward Calendar for any new dated commitment.
• Flag anything that affects active mandates (Cindy, Pearce, JME, Mita, Conley Rose patents, 1006 LOI).
• End-of-session: commit + push, leave a clean working tree, update todo/for-next-session.md if anything's in flight.

When to spawn a parallel session

If a topic is sufficiently scoped + self-contained, paste a topic prompt from todo/parallel-mining-sessions.md into a new chat. Each topic there has its own mining prompt that's self-bootstrapping. Already dispatched: Topics 1-10 (mining); Dive 5 (per-property); Dive 6 (communications). Topics queued in the file.

Key cross-references

• context/deep-dive-findings-2026-05-09.md — single takeaway doc indexing everything else.
• context/by-property-deep-dive.md — 10-property profile.
• context/communications-deep-dive.md — 10-mandate matter-keyed mining.
• context/inconsistencies-audit.md — 44 findings ranked by severity.
• banking/monarch-coverage-map.md — what's in Monarch vs. what's not.
• banking/tokyo-star-bank-extraction.md — TSB extraction approach (Path 1: manual CSV).
• scripts/inboxes/README.md — full setup walkthrough for all four connectors (Gmail mail / Gmail calendar / M365 multi-tenant / Monarch).

---

Working notes

This site is generated from the renfroe-holdings Gitea repo. Push to main triggers a 30-second autodeploy on prod-websites; the live site rebuilds on every commit. Authentik forward-auth gates the entire site at the Traefik layer.

Sensitive details — banking IDs, SBA loan numbers, individual transaction memos — live here on purpose; the audience is Austin and any advisor he's chosen to onboard. Do not share the URL outside that audience.

---

Reading guide for AI / LLM assistants

If you're an AI assistant reading this site to help Austin (or being briefed by Austin's primary Claude session), here's how to navigate it productively.

Bootstrap order — read these first, in order

1. context/discovery-summary.md — narrative overview of the whole portfolio
2. context/contradictions.md — the structural tensions you should NOT silently smooth over
3. accounting/accounting-policy.md — 39-section canonical rulebook (read sections 16, 17, 27, 28, 29 for confidence/suspense/evidence/decision-hierarchy/Reporting-Unit framing)
4. accounting/source-of-truth-matrix.md — what Xero IS the source of truth for vs what's owned elsewhere
5. accounting/entity-tax-classification-matrix.md — every entity's lifecycle state, ownership, tax classification, advisor owner
6. accounting/exception-log.md — what's in suspense and why
7. decisions/log.md — append-only decisions of record
8. accounting/advisor-decision-register.md — where each advisor stands

Rules of engagement

• Confidence levels are real. When you see [F] (Final), [P] (Provisional), or [U] (Unknown), treat them as load-bearing. Don't upgrade [P] to [F] without a corresponding entry in accounting/advisor-decision-register.md. Don't "clean up" unresolved items by inferring an answer — that's the headline failure mode this system exists to prevent.
• Source-document references are required. Per accounting-policy §27, no transaction gets cleaned up unless the system preserves the original evidence + classification rationale + advisor uncertainty level. If you write a substantive update, cite the source.
• Decision hierarchy when sources conflict (per accounting-policy §28): executed legal documents > filed tax returns > signed financial statements > bank statements > advisor written opinions > Austin direct correction > email-thread inference > prior LLM inference. Austin direct correction overrides LLM inference silently, but if it conflicts with levels 1-5, don't silently override — log in context/contradictions.md.
• Reporting Unit ≠ Legal Entity. The Xero "Entity" tracking dimension is functionally a Reporting Unit (per §29). Most options ARE legal entities; W 3603 + Oceana 433 are personally held — they appear in management views but no operational P&L flows through them.
• JME is project-driven, not monthly. Don't ask for "monthly trial balances" — they don't exist. The repo's RHG cadence is quarterly Path A unless JME later supports monthly exports.
• The "Entity" tracking category has only two values that aren't legal entities (W 3603 + Oceana 433) plus one synthetic ("Consolidation Eliminations" — planned). Adding a third tracking category is forbidden — Xero supports max 2 tracking elements per JE line.
• No Cindy-severance line in any COA. Per Austin direct correction 2026-05-09: Cindy quit before being fired; no separation payout was issued; substantive removal grounds are illegal acts (threats / misappropriation / embezzlement). The "RNIE FINES AND CINDY PAYO" wire's PAYO portion is NOT a severance — purpose unresolved.
• Chuck Murphy is a friend, not Austin's brother. Per Austin direct correction 2026-05-09. Don't reintroduce the "brother" framing if you encounter it in older email mining.
• Only ONE GK exists today (existing Renfroe Holdings GK, Mita owner, formed 2025-01-24). A second GK is proposed, not yet formed — Tohyama Office engaged to execute formation, but Austin hasn't provided the required forms / US-LLC existence cert / affidavit, and US capital-gain exposure analysis from Pearce + Kim & Rosado is still pending before he greenlights formation. Per context/contradictions.md CON-01.
• New-GK Mita transfer: JP-side is FMV mark-to-market per Endo (ABS) 2026-04-30. US book/tax/5471/depreciation basis + gain recognition all TBD pending Pearce + Kim & Rosado. Don't post US-side FMV step-up or gain until advisor-confirmed.

Where to write findings

• NEW analysis → new file under context/ or accounting/ or tax/ or legal/
• NEW decision → append decisions/log.md
• NEW advisor position → append accounting/advisor-decision-register.md
• NEW open question → open-questions.md + cross-reference in accounting/exception-log.md if it's a transaction in suspense
• NEW contradiction → context/contradictions.md (don't try to resolve silently)
• NEW Austin ask → todo/for-austin.md or todo/austin-decision-board.md
• NEW advisor ask → todo/for-advisors.md + accounting/advisor-ask-packet-template.md if it's substantial enough to warrant a packet

Discipline rules for any Xero mutation

Every Xero-mutating action requires a migration package per xero_migrations/README.md: 1. Dry-run mode (no API writes; CSV of intended changes) 2. Pre-flight scripts/fpa/xero_backup.py snapshot, committed 3. Stable external IDs as idempotency keys (per accounting-policy §30) 4. Draft-first (ManualJournals / Bills as DRAFT; diff to Austin; promote to POSTED only after approval) 5. Post-flight snapshot, committed 6. Written approval (approval.md) from Austin 7. Rollback plan documented

Don't skip any of these, even for "small" changes. The downstream advisor work product depends on books that look clean ONLY if they're actually clean.

Pointers for specific work types

• Building / extending the Xero buildout → accounting/xero-buildout.md is the live scaffold; §3.5 indexes every companion file.
• Drafting an advisor packet → use accounting/advisor-ask-packet-template.md + drop into accounting/advisor-packets/<advisor>/<topic>-YYYY-MM-DD.md.
• Drafting a per-recipient verification site → outreach/README.md + outreach/recipient-scopes.md + drop into outreach/recipients/<recipient>.md.
• Running monthly close → accounting/xero-buildout.md §6.A runbook + scripts/fpa/xero_close_tests.py for the 16-test control battery.
• Read-only state check → python3 scripts/fpa/xero_close_tests.py + python3 scripts/fpa/xero_backup.py are both safe.

What requires Austin sign-off (don't do autonomously)

• Live Xero writes (per §32 migration discipline)
• New Traefik routes / DNS records
• Outbound emails to advisors
• Public-site publishes (especially xero-buildout.austinrenfroe.com style external shares)
• Sending verification sites to recipients (per outreach/README.md)
• Anything that would expose internal facts to a third party
• Force-pushes or destructive git operations