Advisor ask packet template¶

Purpose: Per-advisor, per-decision one-page packet for advisor calls / written engagements. Forces the question, the recommended answer, and the supporting evidence into a fixed structure so we get consistent advisor responses + a fast paper trail.

Status: v1, 2026-05-10. Use this template for every substantive advisor ask.

Template¶

# Advisor ask: <one-line title>

**Advisor:** <Pearce / Kim & Rosado / JME / ABS / Portilla / Stuart Memory / Conley Rose / Withers / etc.>
**Date:** YYYY-MM-DD
**Deadline / why now:** <gating event or hard date>
**Severity:** Critical | Major | Minor

## Facts we believe

- <bullet, sourced — link to repo file + line number / source-doc path>
- ...

## Decision needed

<One sentence — be specific>

## Options

- **Option A — <name>**: <description, pros/cons>
- **Option B — <name>**: <description, pros/cons>
- **Option C — <name>**: <description, pros/cons>

## Recommended answer

<If we have a working hypothesis, state it. If we genuinely don't know, say "no recommendation; advisor judgment.">

## Xero / books impact

- Accounts affected: <COA codes per `accounting/accounting-policy.md` §25>
- JE template: <local-summary | intercompany-clearing | US-tax-adjustment per `accounting/xero-buildout.md` Phase 4>
- Confidence level today: <[F] / [P] / [U] per `accounting/accounting-policy.md` §16>
- Confidence level after advisor confirmation: typically [F]

## Tax / legal impact (plain English)

<Two-three sentences on the consequence to Austin or the entity>

## Source documents attached

- <path on Synology / repo file / Brex API descriptor>
- ...

## Open follow-ups for advisor

- <If this answer cascades into other questions, list them here so the advisor knows what's next>

## Decision register entry (post-call)

After the call, log the answer in `accounting/advisor-decision-register.md`:
- Date
- Advisor + lead
- Decision
- Effective date
- Xero impact
- Source (this packet + meeting notes)
- Status: active

Standing list of advisor packets to draft¶

Use this list to prepare for next advisor sessions. Each entry should become its own file at accounting/advisor-packets/<advisor>/<topic>-YYYY-MM-DD.md when the call is scheduled.

Pearce + Kim & Rosado (2025 working session)¶

JME¶

ABS Partners (Endo)¶

Deliverable cadence + scope (project-driven mirroring JME, vs monthly TB capability?)
Mita basis allocation on Japanese statutory side (matches Pearce's US allocation?)
GK Japanese statutory depreciation method
TSB mortgage covenant reporting requirements
New-GK formation mechanics on JP side (cleared 2026-04-30 with FMV mark-to-market)
5471 / 8858 file format Pearce needs
Mita rental-income recognition timing on JP corporate-tax side
PFIC posture interaction with JP statutory framing

Portilla, Ruy-Díaz y Aguilar (Diego Alcantara)¶

Cindy consignación re-attempt at corrected Mérida address (status update)
Substantive grounds documentation for Cindy removal (illegal acts; whether MEMO RENFROE 30062025 is sufficient)
MX labor exposure on Cindy resignation (final wages; contingent claims)
Cindy criminal complaint — file or not? (cost / risk / leverage trade-off)
RHG SA → S. de R.L. de C.V. conversion timeline (downstream of consignación closure)
Casa Moksha LLC pair activation paperwork (post-conversion)
NOTARIA 78 invoice mapping

Stuart Memory¶

AFR promissory notes — Five Points leg + Mita-side $350K leg (drafting)
AFR rate (at disbursement; §7872 / 1099-INT compliance)
SBA Loan 7803 collection status (post-Jan 2026 reminder)
SBA "Parent" $1.2M loan — entity of record + collection status
SBA negotiation posture post-TRC LOI (re-amortization vs partial settlement)

Conley Rose (Michael W. Piper)¶

§101 OA response on matter # 4447-00106 (CRITICAL — past deadline)
Maintenance fee schedule confirmation for issued patents
CASA MOKSHA trademark progress (US → International → MX)
5 outstanding information requests since 2026-03-28
USPTO Statement of Use / abandonment status on RENFROE INNOVATION trademark (Serial 85804994)

Discipline rule¶

No advisor call without a packet. Each call should produce a logged entry in accounting/advisor-decision-register.md; if the call's substance isn't packetized, future-Claude can't reconstruct what was asked vs what was answered.

Last updated: 2026-05-10. Refresh as packets are drafted + advisor calls happen.