Memo fieldssource · date · judgment · kill · assumptions · data_gaps · size
Ticket fieldsstatus · reason · approved path or no order
Processowner · next review · status code
Solo Fund AI — Desk Map Report (SAMPLE)
Risk preset: Balanced desk
Rules: Single name ≤15%; after add ≤40%; max DD 25%; 90-day review
Holdings context:
NVDA | weight 4% | shares 30 | cost 118.50 | last 131.20 | uPL ~10.7%
01 Brief
Problem: Decide whether to add to NVDA at 4% of a $150k book.
Restrictions: Cap 15% single name; require kill condition before any ticket.
Expected output: Memo with explicit gaps and a ticket outcome.
02 Pass
Single task: Measure headroom to the 15% single-name cap and the minimum viable add size.
Result: ~11 percentage points of weight headroom remain; a 2% add is within cap math but still needs thesis + kill.
03 Memo
Source: User-provided holdings + desk-fetched marks (when available)
Date: sample
Judgment: No market-order add without a written thesis; prefer Hold while correlation and tax lots are unknown.
Kill condition: Cut if thesis breaks OR price −15% from average cost (118.50), whichever first.
Recommendation: Hold / Watch
Size suggestion: If later adding, ≤2% of book per tranche
Assumptions:
1. Stated weight and book size are accurate
2. No leverage
What we don't know (data gaps):
1. Rest of book factor exposure to semis
2. Exact tax lots beyond average cost
3. Near-term event calendar not supplied by user
04 Ticket
Rejected (auto) — no order
Reason: Memo is hold/unclear on actionable add without tighter data gaps closed.
05 Process
Owner: User (solo desk)
Next step: Revisit when thesis is written or gaps close
Status: NO_ORDER
Sample only. Educational. Not financial advice.
Ticket note: Live desk runs use an automatic, rules-based ticket
(not a human committee). When judgment is hold / unclear / risk-off, the ticket defaults to
no order. That conservatism is a product feature.