Inconsistencies Audit — renfroe-holdings repo¶
Built: 2026-05-09 by cross-referencing the canonical files in
context/, accounting/, banking/, tax/, legal/, decisions/,
and todo/ against the new outputs from waves 1 and 2 of this dive
(context/people-graph.md, context/master-timeline.md,
accounting/flow-of-funds.md).
Methodology: systematic read-through of the load-bearing files; grep cross-checks for counterparty names, dollar amounts, dates, ownership claims, and entity attributes; reconciliation of newly landed canonical figures (e.g. ¥835.4M Mita basis, JPY-anchored) against any older file that still cites a stale figure or "TBD/provisional."
Known findings already surfaced in earlier waves (not duplicated
here): Hunter pronoun conflict — RESOLVED 2026-05-10 by Austin direct (Hunter is male, his brother); the 2012 1120-S "her shares" reference is a typo on the source document, not the substantive ownership pronoun.; RFH Xero essentially empty; Pinnacle
¥683.18M wire never transited Brex; "OWNER CONTRIBUTION" memo trap;
Conley Rose new TM mandate (CR 8049-00100) for Casa Moksha; Casa
Moksha Property Manager hire in flight; two distinct active PLOCs at
two banks (Pinnacle + ServisFirst); Murray Brown Woolworth Term Out
date conflict (2023-02-02 vs. 2024-02-02). These are listed at the
end of accounting/flow-of-funds.md and the user prompt for this
audit.
Severity rubric: - HIGH — audit-defensibility issue, tax filing risk, or load-bearing-decision blocker (counterparty identification on a legal filing, debt amount on a balance sheet, jurisdiction/state of formation, ownership %, named-borrower status on PG'd debt). - MEDIUM — operational confusion or duplication risk; advisor would catch it in one pass but it would burn a billable hour. - LOW — cosmetic / housekeeping.
Numbers — dollar-amount / count conflicts¶
Finding 1 — Brex 3529 inflow total cited as $135,232 vs. $137,835¶
Severity: LOW
What the data says: accounting/flow-of-funds.md:206 says
"Brex Casa Moksha Dep 3529 — full history $135,232 USD inflows
across ~18 months." banking/brex.md:73 says "Full-history inflows
~$137,835 USD across ~18 months."
What the repo currently claims: Both files are independently
authoritative for the same number; banking/brex.md is the older
one and probably reflects pre-correction totals (e.g. before the
Ariella $150-net adjustment).
Sources: accounting/flow-of-funds.md:206, banking/brex.md:73.
Recommended fix: Reconcile to the line-item ledger in
accounting/casa-moksha-guest-revenue-ledger.md; pick one figure and
update both files (probably $135,232 net of the Ariella half-refund
and the Bernadette PayPal full-refund). Footnote in each file noting
the recon.
Finding 2 — Casa Moksha Dep CO DASH LLC count: 4 wires totaling $42,294 vs. $42,293.60¶
Severity: LOW
What the data says: decisions/log.md:359 (2026-05-09 entry)
states "$9,709.20 + $22,654.80 + $8,885.60 + $1,044.00 = $42,293.60"
exact, derived from the Brex API memos. banking/brex.md:78 and
context/people.md:132 both round to "$42,294" / "$42,293.60"
inconsistently.
What the repo currently claims: $42,294 (Brex), $42,293.60 (decisions log + people.md), $42,294 (flow-of-funds:210).
Sources: decisions/log.md:359, banking/brex.md:78,
context/people.md:132, accounting/flow-of-funds.md:210.
Recommended fix: Use $42,293.60 as canonical (matches the wire-
level memos); update banking/brex.md and accounting/flow-of-funds.md
totals.
Finding 3 — SBA EIDL Loan 7803 outstanding balance¶
Severity: MEDIUM
What the data says: Multiple inconsistent numbers for the
"~$1.2M" Parent SBA loan and the Woolworth EIDL principal:
- todo/for-austin.md:95 cites Austin's Sept 22, 2025 thread saying
"Woolworth $1.257mm + a separate $497,483 (just called due)".
- accounting/five-points-1006-sba-narrative.md §1, §14 reports
Loan 7803 as "~$500K" original.
- accounting/flow-of-funds.md:119 cites the Monarch manual entry
of $1,748,105 covering "Woolworth EIDL ~$500K + larger ~$1.2M".
What the repo currently claims: Loan 7803 = ~$500K original. But Austin's own Sept 22, 2025 email says Woolworth $1.257mm + $497,483.
Sources: todo/for-austin.md:95, accounting/five-points-1006-sba-narrative.md:127,
accounting/flow-of-funds.md:119, tax/pearce-bevill-thread-summary.md
(SBA/Stuart thread).
Recommended fix: Reconcile against Austin's SBA portal
screen-cap (already on todo/for-austin.md to-do list). Until then,
flag explicitly that the "$500K" figure is one of two competing
candidates (the other being the $497,483 figure that exactly matches
"$1.257mm + $497,483 = $1,754,483" ≈ Monarch's $1,748,105).
Finding 4 — Brex 5803 lifetime txn count: 104 vs ~104¶
Severity: LOW
What the data says: banking/brex.md:35 shows 104. accounting/five-points-1006-sba-narrative.md:918 says "~104 transactions through Apr 16, 2026" — same number, but the latter file's expansion §18.1 (Inflows) is missing dollar totals because Brex CSV "not committed to repo." Yet banking/brex.md and source-data/brex/2026-04-19-full-history-analysis.md clearly DO have dollar totals for 5803.
What the repo currently claims: Five-points-1006 narrative sub-file says transaction-level amounts aren't in repo.
Sources: accounting/five-points-1006-sba-narrative.md:929-933
("No public dollar amounts visible in Brex alert subjects; full
transaction-level amounts are in Austin's local Brex CSV not committed
to repo"); source-data/brex/2026-04-19-full-history-analysis.md
(committed full-history file).
Recommended fix: Update five-points-1006-sba-narrative.md §18.1
to point at source-data/brex/2026-04-19-full-history-analysis.md
for dollar totals; the claim that they're "not committed" is wrong.
Finding 5 — Mita TSB mortgage status framing across files¶
Severity: HIGH
What the data says: context/entities.md § Mita acquisition step
13, accounting/mita-purchase-price-reconciliation.md, and
decisions/log.md 2026-05-08 all establish the ¥835,355,900 paid
to seller + ¥780M TSB advance 2025-07-28 as canonical.
What the repo currently claims: banking/tokyo-star-bank.md:19
still says "Purchase-price figure is provisional — ¥760M sales-
contract base + property changes per Special Changes Addendum yet to
be fully reconciled; do not cite a hard dollar figure for Mita
until that work is done."
Sources: authoritative — context/entities.md:138-149,
accounting/mita-purchase-price-reconciliation.md,
decisions/log.md:305-321 (2026-05-08 entry); stale —
banking/tokyo-star-bank.md:17-22.
Recommended fix: Rewrite banking/tokyo-star-bank.md § "Mita
Garden Hills 1009 — mortgage" to lock in the ¥835.4M / ¥780M
figures and link to the reconciliation memo. Remove the "do not cite
a hard dollar figure" sentence.
Finding 6 — RFH "WF 6248" inflow dollar amount¶
Severity: LOW
What the data says: banking/brex.md:60 lists "Wells Fargo
CHECKING 6248 (personal) | 1 | $45,000". accounting/flow-of-funds.md:175
says "WF 6248 | 1 | $45,000 | Austin personal (Nov 8, 2024
transfer)". banking/wells-fargo-personal.md:13 cites the same
$45,000 transfer.
What the repo currently claims: Internally consistent, but
banking/wells-fargo-personal.md does NOT call out that the WF 6248
balance is also currently the destination for the ¥152M Mita refund
(context/entities.md Mita step 5, step 15) — which would be a
six-figure inbound flow. That's a missing cross-reference, not a
number conflict.
Sources: banking/wells-fargo-personal.md (no Mita refund mention);
context/entities.md:158, 168 (refund flow); todo/for-austin.md:13
(WF 6248 May–Sept 2025 statements outstanding).
Recommended fix: Add a "Pending inflow" section to
banking/wells-fargo-personal.md calling out the expected ¥151,909,800
(~$1.02M USD) refund and the open question on its actual deposit date.
This isn't a conflict per se but the file reads as if WF 6248 is
$22K cash and $45K of one-off activity — significantly understating
its role in the Mita financing chain.
Finding 7 — Cindy share / capital stake in RHG: "1%" implied vs $25 USD economic¶
Severity: MEDIUM
What the data says: context/entities.md:75 says RHG
ownership "(as of 2024 5471 filing): 99% Austin personally" —
implies the other 1% is held by Cindy. legal/cindy-consignation-timeline.md:99
says "Cindy's actual economic stake is ~$25 USD (capital fijo
MXN $500 at current FX). The 46.7M MXN capital variable is 100%
Austin per JME's 2nd packet."
What the repo currently claims: Two coexisting framings — Austin 99% / Cindy 1% (entities.md) vs. Austin 100% of variable + Cindy MXN $500 fixed-capital token (cindy timeline). These are NOT consistent: 99% / 1% suggests proportional-membership arithmetic; the real picture per JME's 2nd packet is that Austin holds 100% of variable capital and Cindy's MXN $500 fixed-capital is the fractional piece with negligible economics.
Sources: context/entities.md:75, legal/cindy-consignation-timeline.md:99-101,
tax/fbar-analysis.md:16-18 ("99% owner of RHG → financial interest").
Recommended fix: Update context/entities.md:75 to reflect the
two-tier picture: "100% of variable capital (the economically
meaningful layer) + 0% of fixed capital (Cindy holds MXN $500 = ~$25
USD as the capital fijo, being removed via Mexican payment-consignation
proceeding). On Form 5471 ownership-percentage purposes the line is
99%/1% but the economic substance is Austin 100%." Cross-reference
to the cindy-consignation-timeline file. This matters for 5471
reporting — the percentages on the form should be sourced from a
single reasoned position.
Finding 8 — "Five Points BHM" — entity name, formation state, and forfeiture jurisdiction conflict¶
Severity: HIGH
What the data says: tax/pearce-bevill-thread-summary.md:43, 150-151
says "Five PTS BHM is a TX LLC formed Oct 2024 holding the 1006 /
Woolworth building. Notice of Forfeiture (TX)" — implying the
forfeiture is TX side. But decisions/log.md:301 (2026-05-08 entry)
says "Five Points BHM Notice of Forfeiture of Right to Transact
Business filed by Alabama SoS Nov 12 2025." accounting/five-points-1006-sba-narrative.md:338-344
says same — "Alabama Secretary of State filed a notice of
forfeiture against Five Points BHM Holdings, LLC." The recorded
ServisFirst Assignment of Mortgage (Dec 23, 2024) lists Five Points
BHM Holdings, LLC's address as 210 Lavaca Street #3101, Austin TX
78701 (accounting/five-points-1006-sba-narrative.md:167, 654).
What the repo currently claims: Two conflicting jurisdictions (TX for formation per Pearce; AL for forfeiture per decisions log). Possibilities: (a) FP BHM is TX-formed and foreign-qualified in AL (would explain both — TX formation, AL ops, AL-side forfeiture for missing AL annual qualification report); (b) one of the two file sources is wrong on jurisdiction. Also: legal name appears as both "Five Points BHM LLC" (entities.md throughout) and "Five Points BHM Holdings, LLC" (decisions log + Walding-recorded paperwork + forfeiture filing). The recorded paperwork is the more authoritative.
Sources: decisions/log.md:301 (AL SoS), tax/pearce-bevill-thread-summary.md:43, 150-151, 207
(TX), accounting/five-points-1006-sba-narrative.md:167, 338-344, 654
(both — name "Holdings" + AL forfeiture), context/entities.md:233
(name "Five Points BHM LLC", state not stated), banking/brex.md:25
("Five Pts Holdings: Ops").
Recommended fix: This needs Skinner Legal / Pearce confirmation
of (a) state of formation, (b) foreign qualification states, ©
exact legal name — then update context/entities.md Five Points BHM
section with the canonical name, formation state, AL qualification
status, and franchise-tax / annual-report obligations in BOTH states.
HIGH because the entity owns a $5M+ commercial building in Birmingham;
operating with an in-doubt right-to-transact in either jurisdiction
is a real liability exposure.
Finding 9 — banking/jpmorgan-chase.md is internally misleading about RFH's relationship with JPM¶
Severity: MEDIUM
What the data says: banking/brex.md:149 clarifies: "Brex
routes USD wires through JPMorgan Chase as the underlying settlement
bank, which is why the Santander memo shows JPM as the originator."
The "8 of 8 Santander JP Morgan deposits matched 1:1 to a Brex
outbound wire" reconciliation in banking/brex.md:130-149 proves
the wires ORIGINATE in Brex sub-accounts, with JPM only the
correspondent.
What the repo currently claims: banking/jpmorgan-chase.md:1-32
is titled "Banking — JPMorgan Chase (Renfroe Family Holdings, US)"
and frames RFH as a JPM customer, complete with "branch 014694",
"Outbound to Santander MXN" wire schedule, and an open-item list
asking for "JPMorgan Chase account statements for the same 15-month
period." This is misleading — Brex IS the customer (not RFH), and
"branch 014694" is the Brex/JPM correspondent routing.
Sources: banking/brex.md:149, banking/jpmorgan-chase.md:1-38,
accounting/flow-of-funds.md:434-442 (more accurately notes "JPM
activity only from Santander receiving side").
Recommended fix: Either delete banking/jpmorgan-chase.md and
fold any remaining content into banking/brex.md, or rewrite it to
say "RFH does not directly hold a JPM business account; this file
documents JPM's role as Brex's correspondent settlement bank." The
"Provide JPMorgan Chase account statements" open item is unactionable
because there is no JPM account to pull statements from on RFH's
side. (There may be a separate Austin-personal JPM checking; that's a
different account and a different file.)
Finding 10 — banking/brex.md open-item "close 0926 after data pull"¶
Severity: HIGH
What the data says: decisions/log.md:285-291 (2026-05-08 entry)
explicitly says: "Brex 0926 (1006 defunct, zero balance) must NOT
be closed, contrary to the earlier note in banking/brex.md /
Brex transaction analysis." Same in context/entities.md:344 ("Do
NOT close the Brex 0926 account or dissolve the LLC").
What the repo currently claims: banking/brex.md:26 still says:
"0926 | 1006 20th St LLC (Defunct) | no | Bankrupt predecessor;
**close after full data pull**"
Sources: banking/brex.md:26, decisions/log.md:285-291,
accounting/five-points-1006-sba-narrative.md:240-247, context/entities.md:344.
Recommended fix: Edit banking/brex.md:26 to "DO NOT CLOSE
— Sep 2025 Chuck/Stuart analysis: closing would crystallize SBA debt
onto guarantors. See decisions/log.md 2026-05-08." HIGH severity
because this is the kind of stale instruction that gets followed by
accident on a later cleanup pass.
Dates — same event dated differently¶
Finding 11 — RHG SA de CV incorporation date — 2023-02-02 vs. 2025-02-02¶
Severity: MEDIUM
What the data says: context/entities.md:70 and Synology /
RFC RHG230202Q53 confirm 2023-02-02 (the RFC literally encodes
the date: RHG-230202). context/master-timeline.md:226 (2025 Q1
section) erroneously dates "Renfroe Hospitality Group SA de CV
incorporated" as 2025-02-02 with a parenthetical "(NOTE: prior
actual incorporation was 2023-02-02 per RHG entry; verify)."
What the repo currently claims: context/master-timeline.md:226
has 2025-02-02 as a placeholder entry; the canonical date is
2023-02-02 per context/entities.md.
Sources: context/entities.md:70-71, context/master-timeline.md:226,
context/master-timeline.md:321 (correct 2023 entry).
Recommended fix: Delete the erroneous 2025-02-02 row in
master-timeline.md. The 2023-02-02 row at line 321 is correct.
Finding 12 — Brex Primary opening date — Oct 18 2024 vs. "Account opened Oct 18 2024" but other places say "earlier"¶
Severity: LOW
What the data says: banking/brex.md:7 says "Account opened:
October 18, 2024". decisions/log.md:268 (2026-04-22 Moksha rollup)
says "Brex account opened Oct 18, 2024 anyway, so 'pre-2024' is
mostly moot." But decisions/log.md:55-58 (2026-04-19 Brex backfill)
says "Pull Brex transaction history to Jan 1, 2024" — implying
expectation of pre-Oct-2024 activity.
What the repo currently claims: Account-opening date is internally consistent (Oct 18, 2024). The Jan 1, 2024 backfill plan is therefore moot for Brex.
Sources: banking/brex.md:7, decisions/log.md:55-58, 268.
Recommended fix: Update decisions/log.md 2026-04-19 backfill
entry to note that "Jan 1, 2024 → Oct 18, 2024 is empty for Brex
because the account didn't exist; CSV import is Oct 18, 2024 to date."
LOW because the field-level effect is "import nothing for the empty
window," not a real reconciliation gap.
Finding 13 — JME engagement origin — 2024-10-08 vs. "Oct 2024"¶
Severity: LOW
What the data says: context/people.md:165 says "2024-10-08
(Alex Snider's first email to Giovanni; intro received via Iván
Guerrero of Portilla, Ruy-Díaz y Aguilar)."
accounting/jme-deliverable-status.md (referenced) and context/master-timeline.md:270
align on 2024-10-08.
What the repo currently claims: Internally consistent. Listed here only for completeness — no conflict found.
Sources: context/people.md:165, context/master-timeline.md:270.
Recommended fix: None. (Verified consistent; left in this audit as a checkpoint that the date is solid.)
Finding 14 — Stuart Memory parents↔Austin AFR note: "Sep 9, 2025" vs. "Sep 2025"¶
Severity: LOW
What the data says: accounting/five-points-1006-sba-narrative.md:174-178
says specifically Sep 9, 2025 for Austin's email to Stuart; same
in context/master-timeline.md:164 ("2025-09-09"). context/people.md:24
says "As of Sep 9, 2025, Stuart Memory was looking for the
promissory note in his files." All three consistent at the day level.
What the repo currently claims: Internally consistent; the "Sep 2025" framing in some files is just an abbreviation.
Sources: accounting/five-points-1006-sba-narrative.md:174-178,
context/master-timeline.md:164, context/people.md:24.
Recommended fix: None. (Verified.)
Status — file A says "active", file B says "closed"¶
Finding 15 — banking/brex.md has CO DASH LLC as "Unknown — Austin to identify"¶
Severity: MEDIUM
What the data says: decisions/log.md:357-361 (2026-05-09
entry) and open-questions.md:73-86 (Q14, marked CLOSED
2026-05-09) confirm CO DASH LLC = Brian Begin "Hypnotic Visions"
retreat (Jan 12–21 2025) via Coworking Tulum. Wire-level memos
from Brex API closed the question.
What the repo currently claims: banking/brex.md:78 still says
"CO DASH LLC | 4 | $42,294 | Unknown — Austin to identify" and
banking/brex.md:88 repeats "CO DASH LLC — four payments
totaling $42K. Booking platform? Direct corporate client? Retreat
host? — Austin to identify."
Sources: decisions/log.md:357-361, open-questions.md:73-86,
banking/brex.md:78, 88.
Recommended fix: Update banking/brex.md:78, 88 to reflect the
2026-05-09 resolution: "RESOLVED 2026-05-09 (Brex API memo mining):
Brian Begin's 'Hypnotic Visions' retreat (Jan 12–21 2025) via
Coworking Tulum, payment vehicle = Mercury Bank. See
accounting/casa-moksha-guest-revenue-ledger.md." Same for the
"Open items" line. MEDIUM because future reconciliation work would
either re-open the question or work from the stale framing.
Finding 16 — Q9 PFIC analysis status¶
Severity: MEDIUM
What the data says: tax/2025-filing-prep.md and the wave-1
findings have PFIC analysis as Pearce/specialist work. Pearce thread
summary says "ABS Partners SOW finalized via DocuSign 2026-03-01"
(accounting/mita-deep-dive.md, context/master-timeline.md:83)
— meaning the JP-side accountant is engaged, which unlocks PFIC
work.
What the repo currently claims: open-questions.md:52-54 Q9
("PFIC analysis for GK") is still open as if no engagement work has
happened. tax/2025-filing-prep.md has it as item #2 still open.
Sources: open-questions.md:52-54, tax/2025-filing-prep.md (item
2), decisions/log.md (no PFIC-resolution entry exists yet).
Recommended fix: Add a "blocked-on" sentence to Q9 noting the ABS Partners engagement signed 2026-03-01 — it's still open but the gating constraint has shifted from "no JP-side accountant engaged" to "ABS Partners + Pearce coordination on the PFIC trade-or-business defense." LOW-MEDIUM because the open-question is still genuinely open; the framing is just stale.
Finding 17 — tax/2025-filing-prep.md line 43 still asks "Has Form 8832 been filed for RHG (Mexican S. de C.V.)?"¶
Severity: MEDIUM
What the data says: Per Nick Rosado (Jan 27 2025, captured in
tax/pearce-bevill-thread-summary.md:81): "Mexican S.A. de C.V.
is a per se corporation (cannot flow-through). Sociedad de
Responsabilidad Limitada de C.V. (S. de R.L. de C.V.) is NOT per se
→ can elect 8832." Therefore Form 8832 is not available for the
SA period; the question is only operative for the post-conversion
S. de R.L. de C.V. period.
What the repo currently claims: tax/2025-filing-prep.md:43
("Has Form 8832 been filed for Renfroe Hospitality Group (Mexican
S. de C.V.)?") is technically asking about a form that can't be
filed in the SA period. The question is functionally moot for the SA
period and the active form of the question is "is 8832 ready to file
upon S. de R.L. de C.V. conversion completion?"
Sources: tax/pearce-bevill-thread-summary.md:81,
tax/2025-filing-prep.md:38-44, 200-201.
Recommended fix: Rewrite tax/2025-filing-prep.md:43 to:
"RHG SA de CV — 8832 not available (SA per se corp). Question
deferred until S. de R.L. de C.V. conversion completes; then 8832
within 75 days of conversion." Pair with line 50 (which already
addresses the conversion).
Entities — wrong owner / jurisdiction / classification claimed¶
Finding 18 — Renfroe Innovation owner — "Austin personally" vs implication that RFH owns it¶
Severity: HIGH
What the data says: decisions/log.md:333 (2026-05-08 entry)
explicitly: "RI is owned by Austin personally, not by RFH."
context/entities.md:295 confirms: "Owner: Austin Renfroe
personally, sole member. Not a subsidiary of Renfroe Family
Holdings — RI sits parallel to RFH, not under it."
What the repo currently claims: context/entities.md:18-22
ASCII-art structure diagram shows Renfroe Innovation as a sub-LLC
under Renfroe Family Holdings (in the row of W 3101, ATX Marine,
etc.). Visually contradicts the verbal text 250+ lines below in the
same file.
Sources: context/entities.md:18-22 (diagram), context/entities.md:294-296
(text), decisions/log.md:333, context/renfroe-innovation-scope.md.
Recommended fix: Update the structure diagram in
context/entities.md:6-44 to show Renfroe Innovation outside the
RFH sub-LLC tree, parallel to RFH (the same way Oceana 433, W 3603,
W 2612 are shown as personally held). Add a "Note: RI is personally
held; transfer-into-RFH evaluation pending Pearce/Kim & Rosado" line.
HIGH because this is the kind of diagram that gets pasted into
external decks / advisor briefings.
Finding 19 — RHG ownership "may shift to Renfroe Family Holdings"¶
Severity: HIGH
What the data says: Per Austin (tax/2025-filing-prep.md,
todo/for-austin.md:144, legal/cindy-consignation-timeline.md:93-95)
and the canonical resolution in decisions/log.md, post-conversion
ownership of RHG (S. de R.L. de C.V.) goes to Casa Moksha LLC +
Casa Moksha Holdings LLC (the two Texas LLCs formed Oct 2025
specifically to satisfy the two-member minimum). NOT to RFH.
What the repo currently claims: context/entities.md:75 says
"Ownership (as of 2024 5471 filing): 99% Austin personally. Needs
confirmation post-conversion; may shift to Renfroe Family Holdings."
This wording is stale — the post-conversion answer is now known to
be the CM LLC pair, not RFH.
Sources: context/entities.md:75, todo/for-austin.md:144,
legal/cindy-consignation-timeline.md:93-95,
context/entities.md:99-113 (the actual CM LLC + CMH LLC entries).
Recommended fix: Edit context/entities.md:75 to: "Ownership
(as of 2024 5471 filing): 99% Austin personally + 1% Cindy Canto
(consignation in progress). Post-conversion (2026 expected):
Casa Moksha LLC + Casa Moksha Holdings LLC (TX, two-member RFH-
subsidiary pair) — see entries below." HIGH because Form 5471 ownership
percentages are filed-on-paper figures that need a single canonical
position.
Finding 20 — Renfroe Innovation post-2017 federal tax classification¶
Severity: HIGH
What the data says: context/entities.md:299-312 and
context/renfroe-innovation-scope.md document the open question:
"Post-2017-LLC-conversion classification is TBD — defaults to
disregarded SMLLC absent a Form 8832 election to maintain corporate
status, in which case the S-election terminated by operation of law."
Pearce + Kim & Rosado have been asked to confirm.
What the repo currently claims: decisions/log.md:122 (2025-12-06
entry referenced indirectly) per context/master-timeline.md:122
says "Kim & Rosado (Anthony Kim) confirms Renfroe Innovation
federal tax classification carries over under §368(a)(1)(F) 'mere
change'." That's about the AL→TX conversion, not the 2017 Inc→LLC
conversion. The two are different. The 2017 question is still open
per context/entities.md:299-312.
Sources: context/master-timeline.md:122, context/entities.md:299-312,
context/renfroe-innovation-scope.md (full scoping).
Recommended fix: Add a sentence to the 2025-12-06 master-timeline row: "(NOTE: §368(a)(1)(F) ruling covers the 2025 AL→TX leg only; the 2017 Inc→LLC classification question remains open.)" And cross- link the entities.md entry. HIGH because conflating the two conversions could lead to a 2017-era S-election-termination issue being missed.
People — wrong name / email / role¶
Finding 21 — accounting/five-points-1006-sba-narrative.md "Don Buck" reference¶
Severity: MEDIUM
What the data says: accounting/five-points-1006-sba-narrative.md:341
says "Don Buck at Pearce Bevill weighed in same day" and §16.3
explicitly notes the correction: "Daisy B. Buck, CPA ... NOT 'Don
Buck' as I had it in the prior pass." Also context/people.md:97
("Earlier note in this file said 'Don Buck' — corrected 2026-05-09;
same email, the actual name is Daisy.")
What the repo currently claims: The file contains BOTH the correction (§16) AND an uncorrected "Don Buck" reference (§7, line 341). Internal inconsistency within the same file.
Sources: accounting/five-points-1006-sba-narrative.md:341 (stale),
accounting/five-points-1006-sba-narrative.md:794-796 (correction),
context/people.md:97.
Recommended fix: Edit accounting/five-points-1006-sba-narrative.md:341
to "Daisy Buck at Pearce Bevill" — the §16.3 correction was added
later but the earlier reference wasn't updated.
Finding 22 — Hunter pronoun conflict — RESOLVED 2026-05-10¶
Resolution: Austin direct correction 2026-05-10: Hunter is male, his brother. The 2012 1120-S "her shares" reference in Synology is a typo on the source 1120-S form, not Hunter's actual gender. All repo references swept on 2026-05-10 to consistently use he/him/his and brother. Mark Finding 22 RESOLVED.
Finding 22 (original) — Hunter pronoun conflict spread across more files than the prompt called out¶
Severity: HIGH (already known but expanded scope)
What the data says: Per the user's prompt this was already
surfaced. New finding: the conflict is in context/entities.md
twice in the same file — line 252 ("Austin's brother Hunter") vs.
line 296 ("his brother Hunter H. Renfroe"). Plus master-timeline,
people.md, people-graph, RI-scope, RI-historical-IP-spend, five-points-1006,
and decisions log all have one or the other. The 2012 Form 1120-S
"her shares" is the original-document evidence; Synology
Renfroe Innovation/Formation/Assignment of Shares by Hunter to
Austin.pdf (2014-04-01) presumably also uses pronouns.
What the repo currently claims: Eight+ separate references — sometimes "his sister", sometimes "his brother", sometimes "Austin's brother Hunter", sometimes the legal-formation-doc-derived "Hunter H. Renfroe" (gender-neutral).
Sources: context/entities.md:252, 296, 302, context/people.md:26-27,
context/people-graph.md:222-239, 632, context/master-timeline.md:288, 340, 379,
accounting/five-points-1006-sba-narrative.md:16, 47, 99, 372, 511,
accounting/renfroe-innovation-historical-ip-spend.md (per people-graph.md:226),
decisions/log.md:333 ("Hunter assigned her shares").
Recommended fix: Once Austin confirms pronouns: do a single
repo-wide pass to normalize — pick one set and apply globally,
including the legal-doc references where applicable. Add a one-line
note to context/people.md calling out the alias for legal-filing
clarity (the SBA loan PG and the 2014 share assignment both reference
"Hunter H. Renfroe" — that name needs to match exactly across SBA
correspondence, foreclosure recording, and any future loan workout
papers). HIGH per user's prompt.
Finding 23 — Withers London — accounting/five-points-1006-sba-narrative.md:8.cast lists Stuart Memory but not the Memory Legal cross-link¶
Severity: LOW
What the data says: Stuart Memory is at "Memory Memory & Causby,
LLP" (legal/, context/people.md:99). Some files refer to "Memory
Legal" (shorthand), some to the full firm name. The shorthand is fine
once a glossary line connects them.
What the repo currently claims: No conflict — just inconsistent
shorthand. The full firm name "Memory Memory & Causby, LLP" is in
context/people.md and accounting/five-points-1006-sba-narrative.md.
Sources: context/people.md:99, accounting/five-points-1006-sba-narrative.md
(both forms used).
Recommended fix: Add a line in context/people.md Memory Legal
entry: "Often referred to as 'Memory Legal' as shorthand." LOW.
Finding 24 — Chuck Murphy "Austin's brother (?)" — RESOLVED 2026-05-09¶
Severity: RESOLVED (was MEDIUM)
Resolution: Austin confirmed directly on 2026-05-09 that Chuck is
a friend, not Austin's brother, and is no longer running RFH
family-office operations. All "brother" framings in context/people.md,
context/people-graph.md, and accounting/five-points-1006-sba-narrative.md
have been updated to "friend" with the historical role-window noted but
clearly closed. New decisions-log entry on 2026-05-09 supersedes the
2026-05-08 Chuck/Waterloo handoff entry.
What the data said (pre-resolution): context/people.md:35 had
"brother (per RFH-tenant mail context — verify with Austin)";
context/people-graph.md:212-220, 633 flagged it as TBD;
accounting/five-points-1006-sba-narrative.md:62, 221, 375 had asserted
"Austin's brother" in three places without the question mark — those
were the over-confident framings that the user-facing correction
specifically called out.
Stale "TBD" / "open" items the data has actually answered¶
Finding 25 — open-questions.md Q15 NVIO unknown — should also note Q14, Q16, Q17, Q17a, Q17d are CLOSED¶
Severity: LOW
What the data says: open-questions.md correctly marks Q14, Q16,
Q17, Q17d as CLOSED. Q17a still open. Q17b open. Q17c soft-closed
("most likely never confirmed"). Q15 still genuinely open.
What the repo currently claims: Internally consistent. Listed here as a checkpoint — open-questions.md is well-maintained.
Sources: open-questions.md.
Recommended fix: None. Verified.
Finding 26 — banking/brex.md Open items ("CO DASH LLC — Austin to identify"; "Revenue reconciliation against RHG's books")¶
Severity: MEDIUM
What the data says: CO DASH closed (Finding 15). The "Revenue reconciliation against RHG's books — do these totals show up as revenue in RHG's Mexican books?" question is now partly answered — JME's 2nd packet (delivered 2026-05-08) brings the multi-year FS bundle 2023–2025 to repo, which can be diffed against the Brex 3529 totals.
What the repo currently claims: banking/brex.md:88-89 open
items still framed as fully open — they're not.
Sources: banking/brex.md:88-89,
accounting/casa-moksha-guest-revenue-ledger.md,
accounting/jme-deliverable-status.md, decisions/log.md 2026-05-08
JME 2nd packet entry.
Recommended fix: Update both bullets to point at the closed findings + the JME-2nd-packet diff work that's now possible.
Finding 27 — banking/wells-fargo-personal.md Open items still says "extract not run"¶
Severity: LOW
What the data says: accounting/flow-of-funds.md:447 confirms
"Now solved access-wise (Monarch covers 6248) but the txn-level
extraction hasn't run." The Monarch live txns call was rate-limited
2026-05-09 per accounting/flow-of-funds.md:25, 760. Genuine open
item, but the framing could note the access status.
What the repo currently claims: banking/wells-fargo-personal.md:28-30
says "Pull Wells Fargo 6248 statements" without noting that Monarch
already covers 6248 access-wise; just the extraction hasn't been
performed.
Sources: banking/wells-fargo-personal.md:28-30,
accounting/flow-of-funds.md:447, 760.
Recommended fix: Refine the bullet to "Run Monarch txn extraction for WF 6248 (access already covered; Monarch acct ID 163910167476496396; rate-limited 2026-05-09, retry when clear)."
Finding 28 — open-questions.md Q18 (intercompany services agreement) — partially answered¶
Severity: LOW
What the data says: decisions/log.md:48-53 (2026-04-19 entry)
locked in the substance ("intercompany settlements, not capital
contributions"); legal/intercompany-services-agreement-draft.md and
legal/rfh-gk-treasury-framework-draft.md are draft framework docs.
What's still open is the paper (signed agreement) — not the
substance.
What the repo currently claims: Q18 is open as if framework is also undecided.
Sources: open-questions.md:158-162, decisions/log.md:48-53,
legal/intercompany-services-agreement-draft.md,
legal/rfh-gk-treasury-framework-draft.md.
Recommended fix: Refine Q18: "Substance settled (per 2026-04-19 decision); paper still pending counsel review and signature."
Closed-but-still-listed items¶
Finding 29 — todo/for-austin.md "CO DASH LLC" / "Richard Rosenblum" / "Secluded Serenity, LLC" / "Ariella S Laden" all closed¶
Severity: LOW
What the data says: todo/for-austin.md:190-195 correctly marks
these CLOSED with [x]. No conflict.
What the repo currently claims: Verified.
Sources: todo/for-austin.md:190-195.
Recommended fix: None. Well-maintained.
Finding 30 — accounting/flow-of-funds.md Section 6 item #12 "CO DASH LLC vs Brian Begin's vehicle" — actually closed, listed open¶
Severity: LOW
What the data says: decisions/log.md:357-361 closed CO DASH;
open-questions.md Q14 closed; accounting/casa-moksha-guest-revenue-ledger.md
has the resolution.
What the repo currently claims: accounting/flow-of-funds.md:751
still lists open item 12: "CO DASH LLC vs Brian Begin's vehicle vs.
retreat-coordinator's vehicle — confirmed Brian Begin substance,
but legal entity ownership unclear."
Sources: accounting/flow-of-funds.md:751 (open),
decisions/log.md:357-361 (closed), open-questions.md:73-86
(closed).
Recommended fix: Edit row #12 in flow-of-funds.md Section 6 table: "Sub-question only — substance closed (Brian Begin retreat); question is whether CO DASH LLC is Brian's own LLC or his coordinator's. Doesn't affect accounting."
Implicit facts the repo doesn't explicitly state¶
Finding 31 — Brex Primary inflow $4.44M is ~3.4× the Brex 3529 lifetime guest inflow ($135K)¶
Severity: LOW
What the data says: accounting/flow-of-funds.md:170-180 shows
$4.44M Austin personal contributions over 18 months — this dwarfs
all RFH-substance-revenue (RHG guest revenue $135K + W 3101 sweep
$1.23M + GK sweep $1.16M + Treasury sweeps $0.54M). Austin's
personal capital is the dominant funding rail for the entire entity
stack. This is implicit but not called out as such anywhere.
What the repo currently claims: accounting/flow-of-funds.md has
the data but doesn't flag the cash-burn / capital-call frequency.
flow-of-funds.md:589 notes "Austin's $4.44M of contributions to
RFH is what makes the rest of the stack go" — close, but doesn't
quantify run rate or surface a "runway / cash needs" framing.
Sources: accounting/flow-of-funds.md:170-180, 588-589.
Recommended fix: Add a "Cash needs / capital cadence"
subsection to accounting/flow-of-funds.md — at $4.44M / 18 mo =
$246K/mo average, with lumpy flow events (the $1.05M Apr 2 2025 Mita
contribution being the biggest single tick), this is a real ongoing
cash-call pattern that deserves explicit quantification for Austin's
own forecasting. LOW because it's implicit-but-derivable from the
data already in the file.
Finding 32 — Austin Marine and Renfroe Marine are "low-activity" but Renfroe Marine has 7 txns and inbound to Primary¶
Severity: LOW
What the data says: banking/brex.md:32 shows Austin Marine
9975 has only 2 lifetime transactions; Renfroe Marine 3161 has 7
transactions including $17,496 swept to Primary across 3 txns
(banking/brex.md:62, accounting/flow-of-funds.md:178). Renfroe
Marine has revenue activity (the sweeps) but context/entities.md:228
just says "sublicensed; small magnitude."
What the repo currently claims: Internally consistent but under-described — the $17,496 in sweeps is meaningful for Schedule E characterization (rental income on dock-slip lease).
Sources: banking/brex.md:32, 62, accounting/flow-of-funds.md:178, 354,
context/entities.md:226-231.
Recommended fix: Add a "Notable activity" line to
context/entities.md Renfroe Marine entry: "$17,496 inbound to
Primary across 3 sweeps over 18 months — small but real sublicense
income to confirm against partner agreement."
Finding 33 — Casa Moksha M365 staff usage — [email protected] is a separate live mailbox¶
Severity: LOW
What the data says: context/people-graph.md:300-305 says
"[email protected], [email protected], [email protected],
and [email protected] are all live mailboxes."
What the repo currently claims: context/people.md:11 lists
Austin's email as [email protected] only. There's no
acknowledgement that Austin operates from at least 4 distinct
mailboxes ([email protected] + [email protected] +
[email protected] + [email protected]).
Sources: context/people.md:11, context/people-graph.md:441-444
(this is in the canonical updated index but not in people.md),
context/people-graph.md:300-305.
Recommended fix: Update context/people.md Austin entry to list
all four mailboxes (per people-graph.md:441-444). MEDIUM in
operational terms (advisor cc'ing the wrong mailbox could miss key
correspondence) but LOW per the rubric.
Finding 34 — Withers London matter file numbers vs. £3,767 final invoice¶
Severity: LOW
What the data says: context/people-graph.md:341-356 references
"London matter file 3122025 (current, HypeRealms) and the now-closed
3122039/3122043 (Rodrigo)." The £3,767.20 final invoice was issued
2025-09-24 (Rodrigo matter close) and chased through 2025-12-08 by
Daniel Williams, paid Feb 2026.
What the repo currently claims: No conflict surfaced.
Sources: context/people-graph.md:341-356, legal/withers-london-portfolio.md,
context/master-timeline.md:158, 121 (2025-09-24, 2025-12-08 entries).
Recommended fix: None. Verified.
Missing cross-references¶
Finding 35 — context/entities.md Casa Moksha entry doesn't reference the new TM mandate (CR 8049-00100)¶
Severity: MEDIUM (already flagged in user prompt; expanded here)
What the data says: context/people-graph.md:40 says Conley Rose
"also handles CR File 8049-00100 'Casa Moksha in the U.S.' (a
separate IP/trademark file for the Casa Moksha brand)."
What the repo currently claims: context/entities.md Casa Moksha
LLC entry (line 99-105) does NOT reference the trademark file. Casa
Moksha trademark protection is a real value-driver for the entity;
should be in the entity scoping.
Sources: context/entities.md:99-105, context/people-graph.md:40, 383.
Recommended fix: Add an "Active IP" subsection to the Casa Moksha LLC entry: "Trademark prosecution: Conley Rose CR File 8049-00100 ('Casa Moksha in the U.S.') — separate IP file for the brand, distinct from RI matter 4447." Same on the RHG entity entry (since RHG is the operating entity using the brand).
Finding 36 — banking/wells-fargo-personal.md doesn't link to Mita refund ¥151,909,800 destination¶
Severity: MEDIUM (cross-ref of Finding 6)
Sources: banking/wells-fargo-personal.md,
context/entities.md:158, 168, accounting/mita-purchase-price-reconciliation.md,
todo/for-austin.md:13.
Recommended fix: Add explicit cross-reference. See Finding 6.
Finding 37 — banking/tokyo-star-bank.md doesn't link to the Mita reconciliation memo¶
Severity: HIGH (cross-ref of Finding 5)
Sources: banking/tokyo-star-bank.md,
accounting/mita-purchase-price-reconciliation.md, decisions/log.md:305-321.
Recommended fix: See Finding 5. Adding the cross-reference is part of the same fix.
Finding 38 — accounting/afr-loan-amortization-template.md not yet updated with two-level loan correction¶
Severity: HIGH
What the data says: accounting/five-points-1006-sba-narrative.md:697-707
explicitly: "The AFR / §7872 compliance work in
accounting/afr-loan-amortization-template.md applies to the
parents↔Austin loan, NOT the parents↔Five-Points loan the template
describes. Action item: update the template's 'Borrower' row from
'Five Points BHM LLC' to 'Austin Renfroe (personally)'." Same
correction in context/entities.md:238-241 and decisions/log.md
2026-05-08 (informational entry).
What the repo currently claims: The afr-loan-amortization-template.md
file (per accounting/five-points-1006-sba-narrative.md:697-707)
still says "Borrower: Five Points BHM LLC" — i.e. the correction
hasn't been propagated.
Sources: accounting/afr-loan-amortization-template.md (stale),
accounting/five-points-1006-sba-narrative.md:697-707,
context/entities.md:238-241.
Recommended fix: Update accounting/afr-loan-amortization-template.md
Borrower row to "Austin Renfroe (personally)" and add a §-level note
explaining the two-level structure (parents → Austin AFR loan;
separate Austin → Five Points intercompany note). HIGH because this
is the template that drives 1099-INT compliance; getting the borrower
wrong sends the wrong tax form to the wrong taxpayer.
Implicit financial facts (cash dynamics, etc.)¶
Finding 39 — Two distinct PLOCs at two banks with possibly overlapping renewals¶
Severity: HIGH (already flagged in user prompt; expanded here)
What the data says: Per context/people-graph.md:254-266:
- Pinnacle PLOC ($600K, loan #20221215035, originated 2022-07-13,
restated 2025-05-12, renewing again 2026-05 per Brent Boltwood
thread).
- ServisFirst PLOC (separate facility, Sophie Membrino as
banker, "PLOC Renewal" subj 2026-05-05, $$ amount not surfaced in
this repo).
What the repo currently claims: Pinnacle's PLOC is documented
(context/people.md:154); the ServisFirst PLOC is mentioned but no
amount or terms are documented. Two PLOCs at two banks, both
renewing in the same week is a coordination + audit-trail signal
that deserves a unified "Austin's personal unsecured credit lines"
view.
Sources: context/people.md:154, context/people-graph.md:37, 254-266, 372,
accounting/five-points-1006-sba-narrative.md:553-555.
Recommended fix: Create a banking/personal-credit-lines.md (or a
section in banking/) consolidating both PLOCs: bank, $$, originated,
maturity, last renewal, current status, signing rail. Update
open-questions.md if there's a strategic question (consolidate?
keep both?). HIGH because two banks + same-week renewals + the
ServisFirst-side carrying historical baggage from the 2024 1006 note
dispute creates a non-trivial relationship-management surface.
Finding 40 — Renfroe Innovation registered office same as W 3101 — same address Five Points uses¶
Severity: LOW
What the data says: context/entities.md:325 says RI "Registered
office: 210 Lavaca St #3101, Austin TX 78701." accounting/five-points-1006-sba-narrative.md:167, 654
says Five Points BHM Holdings, LLC's recorded address is 210 Lavaca
Street #3101. So 210 Lavaca #3101 is the registered/mailing address
for both RI and Five Points. W 3101 is owned by W 3101 Holdings, LLC
(rented separately to non-Renfroe tenants). The condo is being used
as a registered-office mail-receipt address for at least two LLCs
that don't operate from there.
What the repo currently claims: No conflict, but no explicit note that 3101 is acting as a "convenience registered office" for multiple Renfroe-stack entities. This is fine substantively, but for foreign-qualification / annual-report purposes, all entities receiving service of process at 3101 need a mail-handling protocol.
Sources: context/entities.md:325 (RI),
accounting/five-points-1006-sba-narrative.md:167, 654 (FP BHM),
context/entities.md:189-198 (W 3101 Holdings).
Recommended fix: Add a "Mail-handling note" to context/entities.md:
"3101 functions as the registered-office mail-receipt address for
Renfroe Innovation LLC, Five Points BHM Holdings LLC, and possibly
other entities. The W 3101 condo is leased separately to a tenant
via Revel Property Management; the lease arrangement should
contemplate forwarding registered-office mail to Austin/RFH." LOW
but real; affects how SOS notices flow.
Finding 41 — Renfroe Marine paperwork "Originally written in Austin's personal name (marina's error)" — but the resolution date isn't documented¶
Severity: LOW
What the data says: context/entities.md:230 says "Marina
paperwork: Originally written in Austin's personal name (marina's
error). Austin has confirmed LLC ownership is correct and the marina
is fine with it. Resolved." open-questions.md:225-226 has it as
"Dock 2 Slip 18 marina paperwork in Austin's name → CLOSED
2026-04-19." But there's no documentation of (a) what the marina's
file actually says today vs. before, (b) any signed paperwork
correcting it, or © Lake Austin Marina's confirmation in writing.
"Marina is fine with it" is a verbal-only resolution.
What the repo currently claims: Officially closed.
Sources: context/entities.md:230, open-questions.md:225-226.
Recommended fix: Promote to a legal/advisory-contract-gaps.md
sub-item: "Renfroe Marine — Lake Austin Marina paperwork on Dock 2
Slip 18: confirm with marina (written acknowledgment) that the slip
license is in the LLC's name, not Austin's personally. Verbal
confirmation only as of 2026-04-19." LOW but a piercing-the-veil
exposure if not papered.
Finding 42 — decisions/log.md 2026-04-19 SBA decision title is misleading¶
Severity: LOW
What the data says: Decision title is "Casa Moksha SBA payments
as personal (not Five Points) liability" — but the SBA payments are
NOT Casa Moksha-related. The Woolworth EIDL has nothing to do with
Casa Moksha. decisions/log.md:475-479 (2026-05-08 entry) explicitly
flags the title as misleading: "the loan is the Woolworth EIDL,
not Casa Moksha-related at all. The booking treatment is right;
the entity attribution in the title needs a cleanup entry."
What the repo currently claims: Title not yet fixed.
Sources: decisions/log.md:61-65 (original 2026-04-19 entry with
misleading title), decisions/log.md:475-479 (2026-05-08 self-flag).
Recommended fix: Append-only addition: a 2026-05-09 entry "Title-cleanup: 2026-04-19 SBA payments decision — title mislabeled the loan as 'Casa Moksha SBA' when it's the Woolworth EIDL Loan #4300957803. Treatment unchanged; just clarifying the attribution in the decision title." (Per the append-only convention; don't edit the original entry.)
Finding 43 — accounting/jme-deliverable-status.md "JME promises Feb 2026 financials ~6 weeks overdue"¶
Severity: MEDIUM
What the data says: context/people.md:169 says: "Outstanding
promises: February 2026 financial statements committed 2026-03-25
('later this week or early next week'), ~6 weeks overdue as of
2026-05-08." Today is 2026-05-09 — so it's ~6 weeks + 1 day overdue.
context/master-timeline.md:76 echoes "now ~6 weeks overdue."
What the repo currently claims: "~6 weeks overdue" — accurate as a snapshot; the actual gap is 45 days as of today (Mar 25 to May 9 = 45 days).
Sources: context/people.md:169, context/master-timeline.md:76,
accounting/jme-deliverable-status.md.
Recommended fix: Add a "Last refreshed YYYY-MM-DD" timestamp to the "~6 weeks overdue" lines so the staleness is visible. Also: this is a concrete reason to ping Giovanni Díaz Durán again — JME's outstanding deliverable affects the Xero historical backfill, the Mexican-side intercompany picture, and the upcoming 5471 prep. MEDIUM because operationally the gap is real and growing.
Finding 44 — Five Points "pre-revenue" status but commercial property insurance lapsed¶
Severity: HIGH
What the data says: accounting/five-points-1006-sba-narrative.md:296-303:
"Five Points BHM's commercial property insurance policy expired
04/22/2026. Long email back-and-forth among Austin / Jeff / Joshua
across April 22 – May 2 to get the renewal documented. ... almost
lapsed (Joshua: 'Reaching out because Jeff hasn't gotten a response
on the insurance from you. The current policy is expiring tonight.')."
context/master-timeline.md:57 echoes "Five Points BHM commercial
property insurance lapses (renewal scramble Apr 22 – May 2)."
What the repo currently claims: Open item flagged in the Five
Points narrative file. NOT in context/entities.md Five Points BHM
section, todo/for-austin.md, or open-questions.md. The narrative
file is the only place this critical operational fact lives.
Sources: accounting/five-points-1006-sba-narrative.md:296-303,
context/master-timeline.md:57, context/entities.md:233-279 (no mention),
todo/for-austin.md (no mention).
Recommended fix: Add to todo/for-austin.md under operational
confirmations: "Confirm Five Points BHM commercial property
insurance was renewed and is in force as of today. Policy expired
2026-04-22; near-lapse Apr 22 – May 2 communications. Confirm policy
number, carrier, premium, and effective dates with Edgewood. Document
in legal/advisory-contract-gaps.md." HIGH because an uninsured
$5M+ commercial building during active tenant LOI circulation is
a real liability and lender-covenant risk.
Top 10 priorities (ranked)¶
These are the highest-leverage findings Austin (or his advisors) should act on first, ranked by audit-defensibility / tax-filing / operational risk.
-
Finding 8 — Five Points BHM jurisdiction conflict (TX vs AL, plus name "BHM" vs "BHM Holdings"). HIGH. Owns a $5M building; "right to transact" must be unambiguous in both states. Ask Skinner Legal + Pearce; update
context/entities.md. -
Finding 44 — Five Points commercial property insurance — confirm in force today. HIGH. Near-lapse documented; uninsured commercial real estate during active LOIs is a liability + lender-covenant problem.
-
Finding 22 — Hunter pronoun normalization across 8+ files. HIGH.RESOLVED 2026-05-10. Counterparty identity on PG'd SBA debt + 2014 share assignment must be unambiguous on legal filings. Resolve once, propagate repo-wide. -
Finding 38 — Update
accounting/afr-loan-amortization-template.mdto reflect the two-level loan structure (Borrower: Austin personally, NOT Five Points BHM). HIGH. Drives 1099-INT compliance for the parents↔Austin AFR loan. -
Finding 19 — RHG ownership "may shift to Renfroe Family Holdings" is stale; the answer is now Casa Moksha LLC + Casa Moksha Holdings LLC. HIGH. Form 5471 needs canonical ownership percentages.
-
Finding 5 + 37 —
banking/tokyo-star-bank.md"purchase price provisional" stale; ¥835.4M is locked. HIGH. Anyone reading the bank file would conclude the basis hasn't been computed when in fact it has. -
Finding 18 —
context/entities.mdstructure diagram shows Renfroe Innovation under RFH; it's Austin-personal. HIGH because it's the diagram that gets pasted into advisor briefings. -
Finding 39 — Two PLOCs at two banks (Pinnacle + ServisFirst) renewing same week. HIGH. Document both in
banking/personal-credit-lines.md; surface the consolidate-vs-keep question. -
Finding 10 —
banking/brex.mdline 26 "close 0926 after data pull" — DO NOT CLOSE per Sep 2025 analysis. HIGH because stale instructions that get followed by accident cause real damage. -
Finding 7 — RHG ownership 99%/1% framing vs. economic-substance 100%-Austin/MXN500-Cindy framing. MEDIUM-HIGH. Affects 5471 ownership-percentage line + the cap-table cleanup that the Cindy consignation is paving the way for.
Cross-references¶
context/people.md— canonical people index (Hunter, Chuck, Daisy/Don conflicts)context/people-graph.md— wave-2 deduped people-and-orgs mapcontext/entities.md— entity structure diagram + Five Points + RI conflictscontext/master-timeline.md— date conflicts (RHG 2023 vs 2025; Murray Brown)accounting/flow-of-funds.md— wave-2 financial picture; SBA $$ figuresaccounting/five-points-1006-sba-narrative.md— Don/Daisy Buck inconsistency in same fileaccounting/afr-loan-amortization-template.md— borrower-row needs updatebanking/brex.md— CO DASH stale "Unknown"; 0926 close instructionbanking/jpmorgan-chase.md— misleading framing of RFH-JPM relationshipbanking/tokyo-star-bank.md— Mita basis stale "provisional"banking/wells-fargo-personal.md— missing Mita refund cross-referencedecisions/log.md2026-04-19 SBA decision title — Casa Moksha mislabellegal/cindy-consignation-timeline.md— Cindy economic-stake framingtax/2025-filing-prep.mdline 43 — 8832 question phrased to a moot formopen-questions.mdQ9 (PFIC) — partially answered by ABS Partners engagement