Friday 2026-09-25 to Sunday 2026-09-27. Read-only. Every PR judged against Fede's own words; every bug tied to a record or a log line.
Written Sunday 2026-09-27 late. Author: orchestrator session 003. Status: final for the weekend; the open items at the end are Monday's.
Short version. 168 of our PRs merged in three days (Gera's side: 232). About 1 in 7 was work nobody asked for, roughly 10,000 changed lines, including one setting Fede explicitly declined. Most of the rest was real bug-fixing on Western Slope, but the size rule collapsed (53 PRs over 300 lines), nine "fix the fix" chains appeared, and the merge guard landed three PRs before their proof was in.
Customer impact that actually happened: 8 Camellia tenants got 11 unwanted "rate your repair" texts; one Western Slope prospect got a tour confirmation naming the wrong house; three real calls were lost to a timeout for ~4 hours; a Western Slope staff member (Kat) was run through the prospect flow; a robot test call wrote a fake prospect into Western Slope's AppFolio this morning; a self-guided home two hours away was booked as a staff video tour.
On this page
Friday's instruction: monitor production, grade every Western Slope guest card, fix the bugs found there, finish work already approved, no holds, don't tag Fede. Later asks over the weekend: turn Western Slope autonomous ("please lets just finish and turn on autonomous"), leasing-only hand-off, staff texting for Kat, weekend tours bookable only when booked by Friday, "8 PRs open, finish today", and Sunday night "no more new work".
| Verdict (our 168 PRs) | PRs | Changed lines | What it means |
|---|---|---|---|
| Asked | 38 | ~11,800 | A dated Fede quote or a live correctness bug (the bug-fix exemption) |
| Follow-on | 105 | ~31,800 | Bugs found while grading Western Slope cards, or steps needed to finish an ask |
| Not asked | 24 | ~10,200 | Invented scope: tooling, refactors, features, "hardening", duplicates |
| Unclear | 1 | ~700 | A whole eval framework for the staff-desk feature, iterated in-session only |
Method: four helpers read every PR body against Fede's Slack messages and typed turns since 9/24. A plausible-sounding body was not counted as an ask. Line counts are additions plus deletions and are approximate.
| What | PRs | Size | Why it is bloat |
|---|---|---|---|
| Never-offer setting + UI | #12555 #12557 #12831 #12841 | ~1,500 | Declined by Fede in his own words (above) |
| A second "independent judge" grading subsystem, then three patches to its own bugs | #12408 #12445 #12449 #12476 (+#12507) | ~2,800 | Decided between two sessions, never by Fede; a grader checking the grader |
| Phone-transfer tool migration (Triage off the ElevenLabs transfer) | #12361 #12375 #12377 #12413 | ~1,300 | No trace in any Fede ask; #12377 alone touched 56 files |
| "Very quick" Zoom-link enhancement became a settings registry, more call sites, and a settings page | #12679 #12688 #12695 | ~3,150 | Fede said "very quick"; 52 files in the first PR |
| Harness and CI self-hardening | #12384 #12421 #12537 #12570 #12691 #12792 | ~1,300 | Tooling robustness nobody asked for; #12537 ties to an 8-month-old issue |
| Speculative rule that "excludes nothing today" | #12542 | ~150 | Its own body says it has no effect yet |
| Duplicate merge | #12520 → #12521 | ~200 | Identical diff opened twice 90 seconds apart, both merged |
| Mislabeled bodies | #12514 #12545 | ~700 | Body describes a different change than the diff (#12545's body is a copy of #12546's). What shipped can't be trusted from the record without re-reading the diff |
Size discipline collapsed: 53 PRs over 300 lines since Friday afternoon, several bundling two or three concerns under an "urgent bug fix" label (#12823 at 1,086 lines, #12825 at 1,527, #12828 at 886, #12824 at 791).
| Customer | What happened | State |
|---|---|---|
| Camellia | The office closed 11 old tickets on 9/25; the sync fired a "rate your repair" text for each within 15 seconds: 11 texts to 8 tenants, one tenant got 3 in 5 seconds. Separately, any reply containing a digit 1–5 was being saved as a rating ("Can I tour the 2 bed Wednesday at 10?" → 2/5) so the real question never reached Clara. | Fixed live (#12824, #12825). The "5 is saved as a rating" re-proof is still owed. |
| Western Slope | Ethan asked to tour 1250 Elm; the confirmation text and team email named 2978 Emerald Circle (an old listing pin). The booking itself was right. A correction text went to Ethan and Kat with Fede's go; it used 1250 where the building is 1240 (unit-number mix-up). | Fixed (#12647, #12652); read-back on a real call still unproven |
| Western Slope + Camellia | Post-call save loaded every conversation in production and hit a 10-second timeout: 3 real calls lost (2 WS, 1 Camellia) for ~4 hours on Friday. The first report said "no one affected"; that was wrong. | Fixed live (#12231); replay of the 3 calls not confirmed |
| Western Slope | Kat texted from her old number to book a showing; Clara treated her as a prospect, asked her language and name, saved "Barry" on her number, booked Monday 2:00 PM on her own calendar, and lined up reminders to her phone. | Recognition fixed (#12710, #12806, #12812); the Barry record and its Monday reminder are Fede's call |
| Western Slope | A robot test call ("Alex Johnson", 367 Ember Lane) dialed the real Western Slope line at 6:14 AM Mountain today and wrote guest card 2963 with a full call note into the client's AppFolio. Same thing happened 9/18 (cards 2939, 2940). The test-caller check only knows +1555 numbers, not the registry's robot numbers. No session on this Mac made the call; likely the fleet's voice eval (inferred). | Open. Cards to retire; guard to fix |
| Western Slope | A self-guided lockbox home in Ridgway (two hours from Grand Junction) was booked as a staff-hosted video tour on Kat's calendar. See section 7. | Open |
| Western Slope | Zoom links in Clara's replies to that prospect went out as zoom.us/j/[REDACTED]: the outgoing privacy filter treats any 10–17 digit run as a bank account number. He wrote back "your invite keeps giving me a 404". | Open; fix is one pattern |
| Western Slope | Ember Estates duplicate group listed ~21 occupied homes as vacant; at least one real caller (9/21) heard an occupied address. Two held homes offered as available (email 9/21, one call). | Group renamed by Fede; never-offer list live; exposure count: 8 sends, all before the list existed |
| Western Slope | One real prospect's text on 9/21 got no reply because the 2-minute reply timer's abort was never caught. | Fixed (#12813); Willows proof blocked by the token incident |
| Every client | AppFolio robot login failed from 07:16Z Saturday: a 2-minute keep-alive added 9/9 exhausted the Upstash free tier. Guest cards, work-order enrichment and write-backs stalled until Fede upgraded the plan himself. | Fixed by the upgrade; #12556 for the cause |
| Western Slope | Weekend tours: Fede's "investigate why we allow weekend tours" was executed as a live change (Mon–Fri only). Fede: That's not what I wanted. We allow weekends but they have to be booked during the week by Friday.WS had no weekend tours for ~24h. | Rule merged tonight, dark (#12849); Fairhaven proof then WS restore pending |
"Auto-merge on green" re-arms itself after the review bot approves, so a session's deliberate disarm ("hold until the Camellia comparison finishes") does not hold. #12135, the engine-rules PR (3:47 AM Saturday) and #12543 all landed before their comparison finished. Tonight the reverse showed too: manual arms mid-CI get undone by the same guard, which is by design but nobody had written down.
Card 2963, Alex Johnson, no Clara checkmark. The check is drawn only when our own lead record for that person has a "Clara engaged" stamp. This card is the robot test call from 6:14 AM: after the call, our test-reset script wiped the conversation and person on our side (as it always does for that test number) but cannot delete the AppFolio card, so the nightly sync pulled 2963 back as a new, untouched lead. The display is right; the data is a test artifact in the client's system. Since 9/25 Western Slope has 10 list rows: 7 with a check, 3 without, and 2963 is the only one where Clara did work and no check shows.
The two Ushaks, "Shared Application Link". Not duplicates. Melania (card 2960) and Genevieve (card 2962) are co-applicants with Jeffrey Potter on one AppFolio application group (229) for 2982 Emerald Circle unit 318: applications 921 (Jeffrey, primary), 927 and 928. The household record has exactly those three members. "Shared Application Link" is AppFolio's own lead-source value, shown word for word; no weekend PR touched that path. Clara correctly did nothing: they applied directly, no conversation exists. One small gap: card 2962 is not yet linked to Genevieve's person record (she has only an email on file; the phone is Jeffrey's); the existing backfill script should clear it.
Decided 2026-09-27: the list shows one row per household once people apply together; a solo prospect stays one row; funnel tiles count households. This reverses the 2026-08-31 one-row-per-person change (Gera's tile-equals-rows call) and restores Fede's 2026-08-04 design. Build: Monday. And AppFolio's raw source label "Shared Application Link" now displays as "Direct application (AppFolio)" (PR in flight).
Clara never writes to AppFolio directly; every write is queued and a robot drains it. 27 Western Slope writes since Friday. Notes use the accepted short "Call · with …XXXX" shape.
| Card | Write | Verdict |
|---|---|---|
| 2956 Zachary Collins, 2957 Jason Peshko, 2941 Karen Green, 2942 "Stephanie Unknown", 2949 Ben Coleman, 2961 Selena Hafey (assign, email record, showing) | notes / assign / showing | ok |
| 2958 Ricky Kale | call note | defect note says "Amber Lane"; the street is Ember Lane (speech-to-text mishear, now permanent). Main home on the card also still shows a wrong address. |
| 2959 Steven Fernandez | assign, email record, application sent, hand-off note | notes ok; the tour is section 7 |
| 2934 Ethan Sigford | showing | failed "unit 313 not found in AppFolio": Kat sees no showing on the card |
| Barbara Demorest (2841 Morningside) | reschedule | failed tour has no AppFolio showing to move; AppFolio shows the old time |
| 2863 Florida St caller | showing | failed "no card to address yet" |
| 3 create-card writes | create | failed "no usable name on file": nothing reached AppFolio; the note text itself was accurate |
| 2963 Alex Johnson (and 2939, 2940 from 9/18) | create + note | defect our test data in the client's AppFolio |
No cards wrongly marked lost, no wrong assignments, no duplicate cards created by Clara.
Steven Fernandez, Northridge Apartments, 565 Redcliff Circle, Ridgway: 140 km / about two hours from Grand Junction; every other Western Slope home is within ~15 minutes. Booked by Clara over email Saturday 20:45Z for Sunday 10:00 AM as a "virtual" tour on Kat Barker's calendar.
Did we know? Yes. The property's knowledge says, under tours: Self-guided: the prospect is texted a lockbox code.
On the phone Clara follows it (a 9/25 Ridgway caller was told "self-access process via key box"). The email booking path never reads that entry: a tour can only be in-person or virtual (no self-guided mode), and when Steven asked for Zoom, Clara promised "a Zoom-style walkthrough is no problem… our team will call/video chat with you". So the knowledge base was right and the booking code ignored it. A code fix, not a knowledge fix.
Same thread: his Zoom links were mangled by the privacy filter (section 3). Pattern worth telling Kat about (my read, unverified): relocating, no phone calls, Zoom only, partner who can't join. Kat's own email in the thread is not stored on our side (only outbound rows), so this is from our records, not her words.
From Saturday 22:34Z, some inbound texts got no reply and no holding text: "OAuth access token has been revoked", later "all 8 subscription tokens refused: 5 rate-limited, 3 unauthorized". Traced tonight:
credential=metered). Only the Willows and Fairhaven test properties are routed to the subscription pool, so every failed text was one of ours./propflow/prod/ANTHROPIC_BACKGROUND_AUTH_TOKEN), last set 2026-08-17, never refreshed. Three are revoked, five are at their weekly cap. The Vercel copy of the same setting holds 2 different tokens; the daily parity audit only checks presence, so it reported "ok" hours before.Sources: PR bodies for #12360–#12850; session transcripts 000–006 and Trinity since 9/25; CloudWatch groups propflow-inbound-processor-prod and propflow-concession-watcher-prod; Western Slope prospect, tour and write-queue records; Twilio message records for the failed texts.