Internal operating board. Single authoritative view of where every client is. Human-confirmed facts sit ABOVE the agents (confirmed-facts), so a thing you explain once is not re-raised. Every item is a record or an alert; a person acts (owner tagged). Refreshes twice daily; this is the evening pass of 31 August and the last board of the month. ⚠ Read the honest limit first: the spine underneath this board was last rebuilt on 30 August at 06:40 and was not rebuilt today, so byte figures and stage rows are carried from that verification rather than re-measured. What IS measured today: the care audit at 06:54 that wrote the month-end finding, the site-health loop at 07:14 reporting 100 live sites, 84 OK, 16 warnings, 0 failures - nothing down, and the two money passes at 09:26 and this afternoon that produced everything new on this board. Read the day in one line: no money moved and no demo went out, but two red claims were found to be wrong and a paid client’s blocker changed hands. The structured money book has been unchanged for eight days; the commission ledger has not been written in thirteen and its last content entry is dated 24 July, thirty-eight days ago; the written confirmation log has never once been used since June. ⚠ Every red item below has already been asked of its owner in writing, so the correct reading of this board is awaiting an answer, not nobody has asked. 🔴 27 accommodation pages still have no channel of any kind, and €3,105 to €3,305 still sits outside a clean company account.
confirmed-facts = human ground truth above the agents; unchanged since 16 Aug, and the three-piles ruling it carries still governs how the unsent count is read. Authority order: confirmed facts, then money, then the acts log, then what was said in client channels, then the agents’ summary. ⚠ This is the evening pass, and the spine under it is a day old because the nightly rebuild produced no output. Treat every figure here as carried from 30 August unless it says otherwise. Where earlier rulings retired a claim, the claim stays retired: the psychologist’s build is PAID, the hotel-services care question is CLOSED, the September launch date belongs to the gym client, and the whole coffee-client money question was closed by Ivo himself on 27 Aug and must not be re-raised in any shape. ✅ Two claims joined that list this afternoon and must not come back: the replacement company’s confirmation statement is NOT overdue, and its address query is NOT sitting without a date. Take-downs on this board are client requests honoured, not defects.
🔴💵 NEW - AUGUST CLOSED WITH THREE PAID CARE CLIENTS RECEIVING NOTHING VISIBLE. THE MONTH IS OVER, SO THIS IS NO LONGER „DAY N“: IT IS A MISSED CYCLE ON MONEY ALREADY TAKEN. Written by this morning’s care audit, measured from the client channels rather than carried. The Kiten guest house: care prepaid to July 2027, channel silent since 24 July, 38 days, and our own 27 June message promised her in writing that the next pack comes at the beginning of August. August ended yesterday and the package never came, and it is the one gap on this board the client can check for herself. The card subscriber: billed monthly, last message in her channel was the double-collect escalation, and her last actual care action was 04 July - a monthly-billed client charged for a month in which nothing was delivered. The hotel-services client: paid a full year on 03 Aug, channel last touched 04 Aug on money admin only, 27 days, and no care cycle has ever run on the client who paid furthest ahead. ✅ Not in this item, each with a dated August action: the restaurant (menu prices, 05 Aug), the hotel in Сливен (own-domain go-live, 08 Aug), the scooter account (three assets published, 24 Aug), the gym (a hall banner, 29 Aug), the coffee client (address and hours, 03 Aug). 🔴 The commission consequence, and it is Ivo’s: the 40% care commission on the silent prepaid year was logged on 24 July for a care year whose first month was never delivered, and the ambassador rule makes that 40% contingent on delivery. A live commission-gate breach, not a bookkeeping lag. Elena / Ivo
🔴⚖ A FINISHED, TWICE-REBUILT, LIVE PAGE IS HELD ON ONE READ THAT ONLY IVO CAN DO - DAY 2, AND TWO BUILD SESSIONS WERE SPENT BEHIND THE HOLD. The taekwondo club in Дупница is live and byte-verified at 578,895 bytes. Ivo’s own words in that channel at 16:10 on 29 Aug: do not send yet - research surfaced a 2022 press item naming the club’s chairman and senior coach, unverified, with no known legal outcome either way. The gate is his and it is the right call. What makes it an item is the cost already sunk behind it: after the hold was posted, the same evening ran a full design upgrade at 17:16 and a second press sweep and hero rebuild at 17:43. Two sessions and a photo hunt on a page nobody may send, while the rep who asked for it at 14:24 is still waiting on one word. ✅ Everything else on the row is clean: the has-site pre-check is confirmed, the three photographs with recognisable children are not on the site (verified by name against the served page, zero hits), medal-winners are deliberately unnamed, nothing sent, no price, no domain. One read closes it either way: send, or take it down. Ivo
💵 THE MONEY OUTAGE STOPS BEING AN INCONVENIENCE TOMORROW, AND IT IS NOW DAY 46. CORRECTED THIS AFTERNOON: THERE ARE THREE CARE STARTS TOMORROW, NOT TWO, AND NONE OF THEM CAN BE BILLED. The music studio at €24 a month - agreed, confirmed, delivered on her own domain since 21 Aug, nothing at all to chase, and no rail to charge it on. The German guest house - 49 recorded against 40 offered verbally by the rep, unresolved since 16 Aug and now day 15, and the client has been asking for a payment link she cannot be given for 46 days. The gym client at €19 a month - her own decision that the plan begins in September, deliberately kept off the rep’s list, and never once billed; the morning board left it out of this count and that was the wrong call, because a start nobody bills is the same loss whoever decided the date. Re-confirmed twice today: no working connection to the payments platform, and no such tool is present in the session at all. ⚠ Note the direction of travel on the German row: her contact form was fixed on 28 Aug and her legal-form blocker cleared on 30 Aug, so delivery keeps accelerating on a plan whose price has never been settled. If a plan starts without a confirmed figure and a rail, the first month is simply lost, and there is no second chance at September. Ivo
🇩🇪✅🔴 NEW - THE GERMAN GUEST HOUSE’S GO-LIVE GATE CAME OFF THE CLIENT AND ONTO US, AND THAT TURNS A PATIENT ROW INTO A COUNTDOWN. ONE DOMAIN PICK IS ALL THAT STANDS BETWEEN A PAID BUILD AND A LIVE SITE. ✅ The client settled it herself in a call the rep recorded on 30 Aug 17:31: she will not register a firm and will pay as a private person, because registering would bring a company filing and a premises inspection she explicitly wants to avoid. So the line this board has carried since 16 Aug - „go-live is gated on her accountant naming the legal form“ - is WRONG from 30 August onward and must not be repeated. 🔴 What is left is entirely ours: pick a domain and register it. Two constraints follow from her decision and both are naming constraints, not legal advice: the wording should read as a holiday home rather than a guest house, and the words „guest house“ in any language must stay out of the name and the domain, though the search layer inside the code may keep them. ✅ She has already named her own preference, built on the family name, so this is not even a shortlist exercise. ⚠ The clock is real: the build was paid 15 days ago, nothing is registered, and the Rhine festival that sells the town out falls in the second week of September, roughly ten days away. On the precedent of the hotel that went live on its own domain in one afternoon for about ten dollars, this is a sub-twenty-dollar decision holding a €600 client. The 40-versus-49 price is untouched by any of this and stays open separately. Ivo
#2 BLOCKER - THE PARTNER COMMISSION CUT FROM 30% TO 20% IS CORRECT ON DISK AND STILL WRONG ON THE WIRE, DAY 11. Carried from yesterday’s wire measurement: the partner page serves 200 at 20,037 bytes, reading 30% four times and 20% once - byte-identical across six consecutive measurements from 24 to 30 August, so nothing has shipped in eleven days, and it is the longest-running one-tap item on the board. The local file has said 20% since 20 Aug at 04:41. The partner’s €120 on the German guest-house chain stays gated on that one deploy while the page still promises her the old rate. A commission rate is money, so no agent ships it: this is a one-tap yes from Ivo, not a stall. Ivo
🔴 TWO DEMOS THAT CLIENTS WERE ALREADY SENT ARE SERVING NOT FOUND - DAY 15 AND DAY 11. STILL THE CHEAPEST OPEN ITEM ON THE BOARD, AND ONE OF THEM HAS NOW COST A THREAD. Both return Not Found at 766 bytes on yesterday’s measurement. One was sent on 16 Aug, so a real recipient has had a dead link for fifteen days - and that thread reached its last touch yesterday and closes as no-answer, which means the silence measured our own dead page rather than their disinterest. The other was re-sent on 20 Aug to a host that was already dead. Neither is a take-down; both are unintended. The send engine correctly held both nudges for nine consecutive days, so the guard works and the redeploy simply is not being done - one command each, with a documented fallback if the first tool reports the project missing. ⚠ The asymmetry sharpened again: the take-down machinery has run flawlessly four times in three days, each with snapshot, delete, Not Found and a neighbour check, while these two redeploys, which are strictly simpler, have not run in fifteen days. The capability is emphatically not the constraint. Ivo
🔴 A RETIRED ADDRESS IS STILL SERVING A DIFFERENT BUSINESS TO ANYONE THE REP SENT - DAY 17. Carried: the old address answers 200 at 1,316,093 bytes, byte-identical since 14 Aug, while the correct page serves beside it at 1,513,920. „Which link did she send“ is day 9 unanswered and she has posted in eight further channels since. ✅ Partial progress worth restating: the send engine reversed its hold and queued the follow-up carrying the correct address, which repairs the bad case and is an ordinary nudge in the good one - so the question no longer blocks the follow-up, only the stranger’s page is still live. Retiring the old address ends it without her. Ivo
💵🔴 THE MONEY BOOK STILL UNDERSTATES A SETTLED CLIENT BY €50, AND THE FILE HAS NOT MOVED IN EIGHT DAYS. The rep closed the coffee client in writing at 28 Aug 16:49: „the annual care runs from August, the build is paid in full“. So the build is €150 collected in full. The structured money book still books €100 on that row and its own note still reads „a further 50 not recorded as received“. 26 rows, last written 23 Aug, day 8. ⚠ Note the direction deliberately: the coffee-shop item below is the mismatch where the book claims money nobody confirms; this is the mismatch where money is confirmed and the book does not claim it. Same instrument, both failure modes live at once, on two clients, in the same file. ⚠ Her commission on the €150 annual care, 40% = €60, and on the €150 build are both unbooked. One line in a file. Ivo
💵🔴 MONEY MISMATCH - THE COFFEE SHOP’S FIRST INSTALMENT, DAY 9 AND UNMOVED. Ivo told that channel on 20 Aug that the first €100 instalment is not yet charged. The money book records €100 RECEIVED on 15 Aug, in cash, collected by the rep, sourced to her own words. He re-asked her on 25, 26, 27 and 28 Aug in the daily money message and she has not answered - and note she posted in six client channels across 28 and 29 Aug, so it is not silence in general. Either the money book overstates collections by €100 or the owner does not know a rep is holding a paid instalment. Book it or strike it. ⚠ Read alongside the €50 item above, which is the same instrument failing in the opposite direction. Ivo / Elena
💵🔴 THE NAMED DOUBLE-COLLECT STILL CANNOT BE READ, AND IT IS MONEY AND POSSIBLY A REFUND. Unchanged: the rep stated on 24 Aug that this client’s care runs on a card while the client pays only in cash - the first direct human ownership claim on the unidentified monthly subscription in 47 flagged runs, and it post-dates the June confirmed fact that left the question explicitly open, so it is the answer arriving rather than a re-flag. Two independent checks make it consistent: the gym client’s €19 is recorded as never billed, which cannot be true of a customer auto-charging monthly, and this client’s own June records name her. ⚠ The month-end audit sharpens it: she was billed for August and her last care action was 04 July, so the charge and the delivery are now both in question on the same row. Action is one sitting: read the customer behind that subscription, and if it is her, decide cancel and whether anything goes back. Blocked in practice by the money read being on day 46. Ivo
💵🔴 ONE CLIENT CARRIES TWO PRICES FOUR HOURS APART AND THE FLOOR IS STILL UNRULED. The guest-house channel was seeded on 24 Aug at 250 build plus 19 a month; the rep posted in the same channel at 20:04 that she had sent 100 for the build plus 15 a month, or 120 for the year. Unchanged: no reply from the prospect, no ruling. Five live numbers still sit in front of real prospects: 600/49, 250/19, 200/15, 100/15, and an effective 12.50 a month from the coffee client’s prepaid year, and the annual undercuts the monthly by a third. ✅ The one piece of movement stands from 29 Aug: the Несебър fight club went out at 14:51 and Ivo logged the terms in-channel twenty minutes later at 250 build plus 19 a month, matching the seed rather than undercutting it - the first send since 24 Aug that a later run can reconcile against a number, after five unpriced sends on 27 Aug. One priced send does not settle the floor. The sends are sub-1k and stay hers; what is Ivo’s is the ruling. Ivo
🔴📦 27 LIVE ACCOMMODATION PAGES STILL HAVE NO CLIENT-CHANNEL RECORD OF ANY KIND - DAY 7. Not re-sampled and the reason is sound: the 25 Aug sampling of four of the slugs across all message content returned zero hits of any kind, and the roster has grown by exactly two channels since, both belonging to the 29 Aug builds. The consequence is the point: no link is posted anywhere a human reads, no „no link in the channel“ test can fire, and if any of these 27 businesses is contacted there is nowhere for the reply to land. It is also the direct reason none of them can be sent. ⚠ The contrast is visible in a single afternoon: both builds shipped on 29 Aug got a channel at creation, the link posted and read back, and the rep verified as a member on each. Largest instance ever recorded. Ivo
📤⚠ THE 17 SENDS OF 22 AUGUST REACH THEIR LAST TOUCH TOMORROW WITH NO CHANNEL RECORD AND NO CONFIRMED CLOCK - DAY 9. ✅ The three-row clock defect is closed and stays closed: the log holds 50 rows and every open thread has a cadence clock. What survives is different and is not fixed by a backfill: every one of the 50 rows is still unconfirmed, not one of the 17 client channels carries the send, and the rep is absent from twelve of them, so for those twelve the only person who could follow up is locked out. 🔴 Their +2 and +5 both passed unserved and their +10, the last touch, falls tomorrow, 1 September. The nudge batch is drafted and queued with a local-language line and a screenshot per the send sheet’s own rule. After tomorrow they close as no-answer having had one message each in their whole life. ⚠ Minor artefact recorded so nobody reads it as truth: the logger derives the link from the slug, which is wrong for two now-closed rows - harmless where it occurs. Ivo
💵🔴 THE REFERRAL RAIL CARRIES REAL VOLUME AT A RATE THAT HAS NEVER BEEN RULED. Unmoved for a fourth window; the referrals channel has been silent since 23 Aug. (a) One overseas rep’s code: 15 requests, 1 carried the code, 14 did not - 93% untraceable, because he enters through the bare intake page rather than his own link; the code cannot be patched through the interface, so the correction sits in the request note and nothing was attributed automatically. (b) A second Bulgarian code went live on 23 Aug at 30%, with Ivo’s own words that the 30 is not recorded anywhere and is the whole build fund, above the 20% partner tier and not derivable by analogy. (c) The first Bulgarian code has been live since 21 Aug and is still unruled. Three numbers in one sitting, and it is money. Ivo
🔴 THE REP CANNOT SEE ABOUT 19 CHANNELS, TWELVE OF WHICH HOLD OUTREACH THAT HAS ALREADY BEEN SENT - AND THOSE TWELVE HIT THEIR LAST TOUCH TOMORROW. Carried, and the gap did NOT grow. Both channels created on 29 Aug were member-listed directly: two members each, the rep IN on both, and Ivo caught and corrected his own wrong „you are inside“ claim on one of them in writing before the run ever looked. Two more of the original set went moot when the rep archived their channels herself, so the honest carried figure is about 19, stated as carried. Root cause on the old ones is unchanged and it is a missing capability rather than forgetfulness: there is no way to add a member to an EXISTING channel through the interface we use. The remainder are manual one-clicks; the recurrence needs a tool. Ivo
🔴⏳ TWO THREADS REACHED THEIR LAST TOUCH YESTERDAY AND A THIRD REACHES IT TODAY, ALL THREE HAVING HAD EXACTLY ONE MESSAGE. NOTHING IN THE RECORD SHOWS A FINAL TOUCH WAS SPENT. Under the standing cadence a sent demo gets nudges at +2, +5 and +10 days and is then parked. The restaurant row and the guest-house row both hit +10 yesterday, and the financial-services client hits it today. On the record as it stands all three close as no-answer having received one message in their whole life, so this is not a lead that was worked and failed; it is a lead that was touched once. ⚠ And two of the three carry a defect that makes closing them the wrong lesson. The guest-house row was sent a link that has been serving Not Found at 766 bytes for all fifteen days, so its silence measures our own dead page. The restaurant’s page is live and byte-identical since 17 Aug at 41,880 bytes but ships no click-to-call, no images and no footer badge, a build gate under the 07 Aug no-CTA rule, so it never had a way to answer. The binary is unchanged and is now retrospective on two of the three: patch and spend the last touch, or accept that they closed against our own defects. ✅ The nudge cap is provably intact - 23 approved and zero fired. Ivo
📥⚠ A CLIENT’S CONTENT CORRECTION IS LOGGED, CORRECTLY NOT SHIPPED, AND BLOCKED ON A FOLDER THAT IS NOT A SHARED ONE - DAY 3. Model 2 already matches the owner exactly; model 1 needs four corrections - built area 99 to 99.5, house area 82 to 86.5, bedrooms and bathrooms 2+2 to 2+1, terrace 26.5 to 28.0. The digits were deliberately not shipped alone, and the reason is a standing rule rather than an excuse: the figures and the floor-plan drawing they are read off are ONE claim, so shipping corrected text against an uncorrected plan would put a page in front of buyers whose numbers and drawing disagree. The replacement plan images sit in a local downloads folder that is not a shared location - the fix is to drop them in the exchange folder and it becomes a ten-minute edit. ⚠ Recorded as care work owed, not a money item: this row is free by decision and there is no ask outstanding on it. Page carried at 1,557,573 bytes. Ivo
THE CLIENT-CONFIRMATION FLOW HAS NEVER FIRED ONCE, AND IT IS THE CONTROL THAT IS SUPPOSED TO PRECEDE EVERY COMMISSION. SEVEN PAYMENTS. The confirmation log is still 221 bytes with a June timestamp and has never been used. Behind it sit seven rep-collected payments: €100, €100, an annual care €150 confirmed paid by the collector but with no named holder, €150, €120, €35 and the coffee client’s build confirmed collected in full. No remittance of the company’s 60% has ever been reconciled, and the commission ledger is untouched since 18 Aug, thirteen days. ⚠ Eighth consecutive day with the money book unmoved, so the amount sitting behind zero confirmations is unchanged only because nothing was collected, not because anything was reconciled. ⚠ The month-end audit gives this item its sharpest example yet: a 40% care commission was booked in July on a care year whose first month was never delivered, and an independent client confirmation is exactly the control that would have caught it. The live 49-versus-40 contradiction on the German guest house is the same failure mode from the price side. ⚠ A third person is now collecting in the field with no confirmation instrument behind her. Ivo / Elena
💵 UNRULED AND UNBOOKED COMMISSION LEGS - THE MONEY BOOK HAS NOT MOVED SINCE 23 AUG, DAY 8. (a) The hotel-services annual care €200 - 40% to the rep, or excluded as an owner-collected account? Unruled since 04 Aug. (b) The restaurant’s annual care €150 - unbooked. (c) The coffee shop’s €100 - unbooked. (d) The coffee client carries two legs: the annual care €150 with 40% = €60 unbooked, and his build €150, confirmed collected in full, also unbooked. (e) The music-studio €180 and German guest-house €180 chains are ruled but unpaid, and with the studio delivered on her own domain since 21 Aug the last reason to hold hers is gone. (f) The German deal has three claimants, two with unproven attribution. 🔴 (g) NEW from the month-end audit, and it runs the other way: the ~€48 care commission on the Kiten guest house was booked on 24 July against a year whose first month was never delivered. All of it his. Ivo
💵 CARE REVENUE NOT STARTED ON CLIENTS WHO HAVE PAID FOR A BUILD. The psychologist: build €300 PAID, live on her own domain 32 days, care €29 a month never once billed - his own client, his call, and a full September campaign plus two social packs have been delivered into the unbilled plan. The German guest house: 49 recorded against 40 offered, day 15, nothing mintable until she says which number closed, and her go-live is now blocked on our domain pick rather than on her. The hotel in Сливен: the monthly never started after the prepaid six. The Несебър workshop: the total build price and the monthly fee are recorded NOWHERE on a row that has taken a €100 deposit. 🔴 The gym client belongs in this item and was left out of it this morning: her €19 has never once been billed, her plan starts tomorrow, and although the September date is her own decision, a start nobody bills is the same loss whoever chose the date. ✅ The coffee client is out of this item permanently - his care was prepaid €150 for a full year and the collector has confirmed it. Ivo
💵 €19 A MONTH NOW PROMISES TEN SOCIAL ITEMS A MONTH, AND €19 IS THE STANDARD CARE TIER. Unchanged: the 24 Aug revision to the financial-services offer bundles ten social items - posts, short videos, photos - into the €19 plan. The pack spawned for the psychologist the same day is eight posts, a five-frame carousel and three video cuts, a full session of work. ⚠ And on 29 Aug a 2.59 by 1.74 metre print banner was delivered to the gym client, another full session of design work against a €19 tier that has never once been billed on that account. At €19 delivered monthly this is almost certainly below cost, and because €19 is the standard tier it sets a precedent for every care client. The German channel sells at 600 and 49. ⚠ Read it beside the month-end audit: the promise is being raised on the tier that just failed to deliver at all on three rows. Decide deliberately whether ten items is the standard promise or a one-client sweetener. Ivo
🌐 THE FINANCIAL-SERVICES SITE IS DAY 8 LIVE ON THE CLIENT’S OWN BRANDED DOMAIN WITH NO CONTACT PATH AT ALL, AND ITS THREAD CLOSES TODAY. Carried and byte-stable for a sixth consecutive measurement at 74,332 bytes, content unchanged since 24 Aug: zero call links, zero mail links, „coming soon“ six times, seven unfilled tokens, the company number nowhere, and a contact form with no action that reaches nobody. The go-live decision is recorded, not re-litigated - the deploy itself was clean and byte-verified. What is needed is one message to the client: which positioning is current, because the page argues a leasing angle her own three documents do not support, and the licence wording in writing. Row is unpaid and unpriced. ⚠ The send engine has held its nudge for eleven days on exactly this ground: the row is owed a commercial answer, not a „did you see the site“. 🔴 The day ended with no touch spent, so it closes as no-answer having had one message in its whole life. That makes three closed this way in two days, all three on our own defects. Ivo / the client
🔄✅ THE REOPENED PIZZA ROW IS LIVE AGAIN AND STILL HAS NO CLIENT SURFACE - THE BLOCK IS ONE BUTTON. Carried from yesterday: the owner who refused on 25 Aug contacted the rep at 11:17 on 30 Aug asking for the demo again, and it was restored and byte-verified the same run at 200 / 1,864,663 bytes, hash identical both to local and to the pre-take-down hash recorded on 25 Aug, at the same address she already sent - so the owner sees the exact page, not a rebuild. That was one command only because the take-down deleted the objects but deliberately kept the project name. 🔴 The block is that her channel is archived and no tool here can un-archive it; that is a single click in the client-channels tool and it is Ivo’s. Until then this row has no surface to record into. ⚠ One question must be asked before anything is sent, and it was assumed at build time rather than confirmed: the page is a deliberate 2-in-1 covering both Сезам locations and same-owner was never verified. If the caller runs only one of them, the page shows them a shop that is not theirs. Price and the send back stay the rep’s, sub-1k. Ivo un-archives / Elena sends
🔄 ONE OF OUR OWN MARKETING POSTS IS LIVE TWICE AND CANNOT BE FIXED WHERE IT WAS MADE. Unchanged. The same post published twice on 18 August, byte-identical, same media, both live on the professional network. Created fifteen hours apart, so a double-create rather than a scheduler misfire. Because both are already live, the scheduling tool cannot clean it up: one has to be deleted on the network itself. Small, but it is a live public artefact on Ivo’s own brand. Ivo
⚠ TWO DO-NOT-SEND PAGES ARE STILL UNPATCHED - AND THE GATE HELD AGAIN. Both animate a factual rating and review count with no translate guard, which is two known traps compounded. ✅ Checked name-by-name against the recent approval queues: neither appears in any of them. They stay live, unpatched and unsendable until the numbers are static markup. Ivo
📌 SMALL OPEN ASKS THAT BELONG TO THE REP, DELIBERATELY NOT ESCALATED. Whose the disputed reservations number is, which link she actually sent for the Свети Влас hotel, the internally contradictory intended price on the Велинград row, currency on two cash collections, and whether a third client’s verbatim quote may be touched. ✅ Four items have left this list since 28 Aug, all closed by the rep herself or by execution: the coffee client’s build-50 and care-start-month questions, archiving one channel, and the refused Карнобат row, whose demo was taken down under standing practice. 📥 Seven questions for the new club row remain unchaseable until the send gate at the top is ruled: the hall address, the schedule, the age groups, photo consent, the club’s own red, who the counterparty is, and their own photographs. Elena
🔴 TWO INBOUND REQUESTS FROM 22 AUGUST ARE STILL UNBUILT - DAY 9. The referral-attributed one is blocked on a business name, not on us - Ivo asked on 23 Aug whether the word in the reference is the business name, got zero matches when he searched, and said the page gets made the moment the name is given. Client-side information gap, not a build backlog. The second, from a map link with no code, has no such excuse. ⚠ Both are now nine days older than two builds that were requested, built, channel-closed and link-verified inside about an hour each on 29 Aug. Ivo
✅ NEW, PROCESS - TODAY’S TWO CORRECTIONS CAME FROM THE SAME MISTAKE MADE TWICE: A CALENDAR WAS USED WHERE A DIFFERENT CLOCK APPLIED. No action asked; recorded because it will recur. The registry promised an answer in five working days and this board counted calendar days, which turned working day 3 into „day 7 and overdue“, and it did so on a Monday that is a bank holiday, so the count was wrong twice over in the same sentence. The second correction is the same shape from the other end: a filing this board called overdue since 17 August was in fact clear until August 2027, because a due date was read off the wrong year. ⚠ Both were only caught by opening the register and the acknowledgement email and reading them. The durable form is worth keeping: a deadline is not a number of days, it is a rule plus a calendar, and neither is derivable from the other. ✅ The right consequence has already been taken - the ruling not to refile until the written answer arrives is unchanged, and being three days early rather than seven days late does not make refiling any more sensible. Ivo
⚠ PROCESS - THE NIGHTLY REBUILD FIRED ON TIME AND PRODUCED NOTHING, SO THIS BOARD IS SITTING ON A DAY-OLD SPINE. No action asked; recorded so nobody reads today’s figures as freshly measured. The schedule ran at 06:31 this morning and the next fire is set for 06:37 tomorrow, so the timer is healthy. But the spine still carries a 30 August 06:40 stamp and no backup was cut today, where every previous day cut one at the moment of rebuild. ⚠ The spine file WAS written at 07:08, which makes this sharper rather than softer: the write was the care audit adding its month-end finding, so a file-modified time would have reported this agent healthy when it produced nothing. A run is not a result, and neither a last-run timestamp nor a file timestamp is evidence that anything was produced. ✅ The correct handling is what this board has done: every carried figure is labelled as carried, and the four things genuinely measured today are named - the care audit, the site-health loop and the two money passes. ⚠ If tomorrow’s 06:37 fire also produces no rebuild, this stops being a note and becomes a red item. Ivo
⚠ PROCESS - A DAILY MESSAGE HAS BEEN NAMING THE WRONG PERSON AS A COMMISSION CLAIMANT FOR SEVERAL RUNS, AGAINST A CORRECTION SITTING IN THE SAME FILE. Caught and corrected in writing today; no money moved on it. The three claimants on the German guest-house deal are the rep, a partner, and the introducer whose own free site sits in the portfolio - not the fourth name the daily message kept printing, which belonged to someone added to a group chat by accident at the outset and whose name then stuck to the role. Ivo settled the identity on 16 August, in the same file, roughly 1,300 lines above the line that kept getting it wrong. ⚠ The lesson is the one this venture keeps re-learning: a stale claim outlives its fix unless the fix is written where the claim is read. ✅ The money shape is unchanged by the correction - one pool, divided rather than stacked, with the company keeping €420 of the build and €29.40 a month of the care. Ivo
✅ SITE HEALTH RAN THIS MORNING AND NOTHING IS DOWN. The independent loop reported at 07:14: 100 live sites, 84 OK, 16 warnings, 0 failures. The warnings resolve to one broken shared image hitting several internal pages from a single root cause, plus a handful of unarmed redirects - one more warning than yesterday and no new failure. ⚠ Note what this check does and does not cover: it proves the estate is serving, it does not prove any individual page is the right page, which is why the wrong-business address and the two dead sent demos are tracked separately above and are not visible here. Ivo
✅ AN INSTRUMENT THIS BOARD PRINTED FROM FOR FIVE RUNS WAS PRODUCING FALSE NEGATIVES, AND IT IS RETIRED. No action: this is a correction to numbers Ivo has been reading. The check was: list the client channels, see that the newest one returned is still the agency channel from 27 Aug, conclude nothing was created after it. That same query returned the same answer while two channels created on 29 Aug both existed - they surfaced only when searched by name. The reason is structural and worth keeping: the search is relevance-ranked, not recency-ranked, so it cannot produce negative evidence. Consequences, stated once: the roster is 120, not 118, and two carried items - the missing channel for a client at closing, and the rep’s membership gap - were both being measured against a stale floor. ✅ Neither gap actually grew. The durable half is the method: a search that ranks by relevance can confirm a thing exists and can never prove one does not. It is the same lesson as the note above it, from a different instrument. Ivo
⚖ WHAT ACTUALLY MOVES A COLD SEND IS AN OPEN QUESTION WITH EVIDENCE ON BOTH SIDES. Stated once, no action asked. Against the cold motion: the car dealer built in June and sent in August, a sixty-day gap, came back „they do not know who ordered it“, angrily; the hair salon refused „we have a website“ because the owner counts a second social page as one; and the hair-and-beauty centre - the strongest has-site pitch the factory has ever built, sent after only a seven-day lag - was hung up on at day 3, which is the important correction: quality and freshness were both present and it changed nothing. For the motion: the child psychologist, briefed 09:11, second revision by 09:44, sent 13:45, answered 23:55 with thanks and a promise to call back - a fourteen-hour build-to-send and the only warm answer in the book since 16 August; and the pizza owner who refused on 25 Aug and came back on 30 Aug of his own accord. Read together, the variable that tracks the outcome is not lag and not build quality but whether a person with a relationship carries the send. Four Bulgarian refusals in four days against one warm deferral and one reopen. It bears on the ~111 rows behind them. Ivo
PROCESS - A REAL CLIENT AT CLOSING STILL HAS NO CHANNEL. Re-confirmed absent from the corrected 120-channel roster, so the finding survives the instrument being retired above. It is the longest-standing tracking gap in the book and it is the owner’s action - agents must not create channels from this file. ⚠ A refusal that archives its own channel has the same shape from the other end, and the reopened pizza row is now the proof of the cost: recent refusals archived their channels within thirty seconds of the instruction, so when one of those owners came back there was nowhere to record it. Worth noting as a shape, not as a complaint. Ivo