Home.LLC runs its own servicing with AI. Sophei is that operation, and this is its screen. Below: the July board, the two dashboards it ships, and the three failed months it kept on the record.
Rendered from the live board, July 2026 run. Private values withheld.
The two dashboards it ships. The same cycle regenerates both as static pages at every month-end close. Investors get one, homeowners get the other, and the homeowner numbers come from the 7 signed contracts, not from summaries.
Row layout from the dashboard generators. Shipped in one day, regenerated every month-end. Private values withheld.
The failure line. The board was not always green. After the human operator left, the scheduled month-end routine fired for three straight months and silently wrote nothing. Sophei's audit found all three, named the root cause, and fixed the cycle the same session.
Rendered from the run log, April through July 2026. The failure log is part of the system. Most vendors would never show you this.
Two dashboards, one for investors and one for homeowners, shipped in one day as static tokenized pages. No SaaS.
Six rows, every one falsifiable against the files on this page.
Verbatim, trimmed, private numbers blacked out. These are the working files behind the screens above.
The run log entry that found the three failures and moved the missing step inside the routine.
# Sophei Learning Loop — Run Log
## 2026-07-07 · Autopilot rebuild session (Claude Code, Fable)
- Type: gap audit + system repair (not a servicing run)
- Found: 3 consecutive failed month-end runs (Apr/May/Jun) — routine fired, zero writes, root cause = manual AVM dependency; registry wrongly showed "live"; no STATUS/runbook/run-log existed until today.
- Fold-back: created STATUS.md + servicing/month-end-runbook.md (pre-flight gate: never stack a new partial run on an unfixed failure; AVM scrape moved INTO the routine); July AVM pull executed same session.
## Backfilled — pre-log history (from verification reports)
- 2026-07-01 · month-end (June): FAILED — no May/June AVM columns existed; zero writes.
- 2026-06-04 · month-end (May): FAILED — same root cause. note: the registry said "live" while these runs failed. Fixing the registry row was part of the repair.
The refusal from the July verification report. The fund workbook's IRR row needed a cash balance no source could confirm. Sophei left the cell empty and handed the decision to Nik.
# July 2026 Sheet-Write Verification Report (Runbook Step 2)
## ⚠️ Top-section alerts (read first)
3. Fund 2a Summary (IRR/MOIC) NOT extended — still "as of 1-Mar-2026." The Net IRR Calculator rows are hand-dated with a hardcoded fund cash balance (col C) I cannot source (last: ██████). Refused to carry the cash number blind into an investor-facing XIRR.
## 5. Structure-vs-process-doc mismatches (stopped rather than improvised)
- Fund 2a Summary requires manual fund cash balance → no July IRR row written (alert #3). note: the cell was still empty when Nik reviewed the run. That is by design.
Everything above is the work product of an agent running live fund books, gated by written rules, and reviewed by one human who sends every word himself. The worst three months stay on the page on purpose. A desk that hides its worst month cannot be trusted on its best one.
Sophei is not for sale. It is captive by charter, services Home.LLC's two funds, and nothing else. What 100x builds for other operators is the same discipline pointed at their desk: the board, the gates, the dashboards, the log, the reviewer. If your monthly cycle lives in one person's head, that is a risk with a leaving date. Opposed to exploring what a written one would take?
CEO and founder, 100x. Also founded Home.LLC, whose home equity funds Sophei services. He reviews every Sophei cycle, sends every homeowner and investor email himself, and keeps the judgment.